-
Notifications
You must be signed in to change notification settings - Fork 49
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
Homematic IP Devices with Battery Levels are not recognized #24
Comments
Polite bump |
You might be able to use this info from the help
|
@pschneider87 did you ever get this working? Pay attention to the battery value is 2.7 for the second entity, so value should evaluate to 5.4 instead of 2?
After looking at the source code I understood that I have to write these rules for the source entity, not the generated one. @notoriousbdg maybe you want to rephrase the description in your script. So for who else is dealing with this, here is what works for me:
homeassistant:
customize:
climate.bad_heizstellglied:
battery_template: "{{ ((value_json.value | float - 2.2) / (3.1-2.2) * 100) | int }}"
climate.schlafzimmer_heizstellglied:
battery_template: "{{ ((value_json.value | float - 2.2) / (3.1-2.2) * 100) | int }}"
climate.wohnzimmer_wandthermostat:
battery_template: "{{ ((value_json.value | float - 2.2) / (3.1-2.2) * 100) | int }}"
sensor.wohnzimmer_wandthermostat_humidity:
battery_sensor_creation_disabled: true
sensor.wohnzimmer_wandthermostat_temperature:
battery_sensor_creation_disabled: true Be aware that these templates are not immediately evaluated. It can take some time till the source entity sends a new battery value and thereby triggers the rule. |
First: awesome work, it's the best battery alert solution I found on the internet.
My issue: I have a bunch of Homematic IP Devices with Battery Info.
At the Moment, all of them report "Normal" as state, but no integer that's why I believe they are not recognized by the script and hidden in the UI
And I think they won't trigger an alert.
How could I solve this?
The text was updated successfully, but these errors were encountered: