Following upgrade from HA OS 7.2 to 7.3 and HA Core 2022.2.2 to 2022.2.3 all Z-Wave devices down showing Retrying setup: None.

Please advise…
Shawn

1 post - 1 participant

Read full topic

First of all, I know this must be a common error, but I have tried everything and nothing seems to work.

I have an individual plug that measures W. And I am using “Integration - Riemann sum integral” to obtain the energy consumption in kWh. This is the integration code:

sensor:
  - platform: integration
    source: sensor.fridge_current_consumption
    name: fridge_energy
    unit_prefix: k
    round: 2

I also modified the state_class and device_class with:

homeassistant:
  customize:
    sensor.fridge_energy:
      last_reset: "1970-01-01T00:00:00+00:00"
      state_class: measurement
      device_class: energy

This is the state as read from Developer Tools:

I have added it to Monitor individual devices but I do not get any value back.

And I am sure there is constant consumption in this device.

What else am I missing?

1 post - 1 participant

Read full topic

Hi,

Have been trying to resolve remote access for about a week now. I deleted the NGNIX add on, deleted the Duck DNS add-on and re-installed Duck DNS.

I configured a brand new Duck DNS domain on a new account. I’ve reconfigured Duck DNS with:

aliases: []
domains:
  - [domain].duckdns.org
lets_encrypt:
  accept_terms: false
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300
token: [checked correct]

Configuration.yaml

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 6

I am getting connection refused (again).

I have checked:

• The duckdns website has the correct external IP
• Port forwards are fine (forwarding 8123 & 443)

When going to https://homeassistant.local:8123 I am getting Not Secure - certificate invalid (to be expected).

Looking at the certificate I see I am seeing the certificate for the old duckdns domain, not the new one. Also noted the files fullchain.pem and privkey.pen in the ssl directory were older, so I deleted them. Hoping that the DuckDNS addon would generate new files but they don’t seem to be in the directory.

I have also cleared every setting in Chrome I can think of, deleted the old certificate from mac os keychain.

I am getting “403: Forbidden” trying to access https://[domain].duckdns.org. Just keeps referencing the old domain’s certificate.

I’d like to restart, I get this error on check config:

Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem'
not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 42).

I assume this is because the files are not there.

How do I get the duck DNS addon to generate new pair of SSL files?

God, I just wish I could get this to work again.

1 post - 1 participant

Read full topic

