Warnings not saying much to me

[Dakhaas]

I get a lot of warnings:

Logger: homeassistant.components.sensor
Source: /usr/local/lib/python3.9/asyncio/events.py:80
Integration: Sensor (documentation, issues)
First occurred: 19:30:11 (1 occurrences)
Last logged: 19:30:11

Setup of sensor platform mqtt is taking over 10 seconds.

Logger: homeassistant.components.hassio
Source: components/hassio/__init__.py:568
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 19:34:41 (1 occurrences)
Last logged: 19:34:41

Can't read Supervisor data:

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:428
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 19:31:26 (3 occurrences)
Last logged: 19:31:26

[0x17C6:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x17c6:1:0x0008]: Message send failure'), DeliveryError('[0x17c6:1:0x0008]: Message send failure'), DeliveryError('[0x17c6:1:0x0008]: Message send failure'), DeliveryError('[0x17c6:1:0x0008]: Message send failure')]
[0x17C6:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure')]
[0x17C6:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x17c6:1:0x0006]: Message send failure'), DeliveryError('[0x17c6:1:0x0006]: Message send failure'), DeliveryError('[0x17c6:1:0x0006]: Message send failure'), DeliveryError('[0x17c6:1:0x0006]: Message send failure')]

Logger: homeassistant.components.sensor
Source: /usr/local/lib/python3.9/asyncio/events.py:80
Integration: Sensor (documentation, issues)
First occurred: 19:30:11 (1 occurrences)
Last logged: 19:30:11

Setup of sensor platform mqtt is taking over 10 seconds.

Logger: homeassistant.setup
Source: /usr/local/lib/python3.9/asyncio/events.py:80
First occurred: 19:29:45 (3 occurrences)
Last logged: 19:30:01

Setup of input_boolean is taking over 10 seconds.
Setup of script is taking over 10 seconds.
Setup of automation is taking over 10 seconds.

and one error:

Logger: homeassistant.config
Source: config.py:454
First occurred: 19:29:35 (1 occurrences)
Last logged: 19:29:35

Invalid config for [automation]: required key not provided @ data['action']. Got None required key not provided @ data['trigger'][1]['platform']. Got None. (See /config/configuration.yaml, line 10).

[tmjpugh]

@Dakhaas

Invalid config for [automation]: required key not provided @ data['action']. Got None required key not provided @ data['trigger'][1]['platform']. Got None. (See /config/configuration.yaml, line 10).

The automation is missing info
Key = the defined data
So it has no data for action and trigger

It say to check line 10 of config file but likely this wrong.

[Dakhaas]

@tmjpugh

It say to check line 10 of config file but likely this wrong.

line 10 actually is commented, line 11 refers to automations file

- id: '1639339730308'
  alias: poco batt boven 90%
  description: ''
  trigger:
  - platform: state
    entity_id: binary_sensor.m2007j20cg_is_charging
  condition:
  - type: is_battery_level
    condition: device
    device_id: eefdf074e09c6a279ec849e73468f4cb
    entity_id: sensor.m2007j20cg_battery_level
    domain: sensor
    above: 90
    below: 89
  action:
  - type: turn_off
    device_id: b1af88310cf780276e2ef3b8ddfff2cf
    entity_id: switch.s26_5
    domain: switch
  mode: single
- id: '1640110380047'
  alias: PCslk-powerup
  description: dan s263 en s266 ook aan
  trigger:
  - platform: numeric_state
    entity_id: sensor.pow3_energy_power

is the beginning of the automations file. Where to look for missing stuff??

[tmjpugh]

NO. it want you to look at config so start there.

many times the cause of these are missing quote mark or some other typo before line indicated.
In any case its is causing and error in your automation.

[finity]

If that is your complete automations file then the second automation there is missing the action section.

[Dakhaas]

the line below the automations part describes which part it is. the actual automations text is much much longer …410 lines

[Dakhaas]

all of config.yaml:
I noticed the spaces before plarform of tts… could that be??

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

# Text to speech
tts:
  - platform: google_translate

# group: !include groups.yaml   <<---- LINE 10
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
sensor: !include sensors.yaml
switch: !include switches.yaml


# Example configuration.yaml entry
logger:
  default: info

google_assistant:
  project_id: hassnnnnnnxxxxxxxx.json
  report_state: true
  exposed_domains:
    - switch
    - light
  entity_config:
    switch.RGB:
      name: rgb
      aliases:
        - BRIGHT_LIGHTS
        - ENTRY_LIGHTS
    light.living_room:
      expose: false
      room: woonkamer

python_script:

# publish mqtt feed of ilumination sensor
# Example configuration.yaml entry
mqtt_statestream:
  base_topic: home
  publish_attributes: true
  publish_timestamps: true
  # Example filter to include specified domains and exclude specified entities
  include:
#    domains:
#      - serre
#    entity_globs:
    entities:
      - sensor.lumi_lumi_sen_ill_mgl01_illuminance
#  exclude:
#    entities:
#      - light.kitchen_light

[Dakhaas]

removed 1 space before tts platform line.
now errors:

Invalid config for [automation]: required key not provided @ data['action']. Got None required key not provided @ data['trigger'][1]['platform']. Got None. (See /config/configuration.yaml, line 10).
02:23:25 – (FOUT) config.py - bericht kwam voor het eerst om 02:23:15 en verschijnt 2 keer
:0:0 ResizeObserver loop completed with undelivered notifications.
02:19:53 – (FOUT) components/system_log/__init__.py

[tom_l]

How to read Home Assistant Configuration Errors

Lets say you have this error: Logger: homeassistant.config Source: config.py:464 First occurred: 16:28:21 (1 occurrences) Last logged: 16:28:21 Invalid config for [script]: not a valid value for dictionary value @ data['sequence'][1]['repeat']['sequence'][7]['entity_id']. Got None. (See /config/configuration.yaml, line 206). And that line 207 (we look for line 207, not line 206 because lists start counting at 0, but your text editor line numbers start counting at 1) is: script: !include scri…

[Dakhaas]

@How to read Home Assistant Configuration Errors

because lists start counting at 0, but your text editor line numbers start counting at 1)

