Hello,
I created an mqtt to manage a xiaomi light, an mqtt that sends data.
My problem is that the value change does not work in both directions.
If I turn on my light manually, I would like the mqtt to go active and if I turn it off via Gladys it turns off the light. I tried but it doesn’t work.
Yes yes I do receive the data because I can modify other device temperature etc but as soon as I check I can no longer change the value by mqtt I can only subscribe to the topic to retrieve the value change.
So basically, what you want is to have a device of type « actuator » in Gladys, which can be controlled in Gladys, and at the same time you can send it states outside of Gladys if ever this lamp was turned on outside of Gladys and you can propagate the state?
If that’s the case, it’s possible.
- Put the device in « this device is a sensor » mode. Copy and paste the displayed topic, it’s a topic that allows sending values from the device to Gladys.
- Then, put the device back in « this device is not a sensor » mode. Copy and paste the displayed topic, this topic is used for « gladys → device » communication.
In general, this view is just a « helper » to help the user configure their device. The MQTT API works in both directions and is described in our API documentation:
Don’t hesitate if you have other questions 
Thank you very much.
I wanted to specify that I do this so that Gladys can run in parallel with Jeedom for the missing features. And it works very well .
Great If you ever have the time to write a small tutorial on the forum (we have a « Tutorials » section), it would help a lot of people who want to use Jeedom with Gladys!