Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 109599 articles
Browse latest View live

Multiple entities within a trigger

$
0
0

When making a trigger for an automation I noticed you can add multiple entities. I am not sure how this works and the documentation seems to be lacking. When I search on Google for multiple entities in a trigger I find fairly old post referring to some blueprints. It seems that this was written when there weren’t multiple entities in a trigger yet.
Can someone explain or refer to a document where it’s explained what it does en how to use it properly? Is it an ‘and’ or ‘or’ function for example.

Say in the following trigger (current_position 0 is closed, 100 is open). does it trigger when 1 of the curtains is not open or when all are not open?

  - trigger: numeric_state
    entity_id:
      - cover.diningroom_curtain
      - cover.livingroom_curtain
      - cover.kitchen_curtain
    attribute: current_position
    above: 95

2 posts - 2 participants

Read full topic


MQTT: Invalid color mode 'xy' received for entity light.xxx

$
0
0

I’ve been getting 100s of these errors since (I tink) 2025.3.0.

I can see posts from 2021, but it’s new to me and I couldn’t find a solution.

I’m running. HA container with Z2M. Z2M is showing no errors and the lights do have "color_mode": "xy".

Does anyone else see this problem and know the cause/fix?

Thanks!

2025-03-12 08:38:56.433 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.study
2025-03-12 08:38:58.840 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_alcove
2025-03-12 08:38:58.904 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_left
2025-03-12 08:38:58.986 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_settee
2025-03-12 08:38:59.089 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_right
2025-03-12 08:39:00.698 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_1
2025-03-12 08:39:00.756 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_3
2025-03-12 08:39:00.806 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_2
2025-03-12 08:39:00.890 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_study
2025-03-12 08:39:00.987 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_kitchen
2025-03-12 08:39:21.535 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_study
2025-03-12 08:39:21.551 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway
2025-03-12 08:39:21.563 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_kitchen
2025-03-12 08:39:21.567 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing
2025-03-12 08:39:21.577 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_3
2025-03-12 08:39:21.579 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_2
2025-03-12 08:39:21.605 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_alcove
2025-03-12 08:39:21.609 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamps
2025-03-12 08:39:21.633 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_settee
2025-03-12 08:39:21.636 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamps
2025-03-12 08:39:21.640 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_right
2025-03-12 08:39:21.643 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamps
2025-03-12 08:39:21.647 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_left
2025-03-12 08:39:21.652 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_tv_lamps
2025-03-12 08:39:21.671 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamps
2025-03-12 08:39:21.685 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_tv_lamps
2025-03-12 08:39:21.719 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_1
2025-03-12 08:39:23.743 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.bedroom_1_ceiling
2025-03-12 08:39:23.745 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.study
2025-03-12 08:39:23.748 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_1
2025-03-12 08:39:23.751 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_3
2025-03-12 08:39:23.756 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing_ceiling_bed_2
2025-03-12 08:39:23.829 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_alcove
2025-03-12 08:39:23.833 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_left
2025-03-12 08:39:23.835 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_settee
2025-03-12 08:39:23.839 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamp_tv_right
2025-03-12 08:39:23.850 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_study
2025-03-12 08:39:23.854 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway_ceiling_kitchen
2025-03-12 08:39:23.936 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.landing
2025-03-12 08:39:23.954 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_lamps
2025-03-12 08:39:23.957 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.hallway
2025-03-12 08:39:23.988 WARNING (MainThread) [homeassistant.components.mqtt.light.schema_json] Invalid color mode 'xy' received for entity light.livingroom_tv_lamps

3 posts - 2 participants

Read full topic

SMLIGHT coordinator switches to USB mode due to SSE connection errors

$
0
0


I am running my SMLIGHT slzb-06m coordinator in ethernet mode and it disconnects and swaps to usb mode then I get a SSE error not sure why. I haven’t messed with any of the firewall settings on my router and it happens every other day or so. Any help ? Attached below is my zigbee2mqtt config yaml
homeassistant:
enabled: true
legacy_action_sensor: true
experimental_event_entities: false
advanced:
network_key:
- 148
- 85
- 246
- 165
- 46
- 232
- 9
- 241
- 70
- 219
- 125
- 85
- 231
- 192
- 161
- 67
pan_id: 12833
ext_pan_id:
- 235
- 20
- 44
- 140
- 47
- 9
- 231
- 238
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password:
frontend:
enabled: true
port: 8099
serial:
port: tcp://192.168.50.210:6638
adapter: ember
baudrate: 115200

