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’)
what card should i be using to show all batteries that are “low” (ive set min to 97 and max to 100 just to give me some results). Note: notifications seem to be working, but i cant work out the card to use?
Running HassIO: 0.92.2 - system health below.
Running Mosquitto broker, where I have enabled the add-on with the following settings.
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
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.
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:
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…
No, none, and the battery sensors are there, I do get warnings, I just don’t see the ‘overview’ card of all the sensors. Do I have to add them manually to a glance card, or?
I’m not sure if that changes anything, but it looks like some of the controllers popped up that were missing.
Just to be clear, the ‘overview’ I’m talking about is this one:
I’ve changed the Lovelace UI to my own setup, instead of the autogenerated, so I guss that could also be why it’s not showing?
Let me rephrase… have the settings in such a way that if you have a new version of the file and i download it, that i don’t have to put my settings in again. Perhaps if you have like a main package and do an include or set some vars. That way we only have to update the main package and the settings are kept. (or am i doing it wrong?)
Yes, if you’ve customized Lovelace UI, then you’ll need to configure Lovelace to show them however you wish. Someone posted an example earlier in this thread that should make it easy. I don’t have any experience customizing Lovelace, so I can’t really offer much guidance.
You shouldn’t lose settings on upgrade unless there is a breaking change. What settings did you lose? Do you know which versions you upgraded from and to?
Ok, great, that was just what I wanted to know, the automatic showing only works for the non-customized UI.
So I found the post by @Three with the custom group-card, and that makes it show the sensors immediately, very nice, thankyou @Three
I can see I have quite a few dublets, so I guess I could delete them, and they will pop up again?
Looking in mqtt, I can see a lot of messages about deleting sensors, but I don’t see them being deleted?
This is one;
I haven’t sent this one, so it’s something the battery sensor thingy is trying to do itself. But I don’t see them being deleted?
EDIT: Hmm, not sure what happened, I just tried it again, deleting battery sensors, and now they are deleted perfectly, weird?
EDIT2: Ahhh, trailing spaces, when copying from the sensor view, it sometimes takes an extra space, and that will make it fail.
