New Error since upgrade to latest HA

Hi All

Just updated to latest HA and I am now getting multiple errors on every instanceni ave running which has been previously stable

any help would be greatly received

http://192.168.0.7:8123/frontend_latest/bf7146608f595468a214.chunk.js:3157:1358 Unable to get property ‘name’ of undefined or null reference

Paul

It has to do with your UI. Are you using Lovelace, Frontend, or CustomUI?

Hi there

I was using the default front end, have just swapped over to lovelace and I still get the same error message

Thanks for the reply

Paul

You’re going to need to give more information then. That error doesn’t have much context. Is there anything else in your logs?

Hi There

Here is what they say

Hi There

Just restarted the HA and this is in Info

http://192.168.0.7:8123/frontend_latest/bf7146608f595468a214.chunk.js:3157:1358 Unable to get property 'name' of undefined or null reference 
‎7‎:‎50‎ ‎PM components/system_log/__init__.py (ERROR) 
Error while setting up platform songpal 
‎7‎:‎48‎ ‎PM components/media_player/songpal.py (ERROR) 
Setup of platform ring is taking over 10 seconds. 
‎7‎:‎48‎ ‎PM util/async_.py (WARNING)

Sytem log as below

18-12-17 19:22:57 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:25:52 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-12-17 19:25:59 INFO (SyncWorker_5) [hassio.docker] Run command ‘python3 -m homeassistant -c /config --script check_config’ on homeassistant/raspberrypi3-homeassistant
18-12-17 19:26:38 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-12-17 19:26:38 INFO (SyncWorker_1) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:26:40 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:26:41 INFO (SyncWorker_0) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.84.2
18-12-17 19:27:12 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:34:03 INFO (SyncWorker_12) [hassio.docker] Run command ‘python3 -m homeassistant -c /config --script check_config’ on homeassistant/raspberrypi3-homeassistant
18-12-17 19:34:41 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-12-17 19:34:41 INFO (SyncWorker_1) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:34:43 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:34:44 INFO (SyncWorker_13) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.84.2
18-12-17 19:35:14 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:40:22 INFO (SyncWorker_11) [hassio.docker] Run command ‘python3 -m homeassistant -c /config --script check_config’ on homeassistant/raspberrypi3-homeassistant
18-12-17 19:41:01 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-12-17 19:41:01 INFO (SyncWorker_3) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:41:04 INFO (SyncWorker_3) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:41:05 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.84.2
18-12-17 19:41:36 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:43:09 INFO (SyncWorker_13) [hassio.docker] Run command ‘python3 -m homeassistant -c /config --script check_config’ on homeassistant/raspberrypi3-homeassistant
18-12-17 19:43:47 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-12-17 19:43:47 INFO (SyncWorker_5) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:43:49 INFO (SyncWorker_5) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:43:51 INFO (SyncWorker_7) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.84.2
18-12-17 19:44:21 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:47:05 INFO (SyncWorker_15) [hassio.docker] Run command ‘python3 -m homeassistant -c /config --script check_config’ on homeassistant/raspberrypi3-homeassistant
18-12-17 19:47:44 INFO (MainThread) [hassio.homeassistant] Home Assistant config is valid
18-12-17 19:47:44 INFO (SyncWorker_13) [hassio.docker.interface] Stop homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:47:46 INFO (SyncWorker_13) [hassio.docker.interface] Clean homeassistant/raspberrypi3-homeassistant Docker application
18-12-17 19:47:47 INFO (SyncWorker_6) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-homeassistant with version 0.84.2
18-12-17 19:48:17 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-17 19:55:52 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token

Looks like the system log is erroring out when attempting to get an error from your log file. Not sure what you can do to stop that. Are you running the latest JS?

JS ;- JavaScript

How can I check or get the latest version ?

Paul

Well, this can typically only be specified in the frontend section:

frontend:
  javascript_version: latest

I believe it’s latest by default.

EDIT: as for seeing what version you are running, that’s based on your browser.

I have just put the java script iot the configuration and that asnt made any difference

I am using edge at the moment (Microsoft Edge 42.17134.1.0)

What do you find best to run HA with ?

I’d steer clear of edge if you can. I use chrome but I’ve heard Firefox is just as good. Edge could be your problem.

I upgraded to the latest ha today and that error has now gone

sounds like a good ole fashion bug then. At least it’s gone now!