Hi!
I have a Vallox ventilation system integration in my HA. The integration provides me a date entity where I can type a date of changing ventilation filter and it also provides a sensor entity with remaining time for filter (its just a date):

And created an input_datetime helper to pass data from Vallox sensor to helper. My code in template.yaml looks like this, but however it doesnt work:

 - trigger:
     - platform: time
       id: set helper
       at: "00:00:00"
     - platform: time
       id: notify
       at: input_datetime.date_vallox
   condition: []
   action:
     - variables:
         notification_time: >
           {% set x = states('sensor.vallox_remaining_time_for_filter') %}
           {{ now().replace(day=x[:2]|int, month=x[3:5]|int, hour=7, minute=0) }}
     - choose:
         - conditions:
             - condition: trigger
               id: set helper
             - condition: time
               after: '00:00:00'
           sequence:
             - service: input_datetime.set_datetime
               target:
                 entity_id: input_datetime.date_vallox
               data:
                 datetime: "{{ notification_time }}"
         - conditions:
             - condition: trigger
               id: notify
           sequence:
             - service: notify.neptun_all_devices
               data:
                 title: Filter changing
                 message: Its time to change ventilation filter!
             - service: notify.persistent_notification
               data:
                 title: Filter changing
                 message: Its time to change ventilation filter!
       default: []

So I dont fully understand this code and possibly typed something wrong.
Service for notifications (neptun_all_devices) work perfectly fine, I checked this.

1 post - 1 participant

Read full topic

Hi Everyone,
I’m pretty new in the home-assistant family.
So far a lot is working properly, but I do have the problem, that 3 shutters in my house are not working with home assistant.
If I’m moving them via KNX switch everything is working. If I’m trying to move with HA, I do not get a reply of the KNX shutter actuator in group monitor from HA.
Other shutters on the same actuator are working properly. At this shutters, which are working I could see a response from the actuator in group monitor at HA.
I copied the configuration from working shutters and edited the group adresses accordingly, but no change of the behaviour of the shutters which are not working.
Could anyone support?
Thanks.
Best regards,
Markus

1 post - 1 participant

Read full topic

Since the HA Ollama integration does not have a configuration option for the LLM model temperature, I was wondering what is the default temperature setting. Or does it default to the value in the Modelfile for the LLM configured in the Ollama integration. IMO a configuration option for a LLM temperature value would be useful in the Ollama integration.

1 post - 1 participant

Read full topic

hello, is it possible to detect when my camera is offline, perhaps an event that would fire when the stream is no longer playing?

my camera often hangs and i would like to reboot it via a smart power socket.

thanks

2 posts - 2 participants

Read full topic

Hello everyone,

I’m facing a persistent issue with a command_line sensor in my Home Assistant configuration and, despite extensive troubleshooting, I can’t get it to work correctly. The sensor entity seems to be registered, the command appears to be triggered, but the sensor’s state does not reflect the expected command output.

My Goal : Create a sensor to get the state of the Matterbridge add-on using the command ha addons info a1b84aa7_matterbridge | grep 'state' | awk '{print $2}' | tr -d '"'.

My current yaml configuration

command_line:
  - sensor:
      name: etat_matterbridge
      unique_id: etat_matterbridge
      command: "echo START_MATTERBRIDGE_STATE && ha addons info a1b84aa7_matterbridge | grep 'state' | awk '{print $2}' | tr -d '\"' 2>&1 && echo END_MATTERBRIDGE_STATE"
      scan_interval: 60
      command_timeout: 15 # Added during debugging

When I go into Developper/States, the sensor state is :

START_MATTERBRIDGE_STATE END_MATTERBRIDGE_STATE

No error in the logs, just this.

(We should be seeing the command return in the middle. It also doesn’t work without these “start” and “end” parts, It’s just the result of a lot of testing)

When I run the command " ha addons info a1b84aa7_matterbridge | grep ‘state’ | awk ‘{print $2}’ | tr -d ‘"’ " in the terminal module, the return is « started » or « stopped » accordingly.

I use HAOS in a VM, and I’ve read some posts pointing out this note in the documentation: :

 Note

If you are using Home Assistant Operating System, the commands are executed in the homeassistant container context. So if you test or debug your script, it might make sense to do this in the context of this container to get the same runtime environment.

As I’m not trying to get out of the homeassistant container to get things like the PC specs or such, I think my command should be working.

Also, I tested the “badlogin” sensor example in the documentation but this time it’s working!

My yaml :

command_line:
  - sensor:
      name: Badlogin
      command: "grep -c 'Login attempt' home-assistant.log"
      scan_interval: 60

(You will see that I adjusted the path part to fit my directories structure)

What am I missing?

Thank you for your time.

1 post - 1 participant

Read full topic

I have been using the Let’s Encrypt add-on for some time and this has worked perfectly for the purpose of just Home Assistant. However, I want to make use of the cert in some docker containers on other machines running things like Emby etc.

I have altered the config so it now generates wildcard certificates so I can split services into subdomains, but now I have hit a couple of issues:

1. The plugin requires manually starting or for HA to be manually restarted (add-on set to run at boot) to generate updated certificates when the 3 month window hits. This was historically not an issue, but very soon Let’s Encrypt will no longer send reminder emails. Because I very rarely reboot my HA, this could quite easily lead to an out of date certificate if I forget to renew it. This is a minor concern, but something I need to think about.

and more importantly:

2. Obviously the cert files this add-on generates are stored in the correct location for HA to use them. At the moment, I just copied them from the ssl folder and manually placed them on the other machines I want to use them on - but moving forward this will be a massive laborious pain. One thing I thought about was changing the add-on config so it only generates for 1 subdomain (ie. ha.name.com) then using a docker somewhere else to generate other certificates (Cert bot?).

What would be the easiest way to make use of and distribute this cert to possibly many many dockers and other applications every time it renews? What do others do here in this situation? It was suggested to me recently that I would setup a reverse proxy and put the certs there, but I use a mesh VPN to access my network and do not open ports in my router. I don’t know if that is applicable to my situation? I’ve never really dealt with things like SSL certs and reverse proxies so please forgive me if this is both an obvious and silly question - but it’s just not something I can had to deal with before. Any advice would be greatly appreciated

4 posts - 3 participants

Read full topic

template:
  - sensor:
      - unique_id: living_room_temp
        name: "Living Room Temp"
        unit_of_measurement: "°F"
        state: >
          {{ (state_attr('climate.family_room', 'current_temperature') | string) ~ "°F" }}

If I don’t concatenate the string, it returns the number beautifully. As soon as I concatenate, I get unavailable as the state.

2 posts - 2 participants

Read full topic

Hey everyone!

I couldn’t find some definitive guides or answers on this so I’m hoping you will be able to help.

I’m looking to setup a ZBT-1 on a AMD based install of HA x64.

Is it as simple as plug and play like the rasberry pi version?

1 post - 1 participant

Read full topic

I added a couple of new end devices today, a Sonoff SNZB-03P and a SNZB-02D. I had the 03P in it’s “final destination” before I ever powered it up, paired it there, but it still inexplicably picked up a router much farther away than two others between. Then the 02D had some battery contact issues that I was sorting while trying to get it to pair, it finally paired direct to my controller but again several repeater/routers are closer.

I tried removing the 02D from the HA network, removing its battery, waiting, then reconnecting it in-situ but close to a nearby repeater, but it still seems to remember its preference for the controller and went back to it.

I’ll try to be patient overnight and hope they re-route to better connections - is this likely to happen with Sonoff end devices? I know the Aqara devices are reputed to stick to their mate once they have chosen it - but they also seem to re-route more easily when repairing.

1 post - 1 participant

Read full topic

I setup wled device to have separate outputs for both channels segment 0 segment 1 and I use type: tile card
I use these devices www.aliexpress.com/item/1005008610921967.html and works great and can run off 24v battery bank

If I configure wled to have separate segments for both channels ha creates the following
light.xx master one that only turns off xx_main segment0
light.xx_main segment0 this controls segment0
light.xx_segment_1 segment1 this controls segment1

If I configure wled to have single segment output ha creates the following
light.xx
light.xx_main

If I power off the device from light.xx it only switches off light.xx_main leaving segment1 still powered on
If I was to use entity card I would have to switch off 2 entities to power off the light would make sense in this setup light.xx would switch both segment0 and segment1

I do not understand why when I power off the device it only powers off half of it
as far as home assistant is concerned there are 3 switches for this device when logic would say you only need 1 or 2 switches depending on if you have single channel output or double channel output
It makes no sense why this would be coded this way
or am I not seeing this correct

Can anyone show me what I am missing

Thanks You

1 post - 1 participant

Read full topic

I did a wee search bit could not find too much on this (but apologies if I missed it). I have 5 ESP32-C3s, all running well for a while now, with an example yaml from one of them, as shown below.

The 5# yamls are identical, w.e.o. lines 2 and 3, which define names. That is it, the remaining 95% of the yamls are the same for each device (all BT Proxy Trackers, for now).

display_name: esp32c3btproxykat
friendly_name: ESP32C3BTProxyKat

As the 5# yamls are the same, I thought to streamline future edits so I only need to make changes in one file, say esp32common.yaml.

So what I have done, having read the esphome packages section is to split my example working yaml into:

1. The original first 3 lines (which includes the names) and package: section, which calls the esp32common.yaml file. I saved this as the original file name esp32c3btproxykat.yaml;

substitutions: # name substitutions ref Digiblur https://digiblur.com/wiki/ha/esphome-bluetooth-proxy-esp32c3/
  display_name: esp32c3btproxykat
  friendly_name: ESP32C3BTProxyKat
  
  packages:
    # wifi: !include common/wifi.yaml - example additional package for wifi
    esp32c3devices: !include common/esp32c3btproxy-common.yaml

2. A new yaml, esp32common.yaml, which contains the remaining 95% of the original yaml, without the above lines. I put this in /homeassistant/esphome/common.

However when I tried to verify it I got the following error:

INFO ESPHome 2025.4.0
INFO Reading configuration /config/esphome/esp32c3btproxykat.yaml...
Failed config

substitutions: None
  display_name: esp32c3btproxykat
  friendly_name: ESP32C3BTProxyKat
  
  Must be string, got <class 'esphome.helpers.OrderedDict'>. did you forget putting quotes around the value?.
  packages: 
    esp32c3devices: 
      esphome: 
        name: ${display_name}
        friendly_name: ${friendly_name}
        min_version: 2024.11.0
        name_add_mac_suffix: False
      wifi: 
        reboot_timeout: 3min
        ssid: !secret wifi_ssid

My understanding was that you could just call the common yaml from the main yaml for each device and that the display_name and friendly_name variables would be passed to the common_yaml. I will admit I am not 100% clear on this though!

I would really appreciate a heads up on why this is failing and how to achieve what it is I am looking to do. Thank you.

ORIGINAL WORKING YAML

substitutions: # name substitutions ref Digiblur https://digiblur.com/wiki/ha/esphome-bluetooth-proxy-esp32c3/
  display_name: esp32c3btproxykat
  friendly_name: ESP32C3BTProxyKat

esphome:
  name: ${display_name}
  friendly_name: ${friendly_name}
  min_version: 2024.11.0
  name_add_mac_suffix: false

wifi:
  # output_power: 8.5dB # enable if having issues with connectivity
  reboot_timeout: 3min
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true # Optional. Required (true) if connecting to a hidden SSID; suggest disable if setting Manual IP

  ap: # Enable fallback hotspot (captive portal) in case wifi connection fails
    ssid: ${display_name}
    password: !secret wifi_ap_password

