I’ve noticed since I recently installed my Blue 2-1 switches that the lights they’re attached to (both in local control and smart bulb modes) will randomly turn off for a couple of seconds, then back on. I was just in the room when one did it and caught the end of a sequence of flashes on the color bar, … yellow, blue.
Has anyone seen this, or know how to stop it?
Are you running non-neutral setup?
No, I have neutrals on all switches. When this has happened, I’ve seen no power issues on other lights on the same circuits. This has happened on multiple circuits.
This is the switch rebooting. Either due to a firmware update (you should see green blinking bar increasing with progress if you have automatic updates enabled) or a wiring/power issue.
What exactly is the load? Wattage?
One has 4 hue bulbs, ~33W. One has some wafer lights ~55W. There is no automatic firmware updates enabled, the switches are on 2.08, so there shouldn’t be an update to happen. And, I’m seeing it several times per day.
I was just in a place where I could see lights from 2 switches and they cycled within a few seconds of each other.
If you are in neutral install, wired properly, this should not be happening. The switch is supposed to auto-sense neutral, can you confirm it shows neutral install?
If so, I’d recommend a delete/hard reset/re-pair with your hub. It is likely that a firmware update has messed with the parameters set up and that there is a conflict or error there.
As with most other devices and as recommended by Inovelli on the firmware update page, any firmware updates where features are added/removed, it is always recomemnded to perform a hard reset after implementing.
How many switches? What are you using for zigbee management (z2m, zha, hubitat)? I had this problem on z2m with very frequent resets but after changing the reporting intervals it improved substantially. Still have it occasionally every few days out of the 49 switches installed. Check your wiring but if that’s not it it may be a reporting issue flooding the switch and causing it to reset.
I have 4 blue switches, and ~20 devices in my network. I’m using home assistant with zha.
The complete light sequence on the color bar is: cyan, blue, yellow.
Looking at the home-assistant logs a bit more, I noticed that the network address of the inovelli switches is being updated a lot, and I’m seeing messages like this:
2023-01-16 21:07:13.627 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xCFEA:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
I see this tens of times for my inovelli switches in a 24 hour period, and occasionally, if at all, for other devices. I just turned off my home assistant box and the switches are going crazy. In 30 minutes, the switches have flashed like this 10 times.
2023-01-16 15:52:26.873 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x0DF0:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:47:27.438 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x0145:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:47:43.016 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xF1FF:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:48:27.455 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xFCBE:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:48:41.952 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x42D9:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:49:12.413 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x2868:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 16:49:41.932 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xED39:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:10:11.967 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x3CA3:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:10:27.035 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x9EFA:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:24:12.188 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xADA9:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:28:12.254 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x373A:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:34:12.227 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xC5D1:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:35:42.556 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x95AD:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:40:57.656 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xA5AA:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 17:52:42.349 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x38C9:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:34:57.266 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x14ED:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:36:12.289 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xEF93:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:38:27.398 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x7E7E:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:39:12.488 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x3ED8:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:39:57.449 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x1F29:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:40:27.349 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xEA19:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 18:53:42.281 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xAD17:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:52:27.682 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x7E91:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:52:57.487 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x74BF:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:53:57.573 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x4631:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:54:27.473 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x7966:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:54:57.599 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x82EC:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:55:12.463 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x701C:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:55:57.651 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x8310:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:56:43.036 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x6D83:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 19:57:12.532 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x27F5:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:00:57.626 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x79E6:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:01:27.667 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xE470:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:01:28.595 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x50FF:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:02:27.604 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x51F9:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:02:57.526 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x49A1:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:03:28.147 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xC8B6:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:04:12.747 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xA965:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:04:42.801 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x3E39:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:05:58.382 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x04CB:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:06:28.076 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x268F:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:07:12.589 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xE3A6:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:48:12.859 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x3CDC:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:48:57.724 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x1CFF:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:49:42.673 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x6147:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:50:27.952 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x86A8:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 20:50:42.866 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x3510:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
2023-01-16 21:07:13.627 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0xCFEA:38:5b:44:ff:fe:ee:0f:de has been reset and re-added or its nwk address changed
I’ve been messing with this some more, and I think this is related (though it’s hard to prove) to some zigbee lights I’m trying to bind to one of my switches (Acuity Brands Lighting (ABL) WF4C_WF6C control via MQTT | Zigbee2MQTT). If they’re in the network, then I’ll get the flashing light behavior, mostly from the switches closer to the the room the lights are in. I think that something about routing these lights’ messages is crashing the switches causing them to reboot. I’m not sure how to prove this more concretely though.
@EricM_Inovelli Are these known issues? 1) switch crashing and rebooting when routing some messages? 2) when it does, and it’s in smart switch mode/zigbee bound to a group, it’s turning the lights on.
My lights started turning on at 2:30 this morning and I had to air gap the switch to get through the night…
I haven’t seen this particular issue. I’ve seen some switches reboot if the air gap is slightly interfering with the air gap mechanism and the switch is rebooting. This is usually on a single switch in an environment (depending on how many switches you have). You are using zha or z2m? There is a fix for excessive broadcast messages in firmware 2.10 but we have discovered a different bug in it so it hasn’t been made widely available. The engineers have been out for the last couple of weeks because of Chinese New Year, but they are back now and working on various issues and new products.
I’ve had the same behavior with both zha and z2m, and with multiple controllers. Is there anything I can do to help root cause? Is it possible to extract any diagnostic data from the switch, for example?
I have a video of this happening in rapid succession when I turned off my hub completely, if I can email it to you (doesn’t look like I can upload videos here)
It’s these bulbs here, so folks are struggling with them in other ways, but I don’t see anyone else mentioning my issue now that they have blue switches in hand, too.
Just to re-enforce, I’m seeing the crashing on all 4 of my blue switches, with firmware 2.08, from the 2211 batch.
Just an FYI I’m still having the problem of random resets on random switches. Hoping its fixed with upcoming firmware update. I’m 100% sure the wiring is good and is not the issue.
I am hoping firmware 2.10 fixes the issue, but it has a different bug in it. We should be getting firmware 2.11 next week with the 2.10 fix, some other bug fixes, and some extra features. If you have the ability to flash 2.10 as an independent file on a switch or two, you might want to try it, but it may be good to wait.
Just a thought here… have you tried running it as just a regular dumb light switch for a few days? If it stops completely you’ll know this is related to Zigbee. If it still does it, it may be something in the switch. Another thought I have, have you checked all wiring connections to the switch are tight and secure?
Yes. With the zigbee lights not on the network I have no issues. I’ve currently got 2 separate meshes with 2 controllers. One network with just the lights and another with everything else. No issues, other than I haven’t had time to manually manage the lights from switch events through ha, so I’m left with turning the lights on and off with Alexa…
Hey Eric, any estimate on the release timing for 2.11 in Z2M?