Lirvano HG07834C RGB Bulb

[Sascha8]

Hi, i've got some problems with the Lirvano HG07834C RGB Bulb from Lidl.

The bulb switches on and goes off after ~300ms. Just a short flicker. This happens always when the brightness value was set more than once to 0. A single change to 0 and back to 100 works fine. A change to 0 and another change to 0 and the issue happens at next time you set brightness to >0

In everyday usage, controlled with Alexa2-Adapter/IOT-Adapterin this happens because the alexa/iot adapter always using the brightness state to switch off a bulb. So it is easy possible that Alexa-routines set the brighness serveral times to 0.

I could reproduce this issue and nailed it to the Zigbee-Adpater after disabling all other adapters. I tried with the latest v1.8.10 and downgraded to v1.8.7 - both versions have this issue.

Would be very thankfull to find a soultuion, because I have three bulbs of this type. 🙃 I have a Livarno Home LED ceiling light (HG08008) too, which doesnt have this issue.

Below the - sorry - long log file. I tried to minimize it, disabled some zigbee devices but they still appear in the log. Most lines are hard to understand if they are ontopic on not. I marked the lines where i did the changes in the object editor.

I started with the bulb "0c4314fffe98bc21" glowing at brightness 70. In iobroker-objects, I set the brighness to: 0 : Bulb goes off. 70: Bulb goes on. 0 : Bulb goes off. 0 : no change. 70: Bulb goes on for ~300ms and goes off.

ieee:0x0c4314fffe98bc21 nwk:38839 (0x97b7) model:HG07834C groups: Gateway: SONOFF Zigbee 3.0 USB Dongle Plus,TI CC2652P + CP2102(N)

Debug_Lidl_HG07834C.txt

[asgothian]

Hi,

Please rerun the test with the following settings:

• Zigbee adapter NOT running with debug activated
• Disable the "zigbee-herdsman-debug info" checkbox in the zigbee adapter settings
• IEEE of the Bulb entered into the state zigbee.0.info.debugmessages

Verify that switching the bulb generates warning messages with the keyword ELEVATED in the iobroker log.

Before posting the log, trim it down to only include the warning messages and any other message which includes the IEEE of the device.

[Sascha8]

okay,

again started with a bright bulb at 70. Then 0: dark 70: bright 0: dark 0: no change 70: 300ms bright, then dark 70: bright

2023-01-27 21:03:53.668 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674849833666,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849833666}
2023-01-27 21:03:53.672 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:03:59.891 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674849839890,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849839890}
2023-01-27 21:03:59.896 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:04:03.891 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674849843889,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849843889}
2023-01-27 21:04:03.896 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:04:08.419 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674849848417,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849843889}
2023-01-27 21:04:08.423 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:04:12.299 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674849852297,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849852297}
2023-01-27 21:04:12.303 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:04:16.546 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674849856544,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674849852297}
2023-01-27 21:04:16.550 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'

[asgothian]

Please repeat the test but leave at least 20 seconds between the state changes

[Sascha8]

30sec pause between changes - same results.

Started with a bright bulb at 70. Then 0: dark 70: bright 0: dark 0: no change 70: 300ms bright, then dark 70: bright

2023-01-27 21:55:00.788 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674852900787,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674852900787}
2023-01-27 21:55:00.792 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:55:30.708 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674852930707,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674852930707}
2023-01-27 21:55:30.712 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:56:00.652 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674852960650,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674852960650}
2023-01-27 21:56:00.655 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:56:30.855 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674852990852,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674852960650}
2023-01-27 21:56:30.901 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:57:00.737 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674853020735,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674853020735}
2023-01-27 21:57:00.742 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 21:57:30.739 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":70,"ack":false,"ts":1674853050737,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674853020735}
2023-01-27 21:57:30.743 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'

[Sascha8]

I added a longer pause... Just do one state change from 70 to 0. This gives more debug msgs. If this helps i can do the complete change procedure...

2023-01-27 22:03:03.836 - warn: zigbee.0 (244690) ELEVATED: User stateChange zigbee.0.0c4314fffe98bc21.brightness {"val":0,"ack":false,"ts":1674853383835,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1674853383835}
2023-01-27 22:03:03.840 - warn: zigbee.0 (244690) ELEVATED Change state 'brightness' at device 0x0c4314fffe98bc21 type 'HG07834C'
2023-01-27 22:06:58.809 - warn: zigbee.0 (244690) ELEVATED publishToState: message received '{"linkquality":171}' from device 0c4314fffe98bc21 type 'HG07834C'
2023-01-27 22:06:58.809 - warn: zigbee.0 (244690) ELEVATED publishToState: value generated '171' from device 0c4314fffe98bc21 for 'Link quality'
2023-01-27 22:06:58.811 - warn: zigbee.0 (244690) ELEVATED publishToState: message received '{"state":"OFF"}' from device 0c4314fffe98bc21 type 'HG07834C'
2023-01-27 22:06:58.811 - warn: zigbee.0 (244690) ELEVATED publishToState: value generated 'false' from device 0c4314fffe98bc21 for 'Switch state'

[asgothian]

This looks normal. The zigbee adapter does not send a second message to the device, and the device acknowledges that it was turned off with the next link quality. I assume that the zigbee-herdsman-converters poll the device status to update it, since the bulb does not report it.

A.

[Sascha8]

And who can finally fix it? is it Koenkk ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[k1tfh]

I have the same problem with HG07834A Livarno Lux GU10 spot RGB. Is there a fix?