2021.7: A new entity, trigger IDs and script debugging

In the http section of your config

Seems the update to python broke tensorflow, tensorflow only supports python 3.6-3.8

2021-07-10 14:48:27 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package tensorflow==2.3.0: ERROR: Could not find a version that satisfies the requirement tensorflow==2.3.0 (from versions: none)

Modbus Users beware with updating to 2021.7.1 if you poll multiple modbus hosts. There is an issue thats been found and currently being fixed if sensor addresses being polled are the same across multiple modbus hosts.

2 Likes

The updated MusicCast integration quietly changed the entity IDs. My device got renamed from media_player.dining_room_main to media_player.dining_room, which broke my automations and dashboard. Not a big deal but it would be good to mention this in the release notes.

Now the device has a unique ID so the entity ID can be overridden.

I have it working on my test install, I just added it in the UI and it just worked. The name for me was home and the latitude and longitude from my Install ( it just auto filled in the UI, I assume from the HA config )

Same here, and I have use_x_forwarded_for enabled and trusted_proxies configured in the http section. What am I missing?

I want to keep using http on my local network. Is that possible?

You can if you use a reverse proxy

I am, but since the last update the external url isn’t working anymore. I am using 8123 for http on my internal network and 8124 for my external network as 443 is used by another server. Set-up was fine in the past but now only the internal network is working.

What does the log say?

I am getting “400: Bad Request” when connecting with the external url.

Log:
2021-07-11 08:42:14 ERROR (MainThread) [homeassistant.components.http.forwarded] Received X-Forwarded-For header from an untrusted proxy 172.30.33.4

I don’t understand the 172 ip address as i am using 192 (also configured as trusted proxy).

It is the internal home assistant docker network. You need to add it as well.

1 Like

172.30.33.4 is the docker container. Did you try adding either that or 172.30.33.0/24 as a trusted proxy?

2 Likes

That’s it! Thanks David and Tom!

yeah, that did the trick, thx a lot!!!

Since the update my tradfri lights, controlled via deconz, won’t change colour anymore. Is this a known issue?

Very strange. I know the API key is valid as I did a curl command and retrieved the json back as expected. I will have to dig deeper.

Not sure if this is the same dependency:

Thank you! Other than this, really enjoying the update and HA in general! Keep up the great work!

Actually this is the more relevant issue:

It is being worked on.

2 Likes

I started using this integration in HACS and the everything is great now. (you will have to change config a little and your devices will be back again)