Hello, I’ve notices that the last Core version of HA had a ZHA quirk for the Tuya water consumption meter - TZE200, but a different version than mine - TZE200_vuwtqx0t.

At this point after trying many, many things I’m stil stuck using it in the Tuya app (only device that I cannot integrate into HA out of 50+), as even Tuya integrations do not expose any of it’s entities. It would be great to circumnavigate Tuya and connect it directly to ZHA, but without a quirk, no entities get exposed. I tried using the quirk that supports the other version, but no luck. Even though it is the same (physically) device.

1 post - 1 participant

Read full topic

I am using a Zooz Zen32 scene controller and I cannot seem to be able to trigger automations using entities. I am able to make it work by setting up the trigger by device. below are the yaml for both automations. The only way I am able to make the entity method work is changing the event type to KeyHeldDown. The keypressed and keypressedx2-5 event types do not trigger. I am only guessing that the entity method needs the keypressed event type to be persistent, since the state of the entity only changes to keypressed for a split second when pressing the physical button on the switch. For KeyHeldDown, it stays in that state for the duration that I hold the button down. I think I would have to build all the automation triggers by device, but I understand using entities is best practice. Hopefully, someone can point me in the right direction.

alias: Test device automation (working)
description: ""
triggers:
  - device_id: 2ac8ce2g0296ac7bd56d3dcf7cc781a3
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: "001"
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 001
    trigger: device
    value: 0
    id: shade_up
  - device_id: 2ac8ce2g0296ac7bd56d3dcf7cc781a3
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: "003"
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 003
    trigger: device
    value: 0
    id: shade_down
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - shade_up
        sequence:
          - action: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.window_server_front_relay_bo_1
      - conditions:
          - condition: trigger
            id:
              - shade_down
        sequence:
          - action: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.window_server_front_relay_bo_2
mode: single

alias: Test entity automation (not working)
description: ""
triggers:
  - trigger: state
    entity_id:
      - event.window_server_front_switch_scene_001
    attribute: event_type
    to: KeyPressed
    id: shade_up
  - trigger: state
    entity_id:
      - event.window_server_front_switch_scene_003
    attribute: event_type
    to: KeyPressed
    id: shade_down
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - shade_up
        sequence:
          - action: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.window_server_front_relay_bo_1
      - conditions:
          - condition: trigger
            id:
              - shade_down
        sequence:
          - action: switch.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: switch.window_server_front_relay_bo_2
mode: single

1 post - 1 participant

Read full topic

Hey kings.

I have made this automation for the computer room.
Basically I want the blind to close when the PC is turned on and the sun is up and to then open when the PC is turned off provided the sun is still up.

This seems to work but was wondering if it could be streamlined?

I am using a wall plug to trigger the event based on the power draw.

thanks!

alias: "computer room blind test "
description: ""
triggers:
  - type: power
    device_id: cb0bff78b458fc3d09ac48e1d0997931
    entity_id: 04f2ec3fc203165ee8a3565d6d798279
    domain: sensor
    trigger: device
    above: 20
conditions:
  - condition: sun
    before: sunset
    after: sunrise
actions:
  - action: cover.close_cover
    metadata: {}
    data: {}
    target:
      entity_id: cover.computer_room_roller_blind
  - if:
      - type: is_power
        condition: device
        device_id: cb0bff78b458fc3d09ac48e1d0997931
        entity_id: 04f2ec3fc203165ee8a3565d6d798279
        domain: sensor
        below: 5
      - condition: sun
        before: sunset
    then:
      - action: cover.open_cover
        metadata: {}
        data: {}
        target:
          entity_id: cover.computer_room_roller_blind
mode: single

1 post - 1 participant

Read full topic

hi ,i’m trying to use a local usb speakerphone directly connected to my home assistant server. I have installed the OPENWAKEWORD addon , uninstall ,reinstall and it doesnt show up in discovered…, and i’ve looked online , and i dont see the 3 dot in assistant configuration window to choose local wake word. Am i missing something ? if someone would help it be nice .

3 posts - 1 participant

