Closed martin31821 closed 3 weeks ago
If you already have a MQTT broker you might as well have a Home Assistant - more complex rules should go there with elaborate long term logging capabilities...
I do agree with you on the long term logging, although I have mine running in grafana/prometheus/mimir.
I was thinking to run more logic directly on device in order to have a sane fallback in case any of the more complex rules fails, thus also the handling of MQTT#lost
.
I have a similar use case: Allow changing global variables from external sources.
The rationale would be to have some "settings", which are not time critical for the operation of the heat pump but I want to be able to change these from MQTT or HTTP.
If we had MQTT subscriptions as rules, then I could just set the global variables as needed in the MQTT subscription rule.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
I'd like to propose an addition to the rule engine in heishamon, namely the possibility to subscribe to MQTT topics and run rules when a message is received on the topic, as well as the possibility to react to connection lost/reconnection events.
Possible usecases might be:
I'm imagining a rule like this:
What do you think of such an extension?