fluefiske
(André Van Stijn)
May 24, 2017, 12:22pm
1
Hello all,
Don’t lauch at me but I am a real noob in programming but wanna try anyhow.
I tried to show a sensor value on the ui home screen but what I do I get an error messag please advice
I tried the following code:
customize:
- sensor.aeotec_zw100_multisensor_6_temperature_5_1
This results in the following:
Adding some lines to the group.yaml
group:
default_view:
view: yes
entities:
group.Main_Floor
Main_Floor:
name: Main Floor
entities:
sensor.aeotec_zw100_multisensor_6_temperature_5_1
results in not starting at all, please advice
ih8gates
(Scott Reston)
May 24, 2017, 12:27pm
2
Use preformatted text when posting YAML.
Tips for new HASS/forum users. Help me out - what did I miss?
Posting your configuration
When you post your configuration, we need to see that you’ve got the spacing/indentation right. Use the “preformatted text”
[image]
YAML tips
YAML can be a harsh mistress. Spaces matter, tabs can break things. Here’s a post with some tips for editing YAML with Notepad++
What Home Assistant install method should I use?
If you’re pretty technical, use whatever works for you. Docker, NAS, All-in-one, Has…
That code for customize doesn’t look right. Assuming that’s customize under your homeassistant: block. Customize code looks like this:
customize:
switch.garage_ceiling_switch_29_0:
friendly_name: Garage Ceiling
fluefiske
(André Van Stijn)
May 24, 2017, 12:53pm
3
Thank you for your quick reply,
I changed the settings of note++ as recommended and changed the code i:
Still not succesfully, for the record I am using Home assistent 0.45.1 running on docker in a Synology 1515+
Thank you for the assistance
ih8gates
(Scott Reston)
May 24, 2017, 12:57pm
4
Are you still seeing the “invalid config” message in your HA interface? What error do you see in home-assistant.log?
fluefiske
(André Van Stijn)
May 24, 2017, 1:06pm
5
This is a copy of the log:
2017-05-24 13:02:38 ERROR (MainThread) [homeassistant.loader] Unable to find component customize
2017-05-24 13:02:38 ERROR (MainThread) [homeassistant.setup] Setup failed for customize: Component not found.
2017-05-24 13:03:07 WARNING (MainThread) [homeassistant.helpers.entity] Update for media_player.woonkamer is already in progress
This is a list of states of my multisensor:
sensor.aeotec_zw100_multisensor_6_alarm_level_5_1 0 node_id: 5
friendly_name: Aeotec ZW100 MultiSensor 6 Alarm Level
sensor.aeotec_zw100_multisensor_6_alarm_type_5_0 0 node_id: 5
friendly_name: Aeotec ZW100 MultiSensor 6 Alarm Type
sensor.aeotec_zw100_multisensor_6_burglar_5_10 0 node_id: 5
friendly_name: Aeotec ZW100 MultiSensor 6 Burglar
sensor.aeotec_zw100_multisensor_6_luminance_5_3 103.0 node_id: 5
unit_of_measurement: lux
friendly_name: Aeotec ZW100 MultiSensor 6 Luminance
sensor.aeotec_zw100_multisensor_6_relative_humidity_5_5 41.0 node_id: 5
unit_of_measurement: %
friendly_name: Aeotec ZW100 MultiSensor 6 Relative Humidity
sensor.aeotec_zw100_multisensor_6_sourcenodeid_5_2 0 node_id: 5
friendly_name: Aeotec ZW100 MultiSensor 6 SourceNodeId
sensor.aeotec_zw100_multisensor_6_temperature_5_1 25.8 node_id: 5
unit_of_measurement: °C
friendly_name: Aeotec ZW100 MultiSensor 6 Temperature
sensor.aeotec_zw100_multisensor_6_ultraviolet_5_27 0.0 node_id: 5
friendly_name: Aeotec ZW100 MultiSensor 6 Ultraviolet
sensor.yr_symbol 4 attribution: Weather forecast from yr.no, delivered by the Norwegian Meteorological Institute and the NRK.
friendly_name: yr Symbol
entity_picture: //api.met.no/weatherapi/weathericon/1.1/?symbol=4;content_type=image/png
ih8gates
(Scott Reston)
May 24, 2017, 1:17pm
6
Are you sure you’ve got “customize” in the right place? It should be a child of homeassistant: – not a sibling.
homeassistant:
customize:
switch.garage_ceiling_switch_29_0:
friendly_name: Garage Ceiling
fluefiske
(André Van Stijn)
May 24, 2017, 1:27pm
7
Yes I did it right:
After this didn’t work I tried this:
Also didn’t work, the error log didn’t show anything and the failure is not present anymore neigther the sensor value?
fluefiske
(André Van Stijn)
May 24, 2017, 1:35pm
8
To be clear this is my goal
This is the current view
cgtobi
(Tobi)
May 24, 2017, 2:06pm
9
Customize seems to work.
Do you have group: !include group.yaml
in your configuration.yaml
?
fluefiske
(André Van Stijn)
May 24, 2017, 2:08pm
10
Hey Tobi,
Yes I have, it looks like this:
group:
multisensor:
- sensor.aeotec_zw100_multisensor_6_temperature_5_1
- sensor.aeotec_zw100_multisensor_6_ultraviolet_5_27
- sensor.aeotec_zw100_multisensor_6_relative_humidity_5_5
- sensor.aeotec_zw100_multisensor_6_luminance_5_3
- sensor.aeotec_zw100_multisensor_6_burglar_5_10
- sensor.aeotec_zw100_multisensor_6_alarm_type_5_0
However it gives an error
fluefiske
(André Van Stijn)
May 24, 2017, 2:09pm
11
Customize did not work this is just a sample of what I would like to achieve
lambtho
(Lambtho)
May 24, 2017, 2:19pm
12
Try with
group:
default_view:
view: yes
icon: mdi:home
entities:
- group.multisensor
multisensor:
control: hidden
name: Multisensor
entities:
- sensor.aeotec_zw100_multisensor_6_temperature_5_1
- sensor.aeotec_zw100_multisensor_6_ultraviolet_5_27
- ...
check this for a complete description of what you should do to group things properly
lambtho
(Lambtho)
May 24, 2017, 2:22pm
13
On your current view, there is a sensor called “Zolder Temperature”, so I assume it works. Your problem is when you try to group your configurations rather than customize I think
cgtobi
(Tobi)
May 24, 2017, 2:49pm
14
And please learn how to format code. This makes life easier for everyone.
I had the same issue where the sensor.aeotec_zw100_multisensor_6_XXXX dispeared after upgrading. I’m still working to get it back I was able to get some sensors back but the burglar sensor seems to be gone.
fluefiske
(André Van Stijn)
May 24, 2017, 7:17pm
16
Thank for sharing, I am until now not able to see any of them in a group, I changed the groups.yaml file as sugested however the error stays in the home screen.
This is the code I used:
group:
default_view:
view: yes
icon: mdi:home
entities:
- group.multisensor
multisensor:
name: Multisensor
entities:
sensor.aeotec_zw100_multisensor_6_luminance_5_3
ih8gates
(Scott Reston)
May 24, 2017, 7:21pm
17
It looks like you’ve got something fundamentally wrong with your configuration.yaml. Or a bad install.
Most of the times where someone sees “component not found” type messages, it’s due to putting a component/key in the wrong place.
Could you post your full YAML, redacting personal stuff. Use preformatted text, not an image.
fluefiske
(André Van Stijn)
May 24, 2017, 7:28pm
18
Thank you for looking deeper into it.
This is my 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: [redated]
longitude: [redacted]
Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 1
metric for Metric, imperial for Imperial
unit_system: metric
customize:
sensor.aeotec_zw100_multisensor_6_luminance_5_3:
friendly_name: Licht Sensor
Show links to resources in log and frontend
introduction:
Enables the frontend
frontend:
Enables configuration UI
config:
http:
Uncomment this to add a password (recommended!)
api_password: [redacted]
Uncomment this if you are using SSL or running in Docker etc
base_url: [redacted]:8123
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:
Track the sun
sun:
Weather Prediction
sensor:
platform: yr
Text to speech
tts:
platform: google
#zwave
zwave:
usb_path: /dev/ttyACM0
group: !include groups.yaml
automation: !include automations.yaml
fluefiske
(André Van Stijn)
May 25, 2017, 6:26am
20
Sorry, I am so noob that I don’t know how to do it so I re-installed Home assistent at another “method used by philhawthorne” and now it is working. Somewhere during the installation something wen’t wrong I think, anyhow everyone thank you for helping me out. I am sure I will ask you in the future some other lame question
Kind regards,
André