Hey, I am a complete noob but there is this super important thing I need to work out:
There is a random joke api: ( https://witzapi.de/api/joke ) that tells a random joke at every refresh.

YEY I AM THAT BAD… I have no idea how to make HA read that line and how to enter the resulting text=joke to an automation code for TTS.

Since this could be the single most important use of HA for me and my depression I really hope anyone can halp me!

1 post - 1 participant

Read full topic

Well, the title sums it up

Whenever there’s an update available (updater triggers), all automation stops working. At least with Core updates. Automation continues to work after manual update. It has been like this since I started using HA (I think over a year ago), last incident was this morning. There was OS and Core update available, so my cars preheating didn’t trigger (or anything else that matters).

Hardware:
Raspberry 3B + Conbee II (problem exist with R4B also).

Is there setting/configuration, I’m not aware of? Is there a possibility to auto update Core too?

2 posts - 2 participants

Read full topic

I have set up an automation that is triggered by a group which includes my laptop’s camera and microphone.

The automation creates a scene on the fly (before_online_meeting) with the state of my office including lights, Spotify and Chromecast audio speakers

Once it has done that it pauses the media_players and sets lights to 100% brightness and I’m ready to start my meeting.

The same automation is triggered by the microphone and camera group again when they are switched off, but this time the automation attempts it turn on the scene created in the earlier run. Everything seems to work fine. Lights go on, music starts playing again.

However, there is some behaviour in Spotify which I can’t explain.

1. It starts the song it was paused on playing from the start instead of resuming the song.
2. Most importantly, the automation clears the Spotify queue. This has the effect that if am listening to a song in a playlist, it will start this song again after the meeting, however the music will stop after that song as the queue is empty.

Could someone explain what is happening here and help me optimise the automation so that Spotify’s queue isn’t cleared.

alias: meeting_toggles_office_music_lights
description: ''
trigger:
  - platform: state
    entity_id: group.meeting
    from: 'off'
    to: 'on'
    id: start
    for:
      hours: 0
      minutes: 0
      seconds: 2
  - platform: state
    entity_id: group.meeting
    id: stop
    from: 'on'
    to: 'off'
    for:
      hours: 0
      minutes: 0
      seconds: 5
condition:
  - condition: zone
    entity_id: person.name
    zone: zone.home
action:
  - choose:
      - conditions:
          - condition: trigger
            id: start
        sequence:
          - service: scene.create
            data:
              scene_id: before_online_meeting
              snapshot_entities:
                - media_player.spotify_username 
                - media_player.office_speakers
                - light.office_dimmer
                - light.gallery_spots
          - service: media_player.media_pause
            target:
              entity_id:
                - media_player.spotify_username
                - media_player.office_speakers
            data: {}
          - service: light.turn_on
            data:
              brightness_pct: 100
              transition: 2
            target:
              entity_id:
                - light.office_dimmer
      - conditions:
          - condition: trigger
            id: stop
        sequence:
          - service: scene.turn_on
            target:
              entity_id: scene.before_online_meeting
            data: {}
    default: []
mode: single

1 post - 1 participant

Read full topic

Hi all,

long time HA user here. I keep getting a very annoying problem with ZHA. I have 3 Thermostats from HAMA https://www.amazon.de/Hama-Heizkörperthermostat-Heizungssteuerung-programmierbarer-Heizungsthermostat/dp/B08GSRV3PB?th=1 and am controlling those via Zigbee. I am using a Tasmota flashed Sonoff Zigbee Bridge, which works like a charm with all my lights. Thermostats work also, although I got some connection issues sometimes which make the Thermostat show up as unavailable for a few seconds.

A big problem however is that sometimes I notice the flat get cold and true enough, when I go to HA the thermostat is set to 16°C. I feel like this doesn’t have to do with the Thermostat being unavailable, as sometimes the previous temperature is retained after it comes back.

Already thinking about switching back to manual thermostats

Any ideas?

1 post - 1 participant

Read full topic

also i have that device > https://eurotronic.org/wp-content/uploads/2021/12/Air-Quality-Sensor-Z-Wave-Plus_BDA-Web.pdf
And frankly i cant link it with gen5 ; that documentation seems to me as nonsense, after holding button 10sec nothing happening

when i try to press button 3x within 1sec (CRAZY?) nothing …

any idea?

1 post - 1 participant

Read full topic

Don’t you hate it when things break? I have absolutely no idea what happened when I was making some config changes and now I’m getting hit with this error and unable to restart HASS and get a [Object Object] flash up.

Does it make sense to anyone?

Logger: aiohttp.server
Source: components/modbus/validators.py:236
First occurred: 6:47:36 PM (1 occurrences)
Last logged: 6:47:36 PM

Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py”, line 435, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 98, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 79, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 219, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 137, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/api/init.py”, line 331, in post
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1630, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1667, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File “/usr/src/homeassistant/homeassistant/components/hassio/init.py”, line 595, in async_handle_core_service
errors = await conf_util.async_check_ha_config_file(hass)
File “/usr/src/homeassistant/homeassistant/config.py”, line 928, in async_check_ha_config_file
res = await check_config.async_check_ha_config_file(hass)
File “/usr/src/homeassistant/homeassistant/helpers/check_config.py”, line 182, in async_check_ha_config_file
config = config_schema(config)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 272, in call
return self._compiled([], data)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 386, in validate_mapping
cval = cvalue(key_path, value)
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 215, in _run
return self._exec(self._compiled, value, path)
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 339, in _exec
v = func(path, v)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 817, in validate_callable
return schema(data)
File “/usr/src/homeassistant/homeassistant/components/modbus/validators.py”, line 236, in duplicate_modbus_validator
if hub[CONF_TYPE] == SERIAL:
KeyError: ‘type’

2 posts - 1 participant

Read full topic

Hello, I have Home assistant version 2022.2.3. I am using Broadlink RM pro to control RF fan and some broadlink mini to control TV and air conditioner. Since a few days when I try to reset my home assistant to update a version I get an error message when I press “check configuration”:

Invalid config for [switch.broadlink]: [fan_speed_1] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_1. (See ?, line ?).
Invalid config for [switch.broadlink]: [fan_speed_2] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_2. (See ?, line ?).
Invalid config for [switch.broadlink]: [fan_speed_3] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_3. (See ?, line ?).
Invalid config for [switch.broadlink]: [fan_speed_4] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_4. (See ?, line ?).
Invalid config for [switch.broadlink]: [fan_speed_5] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_5. (See ?, line ?).
Invalid config for [switch.broadlink]: [fan_speed_6] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->fan_speed_6. (See ?, line ?).
Invalid config for [switch.broadlink]: [direction_1] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->direction_1. (See ?, line ?).
Invalid config for [switch.broadlink]: [direction_2] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->direction_2. (See ?, line ?).
Invalid config for [switch.broadlink]: [light_1] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->light_1. (See ?, line ?).
Invalid config for [switch.broadlink]: [light_2] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->light_2. (See ?, line ?).
Invalid config for [switch.broadlink]: [turn_off_fan] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->turn_off_fan. (See ?, line ?).
Invalid config for [switch.broadlink]: [power_on] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->power_on. (See ?, line ?).
Invalid config for [switch.broadlink]: [roomba] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->roomba. (See ?, line ?).
Invalid config for [switch.broadlink]: [roomba] is an invalid option for [switch.broadlink]. Check: switch.broadlink->switches->0->roomba. (See ?, line ?).

I didn’t have this problem before. It’s the code:

switch:

  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      fan_speed_1:
        friendly_name: "Set Fan speed 1"
        command_on: "..."
        
 - platform: broadlink
    mac: '...'
    host: ...
    switches:
      fan_speed_2:
        friendly_name: "Set Fan speed 2"
        command_on: "...""
    
 - platform: broadlink
    mac: '...'
    host: ...
    switches:
      fan_speed_3:
        friendly_name: "Set Fan speed 3"
        command_on: "..."
        
  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      fan_speed_4:
        friendly_name: "Set Fan speed 4"
        command_on: "...""
        
  - platform: broadlink
    mac: '....'
    host: ....
    switches:
      fan_speed_5:
        friendly_name: "Set Fan speed 5"
        command_on: "..."
        
  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      fan_speed_6:
        friendly_name: "Set Fan speed 6"
        command_on: "...."  
    
  - platform: broadlink
    mac: '....'
    host: ...
    switches:
      direction_1:
        friendly_name: "Set Direction 1"
        command_on: "...."
 
  - platform: broadlink
    mac: '...'
    host: ....
    switches:
      direction_2:
        friendly_name: "Set Direction 2"
        command_on: "...."    
        
        
  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      light_1:
        friendly_name: "Set Light 1"
        command_on: "..."
        
  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      light_2:
        friendly_name: "Set Light 2"
        command_on: "..."
        
  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      turn_off_fan:
        friendly_name: "Turn off fan"
        command_on: "..."
   
  - platform: broadlink
    mac: '...'
    host: ....
    switches:
      power_on:
        friendly_name: "Turn on and off TV"
        command_on: "..."
        command_off: "..."

  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      roomba:
        friendly_name: "Roomba On/Off"
        command_on: "..."
        command_off: "..."

  - platform: broadlink
    mac: '...'
    host: ...
    switches:
      roomba:
        friendly_name: "Roomba Dock"
        command_on: "..."
       

What is the problem? Is something changed in this version?

2 posts - 2 participants

Read full topic

I am trying to build an automation where within a certain timeframe, I want the bathroom fan turned on with the bathroom light turning on and depending on how long the bathroom light stays on, I want two paths:

• Path1: more than 10 seconds, turn the fan off 15 minutes after the light goes off.
• Path2: (default): less than 10 seconds, turn the fan off when the light goes off.

I’ve tried building this automation using the GUI editor but I’m not getting desired behavior as automation always goes the default route, turning fan off immediately after light is off, regardless of the time the light was on. As shown in the screenshot below, time on was >10s but still went default route.

The value_template: "{{as_timestamp(now()) | int - as_timestamp(states.light.baie_light.last_changed) | int}} reports true when tested under developer tools so it doesn’t make sense to me. Is this a limitation of the visual editor?

My automation has an additional option which works fine but concerning failing option starts at line 32:

alias: Fan Automation 
description: ''
trigger:
  - platform: device
    type: turned_on
    device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
    entity_id: light.baie_light
    domain: light
condition: []
action:
  - choose:
      - conditions:
          - condition: time
            after: '22:00:00'
            before: '07:00:00'
        sequence:
          - type: turn_on
            device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
            entity_id: light.baie_fan
            domain: light
          - wait_for_trigger:
              - platform: device
                type: turned_off
                device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
                entity_id: light.baie_light
                domain: light
            continue_on_timeout: false
          - type: turn_off
            device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
            entity_id: light.baie_fan
            domain: light
      - conditions:
          - condition: time
            after: '07:00:00'
            before: '22:00:00'
        sequence:
          - type: turn_on
            device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
            entity_id: light.baie_fan
            domain: light
          - wait_for_trigger:
              - platform: device
                type: turned_off
                device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
                entity_id: light.baie_light
                domain: light
            continue_on_timeout: false
          - choose:
              - conditions:
                  - condition: template
                    value_template: >-
                      {{as_timestamp(now()) | int -
                      as_timestamp(states.light.baie_light.last_changed) | int >
                      10}}
                sequence:
                  - delay:
                      hours: 0
                      minutes: 15
                      seconds: 0
                      milliseconds: 0
                  - type: turn_off
                    device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
                    entity_id: light.baie_fan
                    domain: light
            default:
              - type: turn_off
                device_id: 781ee485eb41ce9a494fc8a3ceb8a17e
                entity_id: light.baie_fan
                domain: light
    default: []
mode: restart

1 post - 1 participant

Read full topic

Hi,

Please see my templates below to calculate Net Metering correctly for the Shelly 3EM with 3-phase and solar(single or 3-phase), as used in Australia and many other countries.

This uses the shelly instantaneous power sensors to achieve the best possible accuracy, as the counters are updated approx. every second.
The energy import and export daily sensors can then be used in the HA new Energy Dashboard.

Setup your Shelly 3EM using the core integration.
Tested and working on HA 2022.2.3 Shelly FW 20211109-131251/v1.11.7-g682a0db

Let me know if this helps you out!

# Shelly 3EM templates for 3-phase Net Import, Export and Consumption(if you have solar generation details)
# This uses the shelly instantaneous power sensors to achieve the best possible accuracy. 
# Shelly Sensors are  sensor.l1_power, sensor.l2_power, sensor.l3_power for the three phases
# Solar generation in W is used to calculate consumption via sensor.power_solargen

sensor:
  - platform: template
    sensors:

      # Template sensor for values of power import (active_power > 0)
      power_import:
        friendly_name: "Power Import"
        unit_of_measurement: 'W'
        value_template: >-
          {% if (states('sensor.l1_power')|float + states('sensor.l2_power')|float + states('sensor.l3_power')|float) > 0 %}
            {{ states('sensor.l1_power')|float + states('sensor.l2_power')|float + states('sensor.l3_power')|float }}
          {% else %}
            {{ 0 }}
          {% endif %}
        availability_template: "{{
            [ states('sensor.l1_power'),
              states('sensor.l2_power'),
              states('sensor.l3_power')
            ] | map('is_number') | min
          }}"

      # Template sensor for values of power export (active_power < 0)
      power_export:
        friendly_name: "Power Export"
        unit_of_measurement: 'W'
        value_template: >-
          {% if (states('sensor.l1_power')|float + states('sensor.l2_power')|float + states('sensor.l3_power')|float) < 0 %}
            {{ (states('sensor.l1_power')|float + states('sensor.l2_power')|float + states('sensor.l3_power')|float) * -1 }}
          {% else %}
            {{ 0 }}
          {% endif %}
        availability_template: "{{
            [ states('sensor.l1_power'),
              states('sensor.l2_power'),
              states('sensor.l3_power')
            ] | map('is_number') | min
          }}"

      # Template sensor for values of power consumption
      power_consumption:
        friendly_name: "Power Consumption"
        unit_of_measurement: 'W'
        value_template: >-
          {% if (states('sensor.power_export')|float) > 0 %}
            {{ (states('sensor.power_solargen')|float) - states('sensor.power_export')|float }}
          {% else %}
            {{ states('sensor.power_import')|float + states('sensor.power_solargen')|float }}
          {% endif %}


  # Sensor for Riemann sum of energy import (W -> Wh)
  - platform: integration
    source: sensor.power_import
    name: energy_import_sum
    unit_prefix: k
    round: 1
    method: left

  # Sensor for Riemann sum of energy export (W -> Wh)
  - platform: integration
    source: sensor.power_export
    name: energy_export_sum
    unit_prefix: k
    round: 1
    method: left

  # Sensor for Riemann sum of energy consumption (W -> Wh)
  - platform: integration
    source: sensor.power_consumption
    name: energy_consumption_sum
    unit_prefix: k
    round: 1
    method: left

utility_meter:
  energy_import_daily:
    source: sensor.energy_import_sum
    cycle: daily
  energy_import_monthly:
    source: sensor.energy_import_sum
    cycle: monthly
  energy_export_daily:
    source: sensor.energy_export_sum
    cycle: daily
  energy_export_monthly:
    source: sensor.energy_export_sum
    cycle: monthly
  energy_consumption_daily:
    source: sensor.energy_consumption_sum
    cycle: daily
  energy_consumption_monthly:
    source: sensor.energy_consumption_sum
    cycle: monthly

1 post - 1 participant

Read full topic

Hi there,

I created an automation. This should trigger an Alexa greeting every morning.
So far this has never been triggered. This morning I tested it again, unfortunately it doesn’t work.

What can be the reason?

Here the automation:

alias: Guten Morgen Bad
description: ''
trigger:
  - type: motion
    platform: device
    device_id: 66dfc7837dc98ce07e01289bfdf5195f
    entity_id: binary_sensor.lumi_lumi_sensor_motion_aq2_8190c306_ias_zone
    domain: binary_sensor
condition:
  - condition: time
    after: '05:00'
    before: '07:40'
  - condition: template
    value_template: >-
      {{ now() - timedelta(hours=18) > state_attr('automation.guten_morgen_bad',
      'last_triggered')  }}
