I have a MOES Zigbee three gang light switch. Model: ZTS-US
I had a HA setup on a Rasp Pi 3B and the switch was functioning fine. Later, after a few updates, it got to the point where HA would not respond. I then installed HAOS on a cheap PC with 8GB of RAM. Of course it is a lot faster.
Anyway, after reconfiguring the light switch, I am having an issue now. When I click on any of the switches in HA, all three of them will turn on or turn off.
Whatever has changed? As I mentioned, I just built a new system, and added the switch again to the new system. I did this the same way as before. I am not sure what information you are wanting.
Your old install picked up a quirk for your switch, while your newer one did not.
Easiest way to try & fix this is to attempt to reconfigure/re-pair your switch until you see it pick up the correct quirk. The below is just an example to show you where to look for it in the device page:
If that doesn’t work, see if you can fire up your old system & check the device page for your switch. It should still show the details even if it’s unavailable.
Otherwise, grab the 2 lines under the device info (model name & Manufacturer ID) & post them here.
Yep, it seems to be picking up the correct quirk. Went down a rabbit hole trying to understand why your switch would behave like that & I think I understand what should be happening.
However, before I go on, can you confirm something? You said all lights turn on when you turn on a single switch, but your screenshot shows the correct status - only a single light is on in HA:
Are the other 2 lights turning on but not reporting their status to HA, or is it working correctly now?
Also, can you check whether the entity IDs are actually different by clicking on each bulb icon & clicking on the cog wheel icon on the top right of the popup? I find it strange that all 3 lights are named identically, but it’s not actually a problem if the entity IDs are different, like light.light, light.light_2 & light.light_3
Anyway, back to the rabbit hole. Those switches require what’s called a tuya magic spell (seriously) to avoid this issue. Now, the strange part is that this was implemented for your switch quirk around 3 years ago. Every time you configure or reconfigure the switch, the magic spell should be called, so you shouldn’t be running into this issue unless your HA version hasn’t been updated in 3+ years.
Try this:
Delete the switch from HA.
Wait a minute, then restart HA
Pair the switch again.
If that still doesn’t work, you’re gonna have to install ZHA toolkit in HACS & try to send the command manually. Instructions on how to do that are here.
I finally have time to mess around with this. It took me a while, but I have ZHA Toolkit installed.
However, it seems the Github solution is a bit dated.
1. Install "ZHA Toolkit" - I did this via HACS
2. Go to "Developer Tools -> Services" in HA
3. Select Service "ZHA Toolkit: execute"
4. Select Command "tuya_magic"
5. In the ieee section select first Tuya entity and click call service - do for each Tuya entity
The “Services” is gone, but I figured out it is now “Actions.”
I am unsure about item #5. Click call service and do for each?
There is nothing to click except at the bottom labeled “Perform Action.”
Okay I got it. I had to restart HA to get it to connect again, but all switches are now operating independently. Thanks for your help (and to the others)!
As far as having to restart, I wonder if that is an ongoing issue. I in another thread from today how another is having their Zigbee network go offline.