0.84: Cloud webhooks, Wunderlist and USGS Earth Quakes

gurbyz · December 23, 2018, 7:58pm

Love the 0.84.6 update that restored the ugly not_home/home states for my device trackers. They’re neatly Away/Home again. Thx very much!

EDIT: Cheered to early… :-/

moskovskiy82 · December 24, 2018, 2:54am

Well indeed it’s an appdaemon (i’m using version 2 and not ready ti upgrade). So it’s weird it was working in 0.8x including 0.83 until the 0.84 came out. Already added the line to storage for legacy api but with no luck

            "group_ids": [
                "system-admin"
            ],

felixkleisen · December 26, 2018, 9:30am

Hi, same here. Hadn’t checked a couple of days and was up to error ID 65000.
Exactly the same error, including the same line numbers.

felixkleisen · December 26, 2018, 9:58am

moskovskiy82:

Ok. Upgraded and now get a whole lot of

10:09:49 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1737303856] Error handling message: {'id': 166, 'type': 'subscribe_events'}
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/connection.py", line 66, in async_handle
    handler(self.hass, self, schema(msg))
  File "/srv/homeassistant/lib/python3.6/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

And indeed App Deamon related. Updating App Deamon resulted in an authorization error (no reply). Turned it of for now and will look later…

nickrout · December 26, 2018, 8:00pm

Are you using a long lived token? If not you need to.

wearybasalt · December 27, 2018, 7:33am

So, does this mean we should slowly move into the lovelace configuration approach instead of configuration.yaml?

gazzaman2k · December 27, 2018, 4:49pm

ive gone back to 83.3 the 84.x mess up my zwave and i cant figure out why? it worked on 84.4 then after that it completly messed up and no longer worked

adamlaakso1 · December 29, 2018, 2:12am

Same issue here. While on 84.6 if you go to /states ; do your lights work fine from here? It does for me but nothing in Lovelace.

ha_steve · December 29, 2018, 4:38pm

you read about the new way you have to do tap_actions, correct?

thomas-be · December 29, 2018, 5:34pm

Strangely enough I find that after enabling them they still get disabled on a reboot. So, apparently in my configuration the additional line is needed.

ttaidapos · December 31, 2018, 9:02pm

Will crime reports ever get fixed? I’ve opened issues and done everything I’ve been told but it has been broken forever. If it’s not going to get fixed, please remove it as a component because people are using it. I just don’t know what else to say honestly.

“crimereports 1.0.0 has requirement requests==2.12.4, but you’ll have requests 2.20.1 which is incompatible.”

nickrout · December 31, 2018, 9:22pm

Looks like it has been fixed.

ttaidapos · December 31, 2018, 9:44pm

I just upgraded to 84.6 and still received the error.

“crimereports 1.0.0 has requirement requests==2.12.4, but you’ll have requests 2.20.1 which is incompatible.”

nickrout · December 31, 2018, 9:50pm

Yes I see the problem. The HA component depends on crimereports v1.0.0 whereas the fix to crimereports was made after the release of 1.0.0. Ask the author of crimereports to make another release?

aidbish · December 31, 2018, 10:21pm

i think fabaff made one to that project a while back. https://github.com/happyleavesaoc/python-crimereports/issues/1

ttaidapos · December 31, 2018, 11:02pm

This is where I’m confused. The issue was reported here:

and also here

But now what?

nickrout · December 31, 2018, 11:03pm

See my last post.?

aidbish · December 31, 2018, 11:06pm

Yes and its waiting to be fixed by the people who made it. until the upstream maintainer fixes there is not a lot you can do