We are talking companion app, i.e. options allowed in the companion app.
Thanks for the explanation. Guess I will need to play with my own local dns then so I can fool the browser to think it goes through my external domain. Before I slammed the door and removed my reverse proxy, the hairpin feature in my router did the job. Need to get creative then. It is mainly Safari or HA app I want it to work in. And long term it will be some voiceboxes I will use. Components ordered. I only want to use voice in browser for playing with voice features. For daily use it is rather pointless to talk to a browser when you can click on an icon much faster 
2 Likes
Just upgraded and my LocalTuya no longer works:
Logger: homeassistant.components.number
Source: components/number/__init__.py:232
Integration: Number (documentation, issues)
First occurred: 6:45:19 PM (1 occurrences)
Last logged: 6:45:19 PM
custom_components.localtuya.number::LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
I will be downgrading for now.
Any advice?
1 Like
3 Likes
Bluetooth was already not working very well since last update, now Airthings BLE is not working at all
You can equally question why the release wasnāt pulled after discovery of the bug to prevent people installing it while the bug was fixed.
3 Likes
Just a heads up.
2023.5.1 is now available.
2 Likes
Hi all
Congratulations to all the HA Team on the voice update. You guys have done a amazing job, I take my hat of to you.
I love all the old phones, esp devices and it is a lot of fun. The only thing is they dont fit in my back pocket. What I do have is a mobile phone. I am not sure if this has already been said but it is a bit of a no brainier. We have the HA app on the mobile phone and our phone has a speaker and a microphone. Would it be possible to add a button to a dashboard where we can just talk to the phone and control HA with the voice. Very similar to the M5 ESP device shown in the release video on YouTube.
Anyway keep up all the good work.
Blacky 
3 Likes
I just upgraded from 2023.4.6 (after rolling back from 5.0) to 2023.5.1, and all Alexa-exposed entities transferred properly. Thanks so much for the quick update!!
6 Likes
Hi all
For once i am happy that no matter what i do it just does not install the updateā¦
Iām sorry if this rubs anyone the wrong way but I give zero f*'s about having a conversation with HA if I canāt even do a proper backup of the energy dashboard and database.
Priorities should be set on the fundamentals first. Talking to a home automation system about how itās feeling is a gimmick on par with telling Alexa to the fire photon torpedos.
12 Likes
I have energy data from the day the energy dashboard was released. And I have moved system hardware once and recovered from a non-optimal beta OS update once during that time.
Iām assuming you have created a post for the issues your system is having?
Not sure whether this is something on my installation or a larger issue, but since upgrading to 2023.5, new updates fail:
New zwave-js-ui:
23-05-04 21:24:15 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install ghcr.io/hassio-addons/zwave-js-ui/amd64:1.12.0: 500 Server Error for http+docker://localhost/v1.42/auth: Internal Server Error ("Get "https://ghcr.io/v2/": denied: denied")
And new core:
23-05-04 21:26:26 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2023.5.1: 500 Server Error for http+docker://localhost/v1.42/auth: Internal Server Error ("Get "https://ghcr.io/v2/": denied: denied")
Any idea what might be going on? This is on a supervised installation that has been working fine for 3+ years and is kept in pretty good overall shapeā¦
Yes I have.
Up until about a week ago I had two years of energy dashboard stats. It too survived moving from one VM to another about a year ago. Come to last week a hardware issues caused corruption, I thought to myself āno problem, Iāll just use the day old backupā except it didnāt include any of the database. Imagine my surprise when using a function called ābackupā with the full backup bullet checked didnāt actually back up everything.
ok, replying to myself in case this helps someone in the future: my HA installation contained a ghcr.io registry entry for private containers, and the token for that registry had expired, causing all Github docker registry pulls to fail, including HA updates. Removin the registry entry (Add Ons / Add On Store / ā¦ menu on upper right / Registries) solved, the issue.
1 Like
Upgraded from 2023.4.6 to 2023.5.1. Held off from the update due to the Google/Amazon device problems that got solved in 2023.5.1. Update went flawlessly - and all my deices were in Google. Thanks for the quick and important fix. I was a bit nervousā¦ Went fine.
1 Like
Like others I wish I had seen this first. This is insane! My entire house uses Google hubs and Routines to control everything from lights to blinds to AC and itās all broken. All of my routines have to be fixed and I donāt remember 1/2 of the shit I had in them. Not happy at all!
Cant you roll back to 2023.4.6 and then upgrade to 2023.5.1 where this bug has been resolved?
1 Like
Itās quite pointless to do thatā¦ They have been removed from Google and therefore they are no longer part of the routines. I have very complex routines in Google and if I roll back, sure the entities will be there again, but all the routines will still be broken. Once the entity is removed the routine doesnāt magically restore itself when adding them back. For example, when I say āgood nightā it closes all the blinds, locks all the doors, closes the garage doors, changes to night mode, ensures the fireplace is off, sets the climate to night and the list goes on.
2 Likes
Donāt know how to read this, we can create a list of entities to show in history.
Thatās ok for me.