No problem, very glad you’re trying to help.
In your latest DDF the ‘modelid’ was TS1001. Changed it to “_TYZB01_bngwdjsr” but no change.
“schema”: “devcap1.schema.json”,
“manufacturername”: “_TYZB01_bngwdjsr”,
“modelid”: “TS1001”,
You understand correctly.
When pushing the ON button on the remote, lamps and switches go ‘ON’ in Domoticz.
But in reality they do not switch on. Pushing the OFF button on the remote switches lamps and switches to OFF in Domoticz. Just checked, same behavior in Phoscon.
You fixed it here:
opened 06:24PM - 11 Dec 21 UTC
closed 01:48AM - 21 Feb 22 UTC
stale
Bug report
## Describe the bug
I connected a [TS004F](https://www.zigbee2mqtt.io/devices… /TS004F.html) aka _Tuya ZigBee Wireless 12 Scene Switch_ found [here on Aliexpress](https://www.aliexpress.com/item/1005001302383925.html) to the Raspbee 2.
https://github.com/dresden-elektronik/deconz-rest-plugin/blob/39099c0ae9e078768bf2e18df2844bbd22b6b44c/bindings.cpp#L3072
Without assigning the button to any group, button 1 and 2 toggled _every single connected light_ on and off respectively.
A deCONZ user with an Aqara Opple Switch instructed me to reset the switch again, and upon establishing the connection with deCONZ, quickly hit the reset button one more time to _"disable 'master' mode"._ I never heard this before, but indeed it works.
The buttons no longer physically switch everything attached to deCONZ on or off.
**The problem is that the REST-API still sends state updates _as if_ everything is switched off and on.** Then within half a minute or so, REST-API realizes nothing was changed, and updates the statuses back to the old value.
This causes problems when further processing is done by anything consuming the REST-API, such as OpenHAB or other domotics solutions. For example, if you use deCONZ to switch on a Zigbee light, and use deCONZ > REST-API > OpenHAB to switch on a Wifi light when the Zigbee light turns on, the result is now that only the Wifi light erroneously turns on while the Zigbee light properly stays off.
## Steps to reproduce the behavior
1. Hold reset button to bind Tuya 4-gang switch
1. Observe button 1 and 2 function like a master switch and physically turn all groups on and off
1. Observe statuses are communicated over REST-API
1. Hold reset button again, this time after the connection is made (light flash) quickly hit the reset button once more
1. Observe button 1 and 2 no longer physically turn all groups on and off
1. Observe REST-API still sends status updates as if all groups turns on and off
## Expected behavior
REST-API follows deCONZ behavior exactly.
## Screenshots
## Environment
- Host system: PC
- Running method: Docker
- Firmware version: 26610700
- deCONZ version: 2.13.01 / 10/6/2021
- Device: RaspBee II
## deCONZ Logs
## Additional context
I don't know this behavior. I don't know if this feature is related to the button itself, to Zigbee or to the deCONZ software. I tried to explain it as best as I could, but if I understood what was going on, I would probably explain it better.
But then I updated from your/my self compiled Beta to the latest public Beta and lost the remote.
Now with your latest DDF it’s working again but still has the ‘ghost’ lamps/switches to ON/OFF.