action:
  - choose:
      - conditions:
          - condition: time
            after: '05:00'
            before: '06:15'
            weekday:
              - mon
        sequence:
          - service: notify.alexa_media_bad
            data:
              message: Guten Morgen Montag
              data:
                type: tts
          - service: media_player.play_media
            data:
              media_content_id: Alexa.Joke.Play
              media_content_type: sequence
            target:
              entity_id:
                - media_player.bad
      - conditions:
          - condition: time
            weekday:
              - tue
            after: '05:00'
            before: '06:15'
        sequence:
          - service: notify.alexa_media_bad
            data:
              data:
                type: tts
              message: Guten Morgen Dienstag
          - service: media_player.play_media
            data:
              media_content_id: Alexa.Weather.Play
              media_content_type: sequence
            target:
              entity_id:
                - media_player.bad
      - conditions:
          - condition: time
            after: '05:00'
            before: '06:15'
            weekday:
              - wed
        sequence:
          - service: notify.alexa_media_bad
            data:
              data:
                type: tts
              message: Guten Morgen Mittwoch
          - service: media_player.play_media
            data:
              media_content_id: Alexa.GoodMorning.Play
              media_content_type: sequence
            target:
              entity_id:
                - media_player.bad
      - conditions:
          - condition: time
            weekday:
              - thu
            after: '05:00'
            before: '06:15'
        sequence:
          - service: notify.alexa_media_bad
            data:
              data:
                type: tts
              message: Guten Morgen Donnerstag
          - service: media_player.play_media
            data:
              media_content_id: Alexa.Weather.Play
              media_content_type: sequence
            target:
              entity_id:
                - media_player.bad
      - conditions:
          - condition: time
            after: '05:00'
            before: '06:15'
            weekday:
              - fri
        sequence:
          - service: notify.alexa_media_bad
            data:
              message: Guten Morgen Freitag
              data:
                type: tts
          - service: media_player.play_media
            data:
              media_content_id: Alexa.TellStory.Play
              media_content_type: sequence
            target:
              entity_id:
                - media_player.bad
      - conditions:
          - condition: time
            weekday:
              - sat
            after: '06:00'
            before: '07:55'
        sequence:
          - service: notify.alexa_media_bad

