Same question here except for Google Home users
During our finalization of the compliance request we discovered an issue that needed to be resolved with the standards alliance. They are currently helping us resolve it right now and hopefully it will be done in the next couple of days. This does mean that we will release a firmware 1.1.5r2 to all users and we might fix a minor bug in this release at the same time. I know the process is slow and I wish we could speed things up, but not rushing helps us reduce the risk of making a mistake. I apologize that the email was sent out early, but everything in it still applies it is just taking a little longer than what we thought.
@thekiefs at this time we are not releasing the firmware broadly to Google Home users. The main reason is that Google Home does not provide users a way to choose which devices get updated and when. This could result in middle of the night updates, updates while on vacation, etc. Since the update can unintentionally change settings, we decided to push the update to Google Home users upon request. PM me if you would like to have this option and I will gladly help you out.
1 Like
Thank you for the update. I definitely appreciate the update and the time you need to ensure the compliance. Iâve been very happy with both the quality of your products as well as the measured approach to issues such as this. Looking forward to the firmware update when itâs ready.
This PR is now available as part of HA 2026.3.
After installing, you the old entities will show as unavailable in Home Assistant and can safely be deleted. You can delete all of them at once from the Entities tab in HA with proper filtering and mult-select.
This most recent update seems to disable the functionality of being able to set the led intensity (on) to 0 to disable the led entirely. I use this functionality to indicate when my motion lights automation which controls that dimmer is enabled (led is dim when light is off and bright when light is on) and disabled (led is turned off entirely)
Now setting the led intensity(on) to 0 seems to have zero effect
Now that I think about it, would it be too much to ask for to have an LED effect that just disables all LEDs? That would make my life a bit easier trying to manage my automations
Using LED on intensity (Load Control) did turn it off, but the Home Assistant update disabled it. LED Intensity(on) does indeed do nothing on a value of 0.
@sebastianrasor are you referring to the firmware update or matter? I am able to change it. You do need to ignore the crossed out entities as they need to be removed and no longer work:
@sebastianrasor we actually do have an âoffâ notification on our other products. I will request it be added to the white series. It does exactly as you describe.
I am referring to the selector underneath the one you circled: âLED Intensity(on)â. Setting this to 0 has no effect.
The prior firmware used a Matter custom cluster to implement this feature - however, Matter Custom Clusters are poorly supported (only Home Assistant supports them). The new firmware now uses a more âMatter standardâ feature referred to a âMode Selectâ which is supported on multiple platforms. Thatâs why you know see these drop-down menus with the available settings for the LED intensity when the device is Off and when it is On. So, with the new firmware, you use these âLED Intensity(off)â and âLED Intensity (on)â Mode Select settings (circled in blue in the post above) to achieve the result you are looking for. After a firmware update, Home Assistant doesnât yet know to drop / disable entities created for the prior firmware - you need to reboot home assistant, and those numeric inputs you previously used will be greyed-out (âNot Providedâ status) after which they can be deleted.
Ok. The âLED Intensity(on)â mode selector still has no effect when itâs set to 0.
@sebastianrasor I did confirm that this is a bug (LED Intensity (on) in 1.1.5 and will be fixed. Do you remember which version you upgraded from in which it worked?
I do not sadly. I think I had already upgraded the switch firmwares to 1.1.5 and was still using the number input just fine, it seems this has only happened after upgrading to home assistant 2026.3 but I canât say for sure thatâs a causal relationship and not just a timing coincidence (I only went down the path of updating my automations to use the new selects after upgrading to home assistant 2026.3)
I have been able to update most of my switches. One will not update. Matter server log shows that the switch receives the update file and then just stops processing it. I have tried a factory reset. Logs below
INFO [matter_server.server.device_controller] <Node:21> Software update found: 1.1.5 (115) from UpdateSource.MAIN_NET_DCL, current 1.0.5 (105)).
2026-03-06 14:49:41.163 (MainThread) INFO [matter_server.server.device_controller] <Node:21> Update to software version 115
2026-03-06 14:49:41.441 (MainThread) INFO [matter_server.server.device_controller] <Node:21> Software update found: 1.1.5 (115) from UpdateSource.MAIN_NET_DCL, current 1.0.5 (105)).
2026-03-06 14:49:41.443 (MainThread) INFO [matter_server.server.device_controller] <Node:21> Downloading update from 'https://files.inovelli.com/firmware/VTM31-SN/Production/1.1.5/VTM31-SN_V115.ota'
2026-03-06 14:49:42.045 (MainThread) INFO [matter_server.server.ota.provider] Update file 'VTM31-SN_V115.ota' downloaded to '/config/updates/21'
2026-03-06 14:49:42.048 (MainThread) INFO [matter_server.server.device_controller] <Node:21> Starting update using OTA Provider.
2026-03-06 14:49:42.051 (MainThread) INFO [matter_server.server.ota.provider] Starting OTA Provider
2026-03-06 14:49:42.054 (MainThread) INFO [matter_server.server.ota.provider] Commission and initialize OTA Provider
2026-03-06 14:49:42.817 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2026-03-06 14:49:44.423 (Dummy-2) INFO [chip.ChipDeviceCtrl] Commissioning complete
2026-03-06 14:49:44.431 (MainThread) INFO [matter_server.server.ota.provider] OTA Provider App commissioned with node id 990021.
2026-03-06 14:49:44.786 (MainThread) INFO [matter_server.server.ota.provider] Waiting for target node update state change
2026-03-06 14:49:44.877 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kIdle: 1> to <UpdateStateEnum.kQuerying: 2>
2026-03-06 14:49:53.799 (MainThread) INFO [matter_server.server.ota.provider] Update state changed from <UpdateStateEnum.kQuerying: 2> to <UpdateStateEnum.kIdle: 1>
2026-03-06 14:49:53.800 (MainThread) INFO [matter_server.server.ota.provider] Cleaning up OTA provider
2026-03-06 14:49:53.800 (MainThread) INFO [matter_server.server.ota.provider] Terminating OTA Provider
2026-03-06 14:49:53.849 (MainThread) ERROR [matter_server.server.client_handler] [281472752426144] Error while handling: update_node (node 21): Target node did not process the update file
```
Hey folks. If we previously installed the 1.1.0 beta manually, what are the steps to remove the beta and get back on the production installation?
FWIW, this works fine for me.
I believe you can just delete the json file in your updates folder and restart the matter server.
Have there been any other reports of this upgrade causing Thread Network instability? Ever since upgrading from 1.0.5 to 1.1.5 for my 33 dimmer switches my Thread has been so unstable. Itâs constantly going offline and coming back or devices will just drop for a few hours then come back again. My Thread network was perfectly stable for a year before I did this upgrade. No matter what I do I canât get my network to be stable for more than 24 hours. Its to the point everyone in my house is bitching at me asking why the lights wonât work and why they are always showing unavailable.
I have ordered a CM5 Lite with 8GB memory to upgrade my HA Yellow CM4 Lite with 2GB of memory hoping this will help. It will be arriving on Wednesday. That said; everything was running without any issues at all prior to the 1.1.5 upgrade so it seems to be clearly linked to that upgrade.
That has certainly worked for me.