No GUI after update - pychromecast error

Configuration
1

I have just updated to 79.2 and have no GUI. This is my error log - but the last line about the pychromecast sticks out. would this prevent the GUI from loading? If so - how would I solve this?

core-ssh:~# hassio ha logs

Error decoding json invalid character '-' after top-level value: 2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up map

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds.

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded notify from homeassistant.components.notify

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded notify.pushbullet from homeassistant.components.notify.pushbullet

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up notify

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded light from homeassistant.components.light

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded light.lightwave from custom_components.light.lightwave

2018-10-02 12:49:21 WARNING (MainThread) [homeassistant.loader] You are using a custom component for light.lightwave which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded cast from homeassistant.components.cast

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up cast

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds.

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded conversation from homeassistant.components.conversation

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded config from homeassistant.components.config

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up discovery

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.2 seconds.

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded script from homeassistant.components.script

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded updater from homeassistant.components.updater

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.setup] Setting up updater

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded sensor.yr from homeassistant.components.sensor.yr

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded sensor.wunderground from homeassistant.components.sensor.wunderground

2018-10-02 12:49:21 INFO (MainThread) [homeassistant.loader] Loaded sensor.darksky from homeassistant.components.sensor.darksky

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded sensor.hue from custom_components.sensor.hue

2018-10-02 12:49:22 WARNING (MainThread) [homeassistant.loader] You are using a custom component for sensor.hue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded sensor.template from homeassistant.components.sensor.template

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up sensor

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up group

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.notify] Setting up notify.pushbullet

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.wunderground

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hue

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.darksky

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.4 seconds.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up tts

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up cloud

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.0 seconds.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up logbook

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setup of domain ifttt took 2.5 seconds.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up conversation

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.1 seconds.

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up config

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.automation from homeassistant.components.config.automation

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.core from homeassistant.components.config.core

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.customize from homeassistant.components.config.customize

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.device_registry from homeassistant.components.config.device_registry

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.entity_registry from homeassistant.components.config.entity_registry

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.group from homeassistant.components.config.group

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.hassbian from homeassistant.components.config.hassbian

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.config_entries from homeassistant.components.config.config_entries

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.script from homeassistant.components.config.script

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.auth from homeassistant.components.config.auth

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.loader] Loaded config.auth_provider_homeassistant from homeassistant.components.config.auth_provider_homeassistant

2018-10-02 12:49:22 INFO (MainThread) [homeassistant.setup] Setting up media_player

2018-10-02 12:49:23 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 0.3 seconds.

2018-10-02 12:49:23 INFO (MainThread) [homeassistant.loader] Loaded media_player.cast from homeassistant.components.media_player.cast

2018-10-02 12:49:23 WARNING (SyncWorker_8) [homeassistant.components.sensor.darksky] Monitored condition temperature_min is deprecated

2018-10-02 12:49:23 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast

2018-10-02 12:49:23 WARNING (SyncWorker_8) [homeassistant.components.sensor.darksky] Monitored condition temperature_max is deprecated

2018-10-02 12:49:23 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.7 seconds.

2018-10-02 12:49:23 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.9 seconds.

2018-10-02 12:49:24 INFO (SyncWorker_4) [pychromecast] Querying device status

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setup of domain group took 3.0 seconds.

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 3.0 seconds.

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setting up switch

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setting up device_tracker

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setting up automation

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setting up light

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setting up script

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.components.switch] Setting up switch.lightwave

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.components.light] Setting up light.lightwave

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.3 seconds.

2018-10-02 12:49:25 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 4.7 seconds.

2018-10-02 12:49:26 INFO (SyncWorker_12) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (SyncWorker_13) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 1.1 seconds.

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.cast entity: media_player.kitchen_bass

2018-10-02 12:49:26 INFO (SyncWorker_0) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.setup] Setup of domain light took 1.1 seconds.

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.loader] Loaded light.hue from homeassistant.components.light.hue

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.components.light] Setting up light.hue

2018-10-02 12:49:26 INFO (SyncWorker_6) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.cast entity: media_player.bass_group

2018-10-02 12:49:26 INFO (SyncWorker_14) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (SyncWorker_15) [pychromecast] Querying device status

2018-10-02 12:49:26 INFO (SyncWorker_16) [pychromecast] Querying device status

2018-10-02 12:49:27 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 2.0 seconds.

2018-10-02 12:49:27 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.asuswrt

2018-10-02 12:49:27 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.google_maps

2018-10-02 12:49:31 INFO (SyncWorker_18) [homeassistant.components.device_tracker.asuswrt] Checking Devices

2018-10-02 12:49:31 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 6.4 seconds.

2018-10-02 12:50:06 ERROR (SyncWorker_13) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2

What is your cast config? Via discovery or by manual configured

3

Discovery.

4