esp32: 
  variant: ESP32C3
  board: esp32-c3-devkitm-1
  framework:
    type: esp-idf # This is important: the default "arduino" framework does not perform well.
    sdkconfig_options:
      CONFIG_BT_BLE_42_FEATURES_SUPPORTED: y # BLE 4.2 is supported by ALL ESP32 boards that have bluetooth, the original and derivatives.
      CONFIG_BT_BLE_50_FEATURES_SUPPORTED: y # Also enable this on any derivative boards (S2, C3 etc) but not the original ESP32.
      CONFIG_ESP_TASK_WDT: y
      CONFIG_ESP_TASK_WDT_TIMEOUT_S: "10" # Extend the watchdog timeout, so the device reboots if the device appears locked up for over 10 seconds.

logger: # Enable logging
  level: DEBUG # Debug=Default; use Verbose if error checking
  # baud_rate: 0  # 0 Enables logging, but disables serial-port logging to free CPU and memory

ota: # Allow Over-The-Air updates
- platform: esphome
  password: !secret ota_password

api: # Enable Home Assistant API; MUST check option under ESPHome Configure!
  encryption:
    key: !secret encryption_key
  on_client_connected: # Only enable BLE tracking when wifi is up and api is connected;Gives single-core ESP32-C3 devices time to manage wifi and authenticate with api
     - esp32_ble_tracker.start_scan:
        continuous: true
  on_client_disconnected: # Disable BLE tracking when there are no api connections live
    if:
      condition:
        not:
          api.connected:
      then:
        - esp32_ble_tracker.stop_scan:
  
# Optional Manual IP
# manual_ip:
#   static_ip: 192.168.53.109
#   gateway: !secret gateway
#   subnet: !secret subnet

captive_portal:

esp32_ble_tracker:
  id: ble_tracker
  scan_parameters: # Bermuda suggests 280/320 or 920/1000 to allow offset BT/Wifi
    interval: 320ms # default 1100ms
    window: 280ms # default 1100ms
    continuous: true
    active: false #defaults to true - selecting false saves power but may not work

bluetooth_proxy:
  active: true # Optional, defaults to false

button:
  - platform: safe_mode
    id: button_safe_mode
    name: Safe Mode Boot

  - platform: factory_reset
    id: factory_reset_btn
    name: Factory Reset

# time:
#  - platform: homeassistant
#    id: homeassistant_time

sensor:
  - platform: uptime
    # The uptime sensor is extremely helpful to know if your device is rebooting
    # when it shouldn't be. This might indicate your interval-to-window timing is
    # too tight, and the window needs to be reduced.
    name: "Uptime Sensor"
    update_interval: 60s

1 post - 1 participant

Read full topic

I’m pretty new to Home Assistant and have just started to wade into building a dashboard. I am using room cards and I would like to change the card color if all relevant entities (lights, fans, covers, media players) in said room are off or closed.

I’ve been Googling and trying different things with no luck. I’m assuming I need (or it’s best) to create a template:

I’ve tried the following, but it always returns “not_all_off”:

- sensor:
      - name: Living Room All Off
        unique_id: living_room_all_off
        state: >
          {% if area_entities('Living Room') | map('states') | select("in",['on','open']) | list | length and 
                          is_state('light.lights_br', 'on') %}
            not_all_off
          {% else %}
            all_off
          {% endif %}

Appreciate any help with this.

1 post - 1 participant

Read full topic

Normally I’m pretty good at scouring the internet finding solutions to stuff, but I cannot for the life of me find a SIMPLE tutorial showing me how to make an actionable notification. I just want to make one that enables or disables an automation. Is anyone willing to help?

2 posts - 2 participants

Read full topic

Hello,

On the dashboard, we find the tag in the HTML header. Is it possible to remove this tag?

I’m asking this question because it’s preventing me from displaying my dashboard on my WebOS TV. I want to integrate my dashboard into a WebOS application. When I test this application on a computer, it works fine. However, the TV blocks access to the dashboard because of this tag.

Thank you for your help.

2 posts - 2 participants

Read full topic

I’m relatively new to this, so may have a schoolboy error. I’m a database software programmer, so I have skills in that area.

I have a number of Sonoff SNZB-02P temperature / humidity sensors scattered around the house (and a couple of smart plugs to help extend Zigbee range)

One of them seems to toggle available / unavailable on a relatively long period. ChatGPT suggests it might have a SLEEP or battery-saving setting (I’m not aware that I have fiddled with any settings).

Others seems to register temperature reliably, varying through the day as I would expect, and then suddenly stop doing that (my assumption is that they become “unavailable”), and then start providing data again.

I found a few topics about this, but not many, and no obvious solutions. Comments tended to be “They are cheap” rather than anything concrete.

If this is the “norm” I would have expected to see more posts about it - presumably folk are actually relying on reasonably worthwhile temperature data to control things?

I need something which will reliably provide a temperature reading “regularly”. House temperature changes slowly, so “instant reporting” not required, per se.

Is this “unreliability” common for this type of sensors?

Can I spend-more-money and guarantee a better solution?

Or some other approach to improve robustness? Lots (how many is that?) or Zigbee repeaters maybe?

One approach I have spent a bit of time on is to try to use a program to detect any toggle between “Available/Unavailable”, in order to see when this happens. My thinking is that the graphs in HA are not a good indicator, because they seem to maintain temperature-assumption after the device becomes unavailable, I would like data to “not exist” and “No assumption made” when a device is unavailable - so that at least I could see when that was happening.

2 posts - 1 participant

Read full topic

I have HA green and added a sonoff zigbee dongle (3.0 v2)
Im hitting the following issue when trying to add a zigbee device.

Logger: homeassistant.setup
Source: setup.py:275
First occurred: April 22, 2025 at 8:58:39 PM (1 occurrences)
Last logged: April 22, 2025 at 8:58:39 PM
Setup failed for 'homeassistant_hardware': Requirements for homeassistant_hardware not found: ['universal-silabs-flasher==0.0.30'].

My version is 2025.4.3

I know the requirement is a python dependency, how do I fix this?
Also, how do I view the raw logs?

Thanks

1 post - 1 participant

Read full topic

Hello everyone,
HAOS RPI4 Z2M
I use a Sonoff P dongle (cc2652p) as coordinator for 3 years, and it works quite well with 76 Zigbee devices, including 44 powered outlets and switches (routers), and two Sonoff P dongles in router mode for two remote access points (gate and garden at 15-20 m of the house).
However, I regularly have connection losses of these two routers and the associated devices .
I see a lot of posts about the Smlight SLZB-06, and I was wondering if it really improves network quality compared to the Sonoff P?
Has anyone migrated from the Sonoff P to the SLZB-06 and noticed a significant improvement?
Thanks for your feedback.

1 post - 1 participant

Read full topic

I have 3 problems with this code

1 icon is only bigger when it is active, I would like the icon to always be bigger.
2 I would like the primary text to be lower
3 I would also like the badge icon to be a bit bigger so that it is readable

unfortunately I can’t get any of the 3 to work. Anyone who wants to / can help me further?

type: custom:mushroom-template-card
primary: Woonkamer
icon: mdi:sofa
layout: vertical
grid_options:
  columns: 4
  rows: 2
badge_icon: >
  {% set number_woonkamer_tellen_aantal=states("sensor.woonkamer_tellen_aantal")
  | int %}

  {% if number_woonkamer_tellen_aantal > 9 %}

  mdi:numeric-9-plus

  {% elif number_woonkamer_tellen_aantal > 0 and number_woonkamer_tellen_aantal
  < 10 %}

  mdi:numeric-{{number_woonkamer_tellen_aantal}}

  {% endif %}
