Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Update MQTT reporting on change of state, mode, beerSet or fridgeSet #435

Open
denisfrench opened this issue Oct 10, 2024 · 2 comments

Comments

@denisfrench
Copy link

I have successfully setup capture of BrewPiLess data within Home Assistant via MQTT.

Control via MQTT is also working, but I have found the lack of immediate feedback makes programmatic MQTT control problematic.

Please consider updating MQTT reporting on change of mode, beerSet or fridgeSet, to complement the MQTT remote control functionality. Update of state upon change would also be useful for monitoring purposes, as it often changes within the Publish Period timeframe.

Likely this is relevant to MQTT control through other approaches, such as NodeRed, Python etc.

Thanks for your work on this 🙂

@glenosAU
Copy link

glenosAU commented Oct 19, 2024

I have used your example from #432 and got brewpiless via MQTT into Home Assistant. The only control I can make work is to set the brew mode but I cannot set the temperature for fridge or beer constant.

EDIT - Actually I can only change mode to any setting except Beer Constant.

Got any tips?

Second edit - worked it out.

@denisfrench
Copy link
Author

Are you certain it is not working? The key issue is that feedback via MQTT is delayed, therefore you will not see it update in HA until the next Publish Period. Check the BrewPiLess webif directly for real-time updates.

For this reason I have given up on control from HA, hence raising this FR.

The YAML from #432 (comment) was otherwise working fine for me. Probalby also check you have the full topic (ie it does not automatically include Base Path) in your "MQTT Remote Control" settings (#432 (comment)), which had me stumped for a while.

Concievably we could reduce Publish Period to 5 or 15 seconds and it would probalby work, but I would rather not spam my MQTT server, and wonder about the load on my BrewPiLess which already spontaniously resets occaisionally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants