That sounds like it might be related to the migration to Lovelace. It doesn’t like when your groups refer to entities that don’t exist. You’ll need to remove them from your groups to fix those.
The automation that adds battery entities to the group runs once a minute now instead of at startup. It’s possible that if you view the UI before the first time the automation runs, your battery entities will not be in the group yet. Refreshing the page in your browser should fix that.
Thank you, All is working now with your latest code
Hi,
it seems great but I don’t know how to install this …
Is the first post is up to date with the latest code ?
Is there an howto that I missed ?
I can’t update the OP anymore. You can find the latest on GitHub at:
Not sure when it changed, but I’m able to edit the OP. I’ve added a link to GitHub in the OP to make it easier for people to find the latest version.
Sorry! ive been playing with this and read a load of topics, but im still stuck!
im seeing this log error
Wed May 15 2019 10:40:33 GMT+0100 (British Summer Time)
Error while executing automation automation.battery_sensor_from_attributes. Service not found for call_service at pos 1: (ServiceNotFound(…), ‘Service mqtt.publish not found’)
Running HassIO: 0.92.2 - system health below.
Running Mosquitto broker, where I have enabled the add-on with the following settings.
{
“logins”: ,
“anonymous”: false,
“quiet_logs”: true,
“customize”: {
“active”: true,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}
mqtt: discovery: true discovery_prefix: homeassistant
- alias: Home Assistant Startup
id: Home_Assistant_Startup
trigger:
- platform: homeassistant
event: start
action:- service: notify.notify
data:
message: Home Assistant is up
RPi info
System Health
arch armv7l dev false docker true hassio true os_name Linux python_version 3.7.3 timezone Europe/London version 0.92.2 virtualenv false Lovelace
mode storage resources 0 views 9
hey, how did you add this “low battery levels” card?
That suggests that MQTT isn’t working. Check your logs to see if you can figure out why MQTT isn’t working
That is the persistent notification that’s automatically created by the package.
Thanks for the reply
so MQTT seems to be working ok now.
Sorry, for the 2nd item - i want to show a card, that has all the “low” battery levels shown only - how do i do that?
[NotoriousBDG] do you have plans to add your wonderful work into custom updater? So everyone can automatically have the latest version.
I have the same problem, and I did use the raw link to copy/paste the content of the battery_alert.yaml file. Also tried to download the file from Github and use that one.
Invalid config for [automation]: required key not provided @ data['action']. Got None
required key not provided @ data['trigger']. Got None. (See ?, line ?). Please check the docs at https://home-assistant.io/components/automation/
First lines of the configuration.yaml:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: !secret home_latitude
longitude: !secret home_longitude
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: !secret home_elevation
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: !secret timezone
customize: !include customize.yaml
packages: !include_dir_named packages
auth_providers:
- type: homeassistant
Thanks! 
That’s not a native feature of the package today. Today it only does persistent notifications and notifications. I can look to add that in a future release.
AFAIK, the custom updater doesn’t support packages. Once it does, I can look at what it would take to add it.
While on the raw link, https://raw.githubusercontent.com/notoriousbdg/Home-AssistantConfig/master/packages/battery_alert.yaml, right click and click save as.
Thanks for the reply. The copy/paste wasn’t the issue. After some debugging, I found the problem.
The package has a conflict with the following line in configuration.yaml:
# automation: !include automations.yaml
For me this is an empty file because I use Node-RED.
I’ve seet this very very cool system up from your examples.
It works very very well, and gives me a lot of great info.
One thing though, ONE of my trådfri controllers (an on / off switch) does not show up on the overview.
I do see the warnings, I’ve changed batteries in it, but for some reason it’s still at 11% which is odd.
Looking in the states I see this:
Battery sensors don’t usually update immediately. Is it still showing 11%?
Hi there
Yes, I guessed that it didn’t update that frequent from the other items that has gotten new batteries, but it’s steady at 11%, and has been like that for weeks.
I had this same issue, and then realized I had changed ikea batteries… all from a new package. apparently they were practically depleted, although the expiry date wasn’t near. Changing to a bigger battery brand immediately made the difference…these sensors and switches update immediately after that. could that be the case in your setup too?
it is remarkable how quickly the Ikea sensors deplete their batteries, while the Philips sensors stay at 100% for over 2 years now…
Ok, swapped the batteries to Maxell, and it now shows 100% in the sensor.
But in the ‘battery monitor’ overview, I don’t see the battery sensor shown.
I seem to have lost the overview of the batteries that I monitor with this clever addition, is there an easy way to get it back?
Do you see any errors in the logs?
