Closed zlymeda closed 10 months ago
Is there anything that can changed in your Jablotron? User rights, pin code ? New device?
Is there anything that can changed in your Jablotron? User rights, pin code ? New device?
none that I know of. however, I noticed yesterday that none of my motion sensors were updated in like 7 hours, even though I was present and moved around a lot. But, what I noticed was that one motion sensor was unavailable. It is battery-powered. So now when I think about it... maybe the battery is dead and that is why no packet can be received.. is it possible?
I though I would see some warning or something in the official Jablotron app, but nope. now I think it might be a dead battery, I will try to check that now.
if that is the case and charging the battery would work, then maybe it would be nice not to crash if the packet is not received, but mark the sensor unavailable if possible - I might even make a contribution if that is the case and I would be able to figure it out :)
I will keep you posted.
@zlymeda
You can try to change the type of the device in Jablotron integration to "empty", so the position will be ignored. You will see if HA the integration will work then.
@kukulich
so unfortunately that did not work. I tried changing everything to Empty expect one device, but still had the same problem.
@zlymeda ok, another idea. Can you change the number of devices? If the broken device is eg. no 8, then change it to 7 devices.
no, still nothing. I will try to debug it in the evening.
@zlymeda Please enable debug of all device packets (in integration options).
@kukulich I was able to debug, find and fix the issue here: https://github.com/kukulich/home-assistant-jablotron100/pull/81
integration now works and no more errors in the logs
Hi,
first of all, thank you for a great integration!
I have been using your component for many months and it was working nicely. Sometimes I faced the below issue and restarting the machine usually fixed it. But not this time. No matter what I do - restart HA, restart machine, this error never goes away. There was no particular change that I know of. I was using version
3.21.0
.I noticed that the permissions were root read/writable so I changed that:
Can you figure out what is the problem from the incoming pockets?
Thanks a lot