Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[petera]

Could you post the config of your hadashboard3.dash file. I think I've discovered a bug in the way the configuration.yaml is passing names to the Dashboard but I just want to confirm this before I report it to Home Assistant.

What I posted a few posts back is still my current main dash file.

Looking at that post you have 3 separate dashboard files, dashboard1.dash, dashboard2.dash and dashboard3.dash. I imagined you were calling them via navigate from a main page. The reason I ask is that I don't see your individual weather widgets configs.

[lviper]

Could you post the config of your hadashboard3.dash file. I think I've discovered a bug in the way the configuration.yaml is passing names to the Dashboard but I just want to confirm this before I report it to Home Assistant.

What I posted a few posts back is still my current main dash file.

Looking at that post you have 3 separate dashboard files, dashboard1.dash, dashboard2.dash and dashboard3.dash. I imagined you were calling them via navigate from a main page. The reason I ask is that I don't see your individual weather widgets configs.

Ahh, so sorry. Misunderstood what you were asking. Here is my weather.dash file. And yes, I call the camera and weather dash files with the navigate widget type. The camera dash is called with navigate using a timeout and return to main argument.

Code: [Select]

title: Weather Panel
widget_dimensions: [140, 140]
widget_size: [1, 1]
widget_margins: [5, 5]
columns: 7

layout:
    - weather_frame(4x3),temperature, apparent_temperature, humidity
    - precip_probability, precip_intensity, wind_speed
    - summary, visibility, wind_bearing
    - minutely_summary(2x1), hourly_summary(2x1), daily_summary(2x1), maindash

weather_frame:
    widget_type: iframe
    refresh: 300
    frame_style: ""
    img_list:
      - https://icons.wxug.com/data/weather-maps/radar/united-states/bowling-green-kentucky-region-current-radar.gif

temperature:
    widget_type: sensor
    title: Current Temp
    entity: sensor.dark_sky_temperature

apparent_temperature:
    widget_type: sensor
    title: Feels Like
    entity: sensor.dark_sky_apparent_temperature

humidity:
    widget_type: sensor
    title: Humidity
    entity: sensor.dark_sky_humidity

precip_probability:
    widget_type: sensor
    title: Precip Probability
    entity: sensor.dark_sky_precip_probability

precip_intensity:
    widget_type: sensor
    title: Precip Intensity
    entity: sensor.dark_sky_precip_intensity

wind_speed:
    widget_type: sensor
    title: Wind Speed
    entity: sensor.dark_sky_wind_speed

summary:
    widget_type: sensor
    title: Current Condition
    entity: sensor.dark_sky_summary

visibility:
    widget_type: sensor
    title: Visibility
    entity: sensor.dark_sky_visibility

wind_bearing:
    widget_type: sensor
    title: Wind Direction
    entity: sensor.dark_sky_wind_bearing

minutely_summary:
    widget_type: sensor
    title: Current Summary
    entity: sensor.dark_sky_minutely_summary

hourly_summary:
    widget_type: sensor
    title: Hourly Summary
    entity: sensor.dark_sky_hourly_summary

daily_summary:
    widget_type: sensor
    title: Daily Summary
    entity: sensor.dark_sky_daily_summary

maindash:
    widget_type: navigate
    title: Main Dashboard
    icon_inactive: fa-home
    dashboard: main



[petera]

Thanks.

It was a localization issue with HA which I reported and it's sorted now. I'm using a combination of sunset/sunrise and cloud cover for lighting automation which is now working properly

If you get a chance you should try Font Awesome and MDI icons. Takes the bare look off the dashboard. The Obsidian skin stands out well on the Dashboard too

[lviper]

.... I'm using a combination of sunset/sunrise and cloud cover for lighting automation which is now working properly

Care to share how you are doing this? I understand the sunrise/sunset using elevation, but I'm curious as to what you use for cloud cover. Which weather sensor are you using? I've tried Dark Sky but it isn't really all that accurate for my location. Either is YR or any of the non-US weather sensors. Yahoo is close but slow to update. Weather Underground is the most accurate and quickest to update but since they don't give out free api keys anymore, I'm afraid the key I already have may stop working at anytime. So I'm looking for an alternative which may have to be Yahoo weather.

If you get a chance you should try Font Awesome and MDI icons. Takes the bare look off the dashboard. The Obsidian skin stands out well on the Dashboard too

I've used some MDI Icons for my dashboard but many of the Font Awesome icons didn't work for some reason. I also haven't tried skinning yet but plan to some day.

[petera]

These are the sensors I used based on Dark Sky Sensors in the configuration.yaml. The automation I configured in the Configuration section of the Home Assistant API using the States in the Developer Tools section

icon1:
  title: Cloud
  widget_type: sensor
  entity: sensor.dark_sky_summary
  units: "%"
  precision: 0


icon2:
  title: Rain
  widget_type: sensor
  entity: sensor.dark_sky_precip
  state_text: 1

icon3:
  title: Humidity
  widget_type: sensor
  entity: sensor.dark_sky_humidity
  state_text: 1

icon4:
  title: Wind Speed
  widget_type: sensor
  entity: sensor.dark_sky_wind_speed
  state_text: 1

icon5:
  title: Temperature
  widget_type: sensor
  entity: sensor.dark_sky_temperature
  units: "°C"
  precision: 0

icon6:
  title: Wind Bearing
  widget_type: sensor
  entity: sensor.dark_sky_wind_bearing
  state_text: 1
