Hello, Did You found a solution for “[homeassistant.components.sms.gateway] Failed to initialize, error ERR_NOTSUPPORTED” ? For now, I just roll back snapshot. Do You use home assistant os or Raspberry PI OS ? After 2021.7 I had Try to Switch to Home Assistant OS but on I’t i even have issue with switching modem AT so for me only working solution is Raspberry Pi OS and I’m installing docker on IT. Hope I’t will be fixed soon.
You don’t have to remove and add. You’ll have a new remote entity.
Yes, this is how all media_players behave. There may be an attribute that says what it’s playing, however it will not be in the main state.
There’s plenty of examples on the forums. Just search remote.send_command.
Here’s an example.
service: remote.send_command
target:
entity_id: remote.tv_room
data:
command:
- VolumeUp
- VolumeDown
delay_secs: 0.6
1 Like
Same here. All my MQTT devices connected using Zigbee2MQTT are unavailable, same with Xiaomi Air Purifier. I already removed database and recorder history, but it did not help.
hi, seeking further assistance in my discoveries using Nginx (since yesterday…) I did post NGINX configuration - connection refused - #8 by Mariusthvdb, but we couldn’t work this out completely.
cut it short, during startup I see this logged frequently:
2021/07/19 23:02:51 [error] 222#222: *7441 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.1, server: mydomain.duckdns.org, request: "GET /api/websocket HTTP/1.1", upstream: "http://172.30.32.1:8123/api/websocket", host: "mydomain.duckdns.org:myport"
after startup it seems this is no longer happening.
@Burningstone suggested it might be
Could be that it’s because NGINX starts faster than HA.
which seems reasonable, because after initial startup there’s always a gap of about 2 minutes:
2021-07-19 23:20:05 INFO (MainThread) [homeassistant.setup] Setup of domain proximity took 0.3 seconds
2021-07-19 23:21:56 INFO (MainThread) [homeassistant.core] Starting Home Assistant
during which the system fully loads.
can I prevent these errors in Nginx log somehow. of course I already have the relevant address in the trusted_proxies:
use_x_forwarded_for: true
trusted_proxies:
# - 127.0.0.1
- 172.30.33.7
- 172.30.32.0/24
# - 172.30.33.0/24
thanks for having a look!
1 Like
The only way I’ve had success in getting detailed information from Android TV devices (both my Chromecast w/google TV and my Bravia TV) was to use ADB debugging.
The Netflix app is especially problematic if I don’t use ADB debug.
Has anyone opened an issue?
Edit:History graph reverting back to all data after striking out some items · Issue #9559 · home-assistant/frontend · GitHub
1 Like
How is that the same problem?
Maybe you’re right, I think I was thinking too much about the Xiaomi devices when I was reading the post. But I did saw some comments about unavailability problems after update to 2021.07. I’ll try to restore 2021.06 and clear database + recorder. And ask my own comment 
Thanks Nick.
I cant find ADB debugging on my Bravia 2020 TV. I looked for this a while ago.
Thanks
Martyn
I keep getting the following error on 2021.7.3 ““Watchdog found a problem with Home Assistant API!”” then home assistant restarts. It has been doing this for the last few days. It usually restarts about every hour but sometimes as often as 10 minutes. I am using the ngnix proxy manager to reverse proxy my installation.
Getting really frustrated. I have restored 2021.6 a few times and ran the updates again. 2021.6 works with out issue. Tried every combo of http config I can think of as that seems to resolve from prior posts with no luck
Ok, but the writing seems too long for the Italian translation.
That’s bound to happen if your card is thin. You can write up a request to abbreviate the verbiage for your language. You may even be able to override it.
I have this exact same problem. But I tried to install today, never used influx before. Installed, configured and if I put the config in the yaml I get this error… any luck finding what to do to solve this?
I have the same error.
As a workaround, I put the port 8009 in the Host variable of the Network config section.
And I can access to the Traccar interface at https://myhomeassistantip:8009
1 Like
I found another problem in log that might be related to problem with InfluxDb.
Logger: root
Source: /usr/src/homeassistant/homeassistant/bootstrap.py:312
First occurred: 1:08:42 PM (1 occurrences)
Last logged: 1:08:42 PM
Uncaught exception
RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd
Any idea?
1 Like
I’m trying to debug the slowness on history page still. I tried running a profile in firefox, and it’s clearly visible when the frame rate goes to almost 0. Whenever I try to link over to see the source of the functions though I get an error like
Error while fetching an original source: NetworkError when attempting to fetch resource.
Source URL: webpack://home-assistant-frontend/chunk.91db54671c6070224573.js
Does anyone know how to debug this further?
I have that in my log too… don’t know exactly when it appears, but have some time now… maybe after I tried to install the custom deps deployment… just happen when starting HA… so I just leave it there! 
PS: If I unistall custom deps the error persists… search very little how to solve this error but don’t find anything…
Is anyone noticing EXTREMELY slow response time for insteon commands? When I send a turn on command it shows sending for a 3 seconds, assuming it doesn’t fail, before its complete. This has only been since 7.0. I’m using an ISY not the insteon hub.
I’ve solve the InfluxDB problem. It was caused by GitHub - jaruba/ha-samsungtv-tizen: 📺 HomeAssistant - For Samsung TVs 2016+, Includes SmartThings API and Channel List Support HACS integration, once I removed it and rebuild HA Core influxDB client start working as expected.
I’m guessing that problem is caused by various python imports.
2 Likes
I am trying to upgrade HA from core-2021.6.3 to core-2021.7.4. When I browse to my HA URL through my reverse proxy, I get a blank page with Error: 400. When I browse straight to my HA instance, it seems to work fine. If I roll back to a snapshot made of core-2021.6.3, HA works through my reverse proxy again. Did anything change that would cause this issue? I am using the official x86_64 Home Assistant OS image if that matters.