Trying to setup input_boolean statement. Need a couple of pointers

1

Here is my boolean statement. Does this statement need to be separated into (3) individuals statements. The result I am looking for if any of the (3) are home to show them home. This only seems to work when dad is turned on then everybody is on. If dad is not_home nobody seems to be home.

Thanks for any help you can provide.

- id: '1528490102093'
  alias: Trigger
  trigger:
  - entity_id: device_tracker.dad
    platform: state
    to: home
  - entity_id: device_tracker.mom
    platform: state
    to: home
  - entity_id: device_tracker.son
    platform: state
    to: home
  action:
  - entity_id: input_boolean.dad
    service: input_boolean.turn_on
  - entity_id: input_boolean.mom
    service: input_boolean.turn_on
  - entity_id: input_boolean.son
    service: input_boolean.turn_on
2

Why not use a group for your trackers?
You’d just need one of the trackers to be home for the group to show home

3

I am trying to do automation’s individually. Or maybe I am looking at it the wrong way. @lolouk44 I think you have already helped me in the past. What I want to happen is if anyone that is being tracked when they come home the automation is triggered by them getting into the home radius. I can go in any direction at this point because I am just getting started.

Thanks

4

Yes.

At the moment any one person coming home will show everyone at home.

5

How do I change that?

6

not too sure why you want to duplicate the device trackers state with an input boolean but anyway here’s one way to achieve what you’re after:

- id: '1528490102093'
  alias: Trigger
  trigger:
  - entity_id: device_tracker.dad
    platform: state
    to: home
  - entity_id: device_tracker.mom
    platform: state
    to: home
  - entity_id: device_tracker.son
    platform: state
    to: home
  action:
  - service: input_boolean.turn_on
    data_template:
      entity_id: >-
        {%- if trigger.entity_id == "device_tracker.dad" -%}input_boolean.dad
        {%- if trigger.entity_id == "device_tracker.mom" -%}input_boolean.mom
        {%- else -%}input_boolean.son
        {%- endif -%}
7

@lolouk44 Can you point me in the direction you stated above device_tracker (Groups) I would like to try that approach.

Thanks.

8

it depends what you want to do. If you want to check if at least 1 person is home, then group your devices trackers in a group. If at least 1 device is home, the group status will be home. If you want a separate automation per each device or want to check if all devices are home, you need to track them separately

9

How can I create something like this screen shot. I have a Household tab and I am tracking device_trackers there. I tried to use the group.Home_Status here is my code:

 Home_Status:
  name: Household
  entities:
   - device_tracker.son
   - device_tracker.dad
   - device_tracker.mom
  House:
  view: no
  entities:
    - group.Home_Status

0bc59b64736ac7fd1bd5f90b619999776ccf02be_1_204x202

10

your indentation is off. also don’t use upper case for internal naming as it’ll give you trouble in one day.

home_status:
  name: Household
  entities:
   - device_tracker.son
   - device_tracker.dad
   - device_tracker.mom
house:
  view: yes
  entities:
    - group.home_status

For more inspiration check my config:
https://github.com/lolouk44/homeassistant/blob/master/groups/__Tab_main%20view.yaml

11

So I tried to do a little copying and pasting to get some of your “States”. But all efforts seem to be failing. Here is what I did:
Created a directory called: Sensor
Added a file called sensor.yaml see code below

- platform: darksky
  api_key: !secret dark
  monitored_conditions:
    - summary
    - icon
    - minutely_summary
    - hourly_summary
    - daily_summary
    - temperature_high
    - temperature_low
    - temperature
    - humidity
    - precip_intensity_max

Then I added this to my config.yaml:
sensor: !include_dir_merge_list sensors

Then I added this to my groups.yaml

 default_view:
    name: Main
    view: yes
    entities:
     - sensor.dark_sky_temperature
     - sensor.dark_sky_humidity
     - sensor.dark_sky_overnight_low_temperature
     - sensor.dark_sky_daytime_high_temperature
     - sensor.pws_precip_1d

I was hoping to see some weather results on my default page but “Nothing”. What did I miss?

Thanks for all of your help!!!

12

Created a directory called: Sensor

Then you wrote this:

sensor: !include_dir_merge_list sensors

One is Sensor, one is sensors.
Match the case and check the s at the end of the word sensor

13

Unbelievable!!! The simple things are killing me.

Thanks again. I am going through you config files very impressive.

14

Quick question trying to duplicate some of you efforts. You use a group.alert group.all_alert group.scenes so on so on. I want to make sure I understand what is suppose to happen here.

First you have a directory called groups:
Then you have these individual yaml files inside the groups folders:
group.alert
group.all_alert
so on, so on

When you are calling the group.alert it will reference back to groups directory or do you have to call it group? Hope this makes some since.

default_view:
  view: yes
  icon: mdi:home
  entities:
    - device_tracker.lolo
    - device_tracker.div
    - sensor.dark_sky_temperature
    - sensor.dark_sky_humidity
    - sensor.dark_sky_overnight_low_temperature
    - sensor.dark_sky_daytime_high_temperature
    - sensor.pws_precip_1d
    - sensor.home_to_verint
    - sensor.lolo_to_home
    - sensor.sunset_time
    - group.alerts
    - group.all_alerts
    - group.scenes
    - group.dates
    - group.Weather
    - group.Vacuum
15

thanks for pointing it out, I don’t have a group.all_alerts, it’s a remnent of a previous config. Now amended.
Anything in the group folder can be referenced. You either call entities one by one and they appear in the top as bubbles, or you group them and you call the group and it shows as a card.
Any of my files starting with a _ are views (the tabs on top): easier for me to differentiate them, they also show up on top of my files in file explorer (though at the bottom in github)

Here’s a snapshot of my front end:

image
image1170×769 108 KB

I’m not too must interested/bothered by the look and feel of the front end as I don’t use it much, (a true smart home should not need human manual interaction in my view), I just need it to be logical for when I actually need manual override.

16

Should the directory be called group or groups for your example?

17

In my setup is called groups. You can check my config.yaml or the structure on github