I only fixed manual config scenario in 0.79, it looks like discovery may have similar issue.

Can you help to isolate which chromecast device caused the issue?

5

No idea how I’d check that?!?!

Am I better off adding them manually then?? And if so, how?

Cheers for the help.

6

I have been having this problem for a while. As soon as I configure (automatically) chromecast, it stops the GUI from working.
I have to drop back to an older version where I hadn’t configured chromecast.

I’ll just have to leave it unconfigured for a while until it gets sorted.

7

I ( kinda of) have the same (similar) issue since, I think, 78.2. I switched to the cast Integration and at first it was working just fine. But ever since 78.2 I no longer see any cast devices in the GUI. I don’t really use any cast components with HA and I’ve been busy working with other things so I have not yet bothered with any trouble shooting

8

I had the same issue with Web UI not coming up. I found this and it fixed the issue for now:

However, my Google Chomecast devices did not show up in the web UI anymore. Google Chromecast setup changed. I deleted the settings in Configuration.yaml file and uncommented the discovery: so that they could be automatically setup. Then they came back in my Web UI.

Hope this helps.

9

For what it’s worth. I run a test and production server. The last stable version I have on prod is 76.2 with manual config, with this version, I still had to cut down my devices to the 3 devices I use for automations and TTS. One of the other devices was causing the timeout issue where the frontend wouldn’t load.

With the test server running 78.3, the retires and timeout address limit has resolved the issue with the front end no loading, however i find after a couple of days, all my devices end up unavailable as the server eventually gives up trying to reconnect.

Thats my experience so far, needless to say, I’m holding onto 76.2 for now, I also found restarting the chromecast/google home device fixed one of the timeout issues, but not for the chromecast audio device.

10

Running version 80.3
Two days ago we had a power outage and after that my Home Assistant wouldn’t load the UI, figured the outage must have messed up the SD card or something like that.

So this is my story so far:

  • Tried to restart the Pi several times but to no avail.
  • Managed to connect via SSH a couple of times so I grabbed my snapshots from the Pi via WinSCP.
  • Calling ‘restart now’ from Putty locked me out completely.
  • Samba share worked so I copied over all my .yaml files.
  • Next I reinstalled Home Assistant and all was good, restored my latest snapshot and rebooted only to find out that it wouldn’t start.
  • Reinstalled Home Assistant again and this time I added my devices again, this time no problem until I added my ChromeCast devices. Doing this locked me out of the UI again, checking the log verified that it is in fact a problem with the ChromeCast devices resulting in a never ending wait in the boot up process.
  • Tried the tip above and deleted the core.config file and it worked wonders and HA started up again.

So now I’m back up again, copied and replaced the base config files with my own and besides having to rename some of the entities in my groups it all works and was rather painless.
But I do want my cast devices to work again, it really is a weird problem as it worked flawlessly before the power outage. I must have restarted the Pi tens of times since the last update and you would think the problem would have shown, but no.

So as far as I know adding Cast units with the discovery feature messes with HA, how do I add the manually and is this a verified solution for the time being?

2 Likes
11

I’d also like to know how to add them manually.

12

Just did an update and believe I have encountered the same thing.

Previously you could just add it into media players with

- platform: cast

Probably still works, I was getting a prompt to change to the configurator for cast though and did so prior to updating.

EDIT: Was able to get back in after deleting the cast stuff from core.config_entries will try adding manual cast config and report back.

1 Like
13

Alright keep us posted once you tried. I’m currently updating to 0.81.6 but couldn’t find anything in the change log about the matter at hand.
Would love to have this resolved, manually adding the devices don’t bother me at all as long as it won’t lock me out again.

14

Likewise - just don’t want to get locked out again myself, however I really want to start using the cast services!

15

Sorry, after all my stuffing around I realised I was late for my train and ran to work. After deleting everything just worked, including chromecast - maybe it’s known devices or something. I didn’t end up adding it back in.

16

I’d be happy to help any way I can, let’s keep this thread alive until we got a valid solution!

Oh and it might be a good idea to post our setup of cast-able units, in the end it might be one of the units that is causing all the trouble.
My setup:
2 Sony Android TVs
1 Sony Surround Receiver
1 Google Home
2 Google Home Minis

17

No idea if it makes any difference, but have you given your cast devices a static IP?

18

2 sony TVs.
2 Google Home. (Tested and worked after removing config as above)
2 Chromecast Audio.
1 Chromecast 2nd gen I think.
2 x Nvidia Shield,
2 x Xiaomi Mi Box
I think that’s it.

EDIT: All static IPs

19

My Cast Devices:

1 Chromecast 2nd gen (I think)
1 Chromecast ultra
1 Chromecast Audio
1 Google Home
1 Google Home Mini

Not everything is on a static IP

20

Gonna try and lock down all my devices with static ip’s, makes the life of home setup way easier anyway so no loss there :slight_smile: