FYI so I updated to 2.4.2.119 late last night, this morning all of my matter devices showed the were still on and would not respond to any commands. Did a full shutdown and reboot on the hub but still no control, strangely all matter devices show they are online. Reset the power on the matter devices and still no control so I rolled back to 2.4.1.177 and the matter devices are again working.
Were they working last night?
I performed the update after all the rules had run to turn them off, they turned on in the morning but did not turn off by rule so I tried to turn them off and they would not respond.
I did a full shutdown of both my hubs and off and on the power to all the matter bulbs and they still would not respond so I rolled back the update and they worked again and they have followed the rules tonight.
Can you pm me your hub id?, I'd like to look at your engineering logs.
Sent
I have the same issue. My matter devices from ATV stopped working with 2.4.2. They are inovelli switches that have 2 children. One is for the load and they stopped working. The other child is for the Led on the switch. Funnel thing is that the do work on 2.4.2
I also did reboots etc. I deleted the devices and drivers rebooted. Added the drivers again, added the devices again and still no response until I rolled back the release
ATV?, what's that
Provision in Apple TV
Is someone working on this or should I open a ticket
Are these thread devices?, or wifi...
Also what platform version are you on now?
These are thread devices provisioned in Apple TV. My current version in 2.3.9.201. The devices are all Inovelli White series switches and use the Inovelli supplied device drivers. When added to Hubitat they create a device with two children. One called the load, is for the switch and the other controls the LED of the switch. The load doesn't work but the LED child does.
unfortunately I'm not familiar with the switch or the driver, but this sounds like the subscription for for the load isn't being renewed as it should on startup.
Is there an initialize command in the driver?, if so does it restore functionality?
Hi, same thing here. My Hubitat stopped working after doing an update. Can you please help? I can still see the switches in the dashboard but they are unresponsive. Thank you
I will need much more info, the running platform version that exhibits the issue, the platform version that does not exhibit this issue, and the driver/device involved.
There is an initialize but does nothing
So I don't know if this will apply to either of you guys but I have Matter devices brought into Hubitat via Hubitat directly and through other methods. Such as I have an Aqara hub with several devices and I bring them into HE through the Aqara Hub's matter bridge function. I haven't had an issue necessarily when updating HE but I have had issues where the Aqara hub has firmware updates then the devices brought in through matter via that hub would not work. I had to go into the hub parent device settings and click configure. I don't know if you might be experiencing a variation of this. So if there is a configure button and you haven't tried it then give it a shot and it might help.
Can you enable debug logging in the driver, then click initialize?
If you don't see any responses, then the initialize command in the driver is not subscribing to the device, this would be an issue with the driver.
The initialize is called upon hub start up and for matter devices must include all the device subscriptions...