I’m grateful for any help.

Greetings Werner

2 posts - 2 participants

Read full topic

Hi,
after updating my HA from 7.2 >> 7.3 Zigbee stopped working out of a sudden. There are no logs or any messaged which indicates there is anything wrong. It just stopped. When moving a switch (e.g. from poweron to poweroff) just nothing happens.

I restored my config to yesterday - nothing happend. I also unplugged and re-plugged the zigbee ConBee stick.

I even waited overnight in the case my entities needed some time to recover from the update, also without success. All other devices and entities are working without any problems and issues.

env:

• Standard HA Image on Raspberry 4B
• Zigbee Stick: ConBee II with the newest Firmware.
  

Anyone an Idea?
Thanks!

1 post - 1 participant

Read full topic

Many threads on this subject, but I don’t find a satisfying answer.

For background; I have a ‘virtual’ battery to store access energy from the solar panels. I would like to find out what the maximum energy stored in that battery was for a calendar year.

I’m using the statistics - max_value for that now. But I noticed that the value dropped at some point. I believe this is because of the number of samples retained or something like that. But of course I do not need to keep all samples over the course of one year to determine the maximum value the way the statistics function works.

I just need to store the current max value and compare that to the current actual value to update the max value. For that I need the max value to be stored in a way that survives reboots. Many threads about that as well, but again I didn’t find a working solution.

Surely some-one has a good solution?

2 posts - 2 participants

Read full topic

So, I’m replacing my Foscam cameras with what are arguably better IP cameras from Amcrest. For one, they support modern, self-signed certificates for HTTPS/SSL, and a much more robust configuration overall.
Problem is: Home Assistant
Amcrest Camera Integration does not support self-signed certificates, nor does it have a way to ignore them.
The Generic Camera Integration documentation has ‘verify_ssl’ listed as an option, but I tried that and HA said: Bite-Me, that setting is in valid.
The Generic Camera Integration also lists ‘still_image_url’ as optional. Well, that too is BS. I tried it and HA spit out: required setting ‘still_image_url’ not found.
On top of all this, again the crappy documentation for Generic Camera, says under ‘verify_ssl’:

or you have a self-signed SSL certificate and haven’t installed the CA certificate to enable verification.

But I cannot find ANYWHERE anything documenting how to install a CA certificate from a self-signed device, only how to have HA create its own self-signed certificate.

Any ideas? Or am I just screwed again with HA? (this is an ongoing theme…)

1 post - 1 participant

Read full topic

I have ZHA with sonoff usb dongle zigbee with original firmware.

Everything is normal, except the fact that i cannot Change any cluster value on any device. What i am missing?

1 post - 1 participant

Read full topic

Hi,

my backup size is growing each day about 10 MB and I don‘t know why because nothing has changed.
Where can I search?

Thanks

2 posts - 2 participants

Read full topic

I’m trying to define the value of a sensor based on a condition. Most of the articles I’ve read say I should be using a value_template but when I try that it says value_template not allowed and my sensor is missing a state value, not sure what I’m missing

template:
  - sensor:
      - name: inverter_exporting
        unit_of_measurement: W
        device_class: energy
        state_class: measurement
        state: 
          {{% if is_state_attr('sensor.inverter_energy_today', 'export_power_indicator', 0) %} state_attr('sensor.inverter_energy_today', 'export_power') | abs
          {% else %} 0
          {% endif % }}

2 posts - 2 participants

Read full topic

Hi there,
I’m trying to setup presence detection in my house. For the moment I use the phone. I use 2 options:

• router based - this options does report whether a device is connected or not
• HASS app based - this incorrectly always reports as being home. This also blocks the possibility of geofencing.

How can I have the HASS app report presence correctly?

At the moment I have no external access to my HASS set-up.

Thanks

1 post - 1 participant

Read full topic