search

kukulich / home-assistant-jablotron100

Home Assistant custom component for JABLOTRON 100+ alarm system
MIT License
65 stars 24 forks source link

Jablotron integration stops updating after a while #94

Open RGB666 opened 2 months ago

RGB666 commented 2 months ago

I have a problem with the Jablotron integration: it stops updating after a while. Each morning, the integration does not update a changing arm/disarm or PG status. However, the status suddenly updates later in the day. What could be causing this?

Sartenovi commented 2 months ago

I have the same problem. I tested all the possibilities that are in my power, but nothing worked. I have to restart HA twice daily. for now this integration is unusable.

Sartenovi commented 2 months ago

small things separated them, because communication breaks down completely. does not work until HA restart

kukulich commented 2 months ago

What's the type of your HA installation?

RGB666 commented 2 months ago

I am running HA on proxmox server (mini PC)

kukulich commented 2 months ago

I don't have any problem on HaOS so I expect it is a problem in virtualization settings.

RGB666 commented 1 month ago

My Jablotron-HA communication stops during the night. In the morning the automatic disarm signal (programmed in the Jablotron calendar) is missed each day. Somewhere during the morning the signal suddenly is recovers at a random time. As all other HA communication have no problems during the night and morning and the Jablotron is connected by a USB port, I have the feeling the USB port goes into a sort of standby/sleep/hibernation mode.(it's or a he usb, or proxmox or the Jablotron hardware itself) I am running HA on a proxmox server. Who can help me debugging my system? How can I check /debug the USB port communication settings?

stewe12 commented 1 month ago

I have the same problem since my installation technician updated Jablotron main unit to the latest version firmware. When Jablotron sends some pointless SMS with battery status, it also changes /dev/hidraw0 to /dev/hidraw1 or the other way. I need to go to integrations and reconfigure the integration. Really annoying feature of the Jablotrons new update.

woodrook commented 1 week ago

Same problem for me since first jablotron integration more than one year ago......randomly integration status change to "unavailable"

I don't no why but I use spook to detect "unavailable" status and reload the integration.

It's a workaroud but it works well. Despite this a fix would be better

kukulich commented 1 week ago

@woodrook The problem is probably in your installation, not in the integration.

woodrook commented 1 week ago

May be but i don't thik so, i've just enabled debug logging

RGB666 commented 1 week ago

Still have the problem as many others.

mkapusnik commented 1 week ago

I encountered the same issue when I moved my HA installation to RPi5 (running in docker on top of raspbian bookworm). Port started to randomly switch between /dev/hidraw0 and /dev/hidraw1. Everytime this changed, integration stopped responding. Previously, I was running it on RPi4 (docker, bullseye) and it was rock stable. I came up with a workaround to spin up HAOS on some older RPi3 and propagated the sensors through "Remote HA" addon to my main instance. Kinda weird setup, I know, but worked reliably. There was no change of the jablotron firmware that I know of, so it does seem somehow related to the underlying system/hw.

Anyway, I updated to recently released 3.26.0 and gave it another try on RPi5 (docker,bookworm). Running stable for about two days now, looks promising.