Tom Butcher

@rrroyal could you turn on homebridge debug mode and send us the logs? https://github.com/homebridge/homebridge/wiki/Basic-Troubleshooting#debug-mode You can also enable this within the config-ui-x

I've been noticing this too. I'm not too sure why this happens specifically but I think its something to do with grammar correction. This page shows it quite well: https://tasmota.github.io/docs/Lights/#gamma-correction....

@muzzymate I've just implemented the feature into 1.9.3-beta.5. By default, a controller's status, when offline, will be set to off. You can change this to "No Response" by setting `"displayUnresponsive"`...

beta.6 _might_ of fixed this issue. Let me know if there is more to work on.

I worked around this issue by installing AppStore++ on a jailbroken device and downgraded the app to get the id and key.

Update your homebridge-tuya-lan to 1.5.0-rc.12. To do this, run npm i -g AMoo-Miki/[email protected]

My mistake, run the command again but remove "AMoo-Miki/" from it so: `npm i -g [email protected]`

Hmmm, this seems weird. I'm guessing you're using ioBroker as an MQTT broker right? https://www.iobroker.net/#en/adapters/adapterref/iobroker.mqtt/README.md If so, I'll try to reproduce the issue and see what could be happening. Also,...

Yep, this is a bug! 😅 I've just released a software update that fixes this. You can update by going into Settings > Software Update and changing the update channel...

On the tasmota devices, do you have Home assistant discovery set to 1 by any chance? (SetOption19)