-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCT5010-0002W detected as CCT5010-0001 with limited functions #14749
Comments
The install code is (AFAIK) only required for joining, and since the device joins fine there is no need to add support for this alternative format.
What happens if you turn on/off the device? |
Actually, it does nothing. Keeps trying like if the device were offline. |
@Koenkk - I do think that there may be an issue with the Install Code logic - the code above is valid (as per the Z-Stack specs) with an a hex encoded 8 byte IEEE ( |
How can I pass my install code then? Tried to add with the IEEE before the code but it doesn't work (as expected) |
I have adapted an extension (not external converter) that Koenkk created when diagnosing the Bosch Alarms. If you add this extension, enable debug logging - I have hard-coded the install code into it. Restart Z2M and hopefully you will see some good log messages Install Code Extension Just to temper expectations though, as Koenkk said above, if the device joins your network without the need for the install code, I don't expect the addition of it to add any additional functionality to what you have already reported... |
Okay, somehow that device started working that same night by its own, it was when 1.28.1 arrived so I thought it was the update that fixed this. Just installed another two ones today, check this. Also, joined without install code too. Don't know what changes but I suppose it will work in no time, but feels weird. Don't know how to debug what happens, why it takes hours to work as expected. Also, the dimmer stays in red like there were an error, but after it begins to work again, it turns green forever. |
But this is hardcoded, not able to test it. I'm going to install a new one right now, I can test it. How do I change the install code? I'll check in a minute. |
@Koenkk So, I didn't report it, but the way to get those working is by stopping Zigbee2Mqtt for a while and then start it again. Something changes in the device and begins to work again. |
@Koenkk Some of the settings doesn't work well with this dimmer. I think this issue may have to be moved to "New Device support"? |
@joaquinvacas can you provide all the settings that don't work. Likely the device doesn't support (simply remove them is the solution) |
The "current level startup". But the device does accept it. I think there may be some differences between the first hw version (0001) and this (0002W) and the way it changes the previous value. |
@Koenkk Sorry, it's in Spanish but as you can see, the manual of the newer device shows "Último nivel (B)" that means last/previous used level. |
Can you sniff the traffic when setting this? maybe they use a special command. https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html |
@Koenkk - I think the install code functionality is generally broken - I tried using it for my bosch siren the other day, which is what originally drove the requirement and the testing for install codes, and couldn't get Z2M to accept the string.. |
@danieledwardgeorgehitchcock but this was working before right? |
Yes it was - I think it stopped when the new code type was introduced..? |
Can you try with z2m 1.27.1, this includes the install code support but not support for the new type. |
I've just bought a schneider Micro Module, CCT5010-0002, and it does not seem to work at all in Zigbee2MQTT Just to add context, the status led on the device itself shortly becomes green after restart, and then it's red all the time when the lamp is on. I assume this might be normal though. |
Shut down Z2M, wait 5min and then start it up again. |
Don't have a sniffer! 😢 Maybe somebody from here could do? |
Hm, yes, this is the case What I found, when the requests were timing out, they were being sent to endpoint 242 instead of endpoint 3. After restart, requests are sent to endpoint 3. Maybe some initialization bug? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Not staled. Actually this should be changed to "new device support" instead of the actual name. @Koenkk |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Changed title |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Not stale. Just not hardware available for debugging. |
FYI, if using ConBee or RaspBee (deconz Zigbee Coordinator adapter from dresden elektronik) then see related issue -> #17492 |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
@Koenkk how can I fix this? I mean, is there any way for debugging it without hardware? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Not stale. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Not stale |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Any updates on this ? I also bought one and it doesn't work well. |
is this device still not working? I was planning to buy one. |
It works almost perfect, there are some minor settings that don't seem to
be "refined" but OK, completely usable.
El vie, 17 nov 2023, 23:12, fariouche ***@***.***> escribió:
… is this device still not working? I was planning to buy one.
Inhave a sniffer if we can make it work
—
Reply to this email directly, view it on GitHub
<#14749 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEJS36XYGLQ3WI5GB54LYE7ONBAVCNFSM6AAAAAARUCC2SOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGE4DEMZXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
hello @joaquinvacas , what minor settings did you make? because I come from the integrated and nothing works |
What happened?
Tried to install a Schneider Electric CCT5010-0002W micro dimmer module with Zigbee2MQTT
Actually it joins, shows all the data like it was joined correctly.
But after that, I can't change anything or use the device at all.
I noticed the device has a Install Code printed on it's side.
The problem here is when I try to add the install code, this shows instead.
How can I get Z2M to support the shorter install code? Or maybe Schneider is hiding some part of the install code that the Wiser app assumes?
Anyway, I can't test it, don't know how to get the "full 95 or 91" install code.
Also, Zigbee2MQTT shows it like a CCT5010-0001 device and not CCT5010-0002W one.
The 2W variant is the updated one, same functions but with bluetooth (didn't need it for joining)
So, here it's joined but after a short time, it shows "Unavailable" like if it was turned off.
What did you expect to happen?
Accept install code to let control the joined device,
How to reproduce it (minimal and precise)
Zigbee2MQTT version
1.28
Adapter firmware version
20220219
Adapter
SONOFF Zigbee 3.0 USB Dongle Plus by ITead CC2652P
Debug log
No response
The text was updated successfully, but these errors were encountered: