#Matter device firmware not updating?
1 messages · Page 1 of 1 (latest)
Matter doesn't mandate that devices use the "standard" OTA update mechanism, so for some vendors the only way to update firmware is via the vendor app.
Is your problem that updates aren't showing up in HA, or that updates are showing up in HA, but are failing when you try to do the update?
i'm not sure what firmware updates you would need for wiz bulbs anyways
i'm fairly certain the one and only firmware update they ever recieved was the one to retrofit Matter functionality into the bulbs in the first place
Wiz bulbs will only update through their app (update notifications are stored on their secure MQTT server).
It turns out this is true. Other Tuya devices are not getting the updates in HA.
I have a sensor (4 of them) that is firmware version 7ish when you buy it but is up to 13 currently. My sensors are all over the place but are matter direct devices I could pull back to Tuya/Smartlife to update.
So far no updates for any devices have pushed via HA.
WIZLEDstrips sepecifically seem to have different firmware on my network.
Only a very limited amount of devices actually support OTA updates with Matter. At time of writing only Third Reality, Nanoleaf, Eve and Innovelli that I'm aware of
I read that there is an issue, when you have Apple Thread Border Routers, your devices are paired to HA only and want to update them via HA OTA. But this is seemingly not your problem.
I've seen Matter OTA functionality from these other vendors:
Leedarson, Aqara, Kasa,
But it's not required to go through the Matter OTA service for certification so don't expect everyone to be on board.
The wiz V2 app updated my A21 bulbs and striplights from 1.29 to 1.33. I did read that this was a matter specific upgrade as 1.29 was the first version to handle Matter certs in the wiz app.
HA still shows all wiz devices at firmware 1.0.
You will have to complain to Wiz about that. Tell them to just publish the correct firmware version info in the BasicInformation cluster. So many ESP32 based products just completely mess that up, it makes you wonder if there's an error in the Espressif framework they all use.
Two days now matter is dropping all devices randomly and ping is fine but won’t take an IP or function. Wiz and others direct Matter integration failures!!
I didnt understand anything about that. Can you try to describe it a bit better ?
my wiz and other Matter devices are not responding. I have HA on Docker and Matter (Beta) on docker. After yesterday’s update nothing is behaving via matter integration.
All matter commissioned devices are not responsive after update. Current state!!! Docker … HA- 2024.10.0 Matter 3.7.0
In the past few days several posts about matter devices dropping and won’t recommission. I assume my issue is the same. This was a sudden new behavior just as others have stated.
The rabbit hole of go read and try 100 things seemed futile for others as well. Things I was able to reconnect did in fact disconnect again.
Hopping there is a real answer and a real fix coming.
OK here's a real answer then. You are running an unsupported configuration (docker) and then run into issues. Something we warn about when we state that its not a supported configuration. The best/only thing to do here is setup a Home Assistant OS based install somewhere. Maybe as a VM, maybe on a spare pi or whatever. Then if you still run into issues with that setup, I'll gladly help you out trying to figure out what is wrong.
That’s finally a real answer but we both know people with the OS are having the same issue and it arrived at the same time.
I appreciate the help you do offer and understand that you don’t want to support Docker.
The right thing for me to do is to peel back to a HA and matter (beta) docker that worked.
Jumping over to HA OS when I know others have the same problem seems like a bad idea.
Or we just wait for an update that fixes something (whatever the real issue is) for all of us.
I haven’t seen a resolution for folks on HA OS. That’s okay… I get it. I was asking why it suddenly broke and verifying it wasn’t a me thing that magically changed that day.
There is no issue that I'm aware of so I still have no clue what you're talking about.
The only real/confirmed issue we have is devices going unavailable when multiple (non-OTBR) Border routers are involved. That one is under investigation. That your issue maybe looks a bit similar does not mean it is the same issue.
If you want support, start by following the documentation what should work and what not.
So flat network, be careful with enterprise class networking stuff like Unifi (make sure to set it up more like consumer grade network). Use Home Assistant OS as it has all the OS-level patches required for Matter (and Thread) to work correctly and then go from there. If you run into issues, start describing exactly what it is you tried, what failed etc.
Shouting, "we all have issues and you should patch it now" is not going to get you anywhere. Especially if there are no known big issues. It works fine for 10.000's of people.
I understand. I didn’t actually say what you put in quotes. I meant no disrespect.
This issue was sudden and looking at my updates the timing matches the matter server 6.6.0 when I updated. On 10/3 it was actually an HA update. There were two HA updates that week but were days before and after the issue/(matter update). I should have looked at this timing more closely.
Thanks for your advice.
OK, all good.
I think that is just a coincidence then. Like I said, the only way to troubleshoot this is by looking at it from a known working situation, which is not docker (as that brings way to many other variables into play).