I’m not sure I understand your question?
Which component/integration are we talking about?
AppleTV. Pyatv is the library used by the Apple TV integration. The error you have is from the custom component. You should migrate to the official integration
At line 21 on my system
19 from homeassistant.helpers.entity import Entity
21 from homeassistant.const import ( <<<<<<< this needs to be replaced with your info?
22 CONF_PORT,
23 CONF_UNIT_SYSTEM_METRIC,
CONF_UNIT_SYSTEM_IMPERIAL
No issues here with 2023.5.2 and GitHub - rospogrigio/localtuya: local handling for Tuya devices v.5.1.0
@piitaya Them not including the local subnet in the secure context seems rather odd to me. The local IP is behind a firewall (or should be) and therefore would seem secure enough. I’m not a network guru by any means though. With all the “smart” assistants in use these days that are always listening for certain keywords and funneling who-knows-what back to nebulous entities, I’m really shocked (well, not really).
Edit: looks like I hit the wrong reply icon. This was supposed to be tucked in with the replies earlier in the thread.
It’s not about what the devs included or left out. It is not possible. Web browsers do not support insecure access to microphones.
The HA app will get this local access feature eventually though.
3 Likes
Hi all. Looks like my entire database was corrupted following 2023.5.2. Within five minutes of install. Stupidly, I panicked and restored last night’s backup before troubleshooting.
I plan on giving .5.2 another shot. Has anyone else experienced this? Anything I should watch for or log during the upgrade that might be useful for the devs?
Thanks.
Wasn’t talking about the HA devs. My comment was directly solely at the browser devs.
No idea if there is information on which microphone devices might be supported?
I found this one and it looks very good.
I found a solution to getting https
Actually several but one is better.
I already have a webserver with ports 80/443 exposed to the world. I have domain and Lets Encrypt certificates. I use Ubiquiti Edgerouter. When you add a port forwarding to an Edgerouter it also enables hairpin routing which means that when you access your public IP from within the local network, the router forwards the traffic the same way as if the traffic comes from outside.
And for home assistant I used to have a virtual host for a subdomain to reverse proxy to Home Assistant and with that it translates https to http. That is what I shut down. Too dangerous. And with that I lost local https via hair pin.
The solution is to setup the reverse proxy / virtual host to a different port than 443. One that the router does not have a port forwarding rule for. And then you manually create the hairpin routing rules but still not NAT rules. Then it works. From inside my browsers access my subdomain URL with the alternative port and the router hairpins this to the webserver which handles the ssl and forwards the traffic without https to home assistant. So now I can play with voice 
An alternative if you already use pi-hole is to add a subdomain for which you have ssl certificate and let it point to a reverse proxy (nginx or Apache). The end goal is to fool the the browser to think it talks to a server with the domain name for which you have a valid ssl.
If anyone wants more details we should take that to a new thread. But the tldr; it can be done!
Most browsers do not consider self signed certificates as secure anymore.
There was a time they accepted it, long time ago. But unfortunately not anymore.
Well…kinda, but I found this thread AFTER downgrading. I’ve now found the fix at fail to load in beta 2023.5.b0 · Issue #149 · garbled1/homeassistant_ecowitt · GitHub which worked for me and was stupid easy (a good thing in my case LOL).
Anyone having problem with the layout again? My layout is shifted down after update. See screenshot.
I have restarted phone, app with force close and deleting cache and also home assistant. Nothing helped
1 Like
Hello, I don’t know if it’s since 2023.5.x but the service tts.speak (Text-to-Speech (TTS) - Home Assistant ) seems broken.
In dev tools, I can’t have the service running.
Someone can check if it’s the same ? Thank you
never was aware of this service… but indeed I can not use the service, as I can not select a device/area/entity
You can still import signatures for self-signed certs (chrome and firefox, what I use. You just need to tell them what to trust, rather than having someone else define trust for you. 
2 Likes
ONVIF
Since 2023.5.2, I am getting these errors
Logger: homeassistant.config_entries
Source: config_entries.py:863
First occurred: May 6, 2023 at 9:43:54 AM (1 occurrences)
Last logged: May 6, 2023 at 9:43:54 AM
Error occurred loading flow for integration onvif: cannot import name 'retry_connection_error' from 'onvif.client' (/usr/local/lib/python3.10/site-packages/onvif/client.py)
Logger: homeassistant.setup
Source: setup.py:214
First occurred: May 6, 2023 at 9:41:55 AM (2 occurrences)
Last logged: May 6, 2023 at 9:42:26 AM
Setup failed for custom integration tapo_control: Unable to import component: cannot import name 'retry_connection_error' from 'onvif.client' (/usr/local/lib/python3.10/site-packages/onvif/client.py)
Setup failed for onvif: Unable to import component: cannot import name 'retry_connection_error' from 'onvif.client' (/usr/local/lib/python3.10/site-packages/onvif/client.py)
And for the Tapo Control integration:
Logger: homeassistant.setup
Source: setup.py:214
First occurred: May 6, 2023 at 9:41:55 AM (2 occurrences)
Last logged: May 6, 2023 at 9:42:26 AM
Setup failed for custom integration tapo_control: Unable to import component: cannot import name 'retry_connection_error' from 'onvif.client' (/usr/local/lib/python3.10/site-packages/onvif/client.py)
Setup failed for onvif: Unable to import component: cannot import name 'retry_connection_error' from 'onvif.client' (/usr/local/lib/python3.10/site-packages/onvif/client.py)
You have an old version of the TAPO custom component installed that is pinning the onvif library to an old version. Upgrade that custom component to the latest version
I very recently applied an update for Tapo. Not sure where to find the version number or how to apply the update again.
Look under the HACS icon on the left panel
Here: http://HA IP Address:8123/hacs/repository/323923603