I wonder if the problem isn’t that the VTM31-SN is suffering from a radio failure that causes it to jabber on the Thread network and knock all of the other Thread devices off?
How does Thread deal with a jabbering node?
Can a border router vote a node off of the island if it detects a malfunction?
Just throwing out another possibility that I don’t recall being discussed yet…
Just got my white series dimmer and am having problems as well.
I’m using the switch in smart bulb mode and the button press/scene activation functionality simply doesn’t work 99% of the time.
Every once in while (after dozens of attempts) it will work, but the majority of the time HomeKit isn’t even recognizing the button press at all (can tell by having the accessory open while pushing the button).
I’ve tried the suggestions mentioned above, including factory resetting, but the behavior remains the same.
I have no idea if it’s a thread connection issue or not. The switch is seen within HomeKit no problem, and I can control the lightbar from HomeKit with no issue. However when I check the thread network status, the switch blinks red.
My two thread bulbs on the network are working without issue. And the switch is physically located only a few feet from the bulbs and my Apple TV.
EDIT: So after some additional testing, things are even stranger. If I go an hour or so without touching the switch, the next time I press it to activate the smart bulb scene, it will work exactly ONCE, and then cease functioning again. Additionally, the one time it works, it will often cause my smart bulbs to go haywire, turning off and on multiple times (the scene is setup to only turn them off), and then the bulbs will disconnect from HomeKit momentarily before “healing” themselves.
Testing further, the switch works completely fine in smart bulb mode when controlling other accessories. It’s ONLY the thread bulbs (Nanoleaf) when things go haywire. Both the bulbs and switch work 100% reliably when not interacting with each other.
EDIT 2: Sorry, this is becoming a novel. Did some more expirmenting, and the problem happens when the thread bulbs and switch are controlled at the same time. If I have the switch controlling an unrelated device, and simultaneously turn on/off the bulbs, I get the haywire behavior. Has anyone else experienced anything like this with two thread devices?
@rubixhacker did you get any fix on your dead/non-commissioning switch yet?
This sounds vaguely familiar to what I’m seeing - are you using Home Assistant + Homekit in this instance? I’m wondering if there’s a multiple Matter issue in this case.
@devrsw not sure if this question was directed to me, but no I’m not running HomeAssistant. Just HomeKit (with HomeBridge).
No I haven’t.
I know @EricM_Inovelli was getting the first 3 switches I RMAed shipped to him for further investigation. I still have one in my possession but still have been unable to revive it.
I have disabled multi-admin on all of my other white switches (17 in total) and haven’t had any more enter this state.
From what I am seeing in Home Assistant, it looks like HomeKit is using multi-admin under the hood, it registers the device to two fabrics (Apple and Apple Keychain)
Think I fixed my issue. The Lutron dimmer I replaced didn’t have the neutral wire attached, so I didn’t use it for the Inovelli.
I went back in and attached it, and that seems to have solved my communication issues. 
This is 100% EXACTLY my experience. 20 restarts, a network restart, restarting the nanoleaf bulbs, restarting the switch, nothing works. It was working great for 10 days until my network needed a restart, then it works once for 1 bulb and never again.
How do I firmware update? Are we still on v1.0.0?
PM sent
Not sure if this was mentioned anywhere. Could the configuration document be updated to include the default value for each parameter? Some mention the default, some don’t, and an explicit common format for showing the default would be nice.
For configuration parameter 13, the “**Values of 1 & 2 are not available” isn’t quite clear to me. What happens if I try to set value 1 or 2, then?
From what Eric told me, straight from the engineers, it will go to 300 ms on its own if option 1 and 2 are selected.
I had the same question. So 300ms is the lowest setting possible at the moment.
I had another switch do a reboot as part of normal firmware update, and it factory reset itself and is now unable to commission. So that’s two so far for me.
Also verified it’s not simply the radio not responding, because Lance at Inovelli sent me a test QR code that does get the BLE part of the process kicking off.
No other info yet.
I want to reiterate that it’s not just multi admin scenarios that cause this problem, because I’m using only HA ZBT-1, and commissioned via Android.
I believe 1.0.0 is the only firmware available. Looks like the firmware information for the White series hasn’t yet been added to What is the Latest Firmware Version for Your Device? | Inovelli Help Center
On a separate note, I’m assuming the Aux switches work with the White Series? It’s mentioned in the FAQ for the Aux switch that it is compatible:
This Aux switch works with all Inovelli smart switches except the First Gen switches
I haven’t seen confirmation of this though in either the Aux manual, or in any of the documentation .For example, it’s not listed here: Aux/Add-On Switch • Manual | Inovelli Help Center
Yes, it’s compatible with the white series.
There’s no way to currently control the LED bar lighting effect in HA, right? Are we waiting for Matter 1.4 to potentially allow lighting effect selection, or this potentially possible with a firmware update in the future?
Is there a cluster attribute that controls this? If so, I’m working on adding a pull request to the HQ matter server to allow more custom clusters.
There is reportedly a test/debug version of firmware being distributed manually to a small group of people, but it is not in the main distribution channels…
I’ve wondered what the technical limitations are (at the matter server end?). New to Matter/Thread having had zWave for the past 12 years.
Seems HA has been doing a lot of development on Matter, hopefully someone can outline the deficiencies of the led bar effects in a way that the developers with HA/Matter can implement.
I’d like to add that I use the leaf bulbs too. Turning them off sometimes causes them to glitch out, with 1 going off-on and 1 off.
Leave it alone, works great for 3 switches. Then they never work until I restart the network.
I think it’s also crashing my thread network. Much more instability because of this switch