0.84: Cloud webhooks, Wunderlist and USGS Earth Quakes

I’m seeing an error in mqtt_json component as below. Any idea how to fix it?

- platform: mqtt_json

Dec 13 19:37:15 HASS hass[24629]: 2018-12-13 19:37:15 ERROR (MainThread) [homeassistant.loader] Error loading homeassistant.components.light.mqtt_json. Make sure all dependencies are installed
Dec 13 19:37:15 HASS hass[24629]: Traceback (most recent call last):
Dec 13 19:37:15 HASS hass[24629]:   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/loader.py", line 92, in get_component
Dec 13 19:37:15 HASS hass[24629]:     module = importlib.import_module(path)
Dec 13 19:37:15 HASS hass[24629]:   File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
Dec 13 19:37:15 HASS hass[24629]:     return _bootstrap._gcd_import(name[level:], package, level)
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap>", line 986, in _gcd_import
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap>", line 969, in _find_and_load
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap_external>", line 673, in exec_module
Dec 13 19:37:15 HASS hass[24629]:   File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
Dec 13 19:37:15 HASS hass[24629]:   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/light/mqtt_json.py", line 20, in <module>
Dec 13 19:37:15 HASS hass[24629]:     from homeassistant.components.light.mqtt import CONF_BRIGHTNESS_SCALE
Dec 13 19:37:15 HASS hass[24629]: ImportError: cannot import name 'CONF_BRIGHTNESS_SCALE'
Dec 13 19:37:15 HASS hass[24629]: 2018-12-13 19:37:15 ERROR (MainThread) [homeassistant.loader] Unable to find component light.mqtt_json

Got it!

Modified the config

From:

- platform: mqtt_json

To:

- platform: mqtt
  schema: json
2 Likes

Anyone else seeing logbook not respect the excludes? I have time being displayed in logbook every second :wink:

MyChevy Component now working and no longer requires Selenium.
I tried this component out a few releases ago and the component would not even login to the website.
After upgrading to 0.84.1, it appears to have picked up an upgraded version of this component (1.0.1) which now works and works without needing to install Selenium.
Perhaps should add to the release notes.

1 Like

Just to follow up on this… after clearing caches on my various browsers / quitting / restarting etc, I’m getting correct behavior. It’s weird however, there was a time where about every 3rd load of of a page, I would get random, “generic” lovelace page, the UI showing the actual state name rather than the entity-appropriate name (i.e, ‘not_home’ vs. ‘Away’ or ‘off’ vs ‘Closed’), and/or tap-actions not working.

It’s behaving as though there’s cache race-condtions and whichever wins gets displayed or something…

Love the app, great work everyone. Unfortunately, this update 0.84.1 breaks the HA Client Android app. It returns an “Unknown Error (code: 3)” at the bottom and only shows the HA icon. Hope this gets resolved I rely on the app a lot! Happy Holidays to all you hard working superheroes!

Question to all users. Which method do you prefer? New storage or continuing with yaml?

Hi. It would be very nice to see the report of this issue with logs attached here: https://github.com/estevez-dev/ha_client/issues/new
It would help me to solve the issue. The problem is that I’m on 0.84.1 and all works fine for me.

1 Like

i get this error

Error handling message: {'type': 'subscribe_events', 'event_type': 'state_changed', 'id': 1}
Traceback (most recent call last):
  File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/websocket_api/connection.py", line 66, in async_handle
    handler(self.hass, self, schema(msg))
  File "/home/pi/homeassistant/lib/python3.5/site-packages/homeassistant/components/websocket_api/commands.py", line 102, in handle_subscribe_events
    if not connection.user.is_admin:
AttributeError: 'NoneType' object has no attribute 'is_admin'

Ok I did the jump now I am on 0.84.1 but in frontend I have the below. Not sure what I have to do now: wish to try the new storage method

No config found.

RELOAD UI-LOVELACE.YAML

EDIT: had to press F5 on the browser, now I have the frontend back, but not lovelace, my old (from me not updated) legacy UI. On the top right clicking on the three dots there is a menu CONFIG UI, then I clicked TAKE CONTROL OF UI, then RAW CONFIG UI, but it shows nothing. I am a bit confused …

Ok, I’ll post the logs, give me a few

1 Like

Basically I got my old UI that I can edit with the browser editor, which is fine. But I was using Lovelace, how to use that, and edit the Lovelace configuration I had?

@estevez Ok, Github issue #247, logs are posted :+1:

1 Like

I thought to remove my skybell_cache.pickle and restart HA and, voila, Skybell is working again… thanks!

Skybell is working again… thanks!

in your custom component just comment the line

from homeassistant.helpers.restore_state import async_get_last_state

and reload HA and should work fine

“2018-12-13 22:07:38 ERROR (MainThread) [frontend.js.latest.201812110] http://192.168.1.155:8123/frontend_latest/b5032bfc47fcb9aa775a.chunk.js:2958:250261 TypeError: undefined is not an object (evaluating ‘this.config.name’)”

What I am missing here?

Did you read the instructions in the release notes about how to migrate your old lovelace config to the new one?

For existing Lovelace testers

I have the same error as @madrian
It’s happening with weather card in the classic UI.
I’m using a simple weather.darksky. It used to work great in 0.82 and 0.83.
Now (0.84.1), it doesn’t load and I have the following error in the console:

Uncaught TypeError: Cannot read property 'name' of undefined
    at HTMLElement.computeName (bf7146608f595468a214.chunk.js:3157)
    at runMethodEffect (app-0d042052.js:248)
    at Function._evaluateBinding (app-0d042052.js:248)
    at Object.runBindingEffect [as fn] (app-0d042052.js:248)
    at runEffectsForProperty (app-0d042052.js:248)
    at runEffects (app-0d042052.js:248)
    at HTMLElement._propagatePropertyChanges (app-0d042052.js:248)
    at HTMLElement._propertiesChanged (app-0d042052.js:248)
    at HTMLElement._flushProperties (app-0d042052.js:895)
    at HTMLElement._flushProperties (app-0d042052.js:248)

Read the change log for lovelace:

Specifically, the the new way to config ‘name’

EDIT: Nevermind - I just saw you meant in the Classic UI…