This might be a hack, but simply create an empty services.yaml in <config>/custom_components/, and the warnings for custom_updater and other custom components (variable for me) are gone.
there wont be any references of breaking changes of custom component.
Panic here!
After update I get only the lines below in the log, after that everything freezes. I can’t see that anything happens “behind the scenes” either using a ps -ef.
Running a Hassbian install.
Apr 25 11:40:14 hassbian systemd[1]: Started Home Assistant.
Apr 25 11:40:17 hassbian hass[1845]: 2019-04-25 11:40:17 INFO (SyncWorker_0) [homeassistant.config] Upgrading configuration directory from 0.91.4 to 0.92.0
Apr 25 11:40:17 hassbian hass[1845]: 2019-04-25 11:40:17 INFO (SyncWorker_0) [homeassistant.config] Migrating google tts to google_translate tts
Apr 25 11:40:17 hassbian hass[1845]: Config directory: /home/homeassistant/.homeassistantDoesnt seem smart to me to speak the pin out loud in front of other people. Whats the use case?
Also, is there now a new method to add addons to the sidepanel as iframe?
I thought the solution in 0.91.4 was just a workaround…
Do you have google tts in your configuration.yaml?
Comment it out and test again.
For the Integration xxxx not found when trying to verify its xxxx platform, add a manifest.json file into the folder containing the custom component.
Details here: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
In the breaking changes, look for the google tts changes required.
https://www.home-assistant.io/blog/2019/04/24/release-92/#breaking-changes
That worked, thanx!
Hi,
I’m getting
General Errors:
- Component not found: hue
When I run the hassio addon check config against latest version. Can’t see any breaking changes that would require a change to my hue config setup.
Thanks
This works also for me! Thanks
@fredric.palmgren , @100lv, could it be that the HA User has no permission to write to your configuration yaml?
This update edits the google tts entry in config.yaml and seems to stop if it can’t do this.
Okay, upgraded and found the following issue in lovelace frontend
Using Firefox as the browser, using “Configure UI” you are no longer able to add cards to the interface
Also the UI is notically slower then previous version, addons tkae forever to load through new ingress interface
How to add addons to left panel? I don’t see it in RLS notes, this was possible right?
For add-ons that support ingress there’s a checkbox in each add-on to control whether to add it. I had to restart ha to make it take effect.
One annoyance is that the icons are just the jigsaw pieces (except for Configurator which has a wrench, so maybe it’s configurable and needs the addon devs to change some manifest).
Created manifest.json for my three custom components (sensors). The components are now found. However all of them expect the same setup (keys). They expect “si2key”, “ri4key” and “sited” which are related to another sensor (sl) and not to ikea and pollenniva. I get the following errors when checking my configuration.
Skärmavbild 2019-04-25 kl. 15.05.59
Interesting. I’m running FF 66.0 on Fedora and do not have that problem. I did a couple of ctrl-shift-reloads to force my cache to clear when I was trying to disable the add-ons from my sidebar (I wanted my icons back so I reverted to the manual control).
What FF version are you on? And does the F12 debug log show any JS errors? Are you running an ad blocker?
Um… I removed all my custom panels and used the toggle for ingress instead… all the icons are correct as they were before… only one with a wrench is configurator but the other ones - ssh & web terminal, vscode, log etc… they are all the ones I have previously manually configured. Perhaps you needed to restart?
anyone else having trouble updating? My hassio runs in docker on ubuntu, and it just keeps starting the update then staying at 0.91.4. I tried rebooting the host and that didn’t help. Is there a command to force the update?
What does your manifest.json contain?
Running FF v66.03, and yes also did cache clear, need to leave now. Will check out things further later on.