2021.1: Happy New Year!

haberda · January 9, 2021, 7:11pm

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.

tom_l · January 9, 2021, 7:40pm

Look in configuration / info

isentropik · January 9, 2021, 9:09pm

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.

nickrout · January 9, 2021, 9:56pm

ha.example.com is an example.

isentropik · January 9, 2021, 10:31pm

I’m aware – I blanked out my own domain for privacy reasons.

DavidFW1960 · January 9, 2021, 11:22pm

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.

nickrout · January 9, 2021, 11:39pm

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.

tshin · January 10, 2021, 12:33am

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

nickrout · January 10, 2021, 12:42am

Often a sign that your hard drive is too full.

Awebian · January 10, 2021, 12:51am

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.

nickrout · January 10, 2021, 1:08am

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.

chriswood1001 · January 10, 2021, 8:19am

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?

dorian · January 10, 2021, 8:30am

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”).

CM000n · January 10, 2021, 1:13pm

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.

ngreed · January 10, 2021, 2:27pm

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.

Santobert · January 10, 2021, 9:09pm

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.

chriswood1001 · January 11, 2021, 11:24pm

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.

DavidFW1960 · January 12, 2021, 9:48pm

Well lookee here… with the new supervisor (beta)

Someone is listening!!

ludeeus · January 12, 2021, 9:49pm

Must be a bug

DavidFW1960 · January 12, 2021, 9:50pm

hahahaha!!!

We love you guys. You all rock