I´m not 100 % sure if it´s related to the update to 0.118.4 or the CLI update (at least those´ve been changes I did today), but suddenly a sensor configured in configuration.yaml disappeared:
sensor:
- platform: command_line
name: Pi-Hole Status
scan_interval: 10
command: curl -X GET 'http://192.168.0.1/admin/api.php?status'
value_template: >
{{ value_json.status }}
Can anybody point me into the right direction to debug and fix this?
Does it still appear in developer tools|states?
No it doesn’t 
Why not use the PiHole Integration?
It will be what you called your phone in the Android Companion App. You should also be able to look it up under Config / Integrations / Mobile App
I just implemented that on my 0.118.4 system and it works just fine.
I am not sure what you mean by
Mixed that up with https://github.com/home-assistant/cli but I guess the sensor does not use that cause it’s for HA management. Wrong way.
What does your log say?
Very interesting:
I guess it’s not update related. I added two more sensors yesterday. I think I have an error in my configuration.yaml:
I have 3 sensor snippets in there:
43/1st Pi-hole sensor
76/2nd Router netstat sensor
85/3rd Router callstat sensor
For some reason only the 3rd one is working/available in HA. Last one wins?
The referenced lines (+1) and code blocks all start with:
sensor:
- platform: ...
...
Where’s the error? Do I need to specifiy a sensor name right in the first line, e. g. „sensor NameOfSensor:“? Just a wild guess.
It’s saying you have “sensor” listed multiple times. You should only have it once and all sensors sit under it
Thanks, will fix that. Still new to all that YAML stuff.
After upgrading to 0.118.4 my Netatmo Integration went completely havok. First, about 50% off all my Netatmo sensors were reported as “unavailable”, then after several attempts to debug, including restart, delete the Netatmo Integration, and re-create the Netatmo integration again, and again - I left it overnight and today all Netatmo sensors were “unavailable”. But the camera works as it should. No Netatmo information at all in the log.
So, I gave up and reverted back to 0.118.3 and now everything is back to normal.
Then I re-launched 0.118.4 and now all is well (!)
I’m running the docker HA Core container image on a QNAP NAS.
Netatmo have some technical issues with their API services today:
WTH is the Ad at the Config Dashboard?!
In the Ad is a link to https://www.home-assistant.io/conference
How can I get rid of this Banner?
Press the X on the banner.
Did this. Please don’t do this ever again.
Or bring a privacy-friendly, ad-free “Pro” Version.
Simmer down and read the release notes about it: https://www.home-assistant.io/blog/2020/11/18/release-118/#edit-we-all-hate-ads-but-we-do-like-to-show-off-our-users
There is no plan for an advertisement supported version.
I read that.
Thanks @tom_l
I read that before, but overlooked the passage.
Comforting to know that the core team is clear about the implications.
@mirekmal - thank you so much for this info (which I was completely unable to find myself).
It is so frustrating to have spent now almost two full days trying to find the cause of the problem, just to learn that yet again one of these cloud services failed and caused it all. I have sensitive and delicate equipment monitored and controlled by HA based on temperature and humidity readings.
It just proves how stupid I am to choose cloud services at all.
Is there any way to configure and use these Netatmo devices without having to go through their cloud?
If not, are there any other devices out there which can do the same, without cloud integration?
