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.
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
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.
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
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.
Wow excellent upgrade - but I wonder where my Top panel has gone ? Now I only have a default panel view with “NO” additional panel in the top? Oh no - that’s huge work to recreate. Configuring default panel has also gone.
OK, sticking with 0.109.6 until a finger gets pulled out from somewhere and changing icon/icon color dynamically is supported in the core now that this release breaks the (now deprecated) customizer integration that allows it