@B_lex wrote:

I was hoping my first post here was not going to be a question, but unfortunately I’m able to setup my first automations.
I’ve recently installed Home Assistant Core running in docker on an Odroid N2

The goal of my automations is to lower screens based on the position of the sun(azimuth). While taking into account cloud coverage (high coverage means the screens are not necessary) and wind speed (high wind speed could damage the screens).

The config validation is HA returns: Invalid config for [automation]: required key not provided @ data[‘trigger’][0][‘platform’]. Got None. (See /config/configuration.yaml, line 10).
I’ve validated that both files are valid YAML and scoured the form for a solution without result.

Can someone please have a look and tell me what I’m missing?

My configuration:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# inclusions
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

# Text to speech
tts:
  - platform: google_translate


# Weather sensor
sensor:
  - platform: openweathermap
    api_key: APIKEY
    forecast: true

    monitored_conditions:
      - weather
      - temperature
      - wind_speed
      - humidity
      - pressure
      - clouds
      - rain
      - snow
      - weather_code

  - platform: buienradar
    monitored_conditions:
      - stationname
      - condition
      - symbol
      - humidity
      - temperature
      - feeltemperature
      - windspeed
      - pressure
      - irradiance

My automations.yaml:

# Covers
# Eastside
- alias: "Lower sunscreens on Eastside of the house"
  trigger:
    value_template: "{{ state_attr('sun.sun', 'azimuth') }}"
    # Can be a positive or negative number
    above: 55
  condition:
    condition: and
    conditions:
    # Prefix the first line of each condition configuration
    # with a '-'' to enter multiple
      - condition: numeric_state
        entity_id: sensor.owm_cloud_coverage
        below: 80
      - condition: numeric_state
        entity_id: sensor.owm_wind_speed
        below: 13
  action:
    service: cover.close_cover
    entity_id:
    - cover.overkapping
    - cover.slaapkamer_1_links
    - cover.slaapkamer_1_rechts
    - cover.slaapkamer_2_groot

# Southside
- alias: "Lower sunscreens on Southside of the house"
  trigger:
    value_template: "{{ state_attr('sun.sun', 'azimuth') }}"
    # Can be a positive or negative number
    above: 105
  condition:
    condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.owm_cloud_coverage
        below: 80
      - condition: numeric_state
        entity_id: sensor.owm_wind_speed
        below: 13 
  action:
    service: cover.close_cover
    entity_id:
    - cover.raam_bij_berging
    - cover.woonkamer_hoekraam
    - cover.slaapkamer_2_klein
    - cover.raam_inloopkast

# Westside
- alias: "Lower sunscreens on Westside of the house"
  trigger:
    value_template: "{{ state_attr('sun.sun', 'azimuth') }}"
    # Can be a positive or negative number
    above: 205
  condition:
    condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.owm_cloud_coverage
        below: 80
      - condition: numeric_state
        entity_id: sensor.owm_wind_speed
        below: 13
  action:
    service: cover.close_cover
    entity_id:
      - cover.master_bedroom
      - cover.woonkamer_links_hoek
      - cover.woonkamer_schuifpui
      - cover.woonkamer_keuken

# Northside
- alias: "Lower sunscreens on Northside of the house"
  trigger:
    value_template: "{{ state_attr('sun.sun', 'azimuth') }}"
    # Can be a positive or negative number
    above: 280
  condition:
    condition: and
    conditions:
      - condition: numeric_state
        entity_id: sensor.owm_cloud_coverage
        below: 80
      - condition: numeric_state
        entity_id: sensor.owm_wind_speed
        below: 13 
  action:
    service: cover.close_cover
    entity_id: cover.vide

Posts: 1

Participants: 1

Read full topic

@finity wrote:

I have to say I’m not a fan at all of the new HACS layout & functionality.

the layout of the cards isn’t right. The buttons bleed out from the individual cards:

ex1022×342 28.4 KB

And, why would you put all of the custom plugins mixed together with the themes?

It makes it extremely difficult to find things

And it makes it even harder to add a new repo when they aren’t even listed in any order.

ex1968×785 38.2 KB

And lastly, (and I know this is a non-starter even before I ask since HA “design” seems to be going this direction overall) but can we please bring back the list view instead of the card view?

Posts: 3

Participants: 3

Read full topic

@cavern wrote:

Hello all,

I’m rather new to home Assistant and yaml stuff, so please be kind (and I’m not native english speaking neither).

I’m operating King Q4 covers using tasmota over MQTT on a PS-16-DZ module configutation. It does the job more or less, unless the synchronization of the slider with the on/off commands. The slider has effetc on the staus open/closed, but the action to open or close doesn’t affect the slider at all.

Not ready to dive in the driver code, I’d like to have a dimmer action from home assistant in parallel with the open/close actions but I do not even find how to try that.

For instance, the action below:
payload_open: 'AT+UPDATE="sequence":"1576774195000","switch":"on"'

would also run an increment from 0 to 100 by steps of 5 every 5 seconds.

Any idea how I can do this ?

As info, the full configuration for each cover is like below:

cover Volet_Cheminee:
    platform: mqtt
    name: "volet cheminée"
    device_class: shade
    availability_topic: "tele/volet_cheminee/LWT"
    payload_available: "Connecté"
    payload_not_available: "Déconnecté"
    position_topic: "stat/volet_cheminee/position"
    position_open: 100
    position_closed: 0
    set_position_topic: "cmnd/volet_cheminee/Dimmer"
    command_topic: "cmnd/volet_cheminee/SerialSend2"
    payload_open: 'AT+UPDATE="sequence":"1576774195000","switch":"on"'
    payload_close: 'AT+UPDATE="sequence":"1576774195000","switch":"off"'
    payload_stop: 'AT+UPDATE="sequence":"1576774195000","switch":"pause"'
    retain: true
    optimistic: false
    qos: 1

Posts: 1

Participants: 1

Read full topic

@yonny24 wrote:

I’m playing around with the mariadb. The connection string used core-mariadb not the IP.
It is connected now and feeding in data.

Eventually got grafana to connect by using ‘core-mariadb’ instead of localhost or the IP.
I was almost ready to delete the add on and add the mysql core on ubuntu using command line interface

But I would really like to use msql workbench also. I’ve added odbc connection but cannot get it to connnect to the mysql db.

Had anyone successfully connected to mariadb using the workbench?

Thanks

Posts: 1

Participants: 1

Read full topic

@BertrumUK wrote:

Since updating to 0.110.0 I seem to be hitting the Air Visual limit around 8pm every day - this never happened before the update to 0.110.0. There have been several issues related to this on GitHub here which should have been fixed in 0.110.2 here. Since the 0.110.2 update I hit the limit before midday UK time with 1 restart of HA before this happened.

This is the error seen in the logs - “Error fetching geography data data: Error while retrieving data: call_per_day_limit_reached”

I have a seen this on another persons HA around lunch time today so its not just related to my account…

Is anyone else hitting the API limit since 0.110.0 ?

Posts: 1

Participants: 1

Read full topic

@olmo66 wrote:

estos son los datos de la instalacion de home assistant.
Estado del Sistema

arch	armv7l
dev	false
docker	true
hassio	true
os_name	Linux
os_version	4.19.114-v7
python_version	3.7.7
timezone	Europe/Madrid
version	0.109.4
virtualenv	false

Lovelace

dashboards	1
mode	storage
resources	0
views	1

no encuentro como configurar una ip estatica porque no encuentro el fichero:
/etc/dhcpcd.conf

si lo creo y reinicio el sistema con reboot, al arrancar ya no está el fichero creado.

este fichero la habia modificaco con la instalacion debian lite y habia ido bien.

Posts: 2

Participants: 2

Read full topic

@sergio_pt wrote:

Hi all,

I just noticed an issue when creating a condition to show a badge.
I use the Raw Configuration Editor to add the following:

  - badges:
      - entity: person.sergio_sa
      - entity: person.joana
      - entity: device_tracker.x1_sdrive16d
      - type: entity-filter
        entities:
          - entity: sensor.lixo
          - entity: sensor.plastico
          - entity: sensor.papel
        state_filter:
          - operator: ==
            value: "today"

It works perfectly, but when I refresh the page, it stops working because the double quotes are removed and the condition no longer works:

  - badges:
      - entity: person.sergio_sa
      - entity: person.joana
      - entity: device_tracker.x1_sdrive16d
      - type: entity-filter
        entities:
          - entity: sensor.lixo
          - entity: sensor.plastico
          - entity: sensor.papel
        state_filter:
          - operator: ==
            value: today

Is this just me or this happens to everyone?

Posts: 2

Participants: 2

Read full topic

@crazyboyxx wrote:

Please find the API result below, I need to get the three values of eta fields below:

00:18:17
00:48:17
01:08:19

