Hi @philip, we have been working with the manufacturer to resolve this issue and we have a beta firmware you can test to see if it helps. It also has the enhancement suggested by @andrewk (and a few other small bug fixes). I will PM you with the info to update but if anyone else would like to test it please let me know.
1 Like
I would be happy to beta test again.
1 Like
I’ll PM you with the info once I have it all together.
I would like to test this too.
I also would be happy to test and have about 95 thread devices now (most inovelli) and can induce a traffic event pretty easily by restarting the matter server.
@EricM_Inovelli, do you keep a public list of bugs and feature enhancements tagged to future/planned releases? Would be great to have a place to know that some features are being worked on and roughly where in the sprints/stories they may be.
Also curious if the new updates to Matter/Thread help with firmwares having to be re-certified?
1 Like
It would be nice if we could specify the button delay with more granularity. Afaik the current implementation is a toggle with a 500ms delay, which can feel rather slow. I imagine this won’t be possible in the short term due to limitations of the matter standard, but I wanted to put it out there as I haven’t seen much discussion on it yet.
You can change it. 300ms is as low as it can go right now. It makes a noticeable difference. All of mine are set at 300.
I’ve been having a lot of problems with my White series switches not connecting to the thread border router. I’m using an Alexa show as the border router. Sometimes they don’t work at all for a day or two, and then with no changes, they start working again in Alexa. My switches are like 12 ft line of sight with no obstructions to my thread border router. My devices were working in Hubitat a couple weeks back, but they’ve never recovered after the first spat of connectivity problems.
What home automation system was used in the development and testing of the switches? The problem with Alexa is that it doesn’t offer first class support to troubleshoot issues.
How would I upgrade the firmware on my switches with Alexa?
After reading through this thread, it seems like 2.4Ghz WiFi could be interfering with the thread channels. How do I figure out what thread channel on the 2.4GHZ spectrum my switches are using?
I’m very tech savvy but I’ve been frustrated with the inability to troubleshoot and pinpoint the exact . My thread devices weren’t working last night before bed, but when I woke up they were working again. Been going on like this for a week or longer.
What kind of networking equipment do you have? Many people have reliability problems. If their Wi-Fi router is on the same channel that their thread board router is using. It’s not a one for one match up so for instance, my Apple thread board router uses channel 25, which is in the Wi-Fi channel 11 range so I had to set all my Wi-Fi access points to make sure they weren’t using channel 11 and my reliability problems disappeared
I would double check that you have ipv6 turned on in your router. I’ve seen conflicting information about whether this is necessary. I know that the thread network communicates internally through ipv6 and some people say it doesn’t have to be on, but after months of intermittent connection issues with my White switches (and other Matter over Thread devices), it was all resolved the moment I turned on ipv6 and restarted my modem. It’s like night and day.
You can check if ipv6 is on here: http://test-ipv6.com
I have an automation that notifies me every time a Matter over Thread device goes offline. It used to go off two to three times a day, if even for a few minutes. Now it never happens unless I initiate something myself (like a restart).
Hope this helps!
In order to troubleshoot, I would need to figure out what Thread channel my thread border router (Alexa) is using, else it’s just a guessing game.
Interesting, how would I find the IPv6 address my Inovelli switch if using? I have Ubiquity networking gear and can turn on IPv6. Another challenge is that it works sometimes and other times it doesn’t irregardless if IPv6 is on. I’m looking to understand how it’s working just fine for the first couple months.
In Home Assistant, you can see it there. But I don’t think you really need to know the ipv6 address. It’s just a matter of going to your router and making sure ipv6 is on. I assumed my Centurylink (US) router had it on by default, but it did not. After turning it on, I’ve had no connection issues at all for about 6 weeks now.
Yes you would. Some device apps like nanoleaf let you look at the thread network and it shows the channel.
Just cross posting here in case it’s a firmware bug. TL;DR my dimmers won’t actually turn on at a dim setting if they were turned off at a bright setting.
Just for you. 
Possibly . . . from a cost perspective (if I am thinking of the same updates as you). As far as delays waiting on the CSA, no, because all production updates have to go through the “paperwork” process which is what held us up with fw 1.0.5.
Edit: @hood.tongs-0i I have responded to you in the other thread.
1 Like
Has anybody tried use the White Dimmer with two matter controllers simultaneously?
I’ve noticed that the switches I connected to Google Home (in addition to Home Assistant) are reliably freezing/locking up - including not responding to physical paddle pressing. I need to pull the airgap to revive them. It happens every 1-2 days consistently. When I removed the switch from Google Home (so it’s only controlled by Home Assistant), problem goes away!
Yes. A few different configurations of dual-administration setups.
Apple Home and Home Assistant and SmartThings - work well together
Google Home + Anything else - seems to have more issues.
At one point, I was using Google Nest WiFi pro 6es + Apple TVs in a mixed thread border router environment. Lots of lock-ups and devices dropping off the thread network. Eventually, I removed all the Google nest border routers (switched to Unifi Wifi), and only use Apple border routers now - much more reliable.
2 Likes
Interesting, I haven’t tried all of these but at least the problems with Google Home seem to be common.
I currently have one Thread Border Router that is Google Home device and I also joined the Home Assistant SkyConnect dongle in Thread-only mode to HA onto the same Thread network (HA joined Google’s). I tried disabling SkyConnect and it didn’t make anything better. I’d try disabling the Google’s TBR but that doesn’t seem possible - other than reconfiguring Thread network and all devices from scratch or powering off the Google Home device.