Occasional flickering of iCasa lamps

[vdkeybus]

What happened

For the last 2 weeks, I am trying a CC2652R instead of the Conbee II. There is one highly annoying problem that was never there with the CC2531 and Conbee II: the 4 iCasa lights ICZB-B2FC125 (together in a group) flash occasionally, like once in 5 mins.

They are the only devices that seem to behave like that, and it never happened with the other coordinators. Not sure if the Conbee used Zigbee 3.0 (the slaesh CC2652 does), otherwise that would be a change too.

Also, when turning the lights are turned on on, they briefly light up at full power, rather than at the preset level. This does not always happen, but pretty always when they have been off for a longer time (> 5 mins).

Oct 05 01:39:16 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:16: Received Zigbee message from '0x00158d00013d3ce5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":420025876,"imageType":4364,"manufacturerCode":4137}' from endpoint 1 with groupID 0 Oct 05 01:39:31 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:31: Received Zigbee message from '0x00158d00013d320c', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":420025876,"imageType":4364,"manufacturerCode":4137}' from endpoint 1 with groupID 0 Oct 05 01:39:34 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:34: Received Zigbee message from '0x00158d00013d3cfc', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":420025876,"imageType":4364,"manufacturerCode":4137}' from endpoint 1 with groupID 0 Oct 05 01:39:35 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:35: Received Zigbee message from '0x00158d00013d3202', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":420025876,"imageType":4364,"manufacturerCode":4137}' from endpoint 1 with groupID 0 Oct 05 01:39:42 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:42: Received Zigbee message from '0x086bd7fffe03db78', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0 Oct 05 01:39:42 zacate npm[3125805]: Zigbee2MQTT:info 2020-10-05 01:39:42: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffe03db78', payload '{"brightness":254,"linkquality":126,"state":"OFF","update_available":false}' Oct 05 01:39:42 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:42: Received Zigbee message from '0x14b457fffe40fded', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0 Oct 05 01:39:42 zacate npm[3125805]: Zigbee2MQTT:info 2020-10-05 01:39:42: MQTT publish: topic 'zigbee2mqtt/0x14b457fffe40fded', payload '{"brightness":254,"linkquality":126,"state":"OFF","update_available":false}' Oct 05 01:39:53 zacate npm[3125805]: Zigbee2MQTT:debug 2020-10-05 01:39:53: Received Zigbee message from '0x00158d00013d320c', type 'attributeReport', cluster 'lightingColorCtrl', data '{"currentY":24701}' from endpoint 1 with groupID 0 Oct 05 01:39:53 zacate npm[3125805]: Zigbee2MQTT:info 2020-10-05 01:39:53: MQTT publish: topic 'zigbee2mqtt/licht_polyvalente_ruimte_2', payload '{"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_temp":440,"state":"OFF"}' Oct 05 01:39:53 zacate npm[3125805]: Zigbee2MQTT:info 2020-10-05 01:39:53: MQTT publish: topic 'zigbee2mqtt/0x00158d00013d320c', payload '{"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_temp":440,"linkquality":126,"state":"OFF"}'

No other light has this problem.

What did you expect to happen

Light stays off when told to...

Debug info

Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20200830,"transportrev":2},"type":"zStack3x0"}'

[TilmanK]

Is this the light affected?

MQTT publish: topic 'zigbee2mqtt/licht_polyvalente_ruimte_2', payload '{"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_temp":440,"state":"OFF"}'

This is the only message that is sent in the logs provided. I tried to send the same payload to one of my lights, without any problem. What I observed is, that the color settings are sent before the brightness. Maybe your light switches on, when getting a color value.

Could you check what happens, when you send {"color":{"x":0.3805,"y":0.3769},"color_temp":440} as payload to the light while it's switched off?

[redahb]

I can add to this, it is not a problem with the CC2652R stick. I have a group of 6 bulbs from the same manufacturer, and they did the exact same thing on my CC2531: Every so often the group of bulbs flashes. I just had the bulbs turned off from mains to prevent it, because I thought I had some script/automation error in Home Assistant. However on first glance I could not find anything in Home Assistant and I actually even removed every single trigger/script/automation I had on these bulbs. Yet the error persists.

[vdkeybus]

This is curious. The problem does not occur anymore. The only things I can remember that have changed in the meantime are:

• updated HA to 0.115.6 (and subsequent restart);
• renewed Nabu Casa account login (deleted all in .cloud) due to expired keys;
• removed kodi automation.

With @redahb, my setup shares the use of groups for this light.

I took some logs again:

Oct 09 17:47:41 zacate npm[3201603]: Zigbee2MQTT:info 2020-10-09 17:47:41: MQTT publish: topic 'zigbee2mqtt/licht_polyvalente_ruimte_2', payload '{"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_temp":440,"state":"OFF"}' Oct 09 17:47:41 zacate npm[3201603]: Zigbee2MQTT:info 2020-10-09 17:47:41: MQTT publish: topic 'zigbee2mqtt/0x00158d00013d3202', payload '{"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_temp":440,"linkquality":30,"state":"OFF"}'

[github-actions[bot]]

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

[paulgbrichardson]

Did you ever get to the bottom of the issue. I have four of these bulbs in my dining room and office and its driving me nuts!

[vdkeybus]

No. All seemed fine on the z2m side.

We have somewhat gotten used to the flashes (about 3 in an evening), but it is weird for the neighbours to see the lights flashing. Looks like we're taking pictures at 4am.

It is also the only lamp type I have that exhibits this behaviour.

I simply did not find the time to engage with iCasa. Are you interested ?

Op wo 9 jun. 2021 om 12:55 schreef Paul @.***>:

Did you ever get to the bottom of the issue. I have four of these bulbs in my dining room and office and its driving me nuts!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-857596092, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXHYPRP6WCFWE7MF6RZLTR5CBNANCNFSM4SEAWU4Q .

[paulgbrichardson]

thanks for the response. I've raised a ticket with iCasa. I couldn't see anything coming from my z2m instance either. It feels like a heartbeat waking the lights up but honestly not a clue!

[tungmeister]

@paulgbrichardson Did you get to the bottom of this? I'm also seeing the same issue.

[paulgbrichardson]

@paulgbrichardson Did you get to the bottom of this? I'm also seeing the same issue.

Afraid not. iCasa responded and blamed the co-ordinator but as I can't see anything in the logs I haven't done any more troubleshooting. The lights are in my office which I don't really use in the dark during the summer so I haven't had the lights on recently anyway.

If I get chance soon I'll turn the lights on and turn off z2m and see if they still flicker on their own.

[tungmeister]

@paulgbrichardson interestingly mine seem to have stopped. I'm currently running a cc2351 whilst waiting for my slaesh stick. I had an issue with it randomly crashing (mainly due to too many devices on the network) so I flashed it with the source routing firmware. Since I did that this morning I've been in the room all day (they're bedside lights and I'm renovating the room atm) and they've not flickered once.

[vdkeybus]

I also have observed that when you reset the entire system, the flashes go away for a couple of days, but then they return.

Op ma 2 aug. 2021 om 22:42 schreef tungmeister @.***>:

@paulgbrichardson https://github.com/paulgbrichardson interestingly mine seem to have stopped. I'm currently running a cc2351 whilst waiting for my slaesh stick. I had an issue with it randomly crashing (mainly due to too many devices on the network) so I flashed it with the source routing firmware. Since I did that this morning I've been in the room all day (they're bedside lights and I'm renovating the room atm) and they've not flickered once.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-891318922, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXHZFML3EYOXRR6FES2DT237KRANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[tungmeister]

they're still fine (been in the room all day again) so that's at least 60 hours without any issues - I'll have to see if this changes over the coming week.

[vdkeybus]

It will return. Rest assured.

I just did some tests, there are a few curious things going on.

In test 1, I turn on and off all 4 lights in a group:

