Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamjobstjn wrote:Hi sir,
1st it's the startup bug:
there's a ~50% chance this config gets applied upon boot (so several tries are needed):
addEventHandler TuyaMCUParsed 0x02 addRepeatingEvent 2.5 1 setChannel 4 7
addEventHandler TuyaMCUParsed 0x02 addRepeatingEvent 3 1 setChannel 6 30
(I think it's something similar for retain: true as a mqtt config strategy)
2nd it's when the device disconnects from mqtt server (server down):
gui will still report last config but device will act on default values (e.g. song 5, 10s). Regardless of when or if it reconnects.
a regular hass automation config will stop working here, need to apply the hack above
Additionally the minor issue of requiring delay between mqtt commands, perhaps network related?.
I am unsure how would those ideas fix these issues.