Read full topic

Hello. I just installed a CM4 with an NVMe SSD on my new Home Assistant Yellow (HA Yellow). The boot-up was uneventful, but I suddenly noticed the following error in the logs:

Source: helpers/entity_platform.py:382
integration: Update (documentation, issues)
First occurred: 9:47:03 AM (1 occurrences)
Last logged: 9:47:03 AM

Error while setting up homeassistant_yellow platform for update: 'firmware_version'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/usr/src/homeassistant/homeassistant/components/homeassistant_yellow/update.py", line 165, in async_setup_entry
    entity = _async_create_update_entity(
        hass, config_entry, session, async_add_entities
    )
  File "/usr/src/homeassistant/homeassistant/components/homeassistant_yellow/update.py", line 127, in _async_create_update_entity
    entity = FirmwareUpdateEntity(
        device=RADIO_DEVICE,
    ...<6 lines>...
        entity_description=entity_description,
    )
  File "/usr/src/homeassistant/homeassistant/components/homeassistant_yellow/update.py", line 199, in __init__
    firmware_version=self._config_entry.data[FIRMWARE_VERSION],
                     ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
KeyError: 'firmware_version'

I noticed that the Zigbee Home Automation (ZHA) integration was automatically set up without me configuring anything. Under Settings > Devices & Services, ZHA lists a device:

• Connected via: Nabu Casa Yellow v1.3
• Firmware: 6.10.3.0 build 297

I’m confused because the error suggests that the firmware_version is missing, but the ZHA integration clearly shows the firmware version (6.10.3.0 build 297), and the radio seems ready to use. I haven’t paired any Zigbee devices yet, as I’m trying to avoid interfering with my primary setup on a Home Assistant Green (which uses Zigbee2MQTT with a SkyConnect coordinator).

Any ideas on what might be causing this issue? Is this a bug in the homeassistant_yellow integration, or did I miss a step during setup?

Running on updated core 2025.04.2 and HAOS 15.2.

1 post - 1 participant

Read full topic

My Home Assistant (latest version 2025.4.2) is reporting that four of my Matter devices need updates. They are all Eve Energy Matter switches (not updated to Matter via a firmware update).

It’s reporting the devices firmware is 3.2.1 (which in fact is the current version), but say they need to be updated to 3.5.0. There are Eve devices that have such an update, but not the power swtiches called Eve Energy. Anyway, I’m just going to tell HA to ignore this update for now and check back and do the updates manually.

Please figure out what’s wrong here. It’s not on my end, so it’s something in Home Assistant that is misidentifying the need for an update. Thanks!

1 post - 1 participant

Read full topic

Does HA support multiple instances of emulated_hue: in the same config (like ‘emulated_hue_1’, ‘emulated_hue_2’) on different ports or IP addresses?

I have Alexa triggering an input_boolean to make a REST call to a PC which then runs a script, and I’d like to have multiples without spinning up additional HA instances.

Thanks.

1 post - 1 participant

Read full topic

I’m looking for help with creating a formatted Markdown card. I have tried searching the form (several similar questions since 2022 that are never answered by anyone) and four different AIs… I spent an hour trying them, nothing worked.

I simply want to set the column size so that no matter what the text is, the columns are always wide enough. they dont look good right now…

here’s the YAML, appreciate if someone has the knowledge to share please do. I’d like to learn by a real world example - thank you.

type: markdown
content: >-
  {% set input_minutes = 1440 %}

  {% set hours = (input_minutes // 60) %} {% set minutes = input_minutes % 60 %}

  {% set display_time = '' %} {% if hours > 0 %}
    {% set display_time = display_time ~ hours | int ~ ' hr' ~ ('s' if hours > 1 else '') %}
  {% endif %} {% if minutes > 0 %}
    {% set display_time = display_time ~ ' ' ~ minutes | int ~ ' min' %}
  {% elif hours == 0 %}
    {% set display_time = '0 min' %}
  {% endif %}

  {% set ns = namespace(sensor_name_time=[]) %}

  {% for entity in states.binary_sensor %}
    {% if 'binary_sensor.alarm_' in entity.entity_id %}
      {% if ('door' in entity.name | lower or 
             (entity.attributes.device_class is defined and 
              entity.attributes.device_class == 'door')) %}

        {% set name_without_door = entity.name
           | replace(" Door", "")
           | replace(" Sensor", "")
           | replace("Door ", "")
           | replace("Sensor ", "") %}
        
        {% set time_diff = (now() - entity.last_changed).total_seconds() %}
        {% set hours = (time_diff // 3600) | int %}
        {% set minutes = ((time_diff % 3600) // 60) | int %}
        
        {% set time_display = '' %}
        {% if hours > 0 %}
          {% set time_display = time_display ~ hours ~ ' hr' ~ ('s' if hours > 1 else '') %}
        {% endif %}
        {% if minutes > 0 %}
          {% set time_display = time_display ~ ' ' ~ minutes ~ ' min' %}
        {% elif hours == 0 %}
          {% set time_display = '0 min' %}
        {% endif %}
        
        {% set ns.sensor_name_time = ns.sensor_name_time + [{
            "name": name_without_door,
            "time": time_display,
            "state": entity.state,
            "last_changed": entity.last_changed
        }] %}
      {% endif %}
    {% endif %}
  {% endfor %}

  {% set myList = ns.sensor_name_time | sort(attribute='last_changed',
  reverse=true) %}

  {% if myList | count > 0 %}
    ## Door Activity
    
    |  | Last Change |  |
    |:-----------|------------------:|:----------:|
    {%- for each in myList %} 
    | {% if each.state == 'on' %}<font color="yellow">{{ each.name }}</font>{% else %}{{ each.name }}{% endif %} | {% if each.state == 'on' %}<font color="yellow">{{ each.time }}</font>{% else %}{{ each.time }}{% endif %} | {% if each.state == 'on' %}<ha-icon icon="mdi:door-open" style="color: blue;"></ha-icon>{% endif %} |
    {%- endfor %}
  {% else %}
    ## <ha-icon icon="mdi:door-open"></ha-icon> Door Activity
    
    No activity in the last {{ display_time }}
  {% endif %}

1 post - 1 participant

Read full topic

I’m using the GUI to add a wait template where I want it to continue the automation when 2 sensor values have decreased to 12. Values are the state of charge percentages from 2 batteries.

What needs to be added to get this wait template to work?

{{states(‘sensor.lilygo_rs485_venus_3_marstek_battery_state_of_charge’)==‘12’}}"
{{states(‘sensor.lilygo_rs485_venus_4_marstek_battery_state_of_charge’)==‘12’}}"

6 posts - 3 participants

Read full topic

what is wrong in my script, i never get …count > 0 when add the same item?

sequence:
  - variables:
      var: "{{ variables.todoitems }}"
  - repeat:
      for_each: "{{ var.split(',') }}"
      sequence:
        - if:
            - condition: or
              conditions:
                - condition: template
                  value_template: "{{ '+' in repeat.item }}"
                - condition: template
                  value_template: "{{['todo.todoliste']['items']|selectattr('summary','search',repeat.item)|list|count > 0}}"
          then: null
          else:
            - action: todo.add_item
              metadata: {}
              data:
                item: "{{repeat.item}}"
                due_date: "{{ (now() + timedelta(days=1)).strftime('%Y-%m-%d') }}"
              target:
                entity_id: todo.todoliste
alias: todo_add_items
description: ""

2 posts - 2 participants

Read full topic

I’ve been switching products from Philips Hue and I’ve removed my last Philips bulb from the system and have added 2 of my 3 FLS-PP directly to HA without any problems but the third one is not being discovered during onboarding. The other 2 were fine, discovery went without a hitch but this 3rd one is proving to be a bit of a pain.

I’ve done the reset process, (power on/off cycle) and that seemed to work okay as in the LED strip flashed at the end of the sequence and then went to a what looked like default mode (pure white, 100% bright?) but still no dice. I can add it back to Hue hub without a problem and research says that there was an issue with earlier ones locking into a channel or a device? Can’t find much more on that or which firmware version it was etc.

Question is, is there a way to update the firmware or unlock it from the channel/change HA channel to match?

I deleted the device from the Hue before trying to add it to HA. ‘hardware platform version’ is 1135-0 and software is 020, if that means anything to anyone. I assume it’s like a firmware version.

1 post - 1 participant

Read full topic

Does anyone have a moment to cast their eyes over this?

It’s a fork of the nationalrail component, where I’m trying to standardise storage and usage of the API token, the sensor loads, but I get

Traceback (most recent call last):
  File "/config/custom_components/nationalrailuk/client.py", line 264, in async_get_data
    data = self.process_data(raw_data)
  File "/config/custom_components/nationalrailuk/client.py", line 203, in process_data
    expected_arrival = rebuild_date(time_base, dest["st"])
                                               ~~~~^^^^^^
TypeError: string indices must be integers, not 'str'

and Error validating API token: unexpected data from api

1 post - 1 participant

Read full topic

So there I go, I do have 3 floor house, using sonoff devices through Zbbridge and philips hue light through bridge of philips. And everything is connected to 3 lan devices of tp link. And turns out some sonoff devices lose connection when philips light are on. I did try Zha automation but can’t connected MiniR4 so… don’t really know what to do. Can someone help me out

1 post - 1 participant

Read full topic

I got a Shelly Dimmer 2 that I wrote some automation for to increase the brightness when my TV turns off, and it’s not already above a certain brightness.

alias: Nach Ausschalten von Shield Licht Couch auf 3% setzen
description: ""
triggers:
  - type: turned_off
    device_id: 2c604168eacd9f7d402cbbc62be15a27
    entity_id: 81c94c492e3f7faface655e3bcbf257c
    domain: remote
    trigger: device
conditions:
  - condition: numeric_state
    entity_id: light.licht_couch
    attribute: brightness
    below: 2
actions:
  - type: turn_on
    device_id: c9d902cf185e86540f2f90b08fafddfc
    entity_id: f9d040b10bdb9255352308a4355ec6d8
    domain: light
    brightness_pct: 3
mode: single

The automation works fine, except for the brightness condition. I assumed that the brightness attribute of the entity would be equal to what is shown in the toggle button in the dashboard. For example, this is the toggle for that entity when it is on and set to 20%. As you can see in the settings of that toggle button, it belongs to that entity. But in the developer tools, the brightness value of that entity is completely different (51):

I am very confused by this and must be gettings something completely wrong. Where are the brightness values of that entity coming from, how can I reference the value that I as a simple user can see in the UI of the dashboard button, and how am I supposed to discover this myself?

1 post - 1 participant

Read full topic

I’m trying to create an automation for kitchen freezer.
There is a temperature sensor in it and I would like to get an notification in my iPhone when the temperature goes above -18 degrees.

Below is the code I created and it is not working. The sensor works, but no notification is sent.

Hope somebody can help, because I’m sure many must have this kind of automation.

alias: pakastimen lämpiäminen
description: Hälyttää jos pakastimen lämpötila nousee yli -18 asteen.
triggers:
  - trigger: numeric_state
    entity_id:
      - sensor.pakastimen_lampotilasensori_temperature
    above: -18
    value_template: "  "
conditions: []
actions:
  - action: notify.mobile_app_iphone_marko
    data:
      message: The freezer is getting warmer. Do something, man!
      title: The freezer alert
mode: single

3 posts - 2 participants

Read full topic

Hi all,

I have a notification which sends me the value of a entity but with too many decimals. How do I define how many decimals i want?

5 posts - 3 participants

Read full topic

Hello.

Tried asking about this in the Wireguard Add-on thread, but got no response. As far as I, as a total layman, can deduce, it very possibly isn’t even the problem with the Add-on, but with the HA.

I’ve got HAOS installed on two identical (pretty old) Intel NUCs (Pentium Silver j5005, 16GB RAM) on two different locations. Also have installed the Wireguard Add-on on both of them, configured to use them/it as a site-to-site VPN solution.

For about a year everything worked fine, the LOCAL_LAN clients could reach the REMOTE_LAN clients, LOCAL_LAN clients could reach the REMOTE_HA, REMOTE_LAN clients could reach the LOCAL_LAN clients and LOCAL_HA instance.

Suddenly, about a month (maybe a bit more) ago, the setup partially stopped working. The part, of course, that’s most important for me. REMOTE_HA can reach both LOCAL_HA and LOCAL_LAN clients, LOCAL_HA can reach both REMOTE_HA and REMOTE_LAN clients, but the clients themselves can’t reach each other nor the HA instance remote to them via the VPN. When doing traceroute from a client, the traffic reaches the HA instalnce local to the client, but just times out there. The ipables -S in the underlying OS shows that forward is enabled, the iproute in both HA instances shows traffic is to be routed to/through the add-on.

Please help. Thanks in advance.

1 post - 1 participant

Read full topic

I managed to disassembly it by removing the rivets, you can replace the rivets with a m2 bolt and nut, just ensure to enlarge holes by drilling them only on the surface with an 5.5 drill, then enlarge the central holes with a 2.5 drill.

The procedure is somewhat similar to any CBU - (generic-bk7231n-qfn32-tuya), you can take 3.3v and ground from there (red circles, check for ground by touching metal shell of cbu, the other pin is 3v3):

Config is really simple, down below, what you won’t find is the remote lock, commented out, since I haven’t found any way to communicate the lock with the apparatus, but AFAIC it’s not a functionality I would use anyway.

substitutions:
  name: R3_WIFI3
  friendly_name: Your Preferred Name
  
bk72xx:
  board: generic-bk7231n-qfn32-tuya

esphome:
  name: $name
  friendly_name: $friendly_name
  min_version: 2024.11.0
  name_add_mac_suffix: false

preferences:
  flash_write_interval: 
    seconds: 30

# Enable logging
logger:
  level: DEBUG

# Enable Home Assistant API
api:
  encryption:
    key: !secret api
  reboot_timeout: 120min

ota:
  - platform: esphome
    password: !secret ota

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: $name
    password: !secret ap
  reboot_timeout: 0s #120min  

captive_portal:

button:
  - platform: restart
    name: "Restart"
    id: button_restart

mdns:

debug:
  update_interval: 30s

text_sensor:
  - platform: libretiny
    version:
      name: LibreTiny Version

sensor:
  - platform: wifi_signal
    name: "RSSI"
    id: sensor_rssi
    update_interval: 30s
    entity_category: "diagnostic"
  - platform: uptime
    name: "Uptime"
    id: sensor_uptime
    update_interval: 60s
    entity_category: "diagnostic"
  - platform: tuya
    sensor_datapoint: 102
    name: Mechanic Lock
  #- platform: tuya
  #  sensor_datapoint: 103
  #  name: Remote Lock
  - platform: tuya
    sensor_datapoint: 104
    name: Local Lock

uart:
  rx_pin: RX1
  tx_pin: TX1
  baud_rate: 115200

tuya:

switch:
  - platform: tuya
    switch_datapoint: 1
    name: Switch
    restore_mode: RESTORE_DEFAULT_OFF

1 post - 1 participant

Read full topic

I really like the idea of having my own voice assistant, but the kids mostly use it for playing music and audiobooks which are coming from Apple Music or some other service. Are there any plans to integrate 3rd party music services.

Greets

Stephan

4 posts - 3 participants

Read full topic

I have HA remote access through NabuCasa cloud and I have it linked to my custom domain.

Past week, I’ve noticed that browser throws out too many redirects error, which is only solvable by clearing the cookies. Clearing the cache does not help.

Things that have happened recently:

• HA OS updated to 15.1 and later to 15.2
• HA vscode extension has been updated

All the rest is fully up to date as of today (April 16th, 2025).

Am I the only one with this issue?

Edit: There is like 65MB of cookies data.

1 post - 1 participant

Read full topic