{
    "type": "ETA",
    "generated_timestamp ": "2020-05-26T00:25:04+08:00",
    "data": [
        {
            "seq": 5,
            "stop": "002438",
            "eta": "2020-05-26T00:18:17+08:00",
            "eta_seq": 1
        },
        {
            "stop": "002438",
            "eta": "2020-05-26T00:48:17+08:00",
            "eta_seq": 2
        },
        {
            "stop": "002438",
            "eta": "2020-05-26T01:08:19+08:00",
            "eta_seq": 3
        }
    ]
}

How can I do that?

Posts: 2

Participants: 2

Read full topic

@guice wrote:

What’s the best Lovelace card to use for Roku? It seems kinda of pointless to have these controls when none of them appear to work. The only thing that works for me is going into the card and changing the Source (it would be nice if the “Power” button sent the Roku to “Home”)

None of these front controls work.

My YAML is simple:

entities:
   - entity: media_player.roku_ultra
type: entities

Is there a better card I can use that can give a better control over the Roku? I don’t really need any remote-control, just the ability to see what app is “playing” and the ability to quickly send Roku back “Home.”

Posts: 1

Participants: 1

Read full topic

@nightmare1 wrote:

I am trying to switch 2 relays using a node mcu esp-12E board
however i can get the tasmota UI working but when i use HA i am getting strange behaviour.
the toggle buttons on HA will toggle the tasmota once but not the other way and the button in HA will flick back a seond later, its as if the device is not sending its state back to HA, i have tried various state_topic instructions but i a think some of this cant be adjusted in the .yaml so im a bit lost.
I will note that it possibly worked for a moment when i changed freindly names or topic name.

Capture2606×757 52 KB

(The relay will eventually be in interlocking mode but this seems to work in tamota ok
i am also using a temp sensor on GPIO4
the relays are GPIO12 and GPIO14, i assum it should still work with nothing attached to the pins as i ahve tried it with and without and the Tasmota to relay part seems to work fine.)

Capture1882×831 78.8 KB

thanks in advance for your help.

Posts: 1

Participants: 1

Read full topic

@mapeje wrote:

I have some Axis cameras with static IP on my camera subnet 192.168.10.x where my main network with HA VM is on 192.168.1.x.
I can access the cameras from the browser but cannot integrate using Axis component.

I am running a Unifi network with USG router with main network on LAN1 and camera network on LAN2.

Posts: 1

Participants: 1

Read full topic

@Da9L wrote:

I want to make one of my IKEA remotes turn on the shower lights and a vent. I have the remote and i could probably connect both the vent and lights to an IKEA outlet. But how would i make the lights and vent turn off automatically after e.g. one hour after they have been turned on ?

I guess it could be done with some script, or automation, but not sure what is the best approach

Posts: 1

Participants: 1

Read full topic

@Aaron_West wrote:

I have 3 TCL Roku TVs
They all have been working for a while but one of them stopped responding to HA commands to it

The 2 working TVs are on Roku 9.2 and the non working one is on 9.3

If i send a remote.rokuname power off the command seems to work and the TV goes off, but the state stays to ON and I get the error in the logs.

Below is the Log error I get
2020-05-25 12:57:52 ERROR (MainThread) [homeassistant.components.roku] Error fetching roku data: Invalid response from API: Error occurred while communicating with device

Posts: 1

Participants: 1

Read full topic

@bhavesh wrote:

Hello All,

Couple of days ago, I noticed that my Life360 badges had stop updating the status. My initial thoughts were, may be my firewall is blocking the connection, as I have recently introduced a new router and firewall in my house. To prov the theory I tried with another GSM router, no firewall. I am still having the issues connecting to Life360.

I had my Life360 integration but I deleted, when I was trying to workout what was going, now I don’t even have integration.

Error message from the log file:
Unexpected error communicating with Life360 server: HTTPSConnectionPool(host=‘api.life360.com’, port=443): Max retries exceeded with url: /v3/oauth2/token.json (Caused by NewConnectionError(’<urllib3.connection.HTTPSConnection object at 0x7f70e2b190>: Failed to establish a new connection: [Errno -2] Name does not resolve’))

18:23:34 – Life360 (ERROR) - message first occurred at 12:49:20 and shows up 44 times

Posts: 1

Participants: 1

Read full topic

@Aaron_West wrote:

This background lives on every page of my HA if I scroll down
Please Help

Screen Shot 2020-05-25 at 1.36.20 PM3298×1786 238 KB

Posts: 1

Participants: 1

Read full topic

@4integration wrote:

Hi,

