White Series Dimmer Switch Firmware Changelog | VTM31-SN

I think the issue you are seeing is that 1.1.5 is not released on Apple Home at this point so It won’t recognize switches on that version properly. I think once the software is released on Apple Home you should be fine. I would not remove them from Apple Home since you may not be able to re-add them at this point.

How many raspis of what type in the cluster? My suspicion (nothing more than that) is that the Inovelli devices (which have a lot of clusters to migrate) are probably timing out since HA is saturated with that volume of devices.

I have 22 dimmers in Apple HomeKit. In fact, 19 of them I added to HomeKit first and then paired them to HA. Anyway, my dimmers are recognized and working in HomeKit and I didn’t do anything to force them. Even the three I added to HA first and then paired to HomeKit are working. I upgraded all my dimmers to 1.1.5 and I updated to the matter.js beta server.

4 pi5 in a swarm with 16gb each and nvme drives. They are quick. Matter server runs outside ha instance as separate stack/service and has pretty low cpu saturation running. HA isn’t even involved in the process during the migration best I can tell.

Python matter server is quick adding, startup and interview.

Thanks!

My other question remains…
Where can I find a list of the current entities/configuration items (for ZHA and the v1.1.5 firmware), and what their values mean?

I’m looking for the equivalent documentation for the White Series Dimmer Switch to this page for the Blue Series mmWave switch: Blue Series mmWave Presence Dimmer Switch • Parameters | Inovelli Help Center

for others migrating to new matter.js. My issue seems to be my file system being on a nas. The new matter server creates 10s of thousands of folders. I got through the initial phase of importing nodes and then when it started migrating nodes before starting server, it would fail pretty quick. I moved the storage to local on the pi and what too 45 min for initial phase took 5 min and then the migration worked and everything came up. looking in to if there are permission / params on NFS and CIFS connections (have and tried both) to the NAS.

Anyone else with Google Home exclusively get the 1.1.5 update?

I’ve been tinkering with 1.1.3 and 1.1.5 for a while now. I’d urge people to take it gently when doing updates. Thread is a relatively slow network. Pushing firmware over it can be a bit taxing. Having devices in a mesh network suddenly reboot and destabilize the mesh at the same time as another bulk transfer is in progress - not a good scenario.

I recommend:

  • wait a couple of minutes after a device comes back online for the mesh to stabilize before starting the next one
  • if there’s any hiccups, STOP immediately and wait until things stabilize.
  • if you have apple thread devices (eg: homepods, appletv) be sure to be running the latest OS releases. Older releases interfered with firmware updates. Apparently it’s fixed in 18.x, but I never saw that. It is definitely fixed in 26.2+.
2 Likes

After updating to 1.1.5 in Home Assistant one of my switches started having a flickering light. It’s installed with no neutral but I do have a bypass installed at the load. I had no issues with flickering on this light on 1.0.5 so I’m not sure what could have changed. I’ve checked all the settings and made sure it’s correct, as well as done a factory reset afterwards to ensure nothing weird was being saved in the config.

can confirm this.. LOL. I got upgrade happy and tried to update 5 at a time, no good.. I found it safe to start one, wait a min or two and start another. no more than 3 at a time until they were back online and stable. I had to reboot my matter/thread HA add-ons a few times due to things “hanging up”..

1 Like

Can you share some more info? Does it happen when at multiple levels? 10%, 20%, etc? It happened even after the factory reset but before adding it back to the network?

Just in case - maybe the updated affected this Switch Mode settings. Some bulbs require Trailing Edge dimming, others require Leading Edge: dimming. There is really no set way of figuring out which is needed, so switch between the two and see what happens.

It happens still after the factory reset before adding to network.

I’ve tried it on all dimming modes as well as on off switch. It actually doesn’t seem to flicker at very low levels such as 10-20% but starts increasing the flicker as I move up to 100%.

In on/off mode it always flickers, same as dimming modes (trailing/leading) 100%

The only ohter suggestion I can think of - you said its happening with one switch - is it possible its the bulbs on that particular switch. You might try swapping the bulbs from a “working” switch with the ones you have on that switch to confirm if its a bulb issue or a switch issue. Or if its a particular brand / model of bulb, you might want to indicate that to Inovelli so they can try and test against that particular brand / model of light (assuming its readily purchasable). Also, I’ve found that if a switch is controlling multiple bulbs and one bulb is going bad, it can affect them all - so if you have a multi-bulb arrangement, try screwing out one out at a time and see if you isolate a bad bulb.

1 Like

Thanks for the suggestion. I did try bulbs from different manufacturers but had the same result. They were philips bulbs and I also tried some GE bulbs. All 8W, 400 lumen.

I did some playing around and set the dimmer brightness to 55% which is about the highest I can go before flickering begins. I turned off the light and back on and the bulbs now are actually at their max brightness but home assistant (and the switch LED bar) only show it at 55% as I would expect but it’s not flickering now.
Currently set to trailing edge dimmer mode.
I have no idea how now the bulbs are at their max (visually from what I know they can output) but the switch reports 55%.

I’m now sort of in a problem solved but something is still definitely weird state.

I was finally able to update all (but one, because its network signal is weak) 25 of my switches. The new options in Home Assistant are very useful! And the dimming profile seems more elegant (it seems like it does some real time calibration depending on the load, which I like)

I was also hoping the newer firmware would fix the intermittent lockup issues I’ve been having with some switches…

Unfortunately it did not :confused: I’m still having an issue where a handful of switches will completely lock up:

  • “No Response” in Apple Home/Home Assistant
  • No load control via paddles
  • Load stays set at same level it was at when it locked up

The only way to fix the issue is to pull the air gap and push it back in. I don’t mind it as much as my finger nails do…

@EricM_Inovelli , any thoughts on this? Are there any diagnostics I can pull after restarting them?

Thank you for your support!

I had this issue a bit, too, but moving to the matter.js beta solved that and many other problems for me I think the python server was doing something that caused my switches to lock up, especially if there was any kind of mesh disruption. Haven’t had a locked switch in more than a month now, and I’ve been running the inovelli 1.1.3 beta firmware for a couple months now.

1 Like

Last week I got an email saying that the latest firmware for the White Series Dimmer was going to be released for Apple Home users. Has anyone actually gotten the firmware update through Apple Home or has it not been actually released yet?

Here’s a home assistant script that will update them one by one for you:

alias: Sequential Matter Device Updates
sequence:
  - repeat:
      for_each: >
        {# Get all Matter entities, filter for update entities that are 'on' #}
        {{ integration_entities('matter') 
           | select('match', 'update\.') 
           | select('is_state', 'on') 
           | list }}
      sequence:
        - action: update.install
          target:
            entity_id: "{{ repeat.item }}"
        - alias: Wait for update to finish
          wait_template: "{{ is_state(repeat.item, 'off') }}"
          timeout: "00:20:00"
          continue_on_timeout: true
        - delay: "00:00:10"
mode: single
icon: mdi:cellphone-arrow-down
description: ""

3 Likes

That will never work for me. I don’t use Home Assistant. I am talking about the firmware update for those of us that only use Apple Home. We got an email last week that it would be rolling out for Apple Home users and I’ve not seen any more info. What I am asking is if anyone that is NOT using Home Assistant if they have gotten any firmware updates yet.