Where has Wordperfect 5.0 gone? Where even Hard-returns were visible.
I see this ‘spaces matter’ and line counting errors as Serious Design Flaws.

Script.yaml:

script_publish_mqtt_lumi:
  alias: script-publish-mqtt lumi
  sequence:
  - service: mqtt.publish
    data:
      topic: home/lumi
      payload_template: '{{ states(''sensor.lumi_lumi_sen_ill_mgl01_illuminance'')
        }}'
  mode: restart
  icon: mdi:alarm-light
pwr_kk_serre_max:
  alias: pwr kk serre max
  sequence:
  - condition: state
    entity_id: sensor.shp24_energy_today
    attribute: unit_of_measurement
    state: '>0.150'
    for:
      hours: 0
      minutes: 0
      seconds: 2
  - type: turn_off
    device_id: 48bfc30edab99c4d2bd32a9736ebbec7
    entity_id: switch.shp24_koelkast_serre
    domain: switch
  mode: single
  icon: mdi:fridge

automations complete:

- id: '1639339730308'
  alias: poco batt boven 90%
  description: ''
  trigger:
  - platform: state
    entity_id: binary_sensor.m2007j20cg_is_charging
  condition:
  - type: is_battery_level
    condition: device
    device_id: eefdf074ec849e73468f4cb
    entity_id: sensor.m2007j20cg_battery_level
    domain: sensor
    above: 90
    below: 89
  action:
  - type: turn_off
    device_id: b1af88310c8ddfff2cf
    entity_id: switch.s26_5
    domain: switch
  mode: single
- id: '1640110380047'
  alias: PCslk-powerup
  description: dan s263 en s266 ook aan
  trigger:
  - platform: numeric_state
    entity_id: sensor.pow3_energy_power
    id: pow3over10
    below: '16'
  condition: []
  action:
  - type: turn_on
    device_id: 8add2c89c1722b
    entity_id: switch.s263_slk_logitech
    domain: switch
  - type: turn_on
    device_id: 6cb4111681dc1c1b05
    entity_id: switch.s266
    domain: switch
  mode: single
- id: '1640110568580'
  alias: Pow3SlkPowerDown
  description: dan spk en moni ook down
  trigger:
  - platform: state
    entity_id: sensor.pow3_energy_power
    from: '0'
    to: '17'
  condition: []
  action:
  - type: turn_off
    device_id: 8add253d1722b
    entity_id: switch.s263_slk_logitech
    domain: switch
  - type: turn_off52ee156c6563d111681dc1c1b05
    entity_id: switch.s266
    domain: switch
  mode: single
- id: '1643305203364'
  alias: 6349 pir auto
  description: ''
  use_blueprint:
    path: homeassistant/motion_light.yaml
    input:
      motion_entity: binary_sensor.pir6349_ias_zone
      light_target:
        device_id: de303909b12ce1067454b92bdfc09898
- id: '1643330695215'
  alias: ZHA - Aqara Opple - Wireless Scene Switch 6 Button
  description: ''
  use_blueprint:
    path: Jarne_Roussard/aqara-opple-6-buttons-for-zha.yaml
    input:
      remote: aaad479a8daa866ba6682d6ea2206de7
      button_top_left_single_press:
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      button_top_right_single_press:
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      button_middle_left_single_press:
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power2
        domain: switch
      button_middle_right_single_press:
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      button_bottom_left_single_press:
      - type: turn_off
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      button_bottom_right_single_press:
      - type: turn_on
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      button_bottom_right_hold_in: []
      button_bottom_left_hold_in: []
      button_middle_left_double_press:
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power2
        domain: switch
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      - type: turn_off
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      button_bottom_left_hold_release:
      - type: turn_off
        device_id: 408eb9504af37302eafe2eb202956c20
        entity_id: switch.t2_badkamer
        domain: switch
      - type: turn_off
        device_id: 408eb9504af37302eafe2eb202956c20
        entity_id: switch.t2_douche
        domain: switch
      - type: turn_off
        device_id: 69af15f75a479c8bbf9b061528c3c740
        entity_id: switch.th5_slkkast
        domain: switch
      - type: turn_off
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      - type: turn_off
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power2
        domain: switch
      - type: turn_off
        device_id: da8d8838ebc9d98dc4d8990f7b173d9f
        entity_id: switch.s260
        domain: switch
      - type: toggle
        device_id: 4780ec46a619b414612c32e619e04b20
        entity_id: light.bw_lt21_2
        domain: light
      button_bottom_right_hold_release:
      - type: turn_on
        device_id: 408eb9504af37302eafe2eb202956c20
        entity_id: switch.t2_badkamer
        domain: switch
      - type: turn_on
        device_id: 408eb9504af37302eafe2eb202956c20
        entity_id: switch.t2_douche
        domain: switch
      - type: turn_on
        device_id: 69af15f75a479c8bbf9b061528c3c740
        entity_id: switch.th5_slkkast
        domain: switch
      - type: turn_on
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power2
        domain: switch
      - type: toggle
        device_id: 4780ec46a619b414612c32e619e04b20
        entity_id: light.bw_lt21_2
        domain: light
      - type: toggle
        device_id: da8d8838ebc9d98dc4d8990f7b173d9f
        entity_id: switch.s260
        domain: switch
      button_middle_right_hold_in:
      - type: turn_on
        device_id: da371e6113c3e3800f91d4003669c2fd
        entity_id: light.cl01_6245a523_level_light_color_on_off
        domain: light
        brightness_pct: 80
      - type: turn_on
        device_id: de303909b12ce1067454b92bdfc09898
        entity_id: light.cl02_level_light_color_on_off
        domain: light
        brightness_pct: 80
      - type: turn_on
        device_id: 4780ec46a619b414612c32e619e04b20
        entity_id: light.bw_lt21_2
        domain: light
        brightness_pct: 80
      button_middle_left_hold_in:
      - type: turn_off
        device_id: da371e6113c3e3800f91d4003669c2fd
        entity_id: light.cl01_6245a523_level_light_color_on_off
        domain: light
      - type: turn_off
        device_id: de303909b12ce1067454b92bdfc09898
        entity_id: light.cl02_level_light_color_on_off
        domain: light
      - type: turn_off
        device_id: 4780ec46a619b414612c32e619e04b20
        entity_id: light.bw_lt21_2
        domain: light
      button_top_left_double_press:
      - type: turn_off
        device_id: f329d23c8c3cca11015eff160a55cb53
        entity_id: switch.th2_buitenverlichting_2
        domain: switch
      button_top_right_double_press:
      - type: turn_on
        device_id: f329d23c8c3cca11015eff160a55cb53
        entity_id: switch.th2_buitenverlichting_2
        domain: switch
      button_middle_right_double_press:
      - type: turn_on
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power1
        domain: switch
      - type: turn_on
        device_id: 26debc57a396b07227e8654fdce970ff
        entity_id: switch.power2
        domain: switch
      - type: toggle
        device_id: da8d8838ebc9d98dc4d8990f7b173d9f
        entity_id: switch.s260
        domain: switch
      button_bottom_left_double_press:
      - type: turn_off
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
      button_bottom_left_triple_press:
      - type: turn_off
        device_id: 31e0e0ee09ef404038
        entity_id: switch.touch
        domain: switch
      button_bottom_right_double_press:
      - type: turn_on
        device_id: 31e0e0e87e7c577abe15de09ef404038
        entity_id: switch.touch
        domain: switch
- alias: rfbridge_demultiplexer
  trigger:
  - platform: mqtt
    topic: tele/RFA/RESULT
    action:
  - service: python_script.rfbridge_demux
    data_template:
      payload: '{{trigger.payload_json.RfReceived.Data}}'
  id: 5dd7816a2dd044b3855050fd73f47395
- id: '1643719902152'
  alias: post lumi 5min
  description: ''
  trigger:
  - platform: time_pattern
    minutes: '5'
  condition: []
  action:
  - service: mqtt.publish
    data:
      topic: lumi
      payload_template:
        payload_template: '{{ states(''sensor.lumi_lumi_sen_ill_mgl01_illuminance'')
          }}'
  mode: single
- id: '1643800522764'
  alias: pir8-lamp cl1
  description: ''
  use_blueprint:
    path: freakshock88/motion_illuminance_activated_entity.yaml
    input:
      motion_sensor: sensor.pir8
      target_entity: light.cl01_6245a523_level_light_color_on_off
      illuminance_sensor: sensor.lumi_lumi_sen_ill_mgl01_illuminance
      no_motion_wait: '2'
- id: '1643800753626'
  alias: zb pir slk-slkkast
  description: ''
  use_blueprint:
    path: freakshock88/motion_illuminance_activated_entity.yaml
    input:
      motion_sensor: binary_sensor.pir6349_on_off
      target_entity: switch.th5_slkkast
      no_motion_wait: '5'
- id: '1643823829103'
  alias: automation--run-script-mqtt-on-pir6
  description: ''
  use_blueprint:
    path: freakshock88/motion_illuminance_activated_entity.yaml
    input:
      motion_sensor: sensor.pir6
      illuminance_sensor: sensor.lumi_lumi_sen_ill_mgl01_illuminance
      target_entity: script.script_publish_mqtt_lumi
- id: '1643898227338'
  alias: serre shp24 getimed script kk verbruik
  description: ''
  trigger:
  - platform: time_pattern
    hours: '2'
  condition: []
  action:
  - service: script.pwr_kk_serre_max
    data: {}
  mode: single
- id: '1644312641529'
  alias: rfknop3-switch slk moni
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff3
  condition: []
  action:
  - type: toggle
    device_id: 6cb4a52ee156c6563d111681dc1c1b05
    entity_id: switch.s266_slk_monitor
    domain: switch
  mode: single
- id: '1644312779283'
  alias: rfknop4 -switch-slk-logitech s263
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff4
  condition: []
  action:
  - type: toggle
    device_id: 8add253de16dbebba53d7bbc89c1722b
    entity_id: switch.s263_slk_logitech
    domain: switch
  mode: single
- id: '1644312934854'
  alias: rfsonof1-slkast1
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff1
  condition: []
  action:
  - type: turn_on
    device_id: 69af15f75a479c8bbf9b061528c3c740
    entity_id: switch.th5_slkkast
    domain: switch
  mode: single
- id: '1644313008623'
  alias: rfsonof2-slkast uit
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff2
  condition: []
  action:
  - type: turn_off
    device_id: 69af15f75a479c8bbf9b061528c3c740
    entity_id: switch.th5_slkkast
    domain: switch
  mode: single
- id: '1644313184806'
  alias: rfsonof5-toggle-douche
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff5
  condition: []
  action:
  - type: toggle
    device_id: 408eb9504af37302eafe2eb202956c20
    entity_id: switch.t2_douche
    domain: switch
  mode: single
- id: '1644313187716'
  alias: rfsonof5-toggle-douche
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff5
  condition: []
  action:
  - type: toggle
    device_id: 408eb9504af37302eafe2eb202956c20
    entity_id: switch.t2_douche
    domain: switch
  mode: single
- id: '1644313254415'
  alias: rfsonof6-toggle-wastafel
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.rfsonoff6
  condition: []
  action:
  - type: toggle
    device_id: 408eb9504af37302eafe2eb202956c20
    entity_id: switch.t2_badkamer
    domain: switch
  mode: single

[Dakhaas]

log of errors after a reboot/update

Error doing job: Task exception was never retrieved
02:55:07 – (FOUT) util/dt.py
Error during xml -> python translation
02:55:07 – (FOUT) /usr/local/lib/python3.9/site-packages/zeep/xsd/types/simple.py
Unable to parse event from E0:62:90:C7:B4:09: { 'SubscriptionReference': None, 'Topic': { '_value_1': 'tns1:RuleEngine/CellMotionDetector/Motion', 'Dialect': 'http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet', '_attr_1': { } }, 'ProducerReference': None, 'Message': None }
02:55:02 – (WAARSCHUWING) ONVIF - bericht kwam voor het eerst om 02:54:39 en verschijnt 5 keer
Error during xml -> python translation
02:55:02 – (FOUT) /usr/local/lib/python3.9/site-packages/zeep/xsd/types/simple.py - bericht kwam voor het eerst om 02:53:46 en verschijnt 12 keer
Error doing job: Task exception was never retrieved
02:54:53 – (FOUT) components/dhcp/__init__.py
[0x17C6:1:0x0300]: async_initialize: all attempts have failed: [DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure'), DeliveryError('[0x17c6:1:0x0300]: Message send failure')]
02:54:43 – (WAARSCHUWING) Zigbee Home Automation - bericht kwam voor het eerst om 02:54:42 en verschijnt 3 keer
Received message for unregistered webhook db07d21eda1981534806d5aac04 from 192.168.10.211
02:54:35 – (WAARSCHUWING) Webhook - bericht kwam voor het eerst om 02:54:35 en verschijnt 2 keer
Invalid discovery topic tasmota/discovery/HomeAssistant:
02:53:52 – (WAARSCHUWING) /usr/local/lib/python3.9/site-packages/hatasmota/discovery.py

Setup of sensor platform mqtt is taking over 10 seconds.
02:53:37 – (WAARSCHUWING) Sensor
Setup of input_button is taking over 10 seconds.
02:53:37 – (WAARSCHUWING) /usr/local/lib/python3.9/asyncio/events.py - bericht kwam voor het eerst om 02:53:07 en verschijnt 8 keer
Unknown cluster 57346
02:53:32 – (WAARSCHUWING) /usr/local/lib/python3.9/site-packages/zigpy/zcl/__init__.py - bericht kwam voor het eerst om 02:53:32 en verschijnt 2 keer
Platform mqtt does not generate unique IDs. ID 2cb868 already exists - ignoring sensor.blauwd
02:53:27 – (FOUT) Sensor
Config entry 'P1 meter (3c39e727d56e)' for homewizard integration not ready yet: Error connecting to the Energy device at 192.168.10.108; Retrying in background
02:53:25 – (WAARSCHUWING) config_entries.py
Setup of weather platform buienradar is taking over 10 seconds.
02:53:17 – (WAARSCHUWING) Weather
Invalid config for [automation]: required key not provided @ data['action']. Got None required key not provided @ data['trigger'][1]['platform']. Got None. (See /config/configuration.yaml, line 10).
02:53:03 – (FOUT) config.py
Can't read Supervisor data: Container addon_a0d7b954_ssh is not running
02:52:52 – (WAARSCHUWING) Home Assistant Supervisor

[tom_l]

@Dakhaas

I see this ‘spaces matter’ and line counting errors as Serious Design Flaws.

Nope. It’s how yaml, python and text editors work. You need to learn it.

Here’s the first issue I found. This:

  trigger:
  - platform: mqtt
    topic: tele/RFA/RESULT
    action:
  - service: python_script.rfbridge_demux
    data_template:
      payload: '{{trigger.payload_json.RfReceived.Data}}'
  id: 5dd7816a2dd044b3855050fd73f47395

Should be:

  trigger:
  - platform: mqtt
    topic: tele/RFA/RESULT
  action:
  - service: python_script.rfbridge_demux
    data_template:
      payload: '{{trigger.payload_json.RfReceived.Data}}'
  id: 5dd7816a2dd044b3855050fd73f47395

action: was indented too far. it should be at the same level as trigger:

[Dakhaas]

@tom_l

You need to learn it.

still no argument that it is not a design flaw.

[Dakhaas]

@tom_l

action: was indented too far. it should be at the same level as trigger:

Wow, you’re good. That was like line 261, or 260

[tom_l]

@Dakhaas

still no argument that it is not a design flaw.

Spaces matter because that is how YAML works.

This:

key_1: value
  key_a: value
  key_b: value

is very different to this:

key_1: value
key_a: value
key_b: value

They define different data structures. Spacing is important in YAML, it’s how it works. You can read more here: http://thomasloven.com/blog/2018/08/YAML-For-Nonprogrammers/

As to why Python starts counting at 0 but most text editors start counting lines at 1, it’s just the way it is.

[123 (Taras)]

Speaking of design flaws, your design of this statement is flawed:

    state: '>0.150'

You appear to be trying to perform a numeric comparison within a State Condition. However, if you review its documentation, you’ll see that’s not the correct type of condition to use for numeric tests. In addition, you made the State Condition monitor the entity’s unit_of_measurement attribute. That’s incorrect because that attribute doesn’t contain a numeric value.

In addition to learning about YAML, I suggest you review the documentation describing the many different types of conditions. I believe the Numeric State Condition may be what you want.

[Dakhaas]

pwr_kk_serre_max:
  alias: pwr kk serre max
  sequence:
  - condition: numeric_state
    entity_id: sensor.shp24_energy_today
    attribute: unit_of_measurement
    above: 0.150
    # for:
    #   hours: 0
    #   minutes: 0
    #   seconds: 2
  - type: turn_off
    device_id: 48bfc30edab99c4d2bd32a9736ebbec7
    entity_id: switch.shp24_koelkast_serre
    domain: switch
  mode: single
  icon: mdi:fridge

better? we’ll see if it works now

The notifications malfunction… there are none. Maybe it needs a reboot.

[tom_l]

@Dakhaas

better?

Nope.

You are monitoring the attribute unit_of_measurement. Which is the string kWh (or Wh), this does not change. You want to monitor the state. So remove attribute: unit_of_measurement from the condition.

[Dakhaas]

pwr_kk_serre_max:
  alias: pwr kk serre max
  sequence:
  - condition: numeric_state
    entity_id: sensor.shp24_energy_today
    # attribute: unit_of_measurement
    above: 0.030
    # for:
    #   hours: 0
    #   minutes: 0
    #   seconds: 2
  - type: turn_off
    device_id: 48bfc30edab99c4d2bd32a9736ebbec7
    entity_id: switch.shp24_koelkast_serre
    domain: switch
  mode: single
  icon: mdi:fridge

It seems it still does not work

[tom_l]

That’s appears to be a script, not an automation. How are you calling the script?

It won’t do anything automatically. For that you need an automation.