ZHA? didn’t you say you installed them using Z2MQTT?
FYI Z2M exposes the switch_type
entity which should allow you to do what you’re looking for Tuya TS0004_switch_module control via MQTT | Zigbee2MQTT
ZHA? didn’t you say you installed them using Z2MQTT?
FYI Z2M exposes the switch_type
entity which should allow you to do what you’re looking for Tuya TS0004_switch_module control via MQTT | Zigbee2MQTT
Yes I did that a few days ago but tonight I have connected first to ZHA and then to Z2M show you the differences
Go in Z2M & show a screenshot of your device settings please, like I asked earlier today. You should be seeing the switch type option if you’re using that model
It’s being wrongly detected as this device judging by the description.
You’ll need to create an external converter for that specific variant to be recognised correctly. Otherwise raise a device support request in the Z2M GitHub and provide all the details there.
Same here. I just have a few Tuya devices because there either wasn’t an alternative or it was dramatically more expensive. I only ever used ‘LocalTuya’; took me 15-20 minutes to get it setup for the first time and have since blocked Internet access to the 3 devices I have with no issues. I would never CHOOSE Tuya, but in my experience the few devices I have work just fine locally.
This is the correct answer with this particular issue. This is why when asking for help with devices its good to provide screenshots of how they show up in the integration at the time.
Yep, for anyone else reading this Tuya are notorious for adding a bunch of random letters to their models depending on vendor, hardware revision & whatever colour underwear the developers wore that day (apparently)
You can see it in the above screenshot - TZ_3000_liygxtcq. That last part changes constantly and EACH variation, which means your device might not be recognised correctly without an external converter &/or a PR to the Z2M GitHub