zigbee2mqtt/0x00158d00013d3cfc {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"ON"} zigbee2mqtt/0x00158d00013d320c {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"ON"} zigbee2mqtt/0x00158d00013d3202 {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":48,"state":"ON"} zigbee2mqtt/0x00158d00013d3ce5 {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"ON"}

zigbee2mqtt/0x00158d00013d3cfc {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d320c {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3202 {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":48,"state":"OFF"} zigbee2mqtt/0x00158d00013d3ce5 {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"}

After this, they regularly report their state:

zigbee2mqtt/0x00158d00013d3cfc {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":48,"state":"ON"} zigbee2mqtt/0x00158d00013d3cfc {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d320c {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3202 {"brightness":254,"color":{"x":0.3805,"y":0.4185},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3202 {"brightness":254,"color":{"x":0.4806,"y":0.4185},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3202 {"brightness":254,"color":{"x":0.4806,"y":0.4185},"color_mode":"color_temp","color_temp":404,"linkquality":48,"state":"OFF"} ...and a couple of mins. later... zigbee2mqtt/0x00158d00013d320c {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":48,"state":"OFF"} zigbee2mqtt/0x00158d00013d320c {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3cfc {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3202 {"brightness":0,"color":{"x":0.4806,"y":0.4185},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d320c {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d320c {"brightness":0,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"}

Observe:

1. Light 0x00158d00013d3ce5 is always missing in the reports. It does respond to commands, though;
2. After a while, all lights report brightness 0 while 254 was set. But they do have a state with brightness==254 and state==OFF;
3. Lights report different color values while they were never set by z2m. E.g. light 0x00158d00013d3202 has an x color value that went from 0.3805 to 0.4806.

In test 2, I manually turn off the lights

zigbee2mqtt/0x00158d00013d3cfc/set {"brightness":"0","state":"OFF"} zigbee2mqtt/0x00158d00013d3cfc {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"} zigbee2mqtt/0x00158d00013d3ce5/set {"brightness":"0","state":"OFF"} zigbee2mqtt/0x00158d00013d3ce5 {"brightness":254,"color":{"x":0.3805,"y":0.3769},"color_mode":"color_temp","color_temp":404,"linkquality":51,"state":"OFF"}

Look how brightness is now 254 immediately after that. And lo and behold, 0x00158d00013d3ce5 suddenly does report again (only now - won't report later anymore).

I see 2 possible options: a) problem = light. But I can't understand at all why any of them (the non-reporting 3e5 flashes just as much as the rest) would turn on and off. It also looks more like a turn-on command quickly followed by a turn-off command, and not like an electric disturbance. Also, iCasa would have been out of business by now. b) problem = coordinator. But it would be sending 'rogue' commands (maybe remnants in a buffer) that don't end up in the logs.

One remaining item is the presence of this every minute or so from every light:

zigbee2mqtt/bridge/logging {"level":"debug","message":"Received Zigbee message from '0x00158d00013d3ce5', type 'commandQueryNextImageRequest', cluster 'genOta', data '{\"fieldControl\":0,\"fileVersion\":420025876,\"imageType\":4364,\"manufacturerCode\":4137}' from endpoint 1 with groupID 0"}

Does this mean I need to update ?

Op wo 4 aug. 2021 om 22:02 schreef tungmeister @.***>:

they're still fine (been in the room all day again) so that's at least 60 hours without any issues - I'll have to see if this changes over the coming week.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-892936126, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH7UJN2QSS56QLGINJLT3GMFTANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[tungmeister]

I don't think it's the lights - when I first experienced the issue I thought it was only happening with one of the bulbs so I complained to Amazon and got another 2 pack sent out. The issue then continued with the new bulb I installed and I noticed it on the other one from the first pack - so I've had the issue with all 3 bulbs I've used now and how I ended up on this issue. As you said if the issue was the bulbs and this happened with all of them the products would never have been released.

[vdkeybus]

I don't think it's the lights - when I first experienced the issue I thought it was only happening with one of the bulbs so I complained to Amazon and got another 2 pack sent out. The issue then continued with the new bulb I installed and I noticed it on the other one from the first pack

• so I've had the issue with all 3 bulbs I've used now and how I ended up on this issue.

The lamps could still have a software bug that affects them all, wouldn't you think ? Or no bug at all for that matter. Apparently these lights are running fine with other coordinators.

I think we need a sniffer for this.

—

You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-893033953, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2KHZTLNDLTIUSAFDTT3HCLFANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[vdkeybus]

Ok. I did some Zigbee network sniffing.

Additional things I noted:

1. the flashes occur approx. every 6..7 minutes;
2. they only affected 3 of the 4 lights (the seemingly unaffected one is the 3202 light, not the 3ce5 that's not reporting its state)
3. a 'flash' is both brief turn-on when the light is off, as well as brief turn-off when the light is on

Attached are a couple of logs that I terminated with 5 secs. after a 'flash'.

There's also logs of a turn-on as well as a turn-on and -off where in both cases, all the lights briefly go to full brightness, to immediately go back to nearly zero and then ramp up in 2s as requested.

Op do 5 aug. 2021 om 08:59 schreef Jeroen Van den Keybus < @.***>:

I don't think it's the lights - when I first experienced the issue I

thought it was only happening with one of the bulbs so I complained to Amazon and got another 2 pack sent out. The issue then continued with the new bulb I installed and I noticed it on the other one from the first pack

• so I've had the issue with all 3 bulbs I've used now and how I ended up on this issue.

The lamps could still have a software bug that affects them all, wouldn't you think ? Or no bug at all for that matter. Apparently these lights are running fine with other coordinators.

I think we need a sniffer for this.

—

You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-893033953, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2KHZTLNDLTIUSAFDTT3HCLFANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[tungmeister]

@Koenkk any thoughts?

[vdkeybus]

This may need to be reopened. I didn't close, so I cannot reopen.

Not even sure if @Koenkk/zigbee2mqtt @.***> is subscribed to this.

Op do 5 aug. 2021 om 13:57 schreef tungmeister @.***>:

@Koenkk https://github.com/Koenkk any thoughts?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-893399413, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXHYLIVYP7M2B7OLMZ2DT3J4BTANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[paulgbrichardson]

@Koenkk any thoughts?

[Koenkk]

If someone can share a Zigbee sniff of the moment it flashes I can look further into this (please provide the wireshark packet number the moment it flashes). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

[vdkeybus]

A couple of e-mails ago I actually did all that. Are there no attachments ?

Op ma 16 aug. 2021 om 17:00 schreef Koen Kanters @.***>:

If someone can share a Zigbee sniff of the moment it flashes I can look further into this (please provide the wireshark packet number the moment it flashes). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-899581322, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2AU4ABOGWNP5BW6GDT5ER2DANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[Koenkk]

A couple of e-mails ago I actually did all that. Are there no attachments ? Op ma 16 aug. 2021 om 17:00 schreef Koen Kanters @.***>: … If someone can share a Zigbee sniff of the moment it flashes I can look further into this (please provide the wireshark packet number the moment it flashes). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4561 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2AU4ABOGWNP5BW6GDT5ER2DANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

I don't see any, you can drag the sniff in the comment box.

[vdkeybus]

Here you go.

icasa_logs_1.zip

[Koenkk]

@vdkeybus thanks, but the sniffs are quite long, could you indicate exactly when the flickering happend in the situation where you send no commands and wait till it flickers? Please provide the wireshark packet no. of this.

[sammyke007]

I have 5 iCasa E27 filament bulbs in my house and had the blinking in the past. Yesterday, after a power outage in my house, they started blinking again. Log isn't showing anything. It does seems to happen once every 7 minutes like someone mentioned above. I forgot what I did a couple of months ago to make it stop :-(. Restarting Z2M or uplugging/plugging the bulbs doesn't seem to help. Crazy thing is, that it blinks once every 6-7 minutes for 3 or 4 times, but then stops blinking for an hour or longer and returns again later :-D

[vdkeybus]

@vdkeybus thanks, but the sniffs are quite long, could you indicate exactly when the flickering happend in the situation where you send no commands and wait till it flickers? Please provide the wireshark packet no. of this.

There's quite a lot of traffic coming in, and I cannot exactly pinpoint the transmission that caused the flicker.

I immediately stopped (within 5 to 10 secs.) any of my logs after observing a flicker event. So the flicker will have happened in the last 5..10 secs of the logs I provided.

After stopping a log, I started a new one. Hence the 7-minute intervals.

I will need to connect light detectors to the host running the sniffer to exactly determine the occurrence of a flicker, but that would obviously be a significantly more elaborate experiment. I can do it if really needed, but I hope the multiple logs of the last 10 secs will be sufficient.

[Koenkk]

@vdkeybus what is the networkAddress of the problematic bulbs?

[vdkeybus]

0x00158d00013d3cfc 0x00158d00013d320c 0x00158d00013d3202 0x00158d00013d3ce5

BTW Maybe we should re-open this issue ?

[Koenkk]

That is the ieeeAddr, not the networkAddress. Anyway I've noticed that most of your sniffs end with a OTA request. I've added some extra debug logging for this in the dev branch. See https://www.zigbee2mqtt.io/information/debug.html on how to enable debug logging. Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

Can you check that everytime the bulb flickers, you see a Device '[MY_ICASA_BULB]' requested OTA logged for this device?

[sammyke007]

My bulbs have been flickering all day now, so I searched for my old CC2531, flashed it, configured ZBOSS, sniffing is working fine... and the flickering stopped for 30 minutes already...

[sammyke007]

While sniffing (with filter enabled for only one of the problematic iCasa bulbs), I see that besides link statusses it also sniffs:

• 9930 1969.901677 0x8bea 0x0000 ZigBee HA 57 ZCL OTA: Query Next Image Request, Seq: 24
• 10068 2018.473810 0x0000 Broadcast ZigBee 51 Many-to-One Route Request, Dst: 0xfffc, Src: 0x0000

But these happen without the flickering for now.

[vdkeybus]

The OTA requests and the flickers do not seem to be related.

All 4 iCasa lamps repeat the OTA requests every minute plus a little bit:

Aug 20 19:34:22 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:34:22: Device '0x00158d00013d3cfc' requested OTA Aug 20 19:34:30 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:34:30: Device '0x00158d00013d3202' requested OTA Aug 20 19:34:46 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:34:46: Device '0x00158d00013d320c' requested OTA Aug 20 19:35:06 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:35:06: Device '0x00158d00013d3ce5' requested OTA Aug 20 19:35:23 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:35:23: Device '0x00158d00013d3cfc' requested OTA Aug 20 19:35:31 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:35:31: Device '0x00158d00013d3202' requested OTA Aug 20 19:35:47 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:35:47: Device '0x00158d00013d320c' requested OTA Aug 20 19:36:07 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:36:07: Device '0x00158d00013d3ce5' requested OTA Aug 20 19:36:24 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:36:24: Device '0x00158d00013d3cfc' requested OTA Aug 20 19:36:33 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:36:33: Device '0x00158d00013d3202' requested OTA Aug 20 19:36:48 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:36:48: Device '0x00158d00013d320c' requested OTA Aug 20 19:37:08 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:37:08: Device '0x00158d00013d3ce5' requested OTA Aug 20 19:37:26 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:37:26: Device '0xccccccfffe26a5d9' requested OTA Aug 20 19:37:26 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:37:26: Device '0x00158d00013d3cfc' requested OTA Aug 20 19:37:34 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:37:34: Device '0x00158d00013d3202' requested OTA Aug 20 19:37:50 zacate npm[1468358]: Zigbee2MQTT:debug 2021-08-20 19:37:50: Device '0x00158d00013d320c' requested OTA

Right now, they're about 10-ish seconds apart, so it's hard to tell if there's a correlation.

[tungmeister]

I've not noticed a single flicker for the last 18 days with mine - In that time I've migrated to a slaesh stick and the flickering still hasn't returned. It's really strange as initially, I had it pretty much constantly before moving to the source routing fw on the cc2531.

[Koenkk]

I doubt more and more this has something to do with z2m, in the sniff you don't see any commands being send to the bulb so they seem to do it on their own. Can somebody check if it also happens with the original gateway?

[vdkeybus]

I think iCasa does not make gateways. Their website says: "Easy to add to your Zigbee gateway"

Is there a way to actually perform the OTA update ?

[sammyke007]

They don't seem to have their own gateway AFAIK. Don't know how to perform OTA then... Flickering has stopped over here for 72h now. The flickering began 5 days ago after a power outage and stopped all of a sudden when I got my sniffer setup ready 2 days later.

[Koenkk]

@vdkeybus

Is there a way to actually perform the OTA update ?

If they provide them yes, otherwise no.

[kisseler]

I have the same phenomenon with my Paulmann Aptare Pendelleuchte. Occasional short blink when OFF and occasional turn off when ON. Period in between 5 Min. and a few hours. I use TI LAUNCHXL-CC1352P-2 with latest firmware. The manufacturer already delivered a new power adapter and zigbee element. After changing those parts, the behaviour did not disappear (for z2m it's a new device). I'm curious to find out what's the problem.

[vdkeybus]

@kisseler If you're able to sniff the packets, could you check the Zigbee chipset manufacturer. I'm not sure, but the Extended ID for my lamps seems to be from Jennic.

[ballwax]

Hi all, just as Informationen, I have exactly the same issues with some Paulmann 929.63 and CC2531 stick.

[kisseler]

I did not have time to go deeper in that issue with Paulman devices. So my solution was: I bought a iluminize Zigbee 3.0 LED Controller, replaced the Paulman controller and everything works as expected, no flickering, good response and additionally the possibility to connect a physical light switch (pulse). I'm still curious what might have been the problem. If anyone needs my spare Paulman controllers, let me know. ;-)

[github-actions[bot]]

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

[paulgbrichardson]

@tungmeister @sammyke007 have you solved your issues? I'm still having flickering and now its getting darker in the UK have the lights on more. Getting to the point where I might have to replace them with something more stable. Very frustrating.

[vdkeybus]

What other devices are in your Zigbee network (brands) ?

I'm also suspicious that the rest of the network, incl. the coordinator, may actually cause the lights to misbehave. I've encountered (other) lamps that needed a re-power every month, and also lamps that are unreachable, though they are 1m from another lamp that readily responds to commands. (In the latter case I suspect a nonsensical Zigbee network topology.)

J.

Op vr 15 okt. 2021 om 10:46 schreef Paul @.***>:

@tungmeister https://github.com/tungmeister @sammyke007 https://github.com/sammyke007 have you solved your issues? I'm still having flickering and now its getting darker in the UK have the lights on more. Getting to the point where I might have to replace them with something more stable. Very frustrating.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-944116228, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXHZYNRSGOWTHK7IEGD3UG7S7HANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[tungmeister]

@paulgbrichardson I've had 0 issues since I setup my new coordinator at the start of August. I've currently got 4 of the bulbs in use and they're all fine. I'm using TRÅDFRI repeaters and my coordinator is a slaesh stick.

[paulgbrichardson]

@tungmeister Thanks - that might be the route I take. I'm on an old TI CC2530 and been thinking of upgrading as the number of devices grow. fingers crossed it works!

[vdkeybus]

But the issue is: I have the slaesh stick as well, and Ikea stuff in between. So essentially the same as Daniel.

Daniel, where are the iCasa lights in your network topology ? With me, they're at the edge and cannot communicate directly with the coordinator.

Op vr 15 okt. 2021 om 11:48 schreef Paul @.***>:

@tungmeister https://github.com/tungmeister Thanks - that might be the route I take. I'm on an old TI CC2530 and been thinking of upgrading as the number of devices grow. fingers crossed it works!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/4561#issuecomment-944156808, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2X7ZAM5WKYEEUHDW3UG72HJANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[sammyke007]

@tungmeister @sammyke007 have you solved your issues? I'm still having flickering and now its getting darker in the UK have the lights on more. Getting to the point where I might have to replace them with something more stable. Very frustrating.

For me it stopped by itself after a week or so... I'm using a ZZH stick (CC2652R). It started after a power outage in my street. Never found out why it started, never found out why it stopped :-D

[tungmeister]

But the issue is: I have the slaesh stick as well, and Ikea stuff in between. So essentially the same as Daniel. Daniel, where are the iCasa lights in your network topology ? With me, they're at the edge and cannot communicate directly with the coordinator. Op vr 15 okt. 2021 om 11:48 schreef Paul @.***>:> … @tungmeister https://github.com/tungmeister Thanks - that might be the route I take. I'm on an old TI CC2530 and been thinking of upgrading as the number of devices grow. fingers crossed it works! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4561 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNXH2X7ZAM5WKYEEUHDW3UG72HJANCNFSM4SEAWU4Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[xaziwb]

Same problem. I have 2 flickering bulbs:

• Oeeone Edison E27 (paired as Paulmann 50064 ???; but working); name: oeeoneBulb01
• Müller Licht Tint retro E27; name: retrotint01 Coordinator: Slaeshs Stick See Network Map attached; Oeeone is near by the coordinator; Müller across the house.