@EricM_Inovelli - any update on the public release timing? Was waiting with bated breath last week! I’m excited to fix the flickering issue and implement energy tracking.
1 Like
Yes, sorry for the delay. We found a few last minute issues that we wanted to take care of. The engineer is just waiting on my approval to package the 1.1.5 update and we will release it this week. I am playing with the idea of releasing it to HA users first and then to Apple users next week, but I am not 100% decided on that yet. From a support perspective it is easier to do staged rollouts.
8 Likes
Staged is fine as long as HA is first 
2 Likes
That works for me! Thanks for the update.
As an Apple Home only user I’m all for letting the brave young men of HA go first. Old age and treachery always win over youth and exuberance. LOL As a retired software engineer I think it always makes sense to stage releases if at all possible.
5 Likes
Come on brother. You’re never a “retired” software engineer.
3 Likes
The testnet dcl has 1.1.3 on it. Perhaps update testnet to 1.1.5 - that’s accessible to the brave/foolish. It would certainly be “staged” 
1 Like
That is actually a good idea. I just entered 1.1.5 into testnet. Early next week I will add it to mainnet which should open it up to all Home Assistant users. Then, mid next week, I will get the compliance certificate signed which should open it up to Apple Home users. I believe that a while after that SmartThings will offer it to their users.
I have 8 running 1.1.5 with no surprises. This is a very diverse thread network. Is there anything in particular to watch out for or that you’re interested in?
I am not sure that I remember this correctly, but:
1.0.0/1.0.5 → 1.1.3 seemed to silently switch the device from On/Off mode to Dimmer mode.
1.0.0/1.0.5/1.1.3 → 1.1.5 all seemed to correctly preserve On/Off/Dimmer mode. I did not have to go back and manually reset some 1.1.5 switches to On/Off mode.
1 Like
I’d love to help test, I am on HomeAssisant (and HomeKit) and have some flickering issues I’d like to see if it resolves
As said above the new VTM31-SN software (1.1.5) is planned to be released to HA users this coming week.
You can either wait till later in the week or set your HA matter configuration to download from the testnet DCL and you will get the same software a little earlier.
I know this might be off topic, but Apple Home really wants to use Adaptive Lighting when it sees the RGB “light” as though its a room light. I find this a bit comical.
Most of the changes have been floating around in betas for a few months so I don’t think there will be any major surprises. As you mentioned there are some things to watch out for like entities that don’t work anymore or settings that get changed from what they were. I recommend everyone read over this article before updating. I also just updated the main post with this link.
VTM31-SN - Firmware (1.1.0+) Update Advisory | Inovelli Help Center
1 Like
Looks like the 1.1.5 update is now available in Home Assistant.
1 Like
Not seeing it here. This will be my first firmware update via HA, however. So maybe I’m missing something.
It can take up to 24 hrs to show up depending on where HA is in its update notification cycle. When it does show up my recommendation is to:
- Start with reviewing @EricM_Inovelli notes further up this topic
- Check for no connection errors in the Matter log within the last 30 mins.
- If good upgrade 1 switch. The process is the same as upgrading anything else in HA.
- If the upgrade fails with “could not process the update” just wait 5 mins and try it again.
When that update is done. Check the config in HA in case anything got defaulted. if it was then follow @EricM_Inovelli’s guidance and then fix any issues. - Wait 5 mins
- Do not attempt to upgrade a second switch while the first one is still upgrading.
- Rinse and Repeat!
Enjoy!
I keep getting "“Target node did not process the update file” error when trying to update from my home assistant. I am using zbt-2 as thread border router.
I saw this occasionally (maybe 3 times on the 20+ switches I’ve upgraded to 1.1.5). Just let the HA upgrade attempt completely timeout (takes about 5 mins) and then try again on the same switch.
Just updated to 1.1.5 yesterday in HA and I’m getting flicker on Hue bulbs, but only on certain brightness levels (sadly, including 100%). Could the update have disabled smart bulb mode?
If you are upgrading from 1.0.5 and earlier it’s more than likely that smart bulb mode has been turned off since the mode-select that controls it has moved. I believe @EricM_Inovelli covered this in the document referred to further up the thread.
You will need to restart HA, remove the (now unused) clusters per his instructions and re-program the switch as you need it (including turning smart bulb mode back on).
1 Like