Amazing work, thank you!
The same as yours…
Tried to make a brand new Lovelace dashboard, but also then I get that bar on the bottom.
I know, it still does not mention that the old one was under http and has to be moved.
I also think the breaking changes part is the important one and should contain all relevant breaking info.
are you also missing other stuff? seems my lovelace just doesnt render good anymore…
my headers texts are coming slow , missing my header button bar, no red error there though
custom:battery-entity
Just for feedback not as comment, developers do a great job with this software.
issues i have with build 110:
- Onvif camera not working for me. I had them configured in the config. First i then removed them, from the config to add them trough integrations. Dicovery method in integration finds my cameras, but i am not able to connect to them. Error cannot create unique id for this camers? Also tried the manual configuration trough the GUI, without succes.
- TTS with google seems to be broken. I have a USB speaker where i use Mopidy to make announce ments. Also a google mini-home is used for this purpose. For both devices the Google TTS is broken.
Use case Internal and external adress???, i suspect that this is the reason TTS is broken? I don’t understand the use case? If you enable SSL, then the internal adres and external adres both should be starting with https As far as i know there is no possibility to differentiate between the use of normal http for internal use and https for external use.
The example in the update anouncement suggest this (external adress: https://myhome.duckdns.org, internal adress: http://10.10.100.10:8123). Have i missed this?
I could understand the use case for some addons (for example addon Unifi controller) who do not support ingress and where you want to use the internal adress to call the underlying service with the internal adress. If this would be the use case for the internal adress then you should only set the adresses without supplying a port in the adress, because the port is defined by the http component of home assistant. For the external adres it is logical that you specify a port, because this depends on how you configured your port-forwarding in the router.
For now i have rolled back to the previous version.
1 Like
How did you restart Home Assistant after making the change?
I had an issue with the beta when it complained about this when I restarted HA by restarting the Home Assistant service from the OS (I run it in a venv) or by rebooting the Raspberry Pi.
When I restarted it from the UI (Configuration > Server Controls), the error went away even after subsequent restarts (however it was restarted). It seemed that restarting via the UI triggered an update that restarting by other means didn’t.
i always restart from this : Configuration > Server Controls
Allright so I got it working. Not sure what did the trick… Uninstalled the custom header, rebooted Home Assistant, still the dark bar on the bottom… Installed it again, uninstalled it, and rebooted again. Boom, the original header is back. Also after cache cleared. Whut…
The old base_url was in http component and didn’t need the “https://” part.
The new ones are located in homeassistant component and certainly need the “https://” part. This should have been informed better.
edit: But the perfect thing and long waited thing is, now I can make the same automation while I am connected to home network or not, with just passing the url:
url: /local/image.jpg
1 Like
yes, installec custom-header 1.3.9 (beta) black bar is gone
Do you have mysterious warnings in the log about deprecated stuff?
There was a blog post aimed at developers that has impact on custom components. And it was not mentioned in the release notes for 0.110
The blog is here https://developers.home-assistant.io/blog/2020/05/14/entity-class-names/
This is mainly for developers. But it is important to know that if you e.g. use the AlexaMediaPlayer custom component you will find some of these warnings in the log
AlarmControlPanel is deprecated, modify AlexaAlarmControlPanel to extend AlarmControlPanelEntity
SwitchDevice is deprecated, modify AlexaMediaSwitch to extend SwitchEntity
SwitchDevice is deprecated, modify DNDSwitch to extend SwitchEntity
SwitchDevice is deprecated, modify ShuffleSwitch to extend SwitchEntity
SwitchDevice is deprecated, modify RepeatSwitch to extend SwitchEntity
MediaPlayerDevice is deprecated, modify AlexaClient to extend MediaPlayerEntity
and then you may - like me - spend some time trying to find what you need to fix in the configuration. You may even find some bug reports or other answers from developers saying it is a custom component bug with no further explanation.
Well. That is not the whole truth. There is a breaking change that is only announced in the blog post.
Don’t panic. It is just a warning that some class names are deprecated - to be renamed. And it is the authors of the custom components that need to fix it. So the problem should go away by itself when the custom components that triggers these warnings get updated and here and now all works like normal.
5 Likes
alright so I’m either stupid or extremely blind… Where do I enable ‘show beta’ in HACS? lol
yeah, if you click on an plugin, its on the top right, but seems the button is missing …
you need to click on an invisible button, just scroll to top right , then you see your mouse icon changing
I have the same problem in firefox.
In the android app the icons are displayed.
I’m seeing the same issue in Firefox on Windows 10. Clearing site data, cached content and restarting the browser doesn’t appear to have any impact.
Please. tell me what i am doing wrong with internal and external link config? I have this config:
homeassistant:
customize: !include include/customize.yaml
external_url: "https://xxxxxxxxx.net:8123"
internal_url: "http://192.168.51.3:8123"
http:
ssl_certificate: ssl/fullchain.pem
ssl_key: ssl/privkey.pem
There is ext and int link and ssl in http section. But internal link doesn’t work.
Thanks for help!
No issues with icons in latest Firefox on Ubuntu 18.04
Running 0.110.x since a few days (beta).
They where to small in some custom-cards (button-card, power-wheel) but this is fixed by the authors.
should be here :
1 Like