For Netherlands; Sensor for hoog tarief and laag tarief that reacts as a switch

Thank you all for your replays.
Will look for the best sullotion as soon as I did update my own knoledge on templating and grouping in HA

Hello,

Maybe I should start a new tread, but you help was so good so far that I continiu with this one.
I strarted splitting up my configuration to have it better organized.

My frontend looks like this:

Il try to add some groups now. And would like everything for now on 1 page.

my 1_wire.yalm looks like this:

1-wire:
  view: true
  name: 1-wire
  entities:
    - sensor.28-000b9843014a: CV retour
    - sensor.28-0018984319ae: CV in
    - sensor.28-00259843166c: Voor-zolder
    - sensor.28-000e9843218b: Boiler top

My configuration.yalm looks like this.
homeassistant:
# Name of the location where Home Assistant is running

  # Location required to calculate the time the sun rises and sets
  latitude: 
  longitude: 
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  # 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: Europe/Amsterdam
# Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
#introduction:

# Shows groeps
group:

# Enables the frontend
frontend:

# Enables configuration UI
config:

duckdns:
  domain: 
  access_token: 

#http:
#
# Uncomment this if you are using SSL/TLS, running in Docker container, etc. 

#http:
#   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:

mqtt:
  broker: 
  port: 1883


# 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:

ifttt:
  key: 
  
sensor:

switch:

#Track Iphone's 
device_tracker:

climate:
  - platform: toon
name: Toon Thermostat
host: 
port: 10080
scan_interval: 10

water_heater:
  platform: demo

# Text to speech
tts:
  - platform: google


# cloud:

#camera:
#  - platform: foscam
#    ip:  
#    username:
#    password: 

group: !include_dir_merge_list group/
script: !include_dir_merge_list scripts/
sensor: !include_dir_merge_list sensor/
zone: !include_dir_merge_list zone/
switch: !include_dir_merge_list switch/
device_tracker: !include_dir_merge_list device_tracker/
automation: !include_dir_merge_list automations/
#customize: !include_dir_merge_list customize/

But I don’t get any new groups visible ?
What am I doing wrong ???

My dir layout looks like this ;

there are 2 group: definitions in your configuration file, one empty and 1 with the correct path.

take out the first and see what happens?

That I only did as a misstake in the file I posted. Sorry.
Did check and now its only the one; group:

Thanks anyway !

Now that section looks like this

# Show links to resources in log and frontend
#introduction:

# Shows groups
group:

# Enables the frontend
frontend:

# Enables configuration UI
config:

duckdns:

Should be the other group: definition though, since you have several files in that folder

sorry, don’t understand what you meen ?

you should have left the

group: !include_dir_merge_list group

in your configuration.yaml because you have several yaml files in the folder /config/group

btw, to prevent confusion you best rename that folder to groups. (always prevent to use HA reserved names for you own variables, in any scenario . )

group: is a default value in HA, so call the folder you save you group configuration files in groups

you probably want groups in the View (tab) and not only single ungrouped sensors or other entities?

In that case do something like my view_tabs.yaml, saved in that same /config/groups folder (and since this folder is defined as group: !include_dir_merge_named groups the format of the groups is without a - for each group

##########################################################################################
# Groups: Views (tabs in Front-end) /config/groups/view_tabs.yaml
##########################################################################################
lights_panel:
  name: Lights
  view: true
  icon: mdi:light-switch
  entities:
    - sensor.lamps_badge
    - group.lights_tiles
    - group.activity_lighting_tiles

ikea_tradfri_system:
  name: Ikea Trädfri
  view: true
  icon: mdi:lightbulb
  entities:
    - group.ikea_tradfri_groups
    - group.ikea_tradfri_lights
    - group.ikea_tradfri_hub
    - group.ikea_tradfri_automations
    - group.ikea_tradfri_sensors
    - group.ikea_tradfri_remotes

philips_hue_system:
  name: Philips Hue
  view: true
  icon: mdi:ceiling-light
  entities:
    - group.hue_light_control
    - group.light_automations
    - group.light_effects
    - group.philips_hue_groups
    - group.philips_hue_lights
    - group.philips_hue_lights_reachable
    - group.philips_hue_hub
    - group.philips_hue_sensors
    - group.philips_hue_rest_sensors
    - group.philips_hue_switches

all mentioned groups here are declared elsewhere in my configuration files, either in dedicated group files, or in packages.

# Show links to resources in log and frontend
#introduction:

# Shows groups
#group:

# Enables the frontend
frontend:


group: !include_dir_merge_list groups/
script: !include_dir_merge_list scripts/
sensor: !include_dir_merge_list sensor/
zone: !include_dir_merge_list zone/
switch: !include_dir_merge_list switch/
device_tracker: !include_dir_merge_list device_tracker/
automation: !include_dir_merge_list automations/
#customize: !include_dir_merge_list customize/

and changed the map from group -> groups

Is that what you meen ?

yes, that’s what I tried to say… :wink: im not sure about the trailing / after the folder names. I don’t use that, but havent tried it either. If it still doesn’t work, you could take them out to see what happens.

then about this:

Preformatted text`1-wire:
  view: true
  name: 1-wire
  entities:
    - sensor.28-000b9843014a: CV retour
    - sensor.28-0018984319ae: CV in
    - sensor.28-00259843166c: Voor-zolder
    - sensor.28-000e9843218b: Boiler top

if that is truly the content of your file, I think that is not going to work, since the name of the View (your tab to be) has no underscores to tie the words. It should at least be

preformatted_text_1_wire:
  view: true
  name: 1-wire
  entities:
    - sensor.28-000b9843014a # CV retour
    - sensor.28-0018984319ae #CV in
    - sensor.28-00259843166c # Voor-zolder
    - sensor.28-000e9843218b # Boiler top

what are the sensor names in your configuration? show them in dev-state please, I fear your names are all incorrect… always use underscores _ instead of the - to brake names. and use the # for comments in your files (everything after a # isn’t used by Hassio and only there for you for documenation/ Use a good text editor that shows the files in correct syntax (I am on a Mac and use BB-editor.)

I made the chanches you suggested, no result

I just don’t get the extra tab’s ???

the other tab thats in the map groups looks like this;

Smart meter:
  view: true
  name: Smart meter
  entities:
#   - sensor.toon_gas_used_last_hour
#   - sensor.toon_gas_used_cnt
    - sensor.toon_power_use_cnt
    - sensor.toon_power_use
    - sensor.toon_p1_power_prod_low
    - sensor.toon_p1_power_prod_high
    - sensor.toon_p1_power_prod_cnt_low
    - sensor.toon_p1_power_prod_cnt_high
    - sensor.toon_p1_power_use_cnt_pulse
    - sensor.toon_p1_power_use_cnt_low
    - sensor.toon_p1_power_use_cnt_high
    - sensor.toon_p1_power_use_low
    - sensor.toon_p1_power_use_high
    - sensor.toon_p1_power_solar
    - sensor.toon_p1_power_solar_cnt
    - sensor.toon_p1_heat

and does not show neither.
They both stay on the top ass singele sensors as you can see on de screenshot of the frontend.

The names of the 1-wire sensors I took from the map sensor with the file 1-wire.yalm (see here) and that works.

#1-wire temperature messurements
- platform: onewire
  names:
    28-000b9843014a: CV retour
    28-0018984319ae: CV in
    28-00259843166c: Voor-zolder
    28-000e9843218b: Boiler top

PS I think I got duckdns working now

try:

smart_meter:
  view: true
  name: Smart meter
  entities:
#   - sensor.toon_gas_used_last_hour
#   - sensor.toon_gas_used_cnt
    - sensor.toon_power_use_cnt
    - sensor.toon_power_use
    - sensor.toon_p1_power_prod_low
    - sensor.toon_p1_power_prod_high
    - sensor.toon_p1_power_prod_cnt_low
    - sensor.toon_p1_power_prod_cnt_high
    - sensor.toon_p1_power_use_cnt_pulse
    - sensor.toon_p1_power_use_cnt_low
    - sensor.toon_p1_power_use_cnt_high
    - sensor.toon_p1_power_use_low
    - sensor.toon_p1_power_use_high
    - sensor.toon_p1_power_solar
    - sensor.toon_p1_power_solar_cnt
    - sensor.toon_p1_heat

please show these sensors in the dev-state and front-end? (make a screenshot of the pages ) i havent seen a platform/sensor definition like this before, so am curious for the results this has.

ok, so that’s working alright,

did you already try the view definition I posted above?

what is the difference with mine except a non capital S to start with

Please read carefully, both your config and people’s replies :wink:

You should have an underscore _

smart_meter:

Instead of

Smart meter:

Thanx for your thoughts, but got it right like this from the developers site on github

that is a typo.
but, if you want to persist, feel free…

tryed it, no difference

did you in fact restart between changes? and you did change the name of the folder group to groups?

I’m not sure where to go now.
What is the content of the 2 files you showed in the screenshot, 1_wire.yaml and smart_meter.yaml?

also, where are the groups declared you show? Schakelaar, Licht, Klimaat?

in the folder groups you should have files that either declare regular groups, or groups with the view: true (which are the tabs)

also there is a special group called default view, which is the hand made home page, and prevents HA showing all entities and groups on the home page (which it does if you don’t have a default_view )

maybe this helps:

I did restart eatch time after making a change.

The Dutch names of the groups (tabs) that are showen, probably are made by HAS becourse I have chosen Dutch view.

The files 1-wire and smart_meter, do you meen the one’s in groups or in sensors ? The one’s in sensors do accutaly do what they should do (;

I started accutaly like you probrely meen, to start with a blank frontend and make/fill every group myself

Could you please show me your default_view.yaml ?

Could it be, that somewhere HAS has a standaard frontend.yalm or something ? when I put a # in front of “switch: !include_dir_merge_list switch” the tab with the switches is gone. The same with sensor