0.89: Nissan Leaf, PlayStation 4, Point alarm control, Owlet baby monitor

[aidbish (Adrian)]

no each image has to be built
https://hub.docker.com/u/homeassistant

[Onandon (Marc)]

But the image for RPi3 32-bit is already done for over 6 hours …

[aidbish (Adrian)]

Hass.io. has always has a fair bit of delay

[AhmadK (akasma74)]

@aidbish

Hass.io. has always has a fair bit of delay

could you explain why exactly? just curious…

[aidbish (Adrian)]

No idea but probably some automated build process, just the various posts over time on here, last couple of releases it was the other way around for me, normal HA took day or so to appear

some have only appeared in the last hour or so on dockerhub

[aidbish (Adrian)]

See this post by @DavidFW1960 on how to do a force check

Emotional!

Hassio is always delayed. Takes extra time to build. Always been that way. You can try and force an update via ssh by issuing this command from ssh hassio ha update -o version=0.xx.x It will update that way if it’s available whereas the update ‘prompt’ will take much longer to appear. Usually I check here https://hub.docker.com/r/homeassistant/home-assistant/tags/ and if the update is listed there you can do the ssh update.

[makai]

I was talking about hass.io.

[pvizeli]

If the release is over night (for me), you need wait until I’m up and able to test the image on some device before I push it to stable channel

[andreas1 (Andreas)]

Updated to 0.89.0 and it looks good, but all my webhooks have disappeared and i cant create them again. Known bugg or is there any fix?

[aidbish (Adrian)]

A very valid reason on why delayed.

[AhmadK (akasma74)]

@aidbish

hassio ha update -o version=0.

thanks mate. hassio ha update --version=0.89.0 it is

[DavidFW1960 (David)]

@AhmadK

hassio ha update --version=0.89.0

Yes that changed recently… no longer -o version etc…

[AhmadK (akasma74)]

And it worked, I even didn’t have to restart anything, ssh connection remains alive, but had to clear cache and restart Chrome to get rid of old ESPHome discovery notification.

By the way, a side effect of this

should I open an issue?

[Onandon (Marc)]

What do you mean? I think I rather wait for the update to come up in Hass.io, don’t want to break anything cause of the lady at home

[ajoyce (Al)]

Try deleting the google maps cookie file, then restart twice

[glith]

Nope, still no luck.
I also see this in a separate log row:
“locationsharinglib.locationsharinglibexceptions.InvalidCredentials:
[[“gf.sicr”,null,null,5,null,[null,null,“type: FIRST_AUTH_FACTOR\n”,1,null,“INCORRECT_ANSWER_ENTERED”,null,null,1,6,null,null,null,null,null…”

I have never changed the configuration or the password of the account. The only thing I have done is upgrading HomeAssistant.

[Klagio]

Lovelace picture-elements now shows a big yellow error when an entity_id is not correct.

Logically is a normal thing, but since I have so many entity_id, and there is always a problem (a WiFi bulb that goes offline, an entity_id renamed by the service, and so on) now my picture-elements its clogged by yellow errors.

I wish this will be as it was before 0.89 (when an entity_id does not exist simply show nothing in picture-elements)

[tcastberg (Tor Magnus)]

@glith

I have never changed the configuration or the password of the account. The only thing I have done is upgrading HomeAssistant.

Exactly the same issue for me. I’ve not been able to fix it yet.

[cjsimmons (Chris Simmons)]

Cheers mate. Not sure why, but this time the command worked with no errors. Still getting “Could not bind to port 987” though. Not sure what to do now…

[ajoyce (Al)]

Are you using the ‘nonetype non iterable’ fix that was circulated a while back? I know a lot of people (myself including) were using a patched version of the google maps component to make it work with the new google auth system - if you’re still using this fix then the new restrictions on partial components may have borked it?