0.72: Arlo alarm_control_panel switching to state "unknown" and "pdate of alarm_control_panel.arlo is taking over 10 seconds"

Third party integrations
1

I am seeing the above issue with HomeAssistant 0.72 (which had a major Arlo code update).

I constantly see logs like this:

Jun 27 03:09:44 hassbian hass[11362]: 2018-06-27 03:09:44 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=alarm_control_panel.arlo1, old_state=<state alarm_control_panel.arlo1=unknown; code_format=None, changed_by=None, attribution=Data provided by arlo.netgear.com, device_id=None, friendly_name=Arlo1, icon=mdi:security @ 2018-06-26T20:06:41.099059-07:00>, new_state=<state alarm_control_panel.arlo1=unknown; code_format=None, changed_by=None, attribution=Data provided by arlo.netgear.com, device_id=4R03747YA88F6, friendly_name=Arlo1, icon=mdi:security @ 2018-06-26T20:06:41.099059-07:00>>

Jun 27 03:09:47 hassbian hass[11362]: 2018-06-27 03:09:47 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=alarm_control_panel.arlo1, old_state=<state alarm_control_panel.arlo1=unknown; code_format=None, changed_by=None, attribution=Data provided by arlo.netgear.com, device_id=4R03747YA88F6, friendly_name=Arlo1, icon=mdi:security @ 2018-06-26T20:06:41.099059-07:00>, new_state=<state alarm_control_panel.arlo1=disarmed; code_format=None, changed_by=None, attribution=Data provided by arlo.netgear.com, device_id=4R03747YA88F6, friendly_name=Arlo1, icon=mdi:security @ 2018-06-26T20:09:47.889640-07:00>>

Jun 27 03:10:41 hassbian hass[11362]: 2018-06-27 03:10:41 INFO (SyncWorker_2) [homeassistant.components.arlo] Updating Arlo Hub component

Jun 27 03:10:54 hassbian hass[11362]: 2018-06-27 03:10:54 WARNING (MainThread) [homeassistant.helpers.entity] Update of alarm_control_panel.arlo1 is taking over 10 seconds

Jun 27 03:11:42 hassbian hass[11362]: 2018-06-27 03:11:42 INFO (SyncWorker_10) [homeassistant.components.arlo] Updating Arlo Hub component

2

i didn’t have any problems with 0.72 or 0.77 - but i recently upgraded to 0.8 and whilst i think i had these errors all the time previously, it didn’t really cause an issue. however, with the newest hassio, it now resets the counters everytime it times out.

2018-10-22 11:06:10 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

this of course, causes a bunch of false triggers in my automation. so much so that i had to remove the arlos from any automations.

3

This is exactly what happened to me upgrading to 0.80.
I have completely disabled the Arlo component as HASS continues to reset the internal timers delaying automations.
I have tried to enable it again yesterday but the alarm control panel continues to go in “unknown” state with a lot of Arlo timeout errors in the log.

4

I have similar problems. Arlo is in a unknown state 50% of the time. That’s not good enough. Is someone maintaing this module?

5

Sorry for the late reply, but if anybody feels comfortable enough installing a custom module you could try:

I based it off the original arlo module but made it work more like Arlo’s web interface does - a single event stream being shared amongst multiple devices.

It’s an alpha release but has been working well for me for the last week.

Steve

2 Likes
6

thanks for the tip. I was having the same issue as described and ran into your post. Installing the custom module definitely solved my problem.

7

I just installed the aarlo custom component and it fixed my issue with unknown.