See above:
1 Like
OK, Well being a novice to Home Assistant I had assumed that the Supervisor would have been the place to check on this. Is it reported somewhere else, if so, why not on the Supervisor? I would like to easily check that an update was properly completed. The Host System information does tell me this as I am now at 5.10 after the last upgrade.
Am I just looking in the wrong place?
Thanks,
Rich
1 Like
Anybody else have trouble with the new Motion Blinds integration? I had a problem with it using 2021.1.0 and it still seems to be an issue with 2021.1.1.
Basically, the integration never fully starts and the logs show errors related to initializing the integration. I see that there were commits related to discovery in 2021.1. When I roll back to 2020.12.2 it works again.
Here are some relevant debug logs:
2021-01-09 08:39:08 INFO (MainThread) [homeassistant.setup] Setting up motion_blinds
2021-01-09 08:39:08 INFO (MainThread) [homeassistant.setup] Setup of domain motion_blinds took 0.1 seconds
2021-01-09 08:39:08 INFO (SyncWorker_13) [motionblinds.motion_blinds] Creating multicast socket
2021-01-09 08:39:08 DEBUG (MainThread) [homeassistant.components.motion_blinds.gateway] Initializing with host 192.168.2.xxx (key b9e...)
2021-01-09 08:39:09 DEBUG (MainThread) [homeassistant.components.motion_blinds.gateway] Motion gateway mac: 807d6aaa3f50, protocol: 0.9 2021-01-09 08:39:14 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 1 attempts while waiting on multicast push from update request, trying again...detected
2021-01-09 08:39:19 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 2 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:24 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 3 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:29 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 4 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:34 ERROR (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred on 5 attempts while waiting on multicast push from update request, communication between gateway and blind might be bad.
2021-01-09 08:39:39 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 1 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:41 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: motion_blinds
2021-01-09 08:39:44 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 2 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:49 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 3 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:54 DEBUG (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred at 4 attempts while waiting on multicast push from update request, trying again...
2021-01-09 08:39:59 ERROR (SyncWorker_2) [motionblinds.motion_blinds] Timeout of 5.0 sec occurred on 5 attempts while waiting on multicast push from update request, communication between gateway and blind might be bad.
Things go on like that for some time then:
2021-01-09 08:42:04 DEBUG (MainThread) [homeassistant.components.motion_blinds] Finished fetching Motion Gateway data in 175.025 seconds
2021-01-09 08:42:04 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=motion_blinds>
But nothing is actually available. Then:
2021-01-09 08:42:05 DEBUG (MainThread) [homeassistant.helpers.translation] Cache miss for en: cover.motion_blinds, sensor.motion_blinds, motion_blinds
2021-01-09 08:42:05 DEBUG (SyncWorker_15) [homeassistant.util.json] JSON file not found: /usr/src/homeassistant/homeassistant/components/motion_blinds/translations/cover.en.json
2021-01-09 08:42:05 DEBUG (SyncWorker_15) [homeassistant.util.json] JSON file not found: /usr/src/homeassistant/homeassistant/components/motion_blinds/translations/sensor.en.json
For reference I am using a supervised install on an x86 Debian 10, kernel 5.9.
I also attempted to setup this integration on a RasPi3 Running OS 5.9, same deal.
Look in configuration / info
1 Like
Iâm also having trouble setting up the new oauth neato integration. After following the guide I get a âThe redirect uri included is not valid.â response during the neato integration. When I try to navigate to the auth URL I get âMissing code or state parameter in https://ha.example.com/auth/external/callbackâ.
Could this have anything to do with cloudflare? My supervisor and HA versions are on the very latest.
Iâm aware â I blanked out my own domain for privacy reasons.
This even threw my a while ago. It would be good if that panel showed the core version as well. It already shows a ha os version as well as the supervisor. I understand how this is confusing.
2 Likes
Yes this is confusing. The whole âsupervisor shows core needs to update but once you click update you have to go somewhere else in the gui to check it workedâ is a bit annoying.
2 Likes
I am getting following error updating from Supervisor. Any idea why?
21-01-10 00:30:17 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2021.1.1
21-01-10 00:30:17 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image homeassistant/qemux86-64-homeassistant:2020.12.1 to homeassistant/qemux86-64-homeassistant:2021.1.1
21-01-10 00:30:17 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image homeassistant/qemux86-64-homeassistant with tag 2021.1.1.
21-01-10 00:31:54 ERROR (SyncWorker_0) [supervisor.docker.interface] Canât install homeassistant/qemux86-64-homeassistant:2021.1.1 -> 404 Client Error for http+docker://localhost/v1.40/images/homeassistant/qemux86-64-homeassistant:2021.1.1/json: Not Found (âno such image: homeassistant/qemux86-64-homeassistant:2021.1.1: No such image: homeassistant/qemux86-64-homeassistant:2021.1.1â).
21-01-10 00:31:54 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Often a sign that your hard drive is too full.
Thanks Tom! Found it.
I do think this should also be on the Supervisor window as an additional line item as this is the page where we look for and accept upgrades / updates. As I update and refress the screen I expected on the same screen to see the version increase as it does on the same page for the âHost Systemâ when on the same screen I accept the update.
1 Like
As addons and the core are just are docker images, the supervisor page seems a logical place to put some version info, along with the addon versions.
1 Like
Unfortunately Iâm still facing the same issue with log error:
Error setting up entry Configuration.yaml for neato
AttributeError: 'NoneType' object has no attribute 'encode'
Iâve updated to 2021.1.1, removed my vacuum from my Neato account and re-added it again, rebooted HA several times, but each time it results in the same error. Worse off, deleting the integration and re-adding it results in my Neato integration card showing multiple âConfiguration.yamlâ forcing me to restore a prior docker container state each time.
Thoughts?
Update: Several reboots fixed my problem
I get a 500 server error:
21-01-10 08:29:12 ERROR (SyncWorker_2) [supervisor.docker.interface] Canât install homeassistant/qemux86-64-homeassistant:2021.1.1 -> 500 Server Error for http+docker://localhost/v1.40/images/create?tag=2021.1.1&fromImage=homeassistant%2Fqemux86-64-homeassistant: Internal Server Error (âGet âhttps://registry-1.docker.io/v2/â: context deadline exceededâ).
Since the update to 2021.1.0, I get a lot of network specific problems that prevent some components from being set up.
2021-01-10 13:59:07 WARNING (MainThread) [homeassistant.loader] Pastebin.com
I have a Home Assistant Core installation in a Docker container. I have logged into the container via shell and can definitely reach external addresses from it.
I have also tried disabling each component in turn to see if a particular one is causing the problem. But the problem persisted even when I loaded them individually.
Unfortunately, I am currently at a bit of a loss as to what is causing the problem. 
Upgraded to 2021.1.1 from 2020.12.1 with no issues. Also upgraded to HAOS 5.10 with no issues on a Pi 4. New Years resolution is to build more automations in Node Red to take advantage of all the tech I have added.
This is a known bug in pybotvac that has reappeared since we merged the OAuth changes.
I am not quite sure what is the exact reason for this error. As a result, we get incorrect or at least undocumented data from neato, so we run into a parsing error. An upcoming version of pybotvac will work around this problem. For now, please check your account for broken robots at https://neatorobotics.com. We know of users who were able to fix this issue by deleting old or unknown robots from their account.
When instantiating a new OAuth integration in Home Assistant, make sure you start only one configuration flow at a time. Even though you can click âOpen Websiteâ several times, press it only once and wait until this flow is complete.
1 Like
Thank you, @Santobert!
I apparently did have a dormant/broken robot hiding in my account online. Removing that allowed the Neato integration to connect without error.
2 Likes