I’ve not been able to get the new /media to work with google mini speakers. The speakers behave like they are playing audio but no sound. I also created a new directory under the /www but that will not play either which is weird since /www is how I already play mp3s on google mini speakers. Does /media require external access to play on cast devices?
Happy birthday!
Can’t wait for the update to finish. RPI 3, now takes half an hour for the update, is that normal with this huge update?
Happy Birthday Home Assistant!
I updated the system from 0.114.4 to 0.115.0, my system is installed on the TVBox Tanix using Termux. unfortunity the system was down, I can see a lot of dependencies error, I backed to 0.114.4 and I will try again with more calm.
Thanks all to new features, very nice 
Update:
I can see error: Unable to install package pillow on HASS logs.
I try to install pillow package but I am seeing dependencies errors.
Solution
Install Building on Android
Basic Android support has been added for compilation within the Termux environment. The dependencies can be installed by:
pkg install -y python ndk-sysroot clang make libjpeg-turbo (in my case just ndk-sysroot and libjpeg-turbo)
It work now.
Super Hyped about this release. Happy Birthday indeed.
Is there anything I need to enable to try out the media browser on the Spotify integration?
After upgrade of 115 was done, my spotify integration needed to be re-authenticated, but after that I am unable to see this icon for the nedia browser in Lovelace.
EDIT Turns out I needed to set the config path first for the Media_Browser. Didn’t RTFM ^^
1 Like
Oh my god what a big update is this and what a cool new stuff!..
I am amazed and stunned by all of this!.
Really a great job you all did!!
Many thanks and offcourse Happy Birthday!
That one is huge ! HB HA ! 
Note : do NOT click on all changes, this will eat all your RAM ! 
1 Like
Happy for all the improvements, and additional upgrades, but frontend loads much slower now, alot slower, and getting multiple webhook errors using the mobile app, even after multiple reboots.
What did you add to the config? I’m trying to set it up too but no luck so far
created a new folder
/media
and linked to it:
media_dirs:
music: /media/music
2 Likes
Thanks A LOT guys!
Upgraded seamlessly from .114 to .115 
I know there was a change with the release to the http/reverse proxy but…I don’t understand it. I’m now getting this error in my log:
2020-09-17 15:42:05 ERROR (MainThread) [homeassistant.components.http.forwarded] Too many headers for X-Forwarded-For: ['xxxxxx, xxxxxx', 'xxxxx']
It’s probably my NGINX config but I don’t know what I need to change
server {
listen 80;
listen 443 ssl;
server_name xxxxxxxxxx;
# ssl on;
ssl_certificate /etc/nginx/ssl/casa_cert.pem;
ssl_certificate_key /etc/nginx/ssl/casa_key.pem;
ssl_client_certificate /etc/nginx/ssl/cloudflare.crt;
ssl_verify_client on;
ssl_prefer_server_ciphers on;
location / {
proxy_pass xxxxxxxxxxx/;
proxy_set_header Host $host;
proxy_redirect http:// https://;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Host $remote_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
location /api/websocket {
proxy_pass http://xxxxxxx/api/websocket;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Host $remote_addr;
}
location = /robots.txt {
add_header Content-Type text/plain;
return 200 "User-agent: *\nDisallow: /\n";
}
}
It means that the request that arrives at Home Assistant has two X-Forwarded-For header. My guess is that you are using another reverse proxy, e.g., CloudFlare?
They already set a X-Forwarded-For header. In the config you have there, you are adding a second one. The problem with that: Which one to use?! Which is the real one?
You might want to use proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; instead.
For more information see: Using the Forwarded header | NGINX
Yes, I use Cloudflare. Setting the header to proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; worked, thank you!
1 Like
First of thank you all very much for the great and amazing work.
i just updated to this version, and had to add kodi as an integration, everything is fine except executing an addon from a script is not working anymore.
i had this script but after the update its not working, and i dont have an errors
kodi.call_method
entity_id: media_player.kodi
addonid: script.pseudotv
method: Addons.ExecuteAddon
params:
command: activate
anyone else is experiencing that?
1 Like
Ran the config checker, and it came back with this. Not sure where to begin to figure out what is going on.
Any ideas?
General Errors:
- Platform error tts.google_cloud - Error relocating /usr/local/lib/python3.8/site-packages/grpc/_cython/cygrpc.cpython-38-arm-linux-gnueabihf.so: backtrace: symbol not found
great release guys, just one problem, upon restart, it always discovers my “Velux” on integration page
but i dont want it, and i cant ignore it? how can i remove that ?
always get error below
this wasnt before on 114
thnx
Just updated my Debian 10 test environment. Great work guys. It looks like a busy weekend ahead with my live installation. Cheers and happy birthday.
Ok so this template worked previously and I’m having a hard time figuring out which change caused it. I do it often so…need to figure out how to redo it apparently.
{{ states('sensor.washer_current') | int }} used to take the sensor value and convert it to a number so I could do things like evaluating greater than/less than/equal to. It still works but now it’s rounding the value to the nearest whole number. So instead of 0.46 I get 0.
{{ states('sensor.washer_current') | int > 0.036 }} <- This works but only if the value is higher than 0.5
{{ states('sensor.washer_current') > 0.036 }} <- This gives me an ‘unknown error’ in the template page.
Thank @all for your great work!
As I red about the new shelly integration, I was very happy :slight_smile.
Unfortunalety I get a connection erroer, if I want do connect to a shelly sensoer:
firmware on sensor is V1.8.0
Any ideas why connection fail?
Use float not int 
2 Likes