After latest update 0.90.1 I can NOT connect?

Installation Home Assistant OS
1

Hi All

I just updated to the latest hassio.

core-ssh:~# hassio homeassistant info
arch: armv7
boot: true
custom: false
image: homeassistant/raspberrypi3-homeassistant
last_version: 0.90.1
machine: raspberrypi3
port: 8123
ssl: false
version: 0.90.1
wait_boot: 600
watchdog: true

  • and after that I can NOT connect to HA?

I just get: refused to connect

I have logged on through putty and did the check:
hassio homeassistant check
OK

cant really see what the problem is?
have the url been changed again?

2

I have the same problem… the upgrade was successfully when I start home assistant I see in TOP that the CPU gives a very high CPU.
I don’t now why this is…

I’am lucky that I create an backup before I did this upgrade…

What I am doing now is upgrading first my python to version 3.7.0 in the hope when I do a new upgrade that it works…

3

Finally got it booting, deleted the logfile and removed Plex as Media player?

But some other breaking changes have really messed up my page for tracking?

image
image1008×997 136 KB

4

Looks like all my Guest notifications are Gone?
Its just devices on the Known devices that gives a notification when they are connected to my wifi?
Really don’t understand why this should not be working in this new version?

Any input would be greatly appreciated

UPDATE: I found the new UNIFI configurator, it now demands a admin account? (Before I had a special user account with limited access and that was fine!)

After configuring this I still dont have any of my “device_tracker.samsunggalaxys7” back working?

5

Okay, after some trouble shooting I found the issue that the page did not load:

In the configuration.yaml I have this:

Cloud

cloud:

When I did:

Cloud

#cloud:

I start my home assistant…
Final it is running on 0.90.1

Only I don’t understanding the issue with cloud that I need to block it with # to run home assistant 0.90.1

6

I am running it without blocking it

# Cloud
cloud:
7

All these posts and no log.

8

It looks like you took the axe to some core device/entity files and broke the JSON formatting… that’s the only time I’ve seen yellow errors on such a large scale.