The Latest Firmware of the Shelly 2.5 accepts commands via
shellies/shellyswitch25-/relay//command
which can be configured as topic and Zway-MQTT can control the relay. But Zway-MQTT misses the status updates which are given on
shellies/shellyswitch25-/relay/
Workaround is instantiating two Zway-MQTT which map the same Zway device and configure one as setter for the correct command to the shelly and the other one as getter with the correct topic to catch the status in case any other mqtt client updates the value on the mqtt server. But this results in useless mqtt traffic
A solution would be to provide two field to fully specify the requesting status topic and setting value topic and not specify a postfix for requesting status and one postfix for setting the value
The Latest Firmware of the Shelly 2.5 accepts commands via
shellies/shellyswitch25-/relay//command
which can be configured as topic and Zway-MQTT can control the relay. But Zway-MQTT misses the status updates which are given on
shellies/shellyswitch25-/relay/
Workaround is instantiating two Zway-MQTT which map the same Zway device and configure one as setter for the correct command to the shelly and the other one as getter with the correct topic to catch the status in case any other mqtt client updates the value on the mqtt server. But this results in useless mqtt traffic
A solution would be to provide two field to fully specify the requesting status topic and setting value topic and not specify a postfix for requesting status and one postfix for setting the value