1 post - 1 participant

Read full topic

Before i go down this rabbit hole, would this be possible?

$
0
0

Hi
As title has asked is this type of thing possible before i go down the rabbit hole.

Hardware:
Pi4 8gb
15.6 mobile touch screen wall mounted

HAS OS?

Goal:
Interactive wall calander with following features.
Linking to google calander
Linking to Google tasks
Linking to Solax solar panel info
Waether 5days
Interactive home automation mainly using Phillips Hue but have a mixed ecosystem of zigbee stuff
HD Home run display a channel - Breakfast news between 6:30 - 8:30 and Evening new at 6pm - If HD Home run cant be used then BBC iplayer as i only need BBC 1 for this
Spotify for times outside the TV channel use

I have done some google searching and i think its possible but ive not gone too deep yet on all the articles

Any pointers or similar builds out there i would be very appreciative to read/see

many thanks

1 post - 1 participant

Read full topic

Assist_satellite.start_conversation shows no target, what kind of magic do i need?

$
0
0

I have 2 Voice PE installed.
They have installed the latest version 25.3.0. This version has an entry " * Allow continued conversations if supported by the conversation agent in Home Assistant". I use the OpenAI integration, this integration works with the normal wakeword.

But the action “assist_satellite.start_conversation” in the developer tools shows no target in the ui.

What is missing here?

Regards,
Moses1234

1 post - 1 participant

Read full topic

Mitsubishi Heavy Self Clean operation in Home Assistant

$
0
0

Hello everyone,

I have several Mitsubishi Heavy air conditioners with WF-RAC adapters integrated into Home Assistant via the
GitHub - jeatheak/Mitsubishi-WF-RAC-Integration: WF-RAC homeassistant integration integration. It’s actually a great solution, and the author and contributors did an excellent job. The only issue is that it doesn’t have the Self Cleaning operation. The problem is that even the official Smart M-Air app doesn’t have it either. Only the original physical IR remote has it. I found another great solution with the
GitHub - absalom-muc/MHI-AC-Ctrl: Reads and writes data (e.g. power, mode, fan status etc.) from/to a Mitsubishi Heavy Industries (MHI) air conditioner (AC) via SPI controlled by MQTT integration, but unfortunately, this operation is also missing there.

This is actually a pretty important mode that helps reduce mold growth, which was one of the reasons I chose these MHI units. I believe there are a lot of MHI owners here who have integrated their units into HA and use the Self Cleaning mode.

So, my question is: has anyone managed to find a way to activate this mode via HA?

This mode can only be activated using the original IR remote: after pressing the Off button, the Self Cleaning mode starts. The remote displays the duration of the cleaning process. In the integration or the official app, this just appears as the fan running.

From what I understand, the only way to integrate this mode into HA is through some universal Zigbee IR remote that can read signals from the original AC remote and send the correct command to enable Self Cleaning.

I have a Tuya IR remote, but unfortunately, it doesn’t support signals from the original AC remote.

If anyone has experience with this and can share which IR remotes work with MHI and Self Clean operation, I would really appreciate it. I have an SRK25ZSX-W.

1 post - 1 participant

Read full topic

Issues with Aqara WSDCGQ11LM in Zigbee2MQTT (SkyConnect ZBT-1)

$
0
0

Hi everyone,

I’m having an issue with my Aqara WSDCGQ11LM in combination with Zigbee2MQTT and the SkyConnect ZBT-1. Maybe someone has an idea what could be causing this. This post is about one sensor (office), but unfortunately, all three sensors are experiencing the same issue.

Problem:

  • I pair the sensor as described in the Zigbee2MQTT documentation (holding the button for 5 seconds).

  • The connection works, the sensor transmits data, and everything seems fine.

  • However, after less than an hour, I stop receiving new values.

  • Pressing the pairing button briefly does not bring back new data.

  • LQI is very high, so the signal strength does not seem to be the issue.

  • If I re-pair the sensor, it works again – but only for an hour, then the same issue happens.

Has anyone experienced similar issues or has an idea of what might be causing this? Any help would be greatly appreciated!

Best regards :blush:

2 posts - 2 participants

Read full topic

Error Zigbee

$
0
0

ello,

