Has anyone noticed any weird behavior with the notification bar since the update?
I have one 2-1 that I first needed to update the bootloader using the wire harness before going to 3.04 OTA. Since the update, I’ve had trouble getting the LEDs to ‘clear_effect’ when called from home assistant. Going directly in the Z2M interface has the same issue. I’ll try to factory reset the switch tonight to see if it clears anything up.
Weirdly, it isn’t just when calling ‘clear_effect’ on all/individual LEDs but also manifests at the end of a pre-defined notification scene. The LEDs don’t clear after the scene is complete, e.g. calling aurora effect in red for 5s via Z2M will run the notification for 5s but then the LEDs will ‘stick’ with whatever their last value was. Double-tapping the config button will clear the effect but it doesn’t seem to clear from Z2M.
It’s not obvious to me if this would be at the switch FW level or an interaction with Z2M so wanted to see if anyone else had a similar observation.
I’ve noticed this behavior with the LED effects sometimes failing to clear, as well. It’s not all the time, but it happens a couple of times a week for me (and I use the notifications a lot, multiple times a day).
Semi-relatedly, I wish sending clear_effect to the overall led group would clear out the effects from individual led_effect calls, but it doesn’t seem to. I like to e.g. light up the lower two lights to let me know when something is happening downstairs, but then I have to explicitly clear those two lights, rather than sending clear_effect to the group as a whole. It would be nice if I didn’t have to mix these calls.
Is there any timeline for an update on this? I do find it remarkable that something as core to the Zigbee protocol like scenes is not in standard unit testing rotations for beta testing, either internally or externally.
@andrew.freyer We have a beta firmware available for testing if you are interested. You can PM me and I can help you out. This feature is not used very often which is why it was missed. It is not available on Hubitat, SmartThings, ZHA, Homey, etc. and I have only seen a reference to it maybe once or twice in all the years we have been selling Zigbee devices. I think most people use their hubs to do what the scenes are programmed to do. Given that, I understand your concern and hopefully we can get you and the other user that uses scenes back up and running!
I also make use of scenes - @EricM_Inovelli I suspect there’s a larger-than-you-think crowd of customers that use on-device scenes to aid home automation. We’re just too lazy to upgrade (or I am, at least, and I assume I’m not alone) and so haven’t run into this new bug yet. Give this firmware time to marinate in the wild - I’d bet $ that you’ll see quite a few more complaints.
For what it’s worth, I use scenes to reduce zigbee traffic in my network (~200 devices; about 80 of which are routers). I also use scenes to visually synchronize the behaviors of multiple fixtures. Home Assistant actions or scenes are fine, but lights are not synchronized because there’s a command issued for each group or fixture. If I want those changes to appear as close-in-time as possible, I need to send the zigbee instructions in fast sequence, which can cause some undesirable effects if I have a floors worth of lights I want to control at once.
Edit - @tagd et al., initial testing of the beta firmware is positive. Scenes are working as expected so far!
Fixed LED notification behavior that did not operate as expected.
Are there more details on this?
I have a VZM31-SN directly bound to the VZM-36 fan canopy module. It used to work where if I sent a command directly to the canopy controller light or fan, that the LED on the switch would automatically update to on off, or the percent dimmed. This was without groups - just a pair of direct binds from the switch to the fan module, and LED sync just worked. It was honestly very impressive when I first set it up.
Now, I can’t get the LED to sync. I suspect upgrading to 3.04 introduced this, but it’s not a common interaction for us so it’s been a while. I could reconfigure things to use groups instead, but I’d rather not if this is fixed in 3.06.
Is anyone else having issues updating using ZHA and home assistant? I am on an old firmware, 0x01020212, and have the update entities for all switches in HA to go to 0x01020304 but everytime I go to update a switch it goes to 100% but doesn’t actually update the firmware from what I can tell. It still just lists 0x01020212 and an update available.
Just wanted to point out that we’re coming up on two months of broken 3.0x switches, and one month since the problem with scenes has been well known, more than a month since a beta was pushed. When can we expect 3.06 to get out of beta? No offense, but I see you’re adding features - can I ask that you re-task your engineer and get scenes working again first?
I’m sure you will come up with an amazing 3.07 with new stuff, but I don’t care when that happens, I just want my kitchen lights to work the way they used to.
The fix has been available for some time and it has been requested to reach out via PM if you would like to have access to it. 3.07+ will likely still be in beta for some time especially since the scene feature is not used by very many users.
I asked support and after a few replies I got this detailed response:
This won’t fully work in my case, because I’m using the config button for the fan, and there’s no switch entity exposed for the config button. But, I can work around that by creating groups.