OK… so I updated Hassio and various add-ons today. The Overview screen in both the Ios app and on my PC browser show an extra switch that is not defined in my configuration.yaml I have 2 switches defined- one controls a sonoff outlet and the “driveway silence” controls a pin on an ESP8266 that is integrated to sensor on my .8 mile long driveway. My configuration.yaml is below
Err- this may be my point of confusion. I haven’t followed the Lovelace aspect of HA / Hass to closely and am ignorant by definition. I’ll be searching for a good “how-to” next.
Where would I need to include the ‘show_header_toggle: false’? In my configuration.yaml?
control: hidden is only part of the group config - see the doc I referenced however the errors you have are all going to be entity_id’s that are invalid… look for 2 underscores or underscores at start or end of entity name and fix. Also look at automations and look at time changes in release notes.
when you have HA starting with no errors, then worry about the small stuff…
I was error free before modifying the group.yaml & removing the ‘control: hidden’ from group.yaml took the errors away.
My installation is super basic with only the few switches that I mention & the ios enabled for the app. This group switch only came about with the most recent update- it worked as it should prior to that.
I can confirm that my .HA_Version is 0.86.1
groups.yaml is empty
I’ll post my config.yaml at the bottom of this post.- but its basic.
I took a bit of time to look @ the Lovelace UI documentation here: https://www.home-assistant.io/lovelace/ and - it does look cool but, my UI does not have the cards etc. It appears as it has in “classic” home assisitant.
homeassistant:
Name of the location where Home Assistant is running
name: Home
Location required to calculate the time the sun rises and sets
latitude:
longitude:
Impacts weather/sunrise data (altitude above sea level in meters)
Wow! you really need to learn to format your code correctly. there’s no way most people will try to read thru that to decipher what is relevant to your problem.
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude:
longitude:
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 216
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: America/Chicago
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
#introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
http:
# Secrets are defined in the file secrets.yaml
api_password: *******
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# base_url: example.duckdns.org:8123
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time
history:
# View all events in a logbook
logbook:
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Weather prediction
#sensor:
# - platform: yr
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
# THIS IS FOR THE IOS APP TO WORK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ios:
# THIS IS FOR THE MQTT BROKER TO WORK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
mqtt:
# discovery: true
# discovery_prefix: homeassistant
broker: core-mosquitto
port: 1883
username: '******'
password: '*****'
sensor:
- platform: mqtt
name: "Doorbell"
state_topic: "doorbell"
expire_after: 10
- platform: mqtt
name: "Loft Temperature"
state_topic: "Loft Temperature"
- platform: mqtt
name: "Loft Humidity"
state_topic: "Loft Humidity"
- platform: dht
name: "Main Level"
sensor: DHT22
pin: 11
temperature_offset: 1.58
humidity_offset: 3.4
monitored_conditions:
- temperature
- humidity
switch:
- platform: mqtt
name: "Driveway Silence"
state_topic: "state/doorbell"
command_topic: "doorbell/commands"
payload_on: "Audio Doorbell"
payload_off: "Silent Doorbell"
retain: false
- platform: mqtt
name: "sonoff"
state_topic: "stat/sonoff/POWER"
command_topic: "cmnd/sonoff/POWER"
payload_on: "ON"
payload_off: "OFF"
retain: true
# optimistic: false
# qos: 0
It was set as the default on v86. to go back to the old ui you can (or should be able to…) go to the info buitton in the dev panel (bottom right) then at the bottom of that page you can switch to the old view.
but for future proofing you should start to look into how to get your setup “officially” switched over to lovelace. there are at least 3 ways that I know of that you can use to get there: yaml, auto, & thru the GUI.
I only use yaml since it is the closest to the “old” way of configuring the frontend. read up on the different ways and start making the switch. It isn’t too bad.
Finity- you are correct. This solved the issue that I posted about initially- basically making v86 “look like the way it used to”. This helped me a lot because I’m troubleshooting a remote arduino that I’m sending MQTT commands with the switch.
