Yes, there is local Tuya and Tuya local.
If anyone needs more Tuya in their lives, thereās also Xtend Tuya.
1 Like
The one I posted is also localtuya, it is just another maintainer.
fixed for me now since the latest LocalTuya update
1 Like
Ah man, thatās a bummer. Iād been following the PR for a couple months thinking I could use the S3 addon with Backblazeā¦ didnāt realize it was AWS only.
4 Likes
Has anyone else lost all functionality (including seeing the tab) of the custom:tabbed-card after the upgrade to 2025.5? It is as if they no longer exist in my code.
check the Issues in that repo, the card is borked for now, because of the HA changes in the frontend,
Ive posted a replacement alternative using only core elements which imho is at least just as nice using the exact same screen estate
1 Like
I just wonder if this was mentioned as a change in this release:
All my thermometer entities changed the display precision from one decimal place to two decimal places, e.g.
- before: 21.3
- now: 21.34
Of course I can change this back but is this intended behavior?
Anyone have any idea why my disk usage went from around 160GB to ~32GB after this update?
That is one drastic decrease!!!
Holy smokes, the Network Discovery feature is fantastic!
This would have been so helpful about a month ago when I needed help debugging mDNS for Thread 
1 Like
Wait you were running python 3.12? I would assume that that has been broken by now
If people find devices using their network tools that could be auto discovered by Home Assistant, feel free to send me a message and happy to help! With this info we could automatically detect devices when people set up Home Assistant (or we could detect devices people didnāt know they could connect yet)!
3 Likes
Issue #25381 created, let me know if i can provide anymore info. Thank you
1 Like
Iām having an issue with my cameras which is unrelated to the 2025.5 update, however I noticed something changed.
Previously when Iād click a camera entity it would go straight into playing the feed, now it requires I press play. Is that an intentional change or is it related to my other issue?
This update screwed all my dashboards.
As friendly_name now contains device_name !!
So my dashboard went from:
to:
How to fix it???
Also see:
2 Likes
Iām using the Python 3.13 Backport from GitHub - pascallj/python3.13-backport: Python 3.13 backport for Debian 12 bookworm
Thanks to Pascal for providing it.
1 Like
Hello, great update, thank you!
A minor niggle:
After scanning the QR code of a Long Range capable device, you will get the option to either add it to the existing mesh network or connect it directly using Long Range. Both have pros and cons, mesh networking is recommended for most devices, but if you have a device that needs to be placed far away, Long Range might be the better option.
This is wonderful, however this quote directly contradicts the ordering of the mesh/LR selection. (Long range being ahead of Mesh)
Also, in the dialog, it would be great to have the same context/information provided as the quote, so when one does actually go through the process, they have some clue which mode is more appropriate for their particular use.
question: can modes be easily switched later on?
if so, it would also be nice to say that; ādonāt worry you can always change the mode laterā type blurb.
or if not, maybe link to the documentation page.
also, why no document page linked on dialog?
Hopefully some helpful feedback.
Ouch, I have a dashboard showing nine Traffic Cameras. Nine clicks to get them playing? I havenāt upgraded yet, but I also hope there is an auto play setting.
Anyone have any idea why my disk usage went from around 160GB to ~32GB after this update?
That is one drastic decrease!!!
Well, I figured out where the space was. It was in the overlay2 folder. I use HAOS in a proxmox VM. In my backup from a few days ago, the overlay2 folder was 140GB!!!
I have no idea why it hadnāt been cleaning or purging old layers with any other update, but this one triggered it. I donāt see anything in the release notes regarding itā¦
To be clear, the greyed filler images are unrelated to the update, but I was getting a feed as soon as I clicked into each camera. Maybe itās related to my other issue. There is an option on the camera entity to preload the feed in the background, but it doesnāt make any difference for me.
If you update and all is good, let me know so I can rule out the update?