icon7:
  title: UV Index
  widget_type: sensor
  entity: sensor.dark_sky_uv_index
  state_text: 1

icon8:
  title: Rain Total
  widget_type: sensor
  entity: sensor.dark_sky_precip_accumulation
  state_text: 1

icon9:
  title: UV Index
  widget_type: sensor
  entity: sensor.dark_sky_uv_index
  state_text: 1

icon10:
  title: Cloud Coverage
  widget_type: sensor
  entity: sensor.dark_sky_cloud_coverage
  state_text: 1

icon11:
  title: Daily Rain Intenisity
  widget_type: sensor
  entity: sensor.dark_sky_daily_max_precip_intensity
  state_text: 1
icon123:
  title: UV Index
  widget_type: sensor
  entity: sensor.dark_sky_daily_summary
  state_text: 1

icon12:
  title: Daytime High Appparent
  widget_type: sensor
  entity: sensor.dark_sky_daytime_high_apparent_temperature
  state_text: 1

icon13:
  title: Day Time High
  widget_type: sensor
  entity: sensor.dark_sky_daytime_high_temperature
  state_text: 1

icon14:
  title: Dew Point
  widget_type: sensor
  entity: sensor.dark_sky_dew_point
  state_text: 1

icon15:
  title: Hourly Summary
  widget_type: sensor
  entity: sensor.dark_sky_hourly_summary
  state_text: 1

icon16:
  title: Dark Sky
  widget_type: sensor
  entity: sensor.dark_sky_icon
  state_text: 1

icon17:
  title: Minute Summary
  widget_type: sensor
  entity: sensor.dark_sky_minutely_summary
  state_text: 1

icon18:
  title: Overnight Low App
  widget_type: sensor
  entity: sensor.dark_sky_overnight_low_apparent_temperature
  state_text: 1

icon19:
  title: Overnight Low
  widget_type: sensor
  entity: sensor.dark_sky_overnight_low_temperature
  state_text: 1

icon20:
  title: Ozone
  widget_type: sensor
  entity: sensor.dark_sky_ozone
  state_text: 1

icon21:
  title: Rain Intensity
  widget_type: sensor
  entity: sensor.dark_sky_precip_intensity
  state_text: 1

icon22:
  title: Rain Probability
  widget_type: sensor
  entity: sensor.dark_sky_precip_probability
  state_text: 1

icon24:
  title: Visibility
  widget_type: sensor
  entity: sensor.dark_sky_visibility
  state_text: 1

[lviper]

Ok, thanks. I see you're using darksky for your sensors. I'm curious to see how you did the automation. You mentioned you are using sunrise/sunset with the darksky sensors to automate lights. I'm automating some lights based on sun elevation but wanted to add in cloud cover. I have a room that needs lights during the day if it's partly to mostly cloudy. So I'm curious how you did your automation for that.

[petera]

Use this entity to determine your cloud coverage   entity: sensor.dark_sky_minutely_summary

Returns simple cloud coverage in plain English you can include in your automation. Currently my output is partly cloudy for the hour.

[petera]

You could also try this for a generic approach

automation:
  - alias: 'Rainy Day'
    trigger:
      - platform: state
        entity_id: sensor.precip_intensity
        to: 'rain'
    condition:
      - condition: state
        entity_id: group.all_devices
        state: 'home'
      - condition: time
        after: '14:00'
        before: '23:00'
    action:
      service: light.turn_on
      entity_id: light.couch_lamp

[lviper]

Thanks for that. I actually went a different route using a template sensor to determine if indoor lights need to be turned on. It uses the sun elevation and darksky cloud coverage sensors. Here is the code.

Code: [Select]

  - platform: template
    sensors:
      need_indoor_lights:
        friendly_name: 'Need Indoor Lights'
        value_template: >
          {% if (states.sun.sun.attributes.elevation | int < 22) %}true
          {% elif ( (states.sun.sun.attributes.elevation | int < 40) and (states.sensor.dark_sky_cloud_coverage.state | int > 30)) %}true
          {% elif (states.sensor.dark_sky_cloud_coverage.state | int > 50) %}true
          {% elif ( states.sensor.need_indoor_lights.state == 'true' and ((as_timestamp(now()) - as_timestamp(states.sensor.need_indoor_lights.last_changed)) | float < 1200)) %}true
          {% else %}false
          {% endif %}

This sensor turns true under the following conditions.
If the sun elevation is below 22 then true.
or if the sun elevation is below 40 and cloud coverage is above 30% then true.
or if cloud coverage is above 50% then true.

The timestamp statement may not be needed. I just included it from the example I found. It was put in to offer a buffer for times when the statements are close to keep the lights from turning on and off. I'm only using it to turn lights on, not off.

I use the sensor as a trigger in one automation with a condition of someone home. I use it again as a condition when the front door opens and someone is arriving home in case the lights are off because no one was home when it triggered the other automation.

[petera]

Yes the automation scripting is very powerful and varied so there's so many ways available to come at it. The extensive documentation and the active community input is what makes this product. Once HA has identified the states it's fairly straightforward from there.

You can have your setup as simple or as complex as you choose depending on your level of experience. There appears to be a platform for every element of hardware that you throw at it.

I have all the basics set up at this stage so I'm going to spend the winter months integrating my current setup under the HA roof and develop a lot more scripts for it. X10 is functioning nicely with it now.