During boot of 112.2 it says that the “host” option has been depreciated, please remove it from configuration.yaml.
But what exactly does this refer to?
My configuration.yaml has host option statements in every single platform integration!! Should I remove all of them? I can hardly believe that these integrations can work if the host option statement is removed.
Then there is one “hosts” (with an ‘s’) statement in there. Is that the one?
I’m guessing its the MQTT broker. Are you trying to use the internal one that has now been deprecated?
Using the new logbook and clicking on the log entry, brings up this box:
Log Details (WARNING)
Logger: homeassistant.components.squeezebox.media_player
Source: helpers/config_validation.py:707
Integration: Logitech Squeezebox (documentation, issues)
First occurred: 10:00:29 AM (1 occurrences)
Last logged: 10:00:29 AM
The 'host' option is deprecated, please remove it from your configuration
So, I guess it refers only to the Logitech integration.
Well the docs say ‘host’ is required… I don’t use that integration so can’t really be of more help. Maybe a bug?
Is it setup via YAML or Integrations? (docs say Integrations are preferred) YAML deprecated
you beat me to it but original post says:
Squeezebox
This is now available for configuration via the integrations UI, and configuration of the Squeezebox integration through
configuration.yamlis now deprecated. Please consider using the frontend to configure the Squeezebox integration instead. Servers will automatically be discovered by the “discovery” integration, or by this integration once it is loaded. If the user adds this integration from frontend, it will attempt to automatically discover the server as well.
The Squeezebox integration will now handle individual players coming online or going offline while Home Assistant is running. Previously, the integration would only detect players that were present during startup.
(@rajlaud - #35669) (squeezebox docs )
I had a working setup of smappee in home assistant already for a long time.
But since the update to 0.112, my whole smappee setup is not working anymore.
After the update I had an error in the log stating that the module ‘oauthlib’ was not installed.
After installing it via python pip, I had to install also ‘requests-oauthlib’ and ‘cachetools’.
The next step was to comment out the following in the configuration.yaml:
Only client_id and client_secret was allowed.
After rebooting homeassistant I could add the integration Smappee and login to the smappee webpage.
But now al my existing smappee sensors are not working anymore.
Are we now obligated to work through the paid cloud api?
And the local api is not accessed anymore by the new smappee integration?
That’s an unfortunate turn in the use of smappee.
UPDATE:
I dug into log file and found that HA receives an error message from MySql something like 'the database is full" or so.
Then I tried to delete records directly from within MySql. Again an error about indexes, foreign keys, etc.
Finally, decided to create a new empty database on the external mysql server.
Restarted HA, and… everythign went smooth!
Apparently there was some confusion between HA and existing indexes in mysql db.
Indeed, I lost all my historical data (which I can eventually import into newly created database) but at this moment it’s a little price I pay for enjoying this update.
Thnks all.
Same issue here, my integration (in the config file with token in hard) was working fine with 30 devices before the latest upgrade.
I tried:
Now the device appears automatically in zero-conf but when i try to connect-it, it gives me the same message as in the screenshot.
I tried the integration of the miio and it workd, only the aqara doesn’t.
Should we remove all the previously used entities on Home Assistant ?
I can’t find any information in the logs available in the UI, maybe i am looking at the wrong place ?
I am thinking about rolling back.
Thanks in advance for your help
Thanks in advance
Could have been due to database schema transformation…
Depending on the size of your database and the performance of the hardware you run Home Assistant on, this migration process could add additional time to the first time starting after the upgrade. For most of us, this adds just a couple of minutes, but if you have an enormous database (for example, 30+ GiB), it might take an hour or maybe even two.
Sounds like a good idea to me. Would suggest moving this post to feature requests so it doesn’t get lost.
I’m facing exactly the same problem. My HA is installed as hassio VM in Proxmox. Alternatively, I’ve tried installation HA on RPi and it gave he same error.
I have over 40 devices attached to two Aqara Gateways, and desperately need a solution.
Please hellp!
Which is the reason for my suggestion above. The change is only partially helpful and, as indicated by the question, is confusing.
There should be some way to make the entities “or” and the states “and”.
Well…I updated and now nothing, HA won’t come back on, and I might have panicked and restarted the PI. face palms, Good news is I backed it up just before I started the update. Should I just wait it out or just do a fresh install?
Home Assistant starts just fine, there doesn’t seem to be a problem with that. But later once I go to the Configuration and Server settings and either check config or restart, it doesn’t work as intended. For the check config, it just has the circle animation forever. For the restart, I confirm to restart and nothing happens. If I choose Stop, it stops as intended. This started happening on 0.112 and is still present on 0.112.1
Need delete devices button from list.
Same issue with the Aquara plug, power consumption sensors are missing.
“Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for chineseholiday doing I/O at custom_components/chineseholiday/holiday.py, line 404: res = self.session.get(url, headers=headers)” I see a warning in the log
Then follow the instructions! Go to the github page for that custom component and post an issue.
Okay thank you
Device type is set to router: Device Type: Router
That is maybe the cause
Removing and it comes automatically back
