So another day, another stink bomb hidden in a supervised install.

Now everything seems to be working and there are no unexpected errors in Supervisor. I have never touched systemd-resolved.service. Do I need to enable this service or is it something I can ignore?

Just as an aside in recent months, any docker or supervisor update has forced me to reinstall HA but with a recent supervisor/dns update, everything is working perfectly again.

The docs aren’t all that helpful. Systemd-Resolved - Home Assistant
I wonder if I should enable it and start it and wonder why this happened anyway?

david@debian:~$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

2 posts - 2 participants

Read full topic

When I try to change the name of a dashboard I created I get an error:

extra keys not allowed @ data['mode']. Got 'storage' extra keys not allowed @ data['url_path']. Got 'lovelace-newdashname'

Any ideas?

1 post - 1 participant

Read full topic

Hi is there a crow-sourced device/entity map somewhere for integrated but unknown devices’ entities?

I bought a Breville Smart Dry Connect Dehumidifier and started hacking working out what the 11 different entities did. A few were immediately obvious (temperature, humidity etc) but most I had to try to get the device into different states to work it out and I still don’t know what all the different possibilities are, and some entities remain unknown.

I am sure this must have got asked a lot - but it would save time for others if I could now share this information in a readily accessible way, and maybe even find that information myself, already worked.

1 post - 1 participant

Read full topic

Last week I noticed that my Zwave and zigbee devices had become unresponsive. I investigated after a day or two when the problem didn’t fix itself. I’m running a Home Assistant Blue with Zwave JS and ZHA. Looking into it, it appears that home assistant is not recognizing my Nortek USB stick. For instance, when I try to start Zwave JS I get:
Device ‘/dev/ttyUSB0’ does not exist in Z-Wave JS (core_zwave_js).
And when I physically look at the HA Blue, the Nortek stick’s blue power light isn’t on. I’ve done a hard reboot of the system and the USB stick will initially show power (LED on) but after a while it goes off

And steps for diagnosis would be appreciated.

1 post - 1 participant

Read full topic

Hello All,

Im new to HA and trying to find my way around everything.

I have added the eWeLink Smart Home (v1.2.3) addon from the HACS store. My devices are detected when I go into the web UI. However, when I want to setup an automation I do not see any of my ewelink switches in the trigger section. I select Device as the Action but I only see my other devices such as Tuya bulbs.

The automation I am trying to setup via the UI.

I am using the latest standard firmware from Ewelink.

Why do I need to see them? Is there something else that I need to setup or add to have these visible

Thanks in advance.

1 post - 1 participant

Read full topic

Sorry if this is not filed correctly.
And thanks in advance for helping.

I use the rest sensor.
I got a json-response which basically looks like this:

{
  "OriginResponseTimeChart":
    {
      "2022-03-11T00:00:00Z":1,
      "2022-03-10T00:00:00Z":2,
      "2022-03-09T00:00:00Z":3
    }
}

So no arrays. Just items. But a Json-Timestamp as a attribute-key.
So I need to specify the actual timestamp under “json_attributes” and i don’t know how to do that dynamically. Even hardcoding the timestamp does not really work:

sensor:
  - platform: rest
    name: rt
    resource: https://example.com/json
    headers:
      Accept: application/json
    json_attributes_path: "$['OriginResponseTimeChart']"
    json_attributes:
      - 2022-03-11T00:00:00Z
    value_template: "ok"

1 post - 1 participant

Read full topic

I recently got the idea to start using packages to combine all my “project” related items. So in my configuration.yaml I added the following according to the example:

homeassistant:
  packages: !include_dir_merge_named yaml/projects/

Then I started my first item in a subfolder in the projects folder: devices/schuurkoelkast.yaml

device_schuurkoelkast_package:
  sensor:
  # Logbook sensor
  - platform: template
    sensors:
      logbook_koelkast:
        friendly_name: "Logbook Koelkast"
        value_template: >-
          {% set Koelkast = [
              "sensor.logbook_koelkast",
            ]%}
            {{
              expand(Koelkast)
              |list()|count()
            }}
        unit_of_measurement: "Entities"
  input_boolean:
  # Fridge on/off boolean
  - koelkast_schuur:
      name: Koelkast schuur
      icon: mdi:fridge  
  automation:
  # Turn fridge on
  - id: koelkastschuuraan
    alias: "Koelkast schuur aan"
    trigger:
    - platform: numeric_state
      entity_id: sensor.koelkast_schuur_power
      above: '5'
    condition:
    - condition: template
      value_template: '{{ states.input_boolean.koelkast_schuur.state != "on" }}'
    action:
    - service: input_boolean.turn_on
      entity_id: input_boolean.koelkast_schuur
  # Turn fridge off
  - id: koelkastschuuruit
    alias: "Koelkast schuur uit"
    trigger:
    - platform: numeric_state
      entity_id: sensor.koelkast_schuur_power
      below: '6'
    condition:
    - condition: template
      value_template: '{{ states.input_boolean.koelkast_schuur.state != "off" }}'
    action:
    - service: input_boolean.turn_off
      entity_id: input_boolean.koelkast_schuur
  utility_meter:
  # Daily Energy calculation
  - schuurkoelkast_daily_energy:
      source: sensor.koelkast_schuur_energy
      name: Koelkast Schuur Dagelijkse Energie
      cycle: daily
      tariffs:
        - peak
        - offpeak
  template:     
  - sensors:
    # Energy costs today
      schuurkoelkast_cost_today:
        friendly_name: "Koelkast Schuur kosten vandaag"
        unit_of_measurement: '€'
        value_template: "{{ (states('sensor.schuurkoelkast_daily_energy_peak') | float * 0.225 + states('sensor.schuurkoelkast_daily_energy_offpeak') | float * 0.20709) | round(2) }}"
    # Energy usage today
      schuurkoelkast_daily_kwh:
        friendly_name: "Koelkast Schuur verbruik vandaag"
        unit_of_measurement: kWh
        value_template: "{{( states('sensor.schuurkoelkast_daily_energy_offpeak')|float + states('sensor.schuurkoelkast_daily_energy_peak')|float) | round(2) }}"  
    # Energy usage yesterday
      schuurkoelkast_yesterday_kwh:
        friendly_name: "Koelkast Schuur verbruik gister"
        unit_of_measurement: kWh
        value_template: "{{ (state_attr('sensor.schuurkoelkast_daily_energy_offpeak','last_period')|float + state_attr('sensor.schuurkoelkast_daily_energy_peak','last_period')|float )| round(2)}}" 

This all sounded good in theory, but when I check the code I get the following errors:

Package device_schuurkoelkast_package setup failed. Component input_boolean cannot be merged. Expected a dict.
Package device_schuurkoelkast_package setup failed. Component utility_meter cannot be merged. Expected a dict.

So it seems the sensor and automation parts work fine, but the input_boolean and utility_meter dont work. What am I doing wrong here?

1 post - 1 participant

Read full topic

So Folks,

I had an hickup with HA two days ago. My VM host did run out of space, just a bunch of MBs before the VM would have run out, during an HA update. I fixed that host issue, and for good measures upgraded the stock .vdi file too, and by this destroyed my partition table and lost the whole machine. I got my system on that just 3 sub-versions spanning bug in VirtualBox, yehaa. As luck would have it.

So now Im back with an all new 7.4 .vdi, and just up 2 days and only a bunch of tasmota switches integrated, no data storage. And my DB is already over a 1GB and my backups are growing fast.

and

Well, this time I run samba backup, so no significant space will be taken up by the 7 local backups, and my backup location will not run out of space in the next years, even if I keep adding those backups on a daily basis almost indefinitely, but I got it set to keep only 70 anyway.

Also this way I will never lose my integration again. as my backup gets an exhaus rsnapshot ever night.

SO the QUESTION is: when I start adding weather data, and some stuff that I want stored for years, and not just the about 10 days I think HA does on stock settings. Where will my DB end? And would a MariaDB switch improve that issue? How about the maria DB to fix a performance issue?

For space reasons, I switched the HA disc from SSD to conventional hard drive, as my VM SSD environment is kind of limited with its 512 GB raid 0 setup, while with the conventional drives I got plenty with 4x 20tb in a raid 0 config. But i cant increase the SSD as my space, sata-ports as well as physically, is kind of used up in the HP ProLiant micro gen8. Hence the switch to spinning discs.

Did not see any speed changes yet but could add just a second VM drive for the DB only on the SSD environment, if that would help the speed.

I had quite some performance issues with graphs last time. Kinde of they took 10 to 30 seconds to load in lovelace dashboard. And thats annoying if you just want to take a short look at the temps of last night, to know if you would need to switch on the preheat of the car to defrost it (yes im upgrading to afterburner to automate it, but currently its still manual.

Whats your thoughts and experiences with that guys?
THanks

1 post - 1 participant

Read full topic

Hello,

I did some first steps with Zigbee. For this, I bought a “SilverCrest” ethernet/zigbee gateway and modified it according to Cloud-free integration with Home Assistant - PaulBanks.Org. Then I added a motion detector, also SilverCrest (sold by Lidl).

Up to here, all worked pretty well. Modifying and adding the Gateway worked great. Adding the device also worked as expected.

My problem is that the motion detector entity of the device is almost always unavailable. The device entity itself goes offline after a while if there is no motion but reconnects when motion is detected. Did I miss something in the configuration?

Status of device entity:

Status of Motion detector entity:

1 post - 1 participant

Read full topic

Reaching out to the community since I cannot figure this one out.

I have a trigger that is to update two sensors at the end of the hour, to get a hourly state to be able to visualize graphs in Grafana.

The trigger works the first time and sub-sequent hours for ‘electrical_yield_rate_summary_hour’.
However, the trigger only works the first time for ‘electrical_distribution_consumption_rate_summary_sek_hour’, but not for sub-sequent hours.

Both of the sensors has values.

The only difference is that ‘sensor.electrical_yield_rate_summary’ is update hourly, where-as ‘sensor.electrical_distribution_consumption_rate_summary_sek’ is only updated at reboot or when manually set.

Have I missed something here, or is this a bug/feature?

  - trigger:
      # Trigger at the near end of every hour, since we want to keep hourly states for energy costs.
      - platform: time_pattern
        hours: "/1"
        minutes: "59"
        seconds: "0"
    sensor:
      # We set the hourly state for: electrical_yield_rate_summary
      - name: electrical_yield_rate_summary_hour
        unit_of_measurement: 'SEK/kWh'
        state_class: measurement
        state: >
          {% set snapshot = states('sensor.electrical_yield_rate_summary') %}
          {% if (snapshot == 'unknown' or snapshot == 'unavailable') %}
          {%   set result = 0 %}
          {% else %}
          {%   set result = float(snapshot)/100  %}
          {% endif %}
          {{ result | round(2) }}
      # We set the hourly state for: electrical_distribution_consumption_rate_summary_sek
      - name: electrical_distribution_consumption_rate_summary_sek_hour
        unit_of_measurement: 'SEK/kWh'
        state_class: measurement
        state: >
          {% set snapshot = states('sensor.electrical_distribution_consumption_rate_summary_sek') %}
          {% if (snapshot == 'unknown' or snapshot == 'unavailable') %}
          {%   set result = 0 %}
          {% else %}
          {%   set result = float(snapshot) %}
          {% endif %}
          {{ result }}

4 posts - 3 participants

Read full topic

Device tracking worked (home/not_home) in 2022.2
Yesterday evening (10th of march 2022), I applied latest updates and today checked again for new updates. Currently I have all lates updates (11the of march 2022)
Did a few restarts, checked settings (that were working before) again…
An amount of automation rely on this… please check?
(in the meantime I found After 2022.3 upgrade device trackers aren't changing · Issue #67826 · home-assistant/core · GitHub)
So, at the moment it’s a known problem…

1 post - 1 participant

Read full topic

Hi all,

I’m struggling with the automation where I would like to:

Turn lights on in front-yard when there is motion and lux_low is true + turn lights off after 3 mintues
Turn lights on in front-yard when front-door is open and lux_low is true + turn lights off after 3 minutes

I have two automations configured:

- alias: Voortuin lights when dark and motion
  description: ''
  trigger:
   - type: state
     entity_id: binary_sensor.hue_outdoor_motion_sensor_1_motion
     state: 'on'
  condition:
   - type: state
     entity_id: sensor.lowlux_outside
     state: 'True'
  action:
   - service: light.turn_on
     data:
       entity_id: group.voortuin_lights
   - delay: 00:03:00
   - service: light.turn_off
     data:
       entity_id: group.voortuin_lights

and second automation:

- alias: Voordeur lights
  description: ''
  trigger:
   - platform: state
     entity_id: binary_sensor.openclose_34
     from: 'off'
     to: 'on'
  condition:
   - type: state
     entity_id: sensor.lowlux_outside
     state: 'True'
  action:
   - service: light.turn_on
     data: 
       entity_id: group.voortuin_lights
   - delay: 00:02:00
   - service: light.turn_off
     data:
      entity_id: group.voortuin_lights

Does anyone see the mistake ? Automations are not working

Thanks very much in advance !

Kind regards,

Bart

2 posts - 2 participants

Read full topic

I am trying to add the Hebrew language to TTS translate
google and can be added to the TTS service, it appears at Compare Translate Features for Each Language - Google Translate
Her mark is ‘iw’ but ‘HA’ does not approve of me, he is not on his list,
what can be done?

1 post - 1 participant

Read full topic

Hi all,

I want to accomplish the following: I want to define a flag (or some sort of a control variable), let’s call it emulatePresence. I want to be able to set the value of the flag to true or false, with a button in Lovelace, similar to a light switch.
Depending on the value of this button I want to have certain automations running, e.g. turning lights off and on.

So a simple use case would be, I leave the house and activate the button and depending on the time of day some magical light switching will happen. It will only happen if my cell phone is not recognized by HA. BUT, I don’t want to have this behavior every time I leave the house, only when the button is pressed.

Maybe there is a certain name for this concept of a state or control variable in HA, but I wasn’t able to find anything in the docs. Maybe there is a better way to do it?

Any ideas?

Cheers, BJ!

1 post - 1 participant

Read full topic

Hey there,

I have my RPi running HA equipped with an active cooling fan with pwm-controll. To set the speed I downloaded and modified a script which works fine on it’s own. The script is in /usr/share/hassio/homeassistant and accepts a single argument. It works when called from a terminal connection to my pi. The problem comes with automating it with HA.
I added this to my config:

shell_command:
  pi_fan_pigpio_faster: "/usr/share/hassio/homeassistant/pi_fan_pigpio.py +5"
  pi_fan_pigpio_slower: "/usr/share/hassio/homeassistant/pi_fan_pigpio.py -3"

In my automation I can select the service Shell Command: pi_fan_pigpio_faster, but it does not affect the speed. Here my complete automation:

alias: Lüfter einstellen
description: ''
trigger:
  - platform: numeric_state
    entity_id: sensor.processor_temperature
    above: '60'
  - platform: numeric_state
    entity_id: sensor.processor_temperature
    below: '55'
    for:
      hours: 0
      minutes: 2
      seconds: 0
condition: []
action:
  - choose:
      - conditions:
          - condition: numeric_state
            entity_id: sensor.processor_temperature
            above: '63'
        sequence:
          - service: shell_command.pi_fan_pigpio_faster
            data: {}
      - conditions:
          - condition: numeric_state
            entity_id: sensor.processor_temperature
            below: '55'
        sequence:
          - service: shell_command.pi_fan_pigpio_slower
            data: {}
    default: []
mode: single

Is there someone who can tell me why there is nothing happening?

Best regards,
4nduril

3 posts - 2 participants

Read full topic

So I got this error while modifying an automation…

Now I can’t seem to get rid of it…Below is a snap of my automation.

Does anyone have a clue what I’ve missed?

As code:

action:
  - service: cover.set_cover_position
    data:
      position: |
        {% if trigger.idx == '0' && state_attr('sun.sun', 'elevation') > 10 &&
        states('sensor.bathroom_lumi_illuminance') > 1465 &&
        states('sensor.outdoor') > 15 %}
          50
        {% elif trigger.idx == '1' && state_attr('sun.sun', 'azimuth') > 290 %}
          100
        {% else %}
          {{ state_attr('cover.bathroom_blind_position', 'current_position') }}
        {% endif %}
    target:

5 posts - 3 participants

Read full topic

Hello all.
I want my PC to shut down as soon as my backup is complete.
The only feedback I get from the backup is a mail. I have successfully created an imap_email_content sensor that works and gives the correct status (success/warning/failed).

But now I have a few questions about the implementation:

I can query the status of the sensor in the automation. But if I get a mail with status “successful” every day, the value of the sensor never changes and I can’t set it as a trigger.
I also can’t set a time trigger that queries a condition, because a) I don’t know when the backup is exactly finished and b) the sensor could read the mail from the previous day, because maybe none came today.

So I need a trigger that reads and deletes the mail as soon as a new mail arrives.

Can I realize this somehow or do I understand the sensor basically wrong?

Thanks for your help
Loki

1 post - 1 participant

Read full topic

Hello,

I am trying to get the switchbot integration to work and I am probably just completely stupid but I hope someone can help me. I have bulbs, motions sensors and a switch.

HA (2022.2.6) docker container
In the console of the container I can scan for bluetooth devices.
If I run the switchbot integration it just shows ‘Failed to connect’

But I get this error:
Failed to execute management command 'le on' (code: 20, error: Permission Denied)
In my desperation I tried to run the container with sudo hoping it would change something but it unfortunately did not.

If you need any information let me know and thank you!

1 post - 1 participant

Read full topic

Hello,

I would like my HA to always check on the hour in the morning if the outside temperature is greater than 7 degrees and if the sun has been shining for more than 45 minutes. I have the following configuration in my automation for this

alias: KLIMA Fußbodenheizung bei Sonne abschalten
description: ''
trigger:
  - platform: time
    at:
      - '08:00:00'
      - '09:00:00'
      - '10:00:00'
      - '11:00:00'
      - '12:00:00'
condition:
  - condition: numeric_state
    entity_id: sensor.netatmo_zuhause_wohnzimmer_balkon_temperature
    above: '7'
  - condition: state
    entity_id: weather.dwd_weather_city
    state: sunny
    for:
      hours: 0
      minutes: 45
      seconds: 0

Although the sun has been shining all day, it breaks my automation at this point:

What is my problem?

Thanks a lot
Loki

2 posts - 2 participants

Read full topic

Hi,

Been trying for a while now, to make a value_template or even an automation, that will list all entities in a group, holding a state that equals “1”.
The purpose of this is to be notified of which garbage container that is giong to be picked up the next day.
I have already converted the sensors for each garbage container, which originaly holds a timestamp, to show remaining days to pickup.

What I would like to achieve:
List all entities whithin the “group.garbage” that is state == 1 ( 1 remaining days untill pickup ).
Then split the entities’ names, from “sensor.days_untill_pickup_xxx” to a Friendly_name etc “food” “paper”, then use does friendly names in a notify string message.

E.g: “Tomorrow the “xxxx” and “xxxx” containers are picked up”

Does anyone have a smart solution to achieve this?

best regards
Christian

2 posts - 2 participants

Read full topic