Simply put, I’m trying to add the humidity from the same device (thermostat) to the secondary information section of this mushroom climate card:

From the UI editor I only have a few options to choose from: Default, Name, State, Last Changed, Last Updated and None

When I try to add it via the code editor I get error messages saying that it’s looking for one of the above terms:

It says that I can edit this via YAML but I’m not quite sure where I’d go about editing it. I assume it means that I need to add that entity so that it shows up as an option in the drop-down from the options I listed above. This feels well above my experience level as I’m missing a key piece somewhere.

I went into Studio Code Server to try to see if there’s an obvious place or Mushroom file I can make this change in but didn’t see anything obvious enough that I felt comfortable messing with it. Seemed like a good spot to admit defeat and ask for help from those who know as this feels like an easier option than what it seems in my head.

I did some searching but much of what I found was pretty dated and/or not relevant stuff about edits and modifications but nothing seemed to touch what I’m asking for specifically with just adding the state of an entity.

1 post - 1 participant

Read full topic

I’m at my wits end here! I’m trying to get the current hvac mode for my nest thermostat, using:

state.get(“climate.hallway.hvac_mode”)

However it’s spitting out the following error:

state.get(“climate.hallway.hvac_mode”) ^ AttributeError: state ‘climate.hallway’ has no attribute ‘hvac_mode’

According to the documentation, hvac_mode should be the correct attribute. Am I missing something here?

Edit: I can set the temperature through pyscript, and I can see/change everything through the card, including the hvac mode. Just can’t find how to access that information through pyscript.

1 post - 1 participant

Read full topic

I am struggling to get a docker container installation to find my network adapters. I have my local lan and a vlan with my iot devices. Basically, it appears that the container sees the network and Home Assistant sees it but it is disabled.

You can see that eth0 is disabled in the System Information.

And for some reason I don’t have an option for network adapters where I normally would. I cant post a second screenshot due to having a new account.

This is a brand new installation so everything is the default except my docker compose file which shows this:

services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /opt/homeassistant/config:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    restart: unless-stopped
    privileged: true
#    network_mode: host
    networks:
      lan:
        mac_address: 78:c7:85:40:56:23
        ipv4_address: 192.168.1.30
      iot_lan:
        mac_address: 78:c7:85:40:57:24
        ipv4_address: 192.168.10.30

networks:
  lan:
    driver: macvlan
    driver_opts:
      parent: enp4s0
    ipam:
      config:
        - subnet: 192.168.1.0/24
          gateway: 192.168.1.1
  iot_lan:
    driver: macvlan
    driver_opts:
      parent: enp4s0.10
    ipam:
      config:
        - subnet: 192.168.10.0/24
          gateway: 192.168.10.1

Running docker network ls shows the networks are there as well:

f522ab5edc8f   homeassistant_default     bridge    local
53627c8b977b   homeassistant_lan         macvlan   local
c943e5338a69   homeassistant_iot_lan   macvlan   local

Is there anything that I am missing in this setup? I can’t find any one having the same issue.

2 posts - 2 participants

Read full topic

I ask because I keep seeing people’s dashboards that have the type of area/room card/tile that I’d like on my dashboard but I’ve explored the included cards/tiles as well as have Mushroom installed and I still don’t seem to be able to click my way to something like what I see. The fact that there are so many similar dashboards tells me that a lot of people have similar custom-coded dashboards or there’s something simple that’s baked in that I’m missing.

For reference, here’s a few samples of what I’m talking about:

To spell out what, specifically, I’m looking for: a card that allows me to have each room name, temp & humidity, a corresponding icon as well as 2-3 little toggles that I can customize with things like maps, fans, etc. for that particular room. Then, a single tap takes me to that room’s subpage for more devices to manage.

What I have currently looks like this:

I like how the above images show two rooms per row, and then each one is equal-ish height to allow more space for info & toggles. I’m just trying to get mine (mushroom cards currently, I think) to look & act more like the ones I posted above.

I tried a horizontal stack with the default “Area” card but the ability to add device toggles & current temp/humidity readings to the card were lacking. I tried to use the “horizontal” option and then select areas but it was mashing things up a bit much in terms of the icon being dead center and laying over the top of other aspects.

