Follow-up with a few more observations/results. The one worked fine so I ended-up doing another and another. Got a bunch done last night and continuing on this morning.
Most switches worked just fine. Things I did/observed. Abbreviations: HA=Home Assistant, MS=Matter Server.
I did all of this one switch at a time, as suggested.
Update had to be done via the MS UI. The HA device pages saw there was a different firmware, but would not offer to do the update.
Doing the update took a few minutes per switch.
After the update, the switches paused for about 10-15 seconds then rebooted. During this period, HA generally didnāt see it going Offline (in the MS), nor Unavailable (in the HA Device). For the most part, within about 2-3 minutes, the HA Device page saw the new (1.0.4r3) Firmware and the switch worked successfully. Around this same time frame, the MS saw that āEndpoint 30ā disappeared.
For a few switches I had to interact with the switch by pressing the Up/Down/Config buttons multiple times before it would actually start responding in HA. (I use events into Node Red flows to control Hue Bulbs). So there was a lag with a few in getting it hooked back up.
For another few (prob 5-6 out of 35), they kept showing Offline in the MS page. I canāt remember if these showed Unavailable in the HA Device page or not.
Oddly, if I went into the HA Device page, I could successfully Ping them. Scratching my head on that!
I could successfully (using HA Device Page) turn on/off the Indicator Light a few times (like 2-3) but then it just went unavailable and would not turn on/off the light nor ping anymore. No clue how it got a few uses as a Swan Song before death!
For the ones that went Offline (MS) or Unavailable (HA), I tried the Air Gap pull trick.
A quick pull (10 seconds off, then back in), did nothing.
A longer pull (5 minutes off, then back in), generally did work. It takes 2-3 minutes after re-engaging for it to show up as Online in MS. I think sometimes pressing buttons (Up/Down/Config) helped to accelerate the reconnect. But that might be placebo effect.
Early on in the process, I had two switches which didnāt come back online (thatās about where I went to bed). When I woke up, one was online and the other still offline. The Air Gap trick worked on that go-round.
I did reboot the whole Matter Server at some point, but I suspect it was not necessary that a longer Air Gap pull mightāve helped.
All-in-all, having good success here. Most are working without any extra effort. And the handful that need extra effort, pressing buttons seems to work for most. And Air Gap pulls (for 5 minutes) seem to be working for the remainder.
Having to do the update in Matter Server (MS) and not via Home Assistant (HA) Device wasnāt a complaint. Just info for others on how to do it Wasnāt immediately intuitive, but also glad to hear itās a known issue theyāre looking into. Definitely would be more obvious for folks in Home Assistant Device pages.
on the 1.0.0 firmware the switch was going into a state where the physical switch no longer responded, but the software commands worked.
Iām stuck in this exact situation currently. Switch has been great for the last month or so until today. Software (HomeAssistant or HomeKit bridge) works fine.
We only have one switch right now so would love to test the beta version.
@wpgraphix : If youāre using Home Assistant, and the switch is added as a device in there, I believe all you need to do is enable the Beta/Test-Net for the Matter Server, and probably reboot.
Go to Home Assistant Settings, then āAppsā, then āMatter Serverā. Then at the top of the web page, itās got a āConfigurationā tab (semi-hidden, not obvious). Scroll down a bit and enable both āUse the latest beta versionā and āEnable test-net DCL usageā. Then reboot.
Via Home Assistant devices, it wonāt offer the update (at least it didnāt for me). So go back through to SettingsāAppsāMatter Server. This time, pick the āOpen Web UIā button. If you just have one Switch/Node it should be pretty simple to find in that UI. Click on the Node, then click the āUpdateā button and it should offer the option to do the update.
Picture below for the Configuration Setting toggle switches:
Yup, just got that update done! Was missing the web ui step
After the update the light cycled and it still wouldnāt. However pulling the airgap and waiting a few, then pushing it back in and weāre golden.
Responding slightly faster to the clicks it seems (but probably placebo). Software controls remain completely fine but also seem a bit snappier (probably placebo). Wish I had my timer ready.
Iāve been running the beta version (1.4r3) for over a month now with no issues at all. Unless you have a problem in principle with beta software, you might want to give it a try.
The beta with the power fix was last November, and no comments on this thread for a month+ - so Iām surprised a new firmware version wasnāt pushed to everyone and was hoping asking might get it pushed out
Inovelli ( @EricM_Inovelli ) may want to comment on this. However from what I understand to push a new production version out means paying CSA for another certification run.
I believe the certification cost to be a non-trivial sum of money. If I were running Inovelli I would probably want to hold off until I was sure that my support people had captured all of the known issues in the current release and that engineering had implemented them and they have been tested in the field.
Inovelli is also working on a Matter 1.5 SDK release for the VTM35 and VTM36 which are probably sucking up most of their engineering time right now and since it impacts reported service effecting issues and again if it were my call I would probably want them fixed first.
One other comment, the latest beta release for the VTM30 was V1.0.4r3 (beta) - March 10, 2026.
As I already said, if you have HA the process to upgrade to a version via the test-net DCL is pretty simple. Iāve tested a bunch of Inovelliās beta releases. So far I have not had any reliability issues as a result.
You are spot on with your assessment. That being said we are internally testing 1.0.5 and will likely be releasing it very soon. So, it is pretty easy to install the 1.0.4r3 beta, but it might be worth waiting just a bit for 1.0.5. We will likely put 1.0.5 up on testnet and as long as there arenāt any major issues add it to the main dcl a week or two later.
Wasnāt immediately intuitive, but also glad to hear itās a known issue theyāre looking into. Definitely would be more obvious for folks in Home Assistant Device pages.