I’m having an issue with my Sonoff ZBDongle-P. I’ve updated the firmware and configured it as found on the internet, but I’m still getting the same error.

I’ve tried with different paths for the key, but the error remains.

Here’s the error log :

[11:29:22] INFO: Preparing to start…
[11:29:22] INFO: Socat not enabled
[11:29:22] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2025-03-12 11:29:23] info: z2m: Logging to console, file (filename: log.log)
[2025-03-12 11:29:23] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #unknown)
[2025-03-12 11:29:23] info: z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-12 11:29:23] info: zh:ember: Using default stack config.
[2025-03-12 11:29:23] info: zh:ember: ======== Ember Adapter Starting ========
[2025-03-12 11:29:23] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-03-12 11:29:23] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-12 11:29:23] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-03-12 11:29:23] info: zh:ember:uart:ash: Serial port opened
[2025-03-12 11:29:23] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-03-12 11:29:26] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-12 11:29:26] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-03-12 11:29:28] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-12 11:29:28] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-03-12 11:29:31] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-12 11:29:31] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-03-12 11:29:33] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-12 11:29:33] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-03-12 11:29:36] error: z2m: Error while starting zigbee-herdsman
[2025-03-12 11:29:36] error: z2m: Failed to start zigbee-herdsman
[2025-03-12 11:29:36] error: z2m: Check

for possible solutions
[2025-03-12 11:29:36] error: z2m: Exiting…
[2025-03-12 11:29:36] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.

Can someone please help me troubleshoot this issue ?

3 posts - 2 participants

Read full topic


Light bulb dashboard template

$
0
0

Hi,
To handle the bulb, I have this below on my remote panel.
There is a way to have a more compact view, i.e. with slide for intensity?
I tried to make this, but without success.
Thanks for help!

3 posts - 3 participants

Read full topic

Value hold helper

$
0
0

Hello,

I am using two Hoymiles inverters, read-out by an OpenDTU and connected to HA via MQTT. One inverter is connected to a battery, that discharges every evening.

My problem is to build the daily total yield. The inverter (or OpenDtu) without battery does shortly send a daily yield of 0 Wh, just after the real max daily value and then shuts off and restarts counting on the next day.

How could I use a helper or template-sensor to cutoff this decrease to 0, so just hold the daily max value and only restart counting from 0 at 0:00?

2 posts - 2 participants

Read full topic

Advice on best history(?) sensor to use

$
0
0

I’m using ESPresense to track the status of my trash bins. The data is noisy, but I can see that it’s useful. The presense source will switch back and forth frequently but I can tell by looking at the history when I moved my trash bin - I just cant figure out how to capture the change in a sensor. Here’s what the history looks like from last evening. I moved the can just after 8pm and you can see that after that point that the status is mostly “espgarage” yellow rather than “esplivingroom” blue. I’ve tried delay_on/off on a template sensor, but that doesn’t appear the best solution.

1 post - 1 participant

Read full topic

File Integration -- there seems to be no way of debugging it?

$
0
0

I use the File integration’s notification feature to write several log files from automations that all use the same script. Mostly they work, but if they don’t, how do you figure out why not?

I have already tried …

  1. Restarting the system several times
  2. Deleting the Entry and setting it up again as below
  3. Disabling the Entry and then re-enabling it

The problem is, there is not much else I can do. Amongst File integration’s shortcomings are that it does not produce error messages, even with debugging enabled, and an entry cannot be checked or edited after it has been created (except to turn the timestamp on or off).

Setup Method

I originally set them up with a configuration file. Sadly, they had to be migrated last year to the new File Integration, where they now have to be edited by hand. That was a retrograde step but here we are.

I have since successfully set up new notification services by hand. This is tedious but works if you do not make a mistake. You have to:

  1. Go to the File integration and click ‘add entry’
  2. Fill in the file path, which in this example is /config/log_files/ground_floor_zone_control.log
  3. Click submit. You then get an new entry in the list with a name like filenotify[/config/log_files/ground_floor_zone_control.log]
  4. To give it a friendly name you have to click the three dots on the right and of the entry and select rename. I called mine “Ground Floor Zone Control Log”
  5. If this is the first one, you have to make sure that you have enabled the path in the configurations.yaml file – in my case:
homeassistant:
  allowlist_external_dirs:
    - /config
  1. Back in the File Integration, if you now click on the “1 entity” link under the name of the entry, it takes you to the Entity view. You will find that it is unhelpfully named ‘File’ with the entity_name notify.file, so you have to edit both by hand, in my case to “Ground Floor Zone Control Log” and notify.ground_floor_zone_control_log respectively.
  2. Restart the system with a full restart (not just a quick start) to ensure the changes ‘take’.
  3. Now the notification service is finally ready to use in an automation!
  4. Repeat for every single notification service that you want (in my case a couple of dozen).

Why the designers think this is straightforward, and better than a single YAML file, is a mystery!

My immediate issue

I have repeated this process several time, usually with success. However in one case (Ground Floor Zone Control Log) it fails. The automation runs fine but:

  • I get no log file content (though other files written using the same script are fine)
  • I get no error messages in the integration
  • I get no log file messages, even with debug enabled in the integration

The only anomaly I can find is that if I navigate to the entity associated with the entry, it is shown as either unknown or unavailable (it keeps switching between the two).

My immediate questions

  1. Can anyone see a problem with my setup procedure that would cause it to work most of the time but fail occasionally?
  2. Does anyone know of a method of debugging a file notification that I have not mentioned?

Suggested future improvements to the File integration (feature requests)

  1. Reintroduce the option to define notification services using a YAML file
  2. In the UI: During setup it should be possible to set a friendly name for the service as well as the path and file name (/config/log_files/ground_floor_zone_control.log and “Ground Floor Zone Control Log”)
  3. This friendly name (“Ground Floor Zone Control Log”) should be reflected in the Entity name
  4. The entity id should be based on the entity name (notify.ground_floor_zone_control_log)
  5. After defining a new entry, it should be possible to see and edit all the parameters supplied when first setting it up.

2 posts - 2 participants

Read full topic

Home Assistant Voice PE (AI Agent): Start Conversations with conversation.process and conversation_id

$
0
0

First of all, I want to thank @NathanCu for the incredible explanatory work in the thread Friday's Party: Creating a Private, Agentic AI using Voice Assistant tools - #8 by NathanCu, where I was able to find and fully understand how to make Assist work with Google Generative AI as a agent generating the corrects prompts.

My goal:

My objective is to enable my satellite (Home Assistant Voice PE) to proactively initiate a conversation by posing a question and, based on my response, executing the appropriate actions accordingly.
For example, if I turn on a light during the day, the agent will ask me if I want to turn off that specific light. If I respond yes, it will proceed to turn it off.

First part: let’s create the question:

We need to create enough context for the model to ensure that when we respond positively, it can correctly understand what action it needs to perform.

Let’s create an automation that:

  • Triggers when I turn on the kitchen light.
  • Checks if it is daytime (sun after sunrise and before sunset).
  • Uses conversation.process to ask me: “Do you want to turn off the kitchen light?”
  • IMPORTANT: To provide the initial context, we will use conversation_id: question_ask.
  • The question will be announced on the designated satellite.
alias: Asking for kitchen light
  description: ''
  triggers:
  - entity_id:
    - light.kitchen
    to: 'on'
    trigger: state
  conditions:
  - condition: sun
    before: sunset
    after: sunrise
  actions:
  - alias: generate question with conversation.precess
    action: conversation.process
    metadata: {}
    data:
      text: 'Ask me without perform any actions unless I respond: Do you want to turn off the kitchen light? Do not perform any actions unless I respond positively. Example: 'Yo brother, do you want to turn off the kitchen light?'"
      agent_id: conversation.google_generative_ai
      conversation_id: question_ask
    response_variable: action_response
  - alias: Formatta la risposta
    variables:
      message: "{% if action_response and action_response.response and action_response.response.speech
        \n    and action_response.response.speech.plain and action_response.response.speech.plain.speech
        %}\n  {{ action_response.response.speech.plain.speech }}\n{% else %}\n  Non
        ho ricevuto una risposta chiara, ma il comando è stato eseguito.\n{% endif
        %}\n"
  - alias: annouce the question
    action: assist_satellite.announce
    metadata: {}
    data:
      message: '{{ message }}'
    target:
      device_id: <<YOUR DEVICE ID>>
  mode: single

Second part: correct action by the model based on our answer

Now we need to ensure that if we respond with “yes,” “ok,” “alright,” etc., without an apparent context, the model can correctly identify the appropriate conversation_id: to execute the correct action if necessary.

Let’s create an intent script that, when we respond positively without apparent context, make the action conversation.process with:

  • text: “yes”
  • conversation_id set to the same one used in the automation (I used “question_ask”)
Question_ask:
    description: >
       # This intent handles generic affirmative responses such as "yes," "ok," "alright," "exactly"  
       # when they are not directly linked to a clear context.  
       #  
       # Functionality:  
       #   - If the user says "yes" without explicitly referring to a previous request,  
       #     a new `conversation.process` is automatically triggered with "yes" as the command.  
       #   - If the "yes" is part of an already structured conversation, the LLM follows the natural flow.  
       #  
       # Output:  
       #   - If the user's confirmation is recognized as independent, the system triggers:  
       #       conversation.process('text': 'yes', conversation_id: 'question_ask')  
       #   - The response generated by the conversation process is returned and announced by Assist.  
       #   - If the model does not generate a clear output, a predefined message is returned.  
       #  
       # Best Practices:  
       #   - For questions requiring confirmation, wait for an affirmative response before executing actions.  
       #   - If the context is unclear, treat the confirmation as generic and allow the system  
       #     to determine whether further clarification is needed.  
       #   - The LLM should always maintain the natural flow of conversation without asking  
       #     for unnecessary confirmations again.  
  
    action:
      - action: conversation.process
        metadata: {}
        data:
          agent_id: conversation.google_generative_ai
          conversation_id: question_ask
          text: "yes"
        response_variable: action_response  
      - stop: ""
        response_variable: action_response  
    speech:
      text: >
        {%- if action_response and action_response.response and action_response.response.speech and action_response.response.speech.plain and action_response.response.speech.plain.speech %}
          {{ action_response.response.speech.plain.speech }}
        {%- else %}
          Ok, done.
        {%- endif %}

In my case, it works perfectly.

Now, if I turn on the kitchen light:

  • My Assist satellite will announce: “Yo bro, do you want to turn off the kitchen light?” (It has Snoop Dogg’s personality).
  • When I respond “yes”, without any apparent context, it will trigger the Question_ask intent, which will execute the correct action taking the context from conversation_id: question_ask

To start a conversation with other conditions, just create onother Automation with your condition.

1 post - 1 participant

Read full topic

Not working Bubble Card PopUp … JavaScript Error

$
0
0

I added a Popup like mentioned in the Bubble Card instructions, but it does not work.

I checked my console and I saw 2 Errors:

bubble-card.js?hacstag=680112919240:2 TypeError: Cannot read properties of null (reading ‘classList’)
at bubble-card.js?hacstag=680112919240:2:60426
at J (bubble-card.js?hacstag=680112919240:2:62134)
at gt.updateBubbleCard (bubble-card.js?hacstag=680112919240:1445:801)
at set hass (bubble-card.js?hacstag=680112919240:1445:720)
at vertical-stack-in-card.js?hacstag=142051833101:92:19
at Array.forEach ()
at set hass (vertical-stack-in-card.js?hacstag=142051833101:91:22)
at VerticalStackInCard. (hui-card.ts:142:26)
at n (fire_event.ts:75:8)
at create-element-base.ts:217:7

and

bubble-card.js?hacstag=680112919240:2 Uncaught (in promise) TypeError: Cannot read properties of null (reading ‘querySelector’)
at bubble-card.js?hacstag=680112919240:2:62570
at J (bubble-card.js?hacstag=680112919240:2:63621)
at gt.updateBubbleCard (bubble-card.js?hacstag=680112919240:1445:801)
at set hass (bubble-card.js?hacstag=680112919240:1445:720)
at vertical-stack-in-card.js?hacstag=142051833101:92:19
at Array.forEach ()
at set hass (vertical-stack-in-card.js?hacstag=142051833101:91:22)
at VerticalStackInCard. (hui-card.ts:142:26)
at n (fire_event.ts:75:8)
at create-element-base.ts:217:7

Is it another Ressource that is blocking something?

This are the other console logs:

MINI-GRAPH-CARD 0.12.1
kiosk-mode.js?hacstag=497319128670:1 ≡ kiosk-mode version 6.7.0
BATTERY-STATE-CARD 3.2.1
vertical-stack-in-card.js?hacstag=142051833101:1 vertical-stack-in-cardVersion: 1.0.1
vacuum-card.js?hacstag=2612912952101:4 VACUUM-CARD 2.10.0
card-mod.js?hacstag=190927524344:1 CARD-MOD 3.4.4 IS INSTALLED
ha-teamtracker-card.js:9 TEAMTRACKER-CARD v0.14.14 IS INSTALLED
bubble-card.js?hacstag=680112919240:1445 Bubble Card v2.4.0
trashcard.js?hacstag=678764124246:453 :wastebasket: TrashCard 2.4.6
xiaomi-vacuum-map-card.js?hacstag=193372044224:1081 XIAOMI-VACUUM-MAP-CARD Version v2.2.4
meteoalarm-card.js?hacstag=361205663272:818 MeteoalarmCard 2.7.2
weather-radar-card.js?hacstag=487680971210:1291 WEATHER-RADAR-CARD Version 2.1.0
mushroom.js?hacstag=444350375431:309 :mushroom: Mushroom :mushroom: - 4.3.1
HA-Firemote.js?hacstag=536329656418:8 :fire: FIREMOTE-CARD :fire: v4.1.8 installed
apexcharts-card.js?hacstag=331701152212:835 APEXCHARTS-CARD v2.1.2
Advanced Camera Card 7.3.5 card-cfbffe2e.js:616

Maybe someone has an idea, what other plugin or extension might block the popup. Thank you in advance!

1 post - 1 participant

Read full topic

Can't get my configuration to work (required key 'platform' not provided) - what's my mistake/error?

$
0
0

Hi guys,

I wanted to implement this great project in my Home Assistant: Google Weather Frog Card

Everything worked out fine so far, however, there is a minor issue that I can’t resolve. The code in the configuration.yaml looks like this:

sensor:
    - trigger:
        - platform: time_pattern
          minutes: "30"
        - platform: homeassistant
          event: start
        - platform: event
          event_type: event_template_reloaded
      action:
        - service: weather.get_forecasts
          target:
            entity_id: weather.hamburgairport 
          data:
            type: hourly
          response_variable: forecast
      sensor:
        - name: "Wetter_HamburgA_Niederschlagsmenge" 
          unique_id: wetter_hamburga_niederschlagsmenge
          state: >
            {{
              forecast['weather.hamburgairport'].forecast[0].precipitation
            }}
            
#Froschi23       

    - trigger:
        - platform: time_pattern
          hours: "1"
        - platform: homeassistant
          event: start
        - platform: event
          event_type: event_template_reloaded
      action:
        - service: weather.get_forecasts
          target:
            entity_id: weather.hamburgairport
          data:
            type: daily
          response_variable: forecast
      sensor:
        - name: "Wetter_HamburgA_Vorhersage_Status"
          unique_id: wetter_hamburga_vorhersage_status
          state: >
            {{
              forecast['weather.hamburgairport'].forecast[0].condition
            }}
    
        - name: "Wetter_HamburgA_Vorhersage_Temperatur"
          unique_id: wetter_HamburgA_vorhersage_temperatur
          unit_of_measurement: °C
          state: >
            {{
              forecast['weather.hamburgairport'].forecast[0].temperature 
            }}

The error that I get is as following:

Konfigurationswarnungen
Invalid config for 'sensor' at configuration.yaml, line 24: required key 'platform' not provided
Invalid config for 'sensor' at configuration.yaml, line 48: required key 'platform' not provided

What am I doing wrong?
Best regards,
Dennis

2 posts - 2 participants

Read full topic


HA Calendar to IPhone - possible?

$
0
0

Hi everyone.

New into HA and trying to find out possibilities for configuration.

I read a lot about the one way - how to integrate iCloud or CalDav or Google calendar into HA.
But.
Not the other way round……

Is it possible to integrate HA calendar into the family‘s iPhone calendars as a family calendar (waste pickups, events etc). So have events from HA calendar pushed onto the phones and see them in the calendar app there as an additional calendar.

Since I can integrate google or caldav calendars into my phone, I am wondering if and how I can make use of a central HA calendar on my Iphone.
Not want to put the whole ICloud calendars into HA.

Hope I could express my issue in an understandable way :joy:

Thanks a lot for hints and suggestions!!

1 post - 1 participant

Read full topic

Issue with 2025.3 and Cloudflared

$
0
0

Hi,
after 2025.3.1 and 2025.3.2 updates i’m unable to access to HA via cloudflared, after login it shows me “Error while loading page lovelace”. Tried to boot in safe mode, tried to clean cache from app and browser, tried multiple devices. Tried also to recreate Cloudflared tunnel, deleting lovelace dashboard, and backup + restore….

The issue is present only if i access via Cloudflared tunnel, in local it works without any issue.

If i rollback the snapshot to 2025.2.5 everything works clear.

From HTTP Inspect:
Error loading page lovelace TypeError: Failed to fetch dynamically imported module: https://myhaaddress/frontend_latest/17322.9e735e9a6d8c9a3.js
Failed to load resource: the server responded with a status of 404 ()

Can someone help me? In Logs i can’t find anything useful…

1 post - 1 participant

Read full topic

ZigBee (ZHA) becoming unstable every 2-3 weeks

$
0
0

Hi,

Firstly I’d like to say thank you to the Nabu Casa team and the Home Assistant community for making such excellent software. Home Assistant has changed my smart home life and I absolutely love it.

I’ve been slowly building up my ZigBee network over the last 6 months and been trying to run my server for longer and longer periods without intervention. I’ve noticed it a couple of times now, but after a couple of weeks I’ll wake up to all my ZigBee devices not working and I have to restart the ZHA integration or Home Assistant to get it to work.

I get a couple of errors - once I got ZIGBEE_DELIVERY_FAILED appear in Home Assistant and another time I got ZHAException: Failed to send request: device did not respond error. I only have the logs for the latter one.

I am wondering if perhaps I have too many routers, as I have quite a small house, and I have about 9 devices that are acting as Zigbee Routers. Before I didn’t have many routers - I didn’t have devices drop out but in the visualisation I had a lot of grey lines so I thought I’d add more devices to help.

Perhaps I just need to trigger a network heal? I’ve never manually done this - I’ve just added more and more devices over time. It doesn’t look very optimized for example my kitchen light is connecting to my lamp in my bedroom - it really should connect to the washing machine or repeater plug which is much closer.

This is what my network looks like. I have the Coordinator at the very front of the house where my internet comes in and my server is, and I have to essentially try and work my way to the back of the house with routers.

Logs

Logger: zigpy.zcl
Source: runner.py:154
First occurred: 11 March 2025 at 05:00:05 (2 occurrences)
Last logged: 11 March 2025 at 05:58:10

[0x15A9:1:0x0020] Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/bellows/zigbee/application.py", line 934, in send_packet send_status, _ = await req.result ^^^^^^^^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 378, in request await send_request() File "/usr/local/lib/python3.13/site-packages/zigpy/application.py", line 835, in request await self.send_packet( ...<14 lines>... ) File "/usr/local/lib/python3.13/site-packages/bellows/zigbee/application.py", line 933, in send_packet async with asyncio_timeout(APS_ACK_TIMEOUT): ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__ raise TimeoutError from exc_val TimeoutError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/general.py", line 630, in check_in_response await self.checkin_response(True, self.CHECKIN_FAST_POLL_TIMEOUT, tsn=tsn) File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 85, in wrapper with wrap_zigpy_exceptions(): ~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/contextlib.py", line 162, in __exit__ self.gen.throw(value) ~~~~~~~~~~~~~~^^^^^^^ File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 70, in wrap_zigpy_exceptions raise ZHAException("Failed to send request: device did not respond") from exc zha.exceptions.ZHAException: Failed to send request: device did not respond

1 post - 1 participant

Read full topic

Tuya wifi LED lamps without Smart Life

$
0
0

I have two unbranded LED lamps that I am using with Smart Life and the Tuya integration. These lamps are working via Wifi and I can see them on my Unifi router where I have given them static IPs. Is there any way to talk directly from HA to these lights and cut out the Smart Life cloud from the setup?

1 post - 1 participant

Read full topic

How to handle different scenes with buttons

$
0
0

Hi,

I am struggling with my scenes. I have a buttons to toggle my scene between “scene on” and “scene off”. This works fine and the lamps will switch on according to the settings in the scene.
The icon of the button switches the color depinging on the status of the lamps (on/off).

Now I have a second button for a second scene with the same lamps but different color and brighness. The second button toggles also between “scene on” and “scene off”.

The issue is now, that the icon of both buttons changes the color because the mechanism can not distinguish between the two scenes.

How can I separate the individual scenes from each other? I think a kind of radio button can help, but I did not find anything. Any ideas?

1 post - 1 participant

Read full topic

Viewing all 109599 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>