So is the only way to achieve these same basic ideas (I don’t need exactly like these in terms of fonts, themes or curved corners or anything like that) to custom code or is there a UI version of these or way to modify the UI options to get similar results, hence why I’m seeing so many of these?

1 post - 1 participant

Read full topic

In a calendar how do you set different target temperatures for different events? For instance in my village hall application an aerobics class doesn’t want the room as hot as say an old peoples’ lunch club.

One option is to write into the event title on the calendar the temperature, so the events become say “10am Aerobics 18C” and 12am Lunch 20C”. Or the temperature could go into the Description box of the event. Then with some code I extract the 18 or 20 numbers and use that as the target temperature. Is this easy to do?
If using the Description box it would be useful to have a figure like 18 always pop up there so it’s the default unless overridden when setting up an event

Any other ideas please?

2 posts - 2 participants

Read full topic

Hi all.

Running Home Assistant Yellow using ZigBee devices through ZigBee2MQTT. Software-wise all is up to date. Core 2025.4.2, Supervisor 2025.04.0; Operating System: 15.2. Now to the point.
I’ve two of the pilots/buttons mentioned in the title - [Marmitek] Zigbee2MQTT). Both were working fine, but on Monday my cat sat for a moment on one of them. After it left I noticed that the button’s LED is blinking like it’s pairing and it stopped working (I’ve it configured to toggle the lights). I went into the Z2M device list and tried to re-interview it but it didn’t work. So I removed it from the network. Now I;m trying to reconnect it but it just won’t reconnect. It constantly blinking LED as it would be paring but nothing happens. I don’t think it’s in pairing mode, as it was blinking all night and all other devices I have stopped blinking and went into sleep mode after a minute or so. I tried to remove the battery for a few hour (like 10-12h) and after reinserting it does the same - blinking, not connecting.

Just to be sure it’s not the Z2M or HA problem I removed one of my PIR sensors from the network the same way I removed the broken button and after I went with PIR pairing it was discovered and interviewed properly in a few seconds, so HA and Z2M works fine. All other devices on Z2M are also working well (I have close to 40 devices on the network, half of them on grid power).

Is it possible to salvage this device?
The PCB is marked “esw-4zaa-cn” and uses the ZS3L chip if that helps.

2 posts - 2 participants

Read full topic

Hi everyone,

I’ve been experiencing issues with Bluetooth since the April updates (2025.3.x). I’m getting an “Invalid config” error for the bluetooth_adapters integration, but when I check the logs, there’s absolutely nothing related to Bluetooth.

The error message is:

Invalid config The following integrations and platforms could not be set up: bluetooth_adapters (Show logs)

And the logs are empty.

I’ve tried using a new Bluetooth dongle, but the problem persists. I also attempted to force the adapter in my configuration.yaml with the following:

YAMLbluetooth: adapters: - mac_address: "30:68:93:B9:4C:AF" active: true

However, I’m still encountering the same issue. As a result, my HomeKit setup (via HomeBridge) is no longer working either.

When I revert back to version 2025.2.5, everything works perfectly.

My setup is Home Assistant OS running on an Intel NUC.

Has anyone else experienced this or have any ideas on what might be causing this and how to resolve it?

Thanks in advance for any help!

1 post - 1 participant

Read full topic

I have an immersion heater that I control with a smart switch.

I have an automation that runs at 9pm every evening, that triggers a “confirmable notification” sent to my phone, to ask if I want the hot water to turn on tomorrow morning.

I have an automation that turns it on at 06:00.

If I select “yes” in the “confirmable notification”, I ‘turn on automation’
If I select “No” in the “confirmable notification”, I ‘turn off automation’

I also have two “threshold sensor” helpers, and two automations that turn off the immersion heater at the two sensor temperatures: 45 and 70 deg C

I’m trying to work out how to get the phone notification to ask me what temperature I want (45 or 70) once I’ve selected ‘yes’, so that I can turn on or off the appropriate temperature control automation.

Can anyone help me with this please?

1 post - 1 participant

Read full topic

