Actually Yes I have searched and I have not found this current issue. I do know that Harmony closed their local API but this is with the web hooks fix that came in with 84.4.
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 attribute 'is_admin'Ever since updating to 0.84 my automations don’t get triggered anymore. Example fo the code:
- id: '10'
alias: Alarmpaneel Algemeen Uit
trigger:
- entity_id: binary_sensor.algemeen_uit
platform: state
to: 'on'
action:
- alias: ''
service: light.turn_off
entity_id:
- group.beneden_lights
- group.boven_lights
Anyone have the same problem?
EDIT: Found the solution!
For some reason the default states for automations seem now to be “off” (something to do with the change in state restoration?
Adding the following to my automations solved it:
initial_state: 'on'
1 Like
Do you use app daemon with an API password? or anything else that does? May have been switched over to use long live tokens. That was my issue.
Yes an app daemon and own tracks as well. Thanks for the tip will dig in this way
The issue here wasn’t that you needed to add that, it was that upon upgrade to 0.84 (where home-assistant switched to a new state engine), the first boot of 0.84 did not have a previous state to resume from, so some automations were turned off.
This was in the release notes, but it didn’t list what some of the effects would be (like random automations not being on), so it’s hard to put that together.
If you go to the developer tools services tab, then select service “automation.turn_on”, then click “Call Service” that will turn on all of your automations and they will stay on through reboots (unless you turn them off).
The line you added will turn them back on even if you wanted them to be off (let’s say you temporarily want to disable one because a guest is staying with your or something)
3 Likes
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… :-/
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"
],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.
And indeed App Deamon related. Updating App Deamon resulted in an authorization error (no reply). Turned it of for now and will look later…
Are you using a long lived token? If not you need to.
So, does this mean we should slowly move into the lovelace configuration approach instead of configuration.yaml?
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
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.
you read about the new way you have to do tap_actions, correct?
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.
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.”
Looks like it has been fixed.
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.”
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?