Devices : Battery level unavailable for the JA-180W #110
Comments
You can enable debug mode, see README, and send packets for the relevant device. It may be possible to fix it then.
It may be possible only by more complicated integration settings.
I think it's situation nobody expected :) I can check source, if it's possible to fix it. |
|
Hi, Thanks for answering. I enabled the logs as explained in the README file, but I don't really understand how I can tackle only the logs from the device events you would be interested in. Currently, the checked params are "Log all incoming packets" and "Log devices packets". The current logs that are displayed are: 2025-01-10 13:32:57.687 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron100] Incoming: 5203820113 Is it helpful ? What else do I need to do ? Regarding your last comment about the empty device, OK, thank you for checking, let me know if I can help you with something. Thanks a lot! |
This is log for device 6. So I need logs for the relevant device. I expect the relevant packets should start with |
|
The device in question is indeed the device 8. Here are some events that happen when it detects me (there are other devices that appear but I suppose it's not an issue ?). Does it help? /$ tail -f /config/home-assistant.log |
The device should be removed after you upgrade to latest release :) |
Device 7: You can log more if you can find |
|
Thanks a lot for the quick response, I can confirm that with the 3.29.0, the device is indeed removed! Regarding the "90" packets you ask me to get for the device 8, does this mean a packet that STARTS with 90, or ENDS with 90, or something else ? 😄 |
Starts with |
|
Thanks for the clarifications. Unfortunately, I'm not able to get a message from the device 8 that starts with 90. This is what I got, that doesn't end with "0e": 2025-01-10 15:34:45.115 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron100] Incoming (device 8): 550900890002c28aaf0212 Nothing starting with 90 from this device, unfortunately. Does this mean it's not able to report the state of its battery? |
|
Try to wait. Some packets can show only a few times a day. |
|
OK, I'll keep you posted! |
|
Hi, I now have a lot of logs from Jablotron, but unfortunately, no one that start with 90 for the device 8 😢 Does this mean that we're out of luck? I'm gonna let the logs run a few more days just to be sure but I'm not too optimistic. |
Yes, it looks so. |
|
I don't know if it helps, but I think I found another bug. If you configure a device type then change it, then the sensors that are not provided anymore (and maybe some diagnostics ? I'm not sure) are not removed. For instance my keypad was first set up as a door opening detector (because I did not see there was a "jump" in my positions), and the door sensor is still there, as unavailable. I therefore deleted it manually, but I don't know if this means that it doesn't add the new sensors neither. |
Hi,
Thanks for this great integration !
I added all my devices, and I can see the events being triggered for them, but one of my motion detectors doesn't report its battery level; instead, it says "Unavailable".
For my 2 others detectors, it works, but their model is different; the 2 that work are JA-150P, and the one that doesn't is a JA-180W. Is there something I can do about that?
Side questions:
Thanks!
The text was updated successfully, but these errors were encountered: