Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

binary_sensor stops working after two days #7

Closed
marceldeklerk opened this issue Apr 29, 2020 · 5 comments
Closed

binary_sensor stops working after two days #7

marceldeklerk opened this issue Apr 29, 2020 · 5 comments

Comments

@marceldeklerk
Copy link

I haven't properly investigated my issue yet, but my Jablotron binary_sensors (motion and magnetic) just stop updating after two days of running the custom_component. I am not entirely sure what had triggered this. A hass restart solves the issue for ~ 2days.

I changed a lot recently:

  • Migrated HASS to a new version, new Raspberry Pi.
  • Updated to latest version of JablotronSystem component.
  • Added a smoke detector to my Jablotron security system.

I expect that the last one is causing my issues.
Also i've noticed that whenever the component is working, movements detected by my PIR's are not always catched by the binary_sensor. The magnetic door contact binary_sensors does not have this issue, and works flawlessly.

Anyone else experiencing the same?
I will investigate this soon.

oh, btw: the alarm_control_panel is not impacted, and continues to function properly.

@Shamshala
Copy link

Shamshala commented May 2, 2020

Have you tried to look into logs in debug mode?

logger:
  logs:
    custom_components.jablotron_system: debug
    custom_components.jablotron_system.alarm_control_panel: debug

@marceldeklerk
Copy link
Author

Yes. I did earlier this week.
Last night, it failed again. I checked the logs this morning.
It looks like it just not receiving any data anymore.

The alarm_contral_panel can still send data (arm/disarm) but also the status is not updated in hass anymore

The log is only just full with:
WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:00:30
DEBUG (ThreadPoolExecutor-0_2) [custom_components.jablotron_system.alarm_control_panel] Data has not been received for 1 seconds, retry startup message

I expect the issue is elsewhere, but not in the jablotron custom component.
Of course a restart of homeassistant fixed it again.
I have to think about the troubleshooting steps. Unlike my earlier assumption, i think this issue got introduced because when i migrated from my Pi3 with Hassbian to my Pi4 running hass (0.109.2) on HassOS version 3.13

Anyone else using the Jablotron integration running hass.io on a Pi4?

@Shamshala
Copy link

Couldn't be the cause USB gets reconnected?

@marceldeklerk
Copy link
Author

Well, physically no one disconnected the cable, that is for sure.

@marceldeklerk
Copy link
Author

This appeared to be an issue with my Raspberry Pi that did not occur anymore since i fully powered if off and on.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants