@EricM_inovelli, I am having an absolute hell of a time with the 3.04 VZM31-SN firmware. Every single updated switch (I have 45, updated about 30 so far) has lost the ability to use scenes at all. Not through groups, not through the switch itself. Scenes are just not being applied at the device itself. z2m handles fine, reports optimistic state updates to HA, but the switches themselves are not responding. My test scenes do not have transitions, and are literally just “on” + brightness.
When I add (programmatically, as noted above, I cannot add in the more conventional way) more than 3 scenes (un-updated switches still handle 15 scenes just fine), there’s a memory space error. INSUFFICIENT_SPACE.
I have updated every software implicated (z2m, HA) here, and the only constant is that updated-firmware VZM31-SNs are failing to handle scenes at all.
I would think I’m the only person in the world experiencing this, as I cannot find anyone else reporting this behavior. But… every single one of my updated switches are exhibiting this behavior. I am at my wits end here.
After updating mine, I had to reconfigure each switch in z2m. Any changes I made to the switch would report properly, for example defaultLocalLevel, but the switch itself seemed to function only with default settings. After reconfiguring everything was ok again.
Oddly enough, I also was having issues with 3 switches in smart bulb mode causing flickering. So far, reconfiguring seems to have fixed that as well.
I am having the exact same problem that @andrew.freyer reports. I have about 40 VZM31-SN, and since upgrading to 3.04 my switches ignore all scene commands - both on/off and level, independently or in conjunction.
When I attempt to add a scene directly on the device, I also receive the INSUFFICIENT_SPACE message. (This also happens on my switches in smart bulb mode, so it’s not limited to Dimmer mode)
I have tried running a reconfigure on each of them, deleting and recreating scenes, groups, putting them in a group by themselves. Everything except scenes works as expected.
One of my switches is brand new and came out of the box with 3.0x firmware and had this problem right off the bat, so I don’t believe it’s caused by the upgrade process.
This firmware has been pretty frustrating. Scenes are a significant part of my configuration. Is it possible to go back to 2.18 where everything worked? If not I’m looking at a pretty large RMA.
My neighbor has a pretty big order of these switches as well and if they’re all at 3.x, I’m going to get a ton of grief for recommending them. More than 100 total switches between us.
I’m not looking forward to hours of downgrading but it’s pretty clear that there was a big miss on this firmware that should be easy enough to confirm or deny.
Can you explain the process you are going through to create scenes? We had several dozen beta testers and they didn’t relay this information to us so I do need some further explanation.
Hi @EricM_Inovelli, thanks for taking a look at this issue. I am using Zigbee2Mqtt. Updated to v2.80.
There is a UI button in z2m that captures current device settings into a scene. Engaging the UI button to record a scene (for a group or a single light) triggers an INSUFFICIENT_SPACE error. I cannot create a single scene from the UI.
Previously created (i.e., before update to fw 3.xx) scenes are enumerated in the z2m UI, but they are not recallable from the UI nor via mqtt. VZM31s and 32s do not respond to scene_recall in any way.
Via an mqtt command, I can create a scene with scene_add through the z2m/[friendly]/set path. If I do this, even with trivially simple scene content: {“scene_add”:{“ID”:2,“name”:“TEST”,“state”: “ON”,“brightness”:255}}, the scene is recognized in the Z2M UI, but it cannot be recalled. Neither pressing the recall button in the UI nor sending an appropriate message with scene_recall via mqtt works to change actual switch state.
I am confident my recall commands are compliant with Z2M specs, as nothing has changed in my automation workflows since this was working prior to 3.xx firmware. I am also able to add and remove scenes for non-inovelli products (e.g., Hue bulbs and Hue groups) just fine.
TL;DR:
old scenes (created under old firmware) do not recall once updated to new firmware; no recall, no action by switches; old scenes are visible
new scenes cannot be created through UI, receive INSUFFICIENT_SPACE error; not saved; no recall, no action by switches
new scenes created via mqtt save, but there is no recall by switches (also, INSUFFICIENT_MEMORY happens after 3 trivially small scenes are stored)
Notes:
other devices (e.g., hue) store and recall scenes just fine
same behavior for both groups of inovelli and individual devices
This matches my experience exactly for all switches with 3.04.
I also have one switch that shipped to me with 3.03 on it which has never worked correctly with scenes, so I do not believe this is an artifact of the 2.x>3.x upgrade process.
Thanks for the reply, I will inform the engineer of what you are experiencing. It seems that this is functionality that those that did beta testing did not use.
Can you provide more info on the load that is attached? I have tested non-neutral with 2x Philips Hue bulbs in Smart Bulb mode and I am not experiencing this. There isn’t a way to downgrade without using a USB flashing tool. I would suggest to attempt to factory reset the switch to make sure there is not any corrupt configuration data from the update.
Edit: Before doing the reset, can you try to change the mode to “Single Pole” to see if that makes a difference? If it is already set to Single Pole, change it to 3-Way Aux Switch and change it back to Single Pole.
Its 3 Philips smart bulbs in one fixture with a bypass.
I already tried switching to single pole from 3-way aux, it seemed to make no difference.
It is interesting it doesn’t always go into the green flashing state as soon as the lights turn off. Sometimes it takes a few minutes, maybe the lights are in a state they are drawing more power even if the light is off?
I am very surprised you are seeing any issue with the bypass installed. I will consult with an engineer to see if they have an explanation. Is the bypass installed at the by the switch or at the light fixture? I am guessing light fixture but just want to make sure. You might want to double check it hasn’t disconnected.
I’m also experiencing flickering since updating firmware, but mine are all neutral installations and all in smartbulb mode. What I’m noticing is that not all bulbs flicker at the same time
5 locations in total.
1 fixture with 2 Philips Hue Par38 bulbs (I ran a reconfigure on this one a few days after updating and all has been good since)
1 fixture with 4 Philips Hue A19 bulbs
1 fixture with 6 Ikea bulbs
2 fixtures each with 4 Philips Hue recessed lights
I have several other locations with various combinations of all of these bulbs and no flickering on any of those.
@MRobi I recommend doing a factory reset on one of these locations to see if there are “cobweb” configuration settings causing problems. I’ve got all of mine in smart bulb mode with neutral and haven’t seen it yet. There are also quite a few other users with this config.
@marcus1060 I will talk to you on your ticket as I believe either the switch or the bypass is defective.
