Closed mikkel75 closed 4 years ago
Hi I will have a look. Possibly i will add a compile switch for this into the definitions.h file, but i am not shure, if this makes sense, because you do not know the state after mqqt_in. Possibly the device fails the in_command.
Hi. Sounds good....just out of curiosity - is it normal for MQTT devices to transmit it's status after a change from MQTT/in ? If so, I would agree that the problem lies with Domoticz...
Yes, it is. Otherwise you can't be shure the device did what you wanted.
Hi,
Great project btw!
I have an issue when I want to be able to monitor and control McLighting devices from my Domoticz system using MQTT. My system looks like this https://1drv.ms/u/s!AlY-U_GE-GiVgsJYYFZF4eo25_vGwg?e=Ivfnb6
The problem is that I get a MQTT message loop, since both McLighting and Domoticz sends out a new MQTT message when it receives one.
I have discussed with the Domoticz developer about a way to update a virtual device WITHOUT triggering a new MQTT message. So far with no luck.
It would be great if McLighting could have such a feature, so that state change based on incomming MQTT wouldn't result in a MQTT out message.
Hope you can help :)
Thanks