I do see two possibilities for the failure:
1.) Somehow, the network does not see the device.
2.) The device is incompatible with ZHA (even though it should be).
How can I find out, which one it is?
I checked the debug-logs, but am not sure, what to look for.
Probably option 3. It’s a Tuya device, so the Zigbee ID is different (something Tuya is known for doing with different whitelabel manufacturers).
Check the ZHA debug logs when pairing the device close to the coordinator. If you don’t see anything matching exactly _TZE200_9i9dt8is or _TZE200_w4cryh2i, then chances are you need a custom quirk.
Thank you!
I checked the logs and there is not even “TZE” in there (just to be sure, I tested it again with the device in the same room and just 2 m away from the controller).
But how do I know whether the device did commicate with the controller at all or not? Isn’t there the possibility that the device is just defective and just does not transmit?
The debug logs should contain that info right under the part where they say “starting interview” or similar. Assuming you set the button in pairing mode correctly, then something should be logged.
Ps. If that is a battery device, press the button every 1-2s during the pairing process to prevent it from going to sleep
Thank you!
I found some interviews in the debug-logs (“INTERVIEW_COMPLETE”) from a few weeks ago. Not a single interview from the last couple of days where I tried to join the new dimmer switch.
Can I assume that there is something wrong with the device itself?
May I ask, where you found these identifiers and what they stand for?
If you’re 100% sure you’re doing the pairing process correctly, then it’s safe to say it’s a device issue. Strange that there’s absolutely nothing in the logs though - even an unsupported device would register something if it’s correctly set to pairing mode.
They were in the blakadder page you linked to in your first post. It’s the model of a particular device, which allows it to be recognised by ZHA as needing a “quirk”.
I had a look at where those quirks for the dimmer are defined for ZHA, and the list is a bit longer:
("_TZE200_dfxkcots", "TS0601"),
("_TZE200_whpb9yts", "TS0601"),
("_TZE200_ebwgzdqq", "TS0601"),
("_TZE200_9i9dt8is", "TS0601"),
("_TZE200_swaamsoy", "TS0601"),
("_TZE200_0nauxa0p", "TS0601"),
("_TZE200_la2c2uo9", "TS0601"),
("_TZE200_1agwnems", "TS0601"), # TODO: validation pending?
("_TZE200_9cxuhakf", "TS0601"), # Added for Mercator IKUU SSWM-DIMZ Device
("_TZE200_a0syesf5", "TS0601"), # Added for Mercator IKUU SSWRM-ZB
("_TZE200_p0gzbqct", "TS0601"),
("_TZE200_w4cryh2i", "TS0601"),
("_TZE204_dcnsggvz", "TS0601"),
("_TZE200_6fjev1mn", "TS0601"), # reported in #4238
Doesn’t help you much though, given that you can’t even get to the point where your device actually sends its model ID to ZHA.
Thanks a lot for all your support. It was a very interesting dive into the details of ZHA.
In the end, it was simple: The device was not in pairing mode.
The LED-strip has four modes of flashing (not described in the manual):
According to the manual, you need to hold the button for 5 seconds in order to enter pairing mode. After doing it, the device entered mode 3 reliably and I expected this to be pairing mode.
Well, since I found mode 4 today, I was wrong. I don’t know how I entered this mode and I am not able to reproduce it reliably. But this was the solution.
Mode 3 is only the mode for “light turned on, but not in a Zigbee-network”.
I am sorry to have taken so much of your time. I paired about 100 Zigbee-devices to my network. Not one of them fooled me like that.