I am migrating from openHAB to Home Assistant and would like to get some input on MQTT

In openHAB I have devices (ot Items in openHAB) configured like this

Number TotalPowerSensorWatt      "Total Power Watt" <energy> {
  channel="mysensors:power:gateway:sensor-total-power:watt", 
     mqtt=">
       [rabbitmq:/myhouse/power/sensor/total:state:*:Power,sensor=${itemName},location=total watt=${state} ]" }	

So when the device (a sensor in this case) get a changed state/measure it will post an event based on a template.
Here it will post:

• To the topic "/myhouse/power/sensor/total"
• With the payload "Power,sensor=TotalPowerSensorWatt,location=total watt=754"

How can I accomplish this in the best way in HA?

Note: I have MQTT connection enabled

Posts: 1

Participants: 1

Read full topic

@MarvinE wrote:

Hi all,

So after a couple of tries to get my BLID and password for my Roomba 960 following this tutorial, I finally managed to find both and added them to the configuration.yaml file like so:

roomba:
   - host: "<hostname>"
     blid: "<BLID>"
     password: "<password>"

After doing so and restarting my server, I got a message that a new integration had been found. So I went to the integrations page and found the following:

When I clicked “configure”, I had to re-enter all the data that I had already entered in the configuration.yaml file… (host, BLID, password). After I did this I pressed submit and it took a couple of seconds to load and threw an error at me:

image616×560 22.4 KB

Can someone explain to me why I have to enter the data twice, and does anyone know what I could be doing wrong here?

Posts: 1

Participants: 1

Read full topic

@hollie wrote:

Hello,

I am running Home Assistant in Docker on OS X 10.14. This has the unpleasant side effect that it is impossible to run the Home Assistant container with network mode ‘host’ (reference).

I have been using Chromecast devices with success up to now for the last year. But now they are no longer working since the upgrade to 0.109.x.

I found this ticket on the Home Assistant GitHub telling that for version 0.109 and later it is required to have mDNS up and running between the network where the Chromecasts are on and the network where Home Assistant is on.

Because of the Docker limitation on MacOS the Home Assistant container is per definition not on the same network as the Chromecast devices.

Is there somebody who got this working on macOS + Docker and who can point me into the right direction?

PS: I have not added this request to this existing Chromecast + v0.109 thread because this issue is specifically related to the way Docker works on macOS.

Thanks!

Posts: 1

Participants: 1

Read full topic

@LeoSum wrote:

Hi there,
I was trying to be smart and make generic scripts that will do the same actions with different entities for me, following “Don’t repeat yourself!”.

For example in my snapcast configuration, when the stream that clients are currently playing goes silent, I want to mute them.

For this, I have an automation that is triggered by the stream switching to “idle” which checks all clients if they currently have this stream selected and mutes them if they do, by calling this script with the entity_id as a passed in variable snapclient_id :

mute_client:
  alias: "Mute Client"
  sequence:
  - delay: 0
  - service: media_player.volume_mute
    data_template:
      entity_id: "{{ snapclient_id }}"
      is_volume_muted: true

In general this works with any client, but whenever more than one client was using the stream, and the script should be run for several clients, it only mutes the first client and fails on the others:

WARNING (MainThread) [homeassistant.components.script] Script script.mute_client already running.

Yeah, I know it’s already running, I inteded it to be. But why is that a problem?
Is this a general limitation of homeassistant?
Can I not spare myself typing effort and redundancy like I planned?
Do I need to make specific scripts for each client?
What would be the best practice in a scenario like mine where I have a lot of scripts that I want to use for multiple entities and sometimes also at the same time.

I already tried to add in delays but this is not really feasible.

Posts: 2

Participants: 2

Read full topic

@Noto wrote:

I’m trying to get my hallway lights to adjust to the sun and weather conditions. Using the Buienradar integration there is a sensor for solar strength. I’m hopeing to use this value to calculate an approptiate brightness level. With the calculation below I would have a 50 brightness nightlight and as long as the irradiation doesn’t go over 1000kW I should be fine (255 is max brightness).

- id: '1581631610216'
  alias: Lampen - Gang movement
  description: ''
  trigger:
  - entity_id: binary_sensor.motion_sensor_158d0001b19074
    platform: state
    to: 'on'
  - data:
      brightness: '{{ ((states.sensor.br_irradiance.state | int) / 5) + 50 }}'
    entity_id: light.gang_lamp
    service: light.turn_on

Can someone help me find the error in this formula?

Posts: 1

Participants: 1

Read full topic