device: Namron 4512750/4512751 issues on firmware 3.10

SanderBlom commented 1 month ago

What happened?

This summer, I ordered 10-15 dimmers from Namron. Initially, I received only 4 devices, with the remaining ones arriving in October. The first batch, which came with firmware version 3.09, performed flawlessly—allowing me to turn the lights on and off and adjust the brightness with immediate response. However, the final batch arrived with firmware version 3.10, which caused issues. The lights would take a few seconds to turn on, and after about 10-15 seconds, I encountered an error in Z2M. So if i turned on the light it would turn on and after about 10-15 sec i get the error message. If I in the same timespan (before the error) I try to adjust the brightness nothing happens until the first error shows up. After the error shows it will then adjust the brightness and 10-15 sec later it will show a new error message.

Turning the light ON

Publish 'set' 'brightness' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genLevelCtrl.moveToLevelWithOnOff({"level":120,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 100 - 8 - 11 after 10000ms)'

Dimming the light

Publish 'set' 'brightness' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genLevelCtrl.moveToLevelWithOnOff({"level":82,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 104 - 8 - 11 after 10000ms)'

Turning the light OFF

Publish 'set' 'state' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 105 - 6 - 11 after 10000ms)'

So all the new dimmers with the 3.10 firmware have this issue that turning them on or off works but after 10-15 sec we get an error message. It also looks like no other commands in the 10-15 sec are processed until the error message is displayed.

After contacting the distributor in Norway about the difference in the firmware, I got this response back (from device manufacture in china):

Changes v3.09 > v3.10 Implementation of Min, Max and start-up level of lightness. Clusters for dimmer settings Min,Max, Start-Up light levels Implement in the dimmer fw in the dimmer MCU the chosen ZB Clusters respectively: (The chosen ZB Cluster is from the zigbee standard for Ballast, not Light control. Since there is no defined ZB Cluster for these settings in the ZB standard library) Cluster 0x301 (Ballast Configuration) Attribute 0x001 (Ballast settings) Attributes set 0x0010 (Min level setting) (6 repeated short push on the self reset switch) 0x0011 (Max level setting) (8 repeated short push on the self reset switch) 0x0012 (Power On level) (5 repeated short push on the self reset switch) These chosen attributes may be implemented in the ZB instructions in the MCU. We think it can be tested by sending commands to the UART Interface on the CPU ( RX/TX) directly via cable. Because we still don’t have any App to test on. It will be available in September.

What did you expect to happen?

I expected that they would respond the same as the other devices with the 3.09 firmware

How to reproduce it (minimal and precise)

Toggle the light on/off and check the error logs about 10-20 seconds after changing the dimmer's state.

Zigbee2MQTT version

1.40.2

Adapter firmware version

20210708

Adapter

Sonoff Zigbee 3.0 USB Dongle

Setup

add-on on Home Assistant

Debug log

info 2024-10-20 20:44:06z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:44:06z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":234,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:44:16z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:44:19z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
error 2024-10-20 20:44:29z2m: Publish 'set' 'state' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 115 - 6 - 11 after 10000ms)'
info 2024-10-20 20:44:39z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":201,"linkquality":57,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:44:49z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:44:59z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
error 2024-10-20 20:45:02z2m: Publish 'set' 'brightness' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genLevelCtrl.moveToLevelWithOnOff({"level":201,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 116 - 8 - 11 after 10000ms)'
info 2024-10-20 20:45:09z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"OFF","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:45:09z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":57,"power_on_behavior":null,"state":"OFF","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
info 2024-10-20 20:45:22z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/lys-soverom-2', payload '{"brightness":135,"linkquality":60,"power_on_behavior":null,"state":"OFF","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'
error 2024-10-20 20:45:32z2m: Publish 'set' 'state' to 'lys-soverom-2' failed: 'Error: ZCL command 0x84b4dbfffec4d232/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 21842 - 1 - 117 - 6 - 11 after 10000ms)'

Konstabel commented 1 month ago

I have the same issue with my Namron 5412751. I just got it two days ago. First command is working, and then I get 7-15sec delay on the next command. In the debug log I can see that it reports Installed_version20 / latest_version10.

info 2024-10-24 20:40:10z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/NamronDimmer2', payload '{"brightness":30,"linkquality":255,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'

SanderBlom commented 1 month ago

I have the same issue with my Namron 5412751. I just got it two days ago. First command is working, and then I get 7-15sec delay on the next command. In the debug log I can see that it reports Installed_version20 / latest_version10.

info 2024-10-24 20:40:10z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/NamronDimmer2', payload '{"brightness":30,"linkquality":255,"power_on_behavior":null,"state":"ON","update":{"installed_version":20,"latest_version":10,"state":"idle"},"update_available":null}'

I would advise you to try to contact namron and hopefully they can come with a fix. They told me that if multiple people experienced the same issue they could potentially look into it.

fyksen commented 4 weeks ago

I have two batches of the 4512751. The ones I ordered first came with the firmware version: 3.09 , the other 3.10

I'm using ZHA, not zigbee2mqtt. But seems like the problems are the same. With the first one I have this issue (sent mail to Namron today): 3.09

When the light is on and an automation turns it off, everything works as expected. However, if the light is already off and I run an automation to turn it off again, then try to turn the light back on using the dimmer button, it doesn't turn on to the minimum set value. Instead, it turns on to the absolute lowest setting possible, resulting in that the light doesn't come on at all. I've set the minimum value by pressing the dimmer six times, but this setting isn't respected when Home Assistant turns off the light after it's already off.

The second seems to have the same problems as you. generally being unresponsive, when send multiple commands, and not send status back to ZHA.

Sorry for piling on in this issue tracker, just wanted to add my findings.

Edit: Found out the firmware software build of the devices.

SanderBlom commented 4 days ago

@fyksen Did you get any response back from Namron?

fyksen commented 3 days ago

@fyksen Did you get any response back from Namron?

Just that they did not support z2m and ZHA. But that they might support it in the future, but right now it was too much work. I asked for firmwares, so I could downgrade them to the same 3.09, but haven't heard back.

I really hope that others also contact Namron about this. It is really easy, just send them a mail on post@namron.com

SanderBlom commented 3 days ago

@fyksen Did you get any response back from Namron?

Just that they did not support z2m and ZHA. But that they might support it in the future, but right now it was too much work. I asked for firmwares, so I could downgrade them to the same 3.09, but haven't heard back.

I really hope that others also contact Namron about this. It is really easy, just send them a mail on post@namron.com

I received a similar response, but they mentioned they'd consider it if multiple people reported the same issue. While they don’t need to officially support it, they should at least publish the firmware and Zigbee cluster specifications for each device. This would make it much easier for us to add support on our own.

Konstabel commented 2 days ago

I received response from Namron today. It was not "possible" to downgrade firmware. So I guess that means that they will not share previous firmware versions. Would be nice to get this working, but I have returned my two dimmers and will test a different maker next time.

Koenkk / zigbee2mqtt