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.
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.