Closed killer0071234 closed 1 year ago
I cannot see any LOWBAT events in your logs. As long as the CCU doesn't send these events we cannot display it.
ok, but how can i get / enable it?
Remove the battery of a device?
Remove the battery of a device?
That won't work. This would result in an UNREACH event, that marks the device unavailable in HA.
Hard to test.
Thats right, i just tested it. The only thing what i got (with the same batteries re-installed) was for 2 seconds the low battery. For me it seems that the CCU is reporting the low battery if it's really pretty low.
2023-01-05 22:08:56.465 DEBUG (XmlRpcServer on port 39731) [hahomematic.central_unit] event: interface_id = RaspberryMatic-BidCos-RF, channel_address = KEQ0513695:0, parameter = LOWBAT, value = True
2023-01-05 22:08:56.466 DEBUG (XmlRpcServer on port 39731) [hahomematic.entity] event: RaspberryMatic-BidCos-RF, KEQ0513695:0, LOWBAT
2023-01-05 22:08:58.598 DEBUG (XmlRpcServer on port 39731) [hahomematic.central_unit] event: interface_id = RaspberryMatic-BidCos-RF, channel_address = KEQ0513695:0, parameter = LOWBAT, value = False
2023-01-05 22:08:58.599 DEBUG (XmlRpcServer on port 39731) [hahomematic.entity] event: RaspberryMatic-BidCos-RF, KEQ0513695:0, LOWBAT
For me it seems that the CCU is reporting the low battery if it's really pretty low.
Thats correct. That's why i added 0.1 V to the warning threshold in the CCU.
Can this be closed here?
Many thanks.
Can this be closed here?
Yes, I close it.
Hi, I know this is already closed but I am still curious:
I got a HM-CC-RT-DN with an almost empty battery. CCU says "Battery empty" (not low) My old Redmatic detects a warning on the data point "FAULT_REPORTING" My HA still won't detect an issue. Are you sure this is an expected behavior ?
cheers Michael
Are you sure this is an expected behavior ?
Yes.
FAULT_REPORTING
is not LOWBAT
Hm, ok, but this is how HM-CC-RT-DN seems to report an empty battery:
Edit: If the datapoint FAULT_REPORTING is set to "6" it means that HM-CC-RT-DN reports an empty battery
Me again: Found it in the eq3 documentation. It's German, hope that is OK https://www.eq-3.com/downloads/download/homematic/hm_web_ui_doku/hm_devices_Endkunden.pdf
FAULT_REPORTING is for HM-CC-RT-DN only. To add FAULT_REPORTING use this.
Many thanks for the infos.
The LOWBAT
from the fault reporting works like a charm.
Many thanks!
DONT'T DELETE THIS.
This is for issues only If you have a feature request, add it as a new discussion, or add your point of view to an existing discussion.
Please answer all questions as good as possible.
Language: as you like -> english/DEUTSCH
Make sure you have read the documentation at https://github.com/danielperna84/custom_homematic#custom_homematic.
Make sure you have read the release notes at https://github.com/danielperna84/custom_homematic/releases.
Make sure you are running the latest version of the custom_component (and Home Assistant) before reporting an issue.
ENSURE that your Backend (CCU/Homegear/...) is working as expected and connected devices are controllable.
custom_component version (if applicable): 1.26.0
known last working custom_component version (if applicable): 1.x.x no one
Home Assistant:
CCU:
Problem-relevant configuration:
Do you use tls? no Do you use callback? no Do you use username and password? yes Which interfaces do you use (hmip/bidcos/wired)? bidcos
Describe the bug A clear and concise description of what the bug is. Low battery alarm (or service message) is not shown in HA.
To Reproduce Steps to reproduce the behavior:
Screenshots (if applicable)
CCU firewall in CCU
device config in CCU
integrations view in HA
device view in HA
entity view in HA
Relevant HA log entries (press full log) VERY IMPORTANT
Diagnostic Information (available on every device)
Expected behavior A clear and concise description of what you expected to happen. The current low battery alarm shall also indicated on the battery diagnostic input of the device.
Additional context Add any other context about the problem here.