-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
MQTT retain setting per item in Gateway config [feat] #311
Comments
I suppose it would be possible to identify the longevity of a value based on the command class being used.. Meters and switches could be retained, as their state is always "correct" (whatever was received last) - while motion sensors and the like are "events" ... Could this be done? |
I would prefer just being able to set the option in the 'Configured Manually' gateway section under each added value. Manual config would allow override of the default and give the highest level of control. |
Yep this is something that could be easily done using gateway values |
did you mean this is already possible using existing gateway configuration, or that it can easily be added as a feature? |
this is my next feature in todos, along with custom qos level :) |
PR ready |
It would be nice to be able to set the RETAIN flag on a per message basis in the gateway config rather than just globally. Some messages (e.g. light status) are more relevant for retained messages than others (e.g. a PIR motion alert).
Setting could either replace or override the global setting in MQTT config.
Not sure if this is useful for others, I am using the software with all messages manually configured in the gateway. I use node-red for most of the workflow items, driven from Zwave2Mqtt messages, with retain every time node-red restarts or deploys it reloads the messages and runs any workflows. Can put a check in the node-red code on message age, but nicer to be able to configure as required at source.
The text was updated successfully, but these errors were encountered: