Hi all,
I am facing the following issue once my HA instance is running about 1-2 days: My HA instance still opened at the Browser is not reacting, only some navigation is still possible, e.g. Configuration → Settings → Server controls → Check configuration
is showing the error message “File configuration.yaml not found”
Also the controlled shutdown is not possible anymore.
The only way to continue is removing the power supply from my PI4. After providing again power the system does boot regularly without any limitations and working as usual.

My PI4 is running with an SDD via USB3, I have only few add-ons (RaspberryMatic CCU) and integrations installed / activated. I am running the latest HA: core-2022.2.3, HA OS 7.3

How can I discover the root cause for that behaviour? Which log can provide me some further insides?
Any hint is welcome!

Thanks, Bastian

1 post - 1 participant

Read full topic

I am simply swapping TPLINK plugs for two devices. What is the best way to do this without making a mess of things?

One is a lamp and the other is a 3D Printer - I am swapping the two.

1 post - 1 participant

Read full topic

Greetings.
I have successfully automated my SONOFF gate switch.
In SONOFF, it’s set with a ‘nudge’ function, so an ‘ON’ is really only an ‘ON’ for half a second.
This emulates my pressing a button to open the gate: there are physical buttons, indoors and out.
Trouble, is, in Home Assistant, the button goes from blue to yellow – and stays that colour.
Ideally, it would go yellow for half a second, just to acknowledge the ‘hit’.
It works if I hit the button twice – colour goes back to blue (= waiting to be hit) – but this is ugly and counter-intuitive.
Any ideas as to how I might code this required brief colour-change?
I’m most grateful.

1 post - 1 participant

Read full topic

Hi,
I could use some advice, trying to have Home Assistant Container core-2021.12.10 running on an Asustor NAS connect to InfluxDb:2.0 Docker on same machine.

Being new to Docker, this might be a setup issue around the Docker Containers, but what I get is the error message below in the HA gui when restarting the HA docker.

2022-02-07 18:00:52 ERROR (influxdb) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to ‘[Errno 2] No such file or directory’. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible.

Does anyone know exactly what that means, and what level of error this is?
Is the ‘[Errno 2] No such file or directory’ string coming from HA or from InfluxDb? If I type an invalid IP I get a different kind of message…
How can I debug this further?

The HA runs in “host” mode network sharing IP 192.168.0.100 with the NAS, influxdb in bridged mode IP 172.17.0.3 publishing port 49155 which is mapped to internal 8086.
I can browse the influxdb from a PC on the local network on http://192.168.0.100:49155
I’ve tried various variants for the setup in HA, but this is the current one:

influxdb:
  api_version:      2
  ssl:              false
  host:             192.168.0.100
  port:             49155
  verify_ssl:       false
  bucket:           e11289f58c66aaa8
  organization:     [16 hexdigits from DB GUI ]
  token:            [TOKEN STRING GENERATED IN DB GUI]
  tags:
    source: HA
  max_retries:      3
  measurement_attr: entity_id
  include:
    domains:
      - sensor
      - binary_sensor

For host I’ve tried at least localhost, 127.0.0.1, 192.168.0.100, and 172.17.0.3 port 8086.
for bucket I’ve tried both the hexstring and the real name home_assistant.

I’ve used influxdb-client-ruby and been able to write data to the InfluxDb that appear in the WEB Gui of the database. This was ran towards 192.168.0.100:49155 from the NAS host.
From within the HA container (shell) I can do a wget http://localhost:49155/index.html and get a file that is obviously originating from the InfluxDb web server.

I’ve tried with InfluxDb:latest as well, same problem.

Any tips or suggestion to what to try would be appreciated a lot.

Rgds,
Sigurd.

1 post - 1 participant

Read full topic

Hi,

How can I migrate from this depricated solution to something that does exactly the same for the mobile app?

ios:
  push:
    categories:
      - name: Forgot Alarm
        identifier: "forgotalarm"
        actions:
          - identifier: "ALARMON"
            title: "Alarm on"
            activationMode: "background"
            authenticationRequired: no
            destructive: yes
            behavior: "default"


automation:
  - id: push_notification_action_forgot_alarm
    alias: "Push notification action - Forgot alarm"
    initial_state: on
    trigger:
      platform: event
      event_type: ios.notification_action_fired
      event_data:
        actionName: ALARMON
    action:
      service: alarm_control_panel.alarm_arm_away
      entity_id: alarm_control_panel.alarm

Cheers,

Michel

1 post - 1 participant

Read full topic

I have a thermostat integrated using MQTT auto discovered. The thermostat has only centigrade(C) as unit of measure. It does not allow to change to F (its an European/Asian version). After integrating, the device temperature shows as 8 degree F. Actually, the 8 is in C not F. It also creates another sensor entity, which shows the converted temperature in F as 47.3, which is correct. All I need is either (1)change the display from F to C or (2) convert the temp to F and keep displaying F. How this can be done ?

1 post - 1 participant

Read full topic

Good day All,

Firstly, thank you to all in advance for your assistance.

I have an MQTT Topic that contains a random string. This string changes every 120 minutes. It contains both letters, numbers and special characters. It is a Client ID.

I want to read this into Home Assistant “Untouched” as a string, but keep getting “Unkown” displayed in Home Assistant. Planning on running an automation when ClientID changes.

- platform: mqtt
  state_topic: "server/clientid"
  name: "Client ID"
  qos: 2

All other sensors, such as temperature, humidity that is a “number” displays 100%. Only have issues with “strings”.

Can anyone advise on how to display this string untouched in Home Assistant?

Kind Regards
Jason

1 post - 1 participant

Read full topic

Hello,

I’m a HA noob, so I’ll just claim that upfront. I recently have implemented HA to my home as I’m attempting to move away from the Insteon cloud based automation. I have successfully linked all my insteon devices and I’m able to control all of the switches, dimmers and I/O devices. My question appears as I’m trying to build scenes to then incorporate to my automation. I have a scene for all my outdoor lighting devices to be turned on at the appropriate levels for the evening hours.

My problem is, I have one device that I cannot assign to a scene. I can see it in the overview. I can see it in the entities page, but it will not appear in the device page. As it doesn’t show up in the device page, I cannot assign it to my scene and so on and so forth.

What am I missing? I can manually control it, but cannot go farther than that. Any help is greatly appreciated.

Thanks.

1 post - 1 participant

Read full topic

While I think this may be possible to fix via yaml, HA continues to encourage all configuration to move to the GUI. If I add a device to a scene, all entities for that device get added and there is no way to delete them. This is bad, in my case, for a light/fan, where I want to include the light in a scene but I don’t want to have the scene change the current fan setting. Near as I can tell, you can’t do this, which seems strange since I would guess a lot of “scenes” for a room with a ceiling light/fan don’t have anything to do with the fan. I suggest that one be able to add an entity to a scene without it dragging any other entities from the device in with it. After all, if you actually want all the entities you can just add the device instead. I guess the other alternative would be to allow entities in a scene that are marked n/a and are not touched by a scene.turn_on. This might actually be slightly more convenient for someone creating scenes by copying and modifying existing ones.

2 posts - 2 participants

Read full topic

Hi,

I have an optional blueprint input variable illuminance_sensor and I just want to listen for state changes and use this as a trigger:

trigger:
  - platform: state
    entity_id: !input "illuminance_sensor"

This works, if the user specifies that sensor, but if the illuminance_sensor is none, I get an error. My current workaround is, to specify a dummy sensor dummy_illuminance_sensor and add it as a default: in the input variable. But is there a better way?

I also tried to use it as a template although I’m not sure what is the best way to specify that I’m not interested in a certain condition, but only in a state change for a certain (optional) entity:

trigger_variables:
  illuminance_entity: !input "illuminance_sensor"

trigger:
  - platform: template
    value_template: "{{ illuminance_entity != none and (states[illuminance_entity].state | float >= 0)  }}"

It doesn’t give any erros but it also doesn’t seem to trigger my automation.

1 post - 1 participant

Read full topic

Hello everyone, help with the config. I didn’t find an answer on the net.

This is an action tab from automation. It shows that when the humidity drops, the switch turns on.

action:
- service_template: >-
{% set low = (states('input_number.input_number_on_watering') | float) %}
{% set humid = states('sensor.test_humid') | float %}
{% if humid < low %}
switch.turn_on
{% endif %}
entity_id: 
- switch.switch_1

I need it to turn off after 10 seconds of this switch. Please tell me how to spell it correctly. For clarity, I’ll throw off a non-working example, it shows what I need.

action:
- service_template: >-
{% set low = (states('input_number.input_number_on_watering') | float) %}
{% set humid = states('sensor.test_humid') | float %}
{% if humid < low %}
switch.turn_on
{% elif states("switch.switch_1") == 'on' > 10 seconds %}
switch.turn_off
{% endif %}
entity_id: 
- switch.switch_1

1 post - 1 participant

Read full topic

Hi,

Now with homeassistant 2202.2 my fan template is broken. I think I must go to values but I have no idea what to change

This worked with the old version:

fan:
  - platform: template
    fans:
      ventilatie:
        value_template: "{{ states('binary_sensor.ventilatiestatus') }}"
        speed_template: "{{ states('sensor.ventilatiespeed') }}"
        percentage_template: "{{ states('sensor.ventilatiespeed') }}"
        turn_on:
          service: script.fan_high
        turn_off:
          service: script.fan_low
        set_speed:
          service_template: >
            {% if speed == 'high' %}
              script.fan_high
            {% elif speed == 'medium' %}
              script.fan_medium
            {% elif speed == 'low' %}
              script.fan_low
            {% endif %}
        speeds:
          - 'high'
          - 'medium'
          - 'low'

Any idea how to get it to work with de value speeds?

1 post - 1 participant

Read full topic

Hi,

I put Shelly wallplugs between all my home appliances (washing machine, coffee machine, dryer etc).
Now I can see the power consumption for all these devices.

Based on variations in power consumption I get notifications when washing machine, dryer etc is finished.

I now also want to count how much coffee I drink, the # of washes I do per day / per week / per month / per year. My goal is to have a sort of statistic overview in Lovelace with my usage.

Anyone suggestions how I can do this best?

Grtz,
Jules

1 post - 1 participant

Read full topic

Hello all,

Since two weeks I have my home assistant up and running at my house (Running HA container v2021.12.10.) My current project is to measure our solar production, energy consumption and our return to grid.

I have a three-phase electrical installation with an older, analog, meter.
In order to measure energy usage and production I am using a Shelly EM and Shelly 3EM.
The EM is used to measure the solar production and the 3EM measures the three separate phases.
I have used the following energy setup.

For grid consumption I use two standard entities from the shelly 3EM (Meter channel A energy and Meter channel B energy). For the third phase I’m using a custom sensor (since this is the phase where solar power is added and the standard Shelly value only delivers data per phase) For the return to grid, I’m also using a custom sensor.
For the solar production I’m using the standard energy returned entity from the Shelly EM.

The three custom sensors are constructed the following way:

• Actual power phase C

  • In order to get the actual watts that are consumed on the phase where the solar energy is being added.

• Actual consumption phase C

  • A corrected kWh sensor that cancels out the solar return to get the actual consumption on the phase where solar energy is being added.|

• Actual return to grid

  • A sensor where I tried to record the actual return to grid.
    I used an If-statement to evaluate if we are in a return to grid scenario (solar power exceeds the power consumption of all power drawn by the three phases.
    If yes, then the states should record this excess.
    Else = 0.0

template:
  - sensor:
    - name: Actual power phase c
      state: >
        {{ (states ('sensor.meter_channel_c_power')|float(0) - states ('sensor.2_zonnemeter_channel_1_power')|float(0))|round(3) }}
      unit_of_measurement: "W"

  - sensor:
    - name: Actual consumption phase c
      state: >
        {{ (states ('sensor.meter_channel_c_energy')|float(0) - states ('sensor.2_zonnemeter_channel_1_energy')|float(0))|round(3) }}
      unit_of_measurement: "kWh"
      state_class: total
      device_class: energy

  - sensor:
    - name: Actual return to grid
      state: >
        {% if states("sensor.2_zonnemeter_channel_1_energy_returned")|float(0) + states("sensor.meter_channel_a_energy")|float(0) + states("sensor.meter_channel_b_energy")|float(0) + states("sensor.actual_power_phase_c")|float(0) < 0 %}
          {{(states ('sensor.2_zonnemeter_channel_1_energy_returned")|float(0) + states("sensor.meter_channel_a_energy")|float(0) + states("sensor.meter_channel_b_energy")|float(0) + states("sensor.actual_power_phase_c')|float(0))|round(3)}}
        {% else %}
          {{(states ('0.0')|float(0))|round(3) }}
        {% endif %}
      unit_of_measurement: "kWh"
      state_class: total
      device_class: energy

The code does not trigger a configuration error, however I’m not getting any values in the “Actual return to grid”. Yesterday we had sunny conditions and the Shelly app did mention some actual return to grid (phase a and b practically not consuming and phase c providing energy). However, it did not show up in the energy overview.

Does anyone see anything wrong in the sensor-code that was used?
(I did receive quite a few “‘float’ got invalid input ‘unknown’ when rendering template”- errors that I think got fixed by adding the “(0)”-argument.

Thank you in advance,
Kind regards

1 post - 1 participant

Read full topic

I’ve spent 3 weeks reading and trying to figure out how I killed my Google Assistant devices in the process of setting up my first HA. The problem is that I’ve done a bunch of add-ons and integrations in a short period, and don’t know exactly which part made the google assistant stop working.

I’m too dumb to figure out how to debug voice assistant. All I can assume is that the voice component is not connecting to google cloud. Everything I call with “Hey Google” gets a response of “I dont know how to help with that, but here are web results”. It could be as simple as setting a timer, still wont work.

On the other hand, within the Google Home app, all devices show up (including entities from Nabu Casa domains)

Might be relevant:

• DuckDNS is setup WITHOUT SSL (Have also tried with SSL, no difference)
• using standard port 8123 on a reserved LAN IP
• Tried factory resetting devices, rejoining home, etc without luck

If anyone can please point me in the direction to where I can debug this error, or which specific HA components may be interfering with Google Assistant, I’d greatly appreciate it!

1 post - 1 participant

Read full topic

I have the following setup:
Two persons and attached to each one of them a device tracker from GPSlogger integration.
In order to save battery, the GPS logger sends the location only if it senses movement.

After the upgrade to version 2022.2.0, when I restart home assistant, the device tracker of GPSlogger does not retain their previous status before the restart and they are displayed as unavailable causing the persons to be displayed as unknown.

In order for them to get the status back the gps logger which is associated to this trackers needs to update again its position and this is not always the case for the reason I have explained before.

Why this does not retain its previous status?

1 post - 1 participant

Read full topic

I have my Coinbase integration working and I can add the three coins I own and I can convert them to my local currency. That works fine. However, I would rather just see one card with my total Coinbase portfolio current value.

I have found various people trying to sum up energy usage and can’t figure out a way to port that to my scenario.

Running HA Core on an unRaid VM with HACS if that info is needed.

1 post - 1 participant

Read full topic

I have found a very crude way of turning the lights on dependending on the light level that comes from outside. This is done by a light sensor which reports the lumens. I would like my lights to turn on with incrementaly according to the lumens measure. Let’s say at 300 lumens i’d like to turn them on at 10 percent brightness 150lux 50% and so on. the only problem I’m having is that i also have a routine that turns the lights off when i leave the door open and turns them back on when i close my door. Only now the lights turn on to a set brightness percentage and i would like to turn them om as bright as they would to the according lux reading. could anyone help me with this?

2 posts - 2 participants

Read full topic

Hello Everyone,

I have noticed over the past few months battery devices such as Thermostats and motion sensors seem to not last very long at all.

In my home I have three zones for heating controlled by three separate Thermostats in each. In the past I would need to change the batteries in each of these maybe once a year.

A few months back a created a heating schedule in Node-Red that is adjusting the heat in each zone based on the time of day. Once node I’m using is the big timer node so it fires every minute. Is it possible this is polling the device and causing the drain. Batteries seem to only be lasting a month or two before they need to be replaced now.

I am running ZWave JS and don’t really see any settings for polling or waking up devices. I have noticed similar fast drains on some motion sensors as well.

Is anyone else noticing this and has anyone found some solutions I could try?

1 post - 1 participant

Read full topic

Does the Protect integration actually detect a person and output an event in HA? I set up a notification automation that should notify my phone if a person is detected on my doorbell camera. I checked in my Protect app and the camera/ app is detecting people, but in my event logs in HA, it does not show any people detections. Is this a limitation of the HA integration or is there something else that needs to be configured in HA to actually get the state changes and/ or events to fire?

1 post - 1 participant

Read full topic