AtomBaf
commented
2 years ago Thanks for your feedback. As you're clearly pointing out, this is a more like a limitation I haven't figure out. You can see for instance (here)[https://github.com/AtomBaf/homebridge-mqtt-tasmota/blob/master/src/switch.js#L19] that an assumption is made on the initial state of the system when the first connection is made.
However, I don't have in my own setup the typical thing you're describing: a timer. What exactly tasmota is publishing when a timer-based event is triggered ? If you can send the mqtt message log, I would modify the code to handle this message as well. It seems easy to applicate. I can do it on my own, but not sure if it would help if you have a different version/setup/device on your own tasmota.
Thx again for your help in understanding these things.
Ogge66
First of all, thank you for a great plugin. Very easy to add all of my devices, naming, index etc.
But something I haven’t figured out is how to sync the device statuses. Lets say I use the wall switch or have a timer set up in the tasmota web interface then it wont change the status in HomeKit. I can see in the logs that MQTT is sending from the tasmota device but nothing is received in homebridge.
Is this a known bug/limitation or am I just missing something obvious?
Thank you!