Open timzinfandel opened 4 months ago
I'm having a similar issue. In my case I have the YSR-MINI-01_rgbcct being recognised as the YSR-MINI-01_wwcw. Up until the Zigbee2MQTT update I ran yesterday, it was happily taking RGB values, but now I can no longer control it properly. Not sure what version I was running before that unfortunately.
See my workaround fix here: https://github.com/Koenkk/zigbee2mqtt/issues/21361#issuecomment-2105394183
Is there some way to force a re-interrogation to get it to be recognized as the correct device again without resorting to custom scripts? I've tried the reconfigure and the interview commands, and I've tried removing and joining it again, but it keeps getting recognized incorrectly.
Using a custom script basically overrides the recognition signature, therefore it's possible the wrong signature to-be-overridden is used.
I can try to put some code together, if my linked workaround won't work.
Is your device still being recognised as Lonsonho ZB-RGBCW?
Hi @dotWee, my issue us the YSR-MINI-01_rgbcct
being recognised incorrectly as a YSR-MINI-01_wwcw
.
What happened?
I'm pairing four strip light controllers from Ysrsai and they are being mistakenly identified as Lonsonho lightbulbs. On/off and color change commands aren't working.
What did you expect to happen?
I expected them to pair as YSRSAI YSR-MINI-01_rgbcct being identified as Lonsonho ZB-RGBCW (a supported device)
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.36.0 commit: unknown
Adapter firmware version
6.10.3.0 build 297
Adapter
EZSP v8
Setup
VIrtualbox on a Macbook Pro
Debug log
No response