badge_color: green
secondary: ""
tap_action:
  action: navigate
  navigation_path: /db-mobiel2025/woonkamer
hold_action:
  action: none
double_tap_action:
  action: none
card_mod:
  style: |
    :host {
      {% if states('sensor.woonkamer_tellen_aantal') | int >= 1 %}
      --ha-card-background: #223448;
      {% endif %}
    }
    ha-state-icon {
      --mdc-icon-size: 64px !important;
    }
    mushroom-template-card .primary {
      margin-top: 20px !important;  # Verschuift de primaire tekst naar beneden
    }
    .badge {
      font-size: 36px !important;  # Verhoogt de grootte van het badge-icoon
    }

1 post - 1 participant

Read full topic

What are the methods I can use to detect me being at home besides WLAN?
I have several automations that depend on being home, coming home or leaving. They have run fine for a long time. My new phone logs off WLAN irregularly. It seems to be a known bug. I’m working on it, but there seems little I can do.
I’ve tried searching the documentation without success. What other methods can I use to detect, whether I am at home? I am not using the cloud and not using location services. My HA is strictly local.
One example: When my phone logged out before six this morning, HA saw me as not at home and did not start the coffee machine. In winter heating will be affected.
I know the cause is the buggy phone, but am looking for a workaround.

2 posts - 2 participants

Read full topic

HI, first post on pretty much any site.

I dont often require help however this has me stumped. Although new to HA and ESPHome I have 40 years in R&D writing all sorts of software, the last project using PHP, Jscript, JSON and SQL.

HA Versions

• Core 2025.4.1
• Supervisor 2025.04.0
• Operating System 15.1
• Frontend 20250404.0

ESPHome 2025.4.0

I have 3 ESPHome devices 2x esp cam 32 and one ESP07 with two relays and an i2c HTU21D all working perfectly.

I bought an Kincony KC868-AG to communicate with some Prolec 433M power sockets and also use the IR to control AV system.

I “stole” a base config for this from one of the HA websites. The first part of the conifg is identical to my other devices and defines base config for wifi etc. and that works.

The devices speciific code is show below

config below

remote_transmitter:

  - id: IR_Tx
    pin: GPIO2
    carrier_duty_percent: 50%

  - id: RF_Tx
    pin: GPIO22
    carrier_duty_percent: 100%
#    setup_priority: 599


remote_receiver:
  # see https://esphome.io/components/remote_transmitter.html#setting-up-infrared-devices
  # for details on discovering the correct codes for your devices
  - id: IR_Rx
    pin:
      number: GPIO23
      inverted: True
    dump: raw

  # see https://esphome.io/components/remote_transmitter.html#setting-up-rf-devices
  # for details on discovering the correct codes for your devices
  - id: RF_Rx
    pin:
      number: GPIO13
    dump: raw
    # Settings to optimize recognition of RF devices
    tolerance: 50%
    filter: 250us
    idle: 4ms
    buffer_size: 2kb


button:
  - platform: template
    name: Cat Lamp On
    on_press:
      then:
        - remote_transmitter.trasmit_raw:
          transmitter_id: RF_Tx
            code: [ -4609, 814, -509, 796, -523, 792, -532, 779, -539, 777, -1199, 1432, -1208, 1394 ]

So removing all of the button code it compiles and runs display received raw codes which is great.

Until we get to “button” this is pretty much the same as other websites which state that it works and yet when I hit install (effectivly compile) I get an error on the last line (code) which states “mapping values are not allowed here”.

I am unsure aboutt whether this is correct
…
- remote_transmitter.trasmit_raw:
transmitter_id: RF_Tx
…

and further I cannot see any indent issues. I am using the inbuilt ESPHome editor which substitutes tabs for spaces so it should be ok.

Any help anyone could render gratefully appreciates

Cheers

1 post - 1 participant

Read full topic