Device toggles light, but Zigbee2MQTT cannot handle the response (if any) and throws error after timeout - Device ID 3004482/3137308/3137309 #21586
Comments
exetico
changed the title
|
I would like to add that this exact thing is happening to me as well, and I have 6 of these devices all having this behaviour. I'm on latest zigbee2mqtt, having it installed as a home assistant add-on. I also tried following the guide for adding support, but because zigbee2mqtt already identifies it as a (wrong) device, I can't get it to use my external converter. It seems it is recognized as an in-line cable dimmer/switch, whereas it is actually an in-wall dimmer/switch. And this is the error I see on turn_off:
|
|
Yes, same error as me 👍. There must be a way to enforce the custom definition for the device. To be honest, I've not found the proper amount of time to fiddle with it, after I submitted the issue. Could you share your work in a gist, and add the reference here, too? If you join the official Discord chat, you'll find my nickname by searching for the issue (use the issue link). Fell free to add me 👍, and send a PM. |
|
I was just playing around a bit actually, as I haven't tried adding an external converter before. I wanted to get it to load the initial converter, and then expand from there. I took this as a reference. (The "Zigbee smart in-wall switch") https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/livingwise.ts And then did what the guide zigbee2mqtt guide states: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html This is what I was trying to make it load: But even after including it in zigbee2mqtt, it would still match it with the "wrong" device after re-pairing. |
|
Same problem, behaviour and error code |
|
@codedesperate Did you get any closer? I'm sorry that I didn't follow up. I've not found time to fiddle with it. |
|
So, I'm trying to update the firmware. But I keep ending in a situation like this: ... ... But, why can that be? I've added this to my local ota index file (generated with zigbee-OTA. Both Here's a example for another device: I just spotted this, just as a extra information 😄... Resources, just to have them here: /src/devices/lightsolutions.ts, 18171#issuecomment-1616416833, Manual |
|
@exetico I tried making a converter, but it kept recognizing it as the Light Solutions wire dimmer, and I couldn't get it to work. Anyways.. Updating to zigbee2mqtt 1.36.1 makes the devices unresponsive. Going back to 1.36.0 fixes this issues. I did read there was an issue with external converters, but this isn't a external converter right? @exetico do you have any issues on 1.36.1? |
|
@codedesperate Fair. It's annoying that it doesn't work that well... I didn't manage to get it to firmware update. Even though I spend hours on that part. Personally I'm thinking about trying to see if it's possible to update it with a Hue Gateway, just to see if it acts better here, on the newer firmware. What firmware are reported from your device? Regarding Zigbee2MQTT, and the question about 1.36.x. Before update: After update: Ater I updated, I turned off the light in Home Assistant. It responded as it would normally do. Same thing with dimming and so on. Just very delayed, with the same issues as normally in zigbee2mqtt: I'd really like to get this product supported, as it's installed in my wall... But I guess someone, or I, need to find the proper amount of time, to get this working as expected. |
|
@exetico I have firmware version 1.00 I don't see OTA ability for these devices in Zigbee2mqtt. Did you find newer firmware versions somewhere? Okay, my issue with 1.36.1 must lie elsewhere. Thanks for letting me know :) |
|
Thats identical to mine, @codedesperate . I asked the company where I ordered it from. You're more than welcome to DM me. I'm not gonna publish it here, in a public place. Regarding 1.36.1, did you get some new issues in the logs for zigbee2mqtt, or? |
|
@exetico Good News! You know when you turn the light on, you can't turn it off straight away, but have to wait like 20 seconds? Well today I migrated from my Sonoff ZBdongle-E to my old Conbee 2. Now the lights reacts instantly to all my commands, also when I execute them quickly. So, it behaves like it should. However, the log still gets riddled with the error messages, but at least they "work" now. This is the specific error:
Also, I flashed the latest stable firmware as be the supported adapters page, but my Aqara Roller shade drivers E1 required a new firmware to function. So I flashed latest firmware for Conbee 2, and so far it haven't given me issues, though I've only ran it for a few hours. I'm gonna buy a Zigstar Stick of Sonoff ZBdongle-P or whatever my googeling tells me will perform the best. I'm on Zigbee2mqtt 1.36.0. 1.36.1 breaks conbee 2 completely as well, every device unresponsive. But I can see on the issues page many conbee 2 users have problems with 1.36.1. EDIT: Just bought this: Listed as recommended, and uses the new CC2652P7. I'll report back when I get it all set up with that coordinator. |
|
Okay, I switched to smlight slzb-07 cc2652p7 today, and it's back to being buggy :( I can control the lights but only with 30 second break between each command, and the log is riddled with errors. |
|
Thanks for the update. I'd really like to see support for this in the future, but I'm not really sure how I can continue on my own. If you end up finding a Hue Bridge, just to test it after the OTA, it would be great to hear if thinks works as expected after that. |
|
I ended up buying a hue bridge, and running only these devices on a hue zigbee network, and then used the hue integration in homeassistant. This works without any issues, but I hope only temporarily until someone clever enough can get it to work with zigbee2mqtt. The hue bridge is reporting firmware 1.00 | 100b-3e8 and showing up-to-date, no update available. So it doesn't seem like a a newer firmware has been officially launched. |
|
@codedesperate could you recap your current (hopefully temporary) solution? So I have a rpi3b+ with a zigbee sonoff adapter and zigbe22mqtt + home assistant. In order to have the light dimmers working as they are supposed to be (fast and reliable) it seems you need to connect them to a philips hue bridge. If I get one, could I connect the hue bridge to the same instance of zigbee2mqtt or I would need a separate instance just for the hue bridge or would I have to set the bridge up directly in home assistant without passing from zigbee2mqtt? |
|
@garret I'm sure he's just adding the Hue Bridge to Home Assistant. Nothing from the Hue Bridge it looped through Zigbee2MQTT. That's my guess. |
|
@garret and @exetico Yeah pretty much. Then in Homeassistant I add the Philips Hue integration, and the hue devices are added. It dosn't touch zigbee2mqtt at all. It does result in two different zigbee networks which is really annoying. Though I run my WiFi on Channel 6, Philisp Hue channel 11, zigbee2mqtt channel 25. And everything works stable. If these devices ever get added to zigbee2mqtt though, I would retire the Hue hub, and repair them with zigbee2mqtt. |
What happened?
If I toggle the light (set on/off) the device does act to it. But, after 10s or so, Zigbee2MQTT throws an error in the log. As stated, the dimmer does turn the light on/off.
If I do another thing, in the period, AFTER the light has turned off, but BEFORE the error from the first action has been thrown, the next action does nothing right away.
But AFTER the error is thrown from the first action, the device turns the lights on.
I'm able to reproduce it over and over again. I only have brightness and light on/off option working, but it seems like this only happens for toggle on/off. Brightnees works most of the times, and a error are never thrown as part of a brightness change.
While debugging I noticed that changing brightness does work every time. Check the last two logs (sorry, there's a few, but I thought it would be useful), where I describe, what's working, and what's not working as expected.
Device shown in GUI as match: https://www.zigbee2mqtt.io/devices/3004482_3137308_3137309.html#light%2520solutions-3004482%252F3137308%252F3137309
Manual in details for the hardware: https://ledpaerer.dk/media/catalog/product/attachment/Manual-engelsk.pdf
Image of the actual product from the manual:
Let me know if I can help with other details. I've also factory reset the device, moved it to another router (hue bulb instead directly to coordinator), and more. Nothing changes the current behavior.
Image from Zigbee2MQTT.
Firmware and ZigBee2MQTT are updated as part of my debugging (after creating the issue), and the dev-channel has been tested, too. Nothing changed the behaviour of the device/situation in general.
What did you expect to happen?
That the light would work properly with the light on/off commands.
How to reproduce it (minimal and precise)
I can reproduce it over and over again, by toggle the light (turning on/off). Error is thrown every time, after the timeout.
Zigbee2MQTT version
main: 1.35.3 commit: fe0742a
dev: 1.35.3-dev commit: 8fb28f9)
Adapter firmware version
20230507(Also tested on 20220219, but I upgraded the firmware today, just to test - I've also factory reset the device and removed it in Z2M during that process, just to secure that everything was erased, if it was a faulty pairing, or similar).Adapter
LAUNCHXL-CC26X2R1(Works with all other devices, not a single one makes problems, and there's a good amount of different devices)Setup
Docker, with Zigbee2MQTT in a container.
The same system also hosts HA, and other things. But I don't think it's related to any of that. All things works just fine, except this dimmer.
Debug log
Here's one example, where I change the power state:
Here another example:
Here's another where I've removed the device, made factory reset of the device, and paired it again. Please don't mind the name change to
0x385b44fffe1b3d45(that's just the original name)And the last case where I also tries to toggle the light, and I end up in some kind of OTA situation, for some reason.
I think it's something related to the device mapping, maybe it's not really the right device.
Some times I also end in a situation with OTA related messages:
Playing with brightness brought one thing to the table. If I set the brightness to 0, it does looks like it's handling the "turn off". And every time I use the "turn on" toggle (not by setting brightness), it turns on, without throwing a error.
But every time I use "turn off", I get the error.
I also noticed that it's not every time the frontend toggles the "switch", if I set brightness to 0. It looks like that's also reflected in the logs.
If I play even more with the brightness and toggles the light off here after, it's also clear that something works, and the device does wierd things, if I use the "turn off" option in ZigBee2MQTT:
The last one are logs where I control the device, by using it's wheel, and it's "on/off" toggle button (pressing in the middel of the large dimmer-wheel), including adjusting brightness.
The text was updated successfully, but these errors were encountered: