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

Configuration
41

you should really start with reading about HA and the configuration.

you have no Tabs do you? Thought that’s the whole issue here?

in groups (and be sure you have a folder named groups (not group, as you had before)

the frontend is never blank if you don’t configure a default_view group. Unless you have that, you can’t have an empty frontend.

is of no use for you to do so. It simply is a group with name default_view and view: true, with several groups/sensors of my preference, just like the other views I showed you.

you are most confusing… your question started out how to crest views, and when I showed you how, you ask why they disappear when you comment out the files they are made in. Which is of course as expected to be.

42

thats the thing,

I (think) I do everything like mentioned in the manuels on top.
Only the Licht tab always stais, no mather what I do.
The switches only go away as a tab as soon as I completely disable them.
I have no control what so ever over the front view except the parts that are put in de configuration.yalm by myself (not by HAS like hue).
It just looks like HAS gets its info from somewhere I can’t figure out.
even making a file default_view.yalm like this

group:
  view: true
  icon: mdi:home
  entities:
    - group.smart_meter
    - group.1_wire

in the groups map still giving no change to the frontent what so ever

I just don’t get it anymore.
Even thinking of starting all over again.

:roll_eyes:

43

See the first overview in the first picture

in groups (and be sure you have a folder named groups (not group, as you had before)

44

in groups (and be sure you have a folder named groups (not group, as you had before)

Siepie:

They are already op here with the changes you suggested

45

you are most confusing… your question started out how to crest views, and when I showed you how, you ask why they disappear when you comment out the files they are made in. Which is of course as expected to be.

I think you don’t understand me.
Only if I conpletely disable them from HAS, they disapear. Otherwise they alsways stay tabs, even if they are not mentioned enywhere in groups

46

There are no views/tabs in your Ha front-end anywhere in your screenshots…

See below for tabs, the small icons under the title Main:

image
image750×1334 130 KB

The only tabs in your screenshot are browser tabs…

47

I think I made a big misstake in understanding.

At this moment I think I mixed up tabs and groeps.

I thought tabs are the “bloks” that you can see all at ones. But they are the row of things on top I understand now.

:face_with_raised_eyebrow:

48

So, what I try to do is to get all the groups I want to see on the first tab.
That I treid all the time, with no suc6

49

Correct, those blocks are called Cards.

And show all on 1 page, because you don’t have any Views (tabs) defined, and you don’t have an explicit default_view.

Once you start creating groups with view: true you will see the tabs showed you.

In those View groups you can list other groups that will then show on that Tab.

If you list ungrouped entities like a sensor, they will show as on your current homepage , above any cards in that view.

See:

image
image750×1334 153 KB

50

Hi Mariusthvdb,

Thanx again for all your help and tries.
I think something was really wrong in the bases.
Becourse the automation card is gone aswell and z-wave still did not work, I diceded to start all over (hopefully for the last time) to build everything up in the right order.

Maybe sometime in the furture, I will need your help again. You have been realy patient with me :grinning:

51

I started all over again, and now I found something strange.

I started with a groups.yaml file looking like this.

#Views
  switches_view:
#    view: yes
    name: Schakelaars
    entities:
    - group.all_switches
    
  lights_view_view:
#    view: yes
    name: Lampen
    entities:
      - group.all_lights

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

When I have this in my configuration.yaml it looks like this

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
group: !include_dir_merge_list groups
#Script: !include_dir_merge_list scripts
sensor: !include_dir_merge_list sensors
switch: !include_dir_merge_list switch
device_tracker: !include_dir_merge_list device_tracker
#automation: !include_dir_merge_list automation
zone: !include zone.yaml

image
image1261×577 49.2 KB

when I make 1 little chance it looks like this

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
#group: !include_dir_merge_list groups
#Script: !include_dir_merge_list scripts
sensor: !include_dir_merge_list sensors
switch: !include_dir_merge_list switch
device_tracker: !include_dir_merge_list device_tracker
#automation: !include_dir_merge_list automation
zone: !include zone.yaml

image
image1256×643 53.5 KB

The map/folder groups is completely empty !?
When I put the groups.yaml in the folder instead of the root, it still looks like the first picture.
Even when quoting out group: !include groups.yaml in the configuration.yaml

52

I did get most working, only not (yet) the coloring ?
I did do the web-load of the custom-ui

frontend:
  extra_html_url:
    - https://raw.githubusercontent.com/andrey-git/home-assistant-custom-ui/master/state-card-custom-ui.html
  extra_html_url_es5:
    - https://raw.githubusercontent.com/andrey-git/home-assistant-custom-ui/master/state-card-custom-ui-es5.html

Any idea why I do not get the colors ?

53

sorry missed this one…

colors for what? and how are you trying to set the colors?

54

Hi Mariusthvdb,

I’m revering to your post of 1-12-2018

I found out that the huidigtarief.yalm is not working completely yet. It’s always high.

55

This is how my huidigtarief.yalm looks like;

#Hoog laag tarief sensor
  - platform: template
    sensors:
      huidig_tarief:
        entity_id: sensor.time
        value_template: >
          {% if 7 < now().hour < 23 and is_state('binary_sensor.workday_sensor','on') %} 
            Hoog
          {% else %} 
            Laag
          {% endif %}
        icon_template: >
          {% if is_state('sensor.huidig_tarief','Hoog') %} 
            mdi:numeric-1-box-multiple-outline
          {% else  %} 
            mdi:numeric-2-box-multiple-outline
          {% endif %}

And this is what I added to customize.yalm;

sensor.huidig_tarief:
  templates:
    theme: >
      if (state === '1') return 'green';
      return 'orange';
    _stateDisplay: >
       if (state === '1') return 'Laag';
       return 'Hoog';
56

not sure what is wrong in your setup, but to be sure: you do have both sensor.time and binary_sensor.workday_sensor in you configuration? If not, this template wouldn’t work of course.

Also, be ware that from .84.5 (i think) up _stateDisplay customizations won’t work anymore. reason for me not to upgrade for now…

57

Thanks a lot
I do have the last update of HASS and did not know that sensor.time is a sensor that has to be in my config.

Will try to do that right away