Closed mwhdc closed 4 months ago
I just upgraded to 2024.3 and I'm seeing the same problem noted above.
same issue here when upgrading to 2024.3
I've observed the same issue since upgrading to 2024.3 a couple hours ago. However, IMHO the logs shared above by @mwhdc might not be related to the root cause. This is because I saw these log messages on 2024.2.5 yesterday as well, as documented in this post, when these broken entity issues were not present. However, it is possible that something in the new HA release combined with an existing issue in the integration to cause this.
I've observed the same issue since upgrading to 2024.3 a couple hours ago. However, IMHO the logs shared above by @mwhdc might not be related to the root cause. This is because I saw these log messages on 2024.2.5 yesterday as well, as documented in this post, when these broken entity issues were not present. However, it is possible that something in the new HA release combined with an existing issue in the integration to cause this.
Interesting, I don't usually run loglevel debug on the Hubitat components so I wouldn't have seen those errors under 2024.2. I didn't see any other red flags in the 2024.3 log but I would be happy to send the whole thing to anyone working on a fix. I just posted an excerpt above for brevity and privacy.
The messages in the original issue are normal (although they'll be improved in the next release). All the <entity unknown.unknown=unknown>
s are happening because the log messages were being emitted before the entities were fully initialized. The "Adding unknown entity for x" messages are fine, but were just poor wording on my part. A better string would have been "Adding generic sensor for x" (which is what's actually happening there).
I'm seeing two issues at the moment:
Working on it 😄
This should be fixed in v0.9.24.
This should be fixed in v0.9.24.
As always, thank you for the quick fix. Your amazing
Yes, thank you! The fix works. I did have to create template switches to replace the light --> switch functionality, but that's not a big deal. Appreciate the quick turn-around.
Looking good! Thanks for the insights and quick fixes. Will close this issue in the morning if there's no further activity.
First noticed this behavior with Core 2024.3.0b0 and waited until imminent 2024.3.0 release to make sure there wasn't a known regression in Core. Normal operation under 2024.2.5, including after reverting.
Issue: Lights and switches that are rendered in the UI as toggles through 2024.2.5 appear as off/on lightning bolts in 2024.3.0b0 and later. Sensors are not populated with values or attributes. Other domains may also be affected. (Entities not provided by the Hubitat integration continue to function normally.)
Environment: Hubitat is C7 hardware running 2.3.8.122. HA is managed OS in Proxmox on Intel NUC. Latest Hubitat integration from HACS.
Debug snippets: