Interesting. That’s a different error than I got.
I rolled back to 2023.6 without issue.
Interesting. That’s a different error than I got.
I rolled back to 2023.6 without issue.
The matter updates, although theoretically good, seem to not be working properly for me. Not the biggest deal, didn’t have access before anyway, but I cannot ping matter devices, it fails every time even if I can control the device no problem, and I also cannot share the device. It either fails, or loads indefinitely. Rest of the update from what I’ve tried seems pretty great though.
Just kidding. Matter server update fixed that (sorta. Some devices don’t give me the option to share devices anymore, but the ones that do have that option work)
I was hoping February was raspberry pi 5 month. Oh well.
tl;dr yes
the proximity entity itself (proximity.*
) is now deprecated, but superseded by sensor entities. Further the configuration is now available via the UI, no YAML configuration needed anymore.
Thanks @balloob for adding the ability to export history data to CSV!!! I have been wanting that for years. HUGE new feature.
Do you think Nabu Casa can convince many more Zigbee device manufacturers to provide their Zigbee device OTA firmware images publicly to third-party Zigbee gateway applications like Home Assistent?
If not then users need to manually upload firmware images collected by unofficial means:
Hoping for a larger open-letter type campaign about making both Zigbee and Z-Wave OTA device firmware available to all!
That’s a problem with what you’re using. Change to the Home Assistant theme and repeat the authentication steps and the integration will work.
Anyone has problems with the update? I can trigger the install. It seems to be installed. But the ui resets and ask me if it should install the update…
Loving the added icons for all services and service parameters! Must have been quite some work, but it’s a great result.
Dear God, please this! Between my wife and father-in-law, I really need them signed in indefinitely.
Same issue with Tuya as others have reported, setup produces an “Invalid Hex Color” error that can’t be dismissed. Only fix for me was to restore HA entirely from a backup.
Thank you for the tip!! That worked!
It’s been said that if the app is running in the background, the access token won’t expire.
Don’t you use a long lived access token for AMP. I thought that was part of the setup for this custom integration. If so, I believe you won’t have a problem. Or am I misunderstanding your question?
refresh the page or open a new window… no need to restart. Also, according to another user, it’s because of your theme. Revert to the default HA theme and you should be good to go
Any communication between HA and Alexa will reauth. Even if you restart HA.
If it is sending location data it is using the token. So they won’t be logged out.
Tuya integration not display qrcode
AND
i created 1 prox sensor with 4 personas and it made 5 different prox sensors with same name
I can inform you that even P115 , with Current-Power/Todays-Total-kWh/ and Total-kWh , is supported.
( I had 7 Plugs and 3 light-strips popping up)( PS: Sorry, i had to Ignore all, after all i was only “testing” )
However , i’ve still havent found support anywhere for ( local-polling ) with Tapo (hub) H200, + T100( motion-sensor) +T310(temp-sensor), outstanding devices which communicate over 866MHz.
It’s very high on my wish-list