Hey everyone i am trying to install Zigbee2MQTT to my home assistant which is running on a raspberry pi 5 and a sonoff zigbee donlge p. my config is this but i keep getting this error message i would love it if anyone has an advice for me.

data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: “-d -d”
log: false
mqtt: {}
serial:
port: /dev/ttyUSB0
adapter: zstack

Error Message:

[00:17:28] INFO: Preparing to start…
[00:17:28] INFO: Socat not enabled
[00:17:28] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2025-04-17 00:17:29] info: z2m: Logging to console, file (filename: log.log)
[2025-04-17 00:17:29] info: z2m: Starting Zigbee2MQTT version 2.2.1 (commit #unknown)
[2025-04-17 00:17:29] info: z2m: Starting zigbee-herdsman (3.4.11)
[2025-04-17 00:17:29] info: zh:adapter:discovery: Matched adapter: {“path”:“/dev/ttyUSB0”,“manufacturer”:“ITead”,“serialNumber”:“da39c046725aee11931581dc8ffcc75d”,“pnpId”:“usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_da39c046725aee11931581dc8ffcc75d-if00-port0”,“vendorId”:“10c4”,“productId”:“ea60”} => zstack: 4
[2025-04-17 00:17:29] info: zh:zstack:znp: Opening SerialPort with {“path”:“/dev/ttyUSB0”,“baudRate”:230400,“rtscts”:true,“autoOpen”:false}
[2025-04-17 00:17:29] info: zh:zstack:znp: Serialport opened
[2025-04-17 00:17:29] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-04-17 00:17:31] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-04-17 00:17:49] error: z2m: Error while starting zigbee-herdsman
[2025-04-17 00:17:49] error: z2m: Failed to start zigbee-herdsman
[2025-04-17 00:17:49] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-04-17 00:17:49] error: z2m: Exiting…
[2025-04-17 00:17:49] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@3.4.11/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:113:27)
at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@3.4.11/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:104:13)
at start (/app/index.js:149:5)

3 posts - 3 participants

Read full topic

Please check my code and why the cell colour does not change when cell=min_cell or max_cell.

type: grid
        cards:
          - type: grid
            cards:
              - type: markdown
                content: |2-
                            <center><font color="#18f50c"><font size=3>01.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor.accu_bms0_max_cell_voltage') == '1' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_1') }}
                            V</font> {% elif states('sensor.accu_bms0_min_cell_voltage') ==
                            '1' %}  <font color="orange">{{
                            states('sensor.accu_bms0_cell_1') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_1') }} V {% endif %}    
                            <br>
                            02.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor..accu_bms0_max_cell_voltage') == '2' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_2') }}
                            V</font> {% elif states('sensor.jk_bms_min_voltage_cell') ==
                            '2' %} <font color="orange">{{
                            states('sensor.accu_bms0_cell_2') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_2') }} V {% endif %}<br>
                            03.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor..accu_bms0_max_cell_voltage') == '3' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_3') }}
                            V</font> {% elif states('sensor..accu_bms0_min_cell_voltage') ==
                            '3' %} <font color="orange">{{
                            states('sensor.accu_bms0_cell_3') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_3') }} V {% endif %}
                            <br>
                            04.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor..accu_bms0_max_cell_voltage') == '4' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_4') }}
                            V</font> {% elif states('sensor..accu_bms0_min_cell_voltage') ==
                            '4' %} <font color="orange">{{
                            states('sensor.accu_bms0_cell_4') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_4') }} V {% endif %}
                            <br>
                            05.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor..accu_bms0_max_cell_voltage') == '5' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_5') }}
                            V</font> {% elif states('sensor..accu_bms0_min_cell_voltage') ==
                            '5' %} <font color="orange">{{
                            states('sensor.accu_bms0_cell_5') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_5') }} V {% endif %}
                            <br>
                            06.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {% if
                            states('sensor..accu_bms0_max_cell_voltage') == '6' %}  <font
                            color="#3090C7">{{ states('sensor.accu_bms0_cell_6') }}
                            V</font> {% elif states('sensor..accu_bms0_min_cell_voltage') ==
                            '6' %} <font color="orange">{{
                            states('sensor.accu_bms0_cell_6') }} V</font> {% else %}
                            {{ states('sensor.accu_bms0_cell_6') }} V {% endif %}
                            <br>
                card_mod:
                  style: |
                    ha-card {
                       box-shadow: none;
                       background: rgba(0,0,0,0);
                       border: white solid 1px !important;
                    }

2 posts - 2 participants

Read full topic

When I rename a device, any automation referencing entities of that device will break. Is this a bug?

The entities are in fact renamed correctly, but automations that reference those entities are not updated. For example:
Let’s say I have a smart plug called “P V2 ladeblok Au3 alleen router” in ZHA:

and an automation that references the power entity:

When I rename the device to “P V2 Au3 router only”:

I get the option to rename entities:

I want that, so I click Rename. However, when I go to my automation, the reference is broken. The automation now lists the old Entity ID, not the new entity name.

Is this a bug?

1 post - 1 participant

Read full topic

I need a virtual entity for lawn_mower for testing.
Is there any integration providing a virtual entity of this domain?

1 post - 1 participant

Read full topic

After updating to 2025.4.2 (I skipped over 4.1) My keen smart vent vent devices have dropped the cover entity which is used to open and close the vents.

I have removed and re-added the device and the problem persists.

The error I received on my dashboard when opening or closing the vent was “Failed to perform the action cover/set_cover_position. ‘KeenVent’ object has no attribute ‘current_cover_tilt_position’”

When I add the device back the temp, pressure, battery and identify attributes show up and work but the cover entity shows up but is “unavailable”

These Keen vents relied on quirks before. I wonder if the quirks got dropped or if something broke the quirks.

I find this error in the log:

Logger: homeassistant.components.cover
Source: helpers/entity_platform.py:633
integration: Cover (documentation, issues)
First occurred: 3:01:50 PM (1 occurrences)
Last logged: 3:01:50 PM

Error adding entity cover.keen_home_inc_sv02_612_mp_1_3 for domain cover with platform zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 633, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 972, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1384, in add_to_platform_finish
    self.async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1023, in async_write_ha_state
    self._async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1148, in _async_write_ha_state
    self.__async_calculate_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1087, in __async_calculate_state
    if state_attributes := self.state_attributes:
                           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/cover/__init__.py", line 294, in state_attributes
    if (current_tilt := self.current_cover_tilt_position) is not None:
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/cover.py", line 125, in current_cover_tilt_position
    return self.entity_data.entity.current_cover_tilt_position
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'KeenVent' object has no attribute 'current_cover_tilt_position'. Did you mean: 'current_cover_position'?

I’m unsure how to proceed.

1 post - 1 participant

Read full topic

Anyone know when HA will receive some attention when it comes to dual-homed setups? My HA servers has NIC’s on two different VLAN’s… Whenever it reboots, it’s kinda a nightmare to ensure the proper NIC is configured as “default”… Otherwise the routing doesn’t work.

1 post - 1 participant

Read full topic

I setup Home Assistant Local, Ollama, and ChatGPT. I can’t for the life of me get any of these to work. I understand that the first two are locally and will have to setup (which I’m new to all this). The YT videos I’m come across were semi-helpful, but set me deeper into the weeds. ChatGPT API I have it set up to use the internet, but that’s giving me the wrong town.

Home Assistant (installed on a ODroid M1)
Agent: Home Assistant
STT: faster-whisper
TTS: piper

Ollama
Home Assistant
Agent: llama3.2 (hosted on another computer)
STT: faster-whisper (working offloading onto another computer, model not loading)
TTS: piper (working on offloading onto another computer.)

ChatGPT
Home Assistant
Agent: ChatGPT (04-mini)
STT: faster-whisper
TTS: piper

Tried setting automation using Weather: Get Forecasts.

Keep in mind that my coding skill is that of a rock, but I can follow directions pretty good. My HA knowledge is a little better, but enough to be dangerous.

2 posts - 2 participants

Read full topic

Hi there
Trying to get one of these controlled locally in HA. I can integrate the light without issue BUT in the Light Preset option of the integration it shows Not Set even though I have saved presets like color painted zones etc.

Anyone know how to resolve this or have a workaround for getting light presets to show and not show the Not Set ?

Thanks

1 post - 1 participant

Read full topic

I have created a card with conditional visibility:

type: entity
entity: sensor.glances_process_plex_media_serv
attribute: name
icon: mdi:server
name: Plex Media Server Status
state_color: true
visibility:
  - condition: state
    entity: sensor.glances_process_plex_media_serv
    state_not: unavailable

When the sensor is available, the card is visible, but when sensor becomes unavailable, the card is not visible. This is how the card is expected to work.

But, the problem is that if the sensor remains unavailable for a long time, like 2-3 days, the card becomes visible again with an error that entity is not available. This should not happen. The card should stay invisible if the sensor is not available, no matter for how long.

What can be done to fix the issue?
Thanks…

1 post - 1 participant

Read full topic

So I have an automation that dims my backyard lights at 11 PM daily. I also have another automation that turns of my pergola lights (subset of the backyard lights) when something is playing on my outdoor TV and then turns it back on when playing stops at a higher brightness.

For the 11 PM automation, it only executes if the TV is not playing.

I was wondering if there is a way I can configure that automation to execute once the TV stops playing but only if the TV is playing, otherwise execute immediately.

2 posts - 2 participants

Read full topic

Hello Community,

I’m relatively new to Home Assistant (using it for a few months), and I’ve been stuck with a persistent issue around OTA firmware updates for my Bosch thermostats (model RBSH-TRV0-ZB-EU) using Zigbee2MQTT.
Before posting, I looked for similar topics, but nothing matched my exact combination of devices and symptoms.

Setup

• Home Assistant: Docker (Supervisor)
• Zigbee2MQTT Version: 2.2.1-1
• Zigbee Coordinator: ZBT-1 (CC2652-based, via USB extension cable)
• Zigbee Channel: Default (not set → likely channel 11)
• Hue Bridge: Zigbee Channel 15
• Wi-Fi 2.4GHz: Channel 11 (manually changed from 7)
• Wi-Fi 5GHz: Channels 36, 40, 44, 48
• Router: Speedport Smart 2
• Devices: 17 Zigbee devices (all via MQTT), including multiple Bosch TRVs

Problem Description

• OTA updates are extremely slow or fail completely.
• The update starts (e.g. for bad_heizung), progresses to ~30–70%, then stops.
• Zigbee2MQTT logs show UART-related errors:
  Error: {“sequence”:1} after 4000ms
  Can’t send DATA frame …

Home Assistant logs show errors from better_thermostat, even though I’ve removed its configuration:

ValueError: could not convert string to float: ‘unavailable’

• The MQTT connection resets, and entities like climate.bad_heizung_thermostat disappear temporarily.

What I’ve Tried

• OTA updates one device at a time
• Thermostats placed directly next to the Zigbee coordinator
• Full restarts: Zigbee2MQTT, MQTT broker, Home Assistant
• Removed better_thermostat from configuration.yaml (no entries left)
• WLAN 2.4GHz channel changed from 7 → 11 (to reduce interference with Zigbee)
• Ports 80 & 443 open (OTA file download confirmed working)

Observations

• Moving Wi-Fi to channel 11 significantly improved stability (less Zigbee overlap)
• Despite no active config, better_thermostat still causes crashes during OTA
• Hue Bridge (on Zigbee channel 15) is unaffected
• One OTA update completed fully, then the same issue reappeared on the next attempt

Questions

1. Are Bosch TRVs (RBSH-TRV0-ZB-EU) known to have OTA issues with Zigbee2MQTT?
2. How can I fully remove or disable better_thermostat if no config entries exist?
3. Is there a way to prevent MQTT from breaking during OTA (“unavailable” payloads)?
4. Are there OTA tuning options (chunk size, retries) that could help?
5. Would it be safer to switch to Zigbee channel 20 (to avoid Wi-Fi), even though the Hue Bridge uses channel 15?

Thanks a lot for any insights or suggestions – much appreciated!

MixDax

1 post - 1 participant

Read full topic

1 post - 1 participant

Read full topic