Just recently this popped up:
It gives no clue as to which light, automation etc.
I can find effect: None ten times in my scenes.yaml…
Usually repairs are really helpful, but this one is vague. Do I just have to replace all instances of ‘None’ with ‘off’?
1 post - 1 participant
Hi everybody,
sorry if this has been asked before, I searched but either it hasn’t, or I used the wrong terms.
My lawn_mower.sheena returns error values; I would like to use these in a mushroom template card, but replace them with more user friendly terms.
{% set entity = "lawn_mower.sheena" %}
{% set moeglichkeiten = {
"EMPTY_BATTERY": "Batterie leer",
"MOWER_STUCK": "Gerät hängengeblieben",
} %}
{{ state_attr(entity, "error") }} # returns "EMPTY_BATTERY" in this case
So {{ state_attr(entity, "error") }} gives me EMPTY_BATTERY. But I don’t understand how to go from there. If the return value is EMPTY_BATTERY, I would like to display Batterie leer. If the return value changes to MOWER_STUCK, it should display Gerät hängengeblieben.
{{ moeglichkeiten }} returns {'EMPTY_BATTERY': 'Batterie leer', 'MOWER_STUCK': 'Gerät hängengeblieben'}.
Is it possible to replace whatever the actual return value is with a mapping from my manually created moeglichkeiten json?
I could do
{% if is_state(entity, "error") == "EMPTY_BATTERIE" %}
Batterie leer
{% elif is_state(entity, "error") == "MOWER_STUCK" %}
Gerät hängengeblieben
{% endif %}
Actually, this is similar to what I am currently doing. But isn’t it possible to map these values, so I don’t end up with a ton of if/else statements if a device has multiple error values?
Thank you in advance for your help 
1 post - 1 participant
Hey community,
I’m currently struggeling with a template sensor, which I’ve created.
The goal is to create a sensor, which contains the earliest alarm of the day. This sensor is used in several automations. In the past, I used this template sensor with a list of alarms provided by an Philips Somneo device and two smartphones. It worked great. But now I’ve added my Galaxy Watch. This next_alarm sensor of the watch works most of the time, but sometimes it responses with times in the past and sometimes with an alarm at noon (I have no clue, where this is comming from).
So I’m trying now to exclude timestamps, which are:
My current template:
{% set activeAlarms = [states('sensor.wecker_mark_next_alarm')] %}
{% if states('person.mark') == 'home' -%}
{% set activeAlarms = activeAlarms + [states('sensor.marks_galaxy_next_alarm'), states('sensor.marks_galaxy_watch7_next_alarm')] %}
{%- endif %}
{% if states('person.nicole') == 'home' -%}
{% set activeAlarms = activeAlarms + [states('sensor.nicoles_pixel_next_alarm')] %}
{%- endif %}
{## Just for testing: Adding two invalid alarms ##}
{% set activeAlarms = activeAlarms + [today_at('12:00') | string] %}
{% set activeAlarms = activeAlarms + [(today_at('07:00') - timedelta(days = 1)) | string] %}
{## End of testing ##}
{## ToDo: Remove alarms in the past + alarms which are not between 4 and 9 am ##}
{{ activeAlarms | sort | first }}
{## For Debugging ##}
{{ activeAlarms }}
Output:
2025-04-16 07:00:00+02:00
['2025-04-18T05:00:00+00:00', 'unavailable', '2025-04-17T10:00:00+00:00', '2025-04-21T03:45:00+00:00', '2025-04-17 12:00:00+02:00', '2025-04-16 07:00:00+02:00']
Do you have any idea how to resolve that? I played around with the reject filter, but that seemed to not work with timestamps.
Thanks in advance!
BR
1 post - 1 participant
Hi All,
I’m new here so hopefully this is an easy answer.
I’ve added my Innr smart plugs to the Energy Dash as individual devices. This worked for a 1-2 hours and then disappeared, all I see now is untracked consumption. When they did report in they were displaying kWh and not w.
Q- What am I doing wrong?
Q - Do I need MQTT or ZigbeeMGTT?
Q - Helpers?
Any answers, guidance and previous posts gratefully received.
Many thanks in advance.
1 post - 1 participant
Hi guys,
I’d like to share an automation for my computer desk lamps and a standing lamp to be controlled via an IKEA Styrbar remote through ZHA. Here I combined many ideas from different topics for my specific need.
While the “building bricks” are taken from different automations and blueprints this automation concentrates more on the hue light color change and has the purpose to share and add room for comments or ideas. 
Big thank you to @epmatt for the blueprint that sparked my idea. Check out his blueprint here: 🎮 ZHA, deCONZ, Zigbee2MQTT - IKEA E2001/E2002 STYRBAR Remote control Universal blueprint - all actions + double click events - control lights, media players and more with Hooks
Setup:
Ikea Styrbar Remote (4 button remote - the square)
3 x Philips hue Play bar named “light.computerlampe1zha”, named “light.computerlampe2zha” and named “light.computerlampe3zha” (will refer only lamp1, 2 & 3)
1 x Philips Centura spot light
1 x light group to combine the Philips lights named (“computerlichter”)
1 x standing lamp (dumb lamp) controlled with on & off through an IKEA smart power plug
Styrbar Remote function:
Pressing up button (short) - Chooses a random hue color for the first (situated left) Philips play bar lamp 1 with full saturation. The next Philips play bar lamp 2 (situated in the center along the Centura spot light) takes the color and adds a value of 60 on the hue color wheel to the already chosen color from lamp1. The same goes for lamp 3 but adding a value of 120 on the color wheel to the initially picked color from lamp 1.
The intention here was to not have 1 color lit up on the computer desk but different colors following each other on the hue color wheel.
Pressing the down button (short) - Switches of the lights on the computer desk
Long press of the previously mentioned buttons dims them.
Left button (short) - Switch on standing lamp behind the computer desk
Right button (short) - Switch off standing lamp behind the computer desk
Automation:
id: 'computertischlampenautomation'
alias: Computertischlampenautomation
initial_state: on
mode: restart
max_exceeded: silent
trigger:
- platform: event
event_type: zha_event
event_data:
device_id: 0d79028138c4d79de300fd9d591866d3
action:
- variables:
command: "{{ trigger.event.data.command }}"
cluster_id: "{{ trigger.event.data.cluster_id }}"
endpoint_id: "{{ trigger.event.data.endpoint_id }}"
args: "{{ trigger.event.data.args }}"
- choose:
- conditions:
- "{{ command == 'on' }}"
- "{{ cluster_id == 6 }}"
- "{{ endpoint_id == 1 }}"
sequence:
- variables:
current_hue: "{{ (range(90)|random + (state_attr('light.computerlampe1zha', 'hs_color')[0] if state_attr('light.computerlampe1zha', 'hs_color') else 0)) % 360 }}"
- service: light.turn_on
target:
entity_id: light.computerlampe1zha
data:
hs_color:
- "{{ current_hue }}"
- 100
transition: 1
- service: light.turn_on
target:
entity_id: light.computerlampe2zha
data:
hs_color:
- "{{ (current_hue + 60) % 360 }}"
- 100
transition: 1
- service: light.turn_on
target:
entity_id: light.computerlampe3zha
data:
hs_color:
- "{{ (current_hue + 120) % 360 }}"
- 100
transition: 1
- service: light.turn_on
target:
entity_id: light.hue_centura_color_spot_1
data:
hs_color:
- "{{ (current_hue + 60) % 360 }}"
- 100
transition: 1
- conditions:
- "{{ command == 'off' }}"
- "{{ cluster_id == 6 }}"
- "{{ endpoint_id == 1 }}"
sequence:
- service: light.turn_off
entity_id: light.computerlichter
data:
transition: 1
- conditions:
- "{{ command == 'move_with_on_off' }}"
- "{{ cluster_id == 8 }}"
- "{{ endpoint_id == 1 }}"
sequence:
- repeat:
while: []
sequence:
- service: light.turn_on
target:
entity_id: light.computerlichter
data:
brightness_step: 10
transition: 1
- delay:
milliseconds: 250
- conditions:
- "{{ command == 'move' }}"
- "{{ cluster_id == 8 }}"
- "{{ endpoint_id == 1 }}"
sequence:
- repeat:
while: []
sequence:
- service: light.turn_on
target:
entity_id: light.computerlichter
data:
brightness_step: -10
transition: 1
- delay:
milliseconds: 250
- conditions:
- "{{ command == 'press' }}"
- "{{ cluster_id == 5 }}"
- "{{ endpoint_id == 1 }}"
- "{{ args == [257, 13, 0] }}"
sequence:
- service: switch.turn_on
target:
entity_id: switch.stehlampezha
- conditions:
- "{{ command == 'press' }}"
- "{{ cluster_id == 5 }}"
- "{{ endpoint_id == 1 }}"
- "{{ args == [256, 13, 0] }}"
sequence:
- service: switch.turn_off
target:
entity_id: switch.stehlampezha
default: []
I’m curious if you’d have some improvement suggestions or other ideas.
1 post - 1 participant
Hi all,
I have following template sensor:
solar_yield_last_year:
friendly_name: Solar Yield Last Year
unique_id: solar_yield_last_year
unit_of_measurement: kWh
icon_template: "mdi:counter"
value_template: "{{ state_attr('sensor.solar_yield_this_year','last_period') }}"
I must admit it’s been a while since I looked at that one.
Seems like last year there was at least one bad reading, because the stat now has a value of… 1.747.592.396.928.103.700.000.000.000.000.000.000,0000000000000000000000000000000 kWh
To be clear, I do not run a nuclear fusion plant in my basement…
I use the SQLite plugin, but can’t find where to remove the data that is causing this.
Spiffo
1 post - 1 participant
Hi,
I have a local setup, HA OS + HA on a mini PC. 3 AiO touch PCs (i5 6600t, lowend GPU) are wall mounted and connected as clients. I’m thinking of setting up voice recognition. id like to use the mic of the AiO PC, process everything voice related on it (on this or one of the AiO PCs? The mini PC is too slow) and make it work with HA.
But how? With a small LM? Did someone do something like this already? Any tips? I’m confused how to do it or if it’s even possible.
Thank you!
Staebchen
1 post - 1 participant
Since some time I have a strange issue with some scripts.
It might be that this started after installing the latest HA update to version 2025.4.2 but I am not sure about that.
This is an example of such a problematic script:
set_slaapduur_current:
alias: Set current Slaapduur
sequence:
- action: input_datetime.set_datetime
target:
entity_id: input_datetime.slaapduur
data:
time: '{% from ''easy_time.jinja'' import time_between %}{{ time_between(''input_datetime.in_slaap'',
''input_datetime.wakker'') }}'
Note the usage of the pairs of single quotation marks.
When I go to Developer tools → ACTIONS, select this script and click on PERFORM ACTION I am getting an error message:
Failed to perform the action script.set_slaapduur_current. Invalid time specified: {% from ‘easy_time.jinja’ import time_between %}{{ time_between(‘input_datetime.in_slaap’, ‘input_datetime.wakker’) }} for dictionary value @ data[‘time’]. Got None
And when I go to Settings → Automations & scenes → Scripts, select the same script and in the top right-hand corner three dots menu select Run script I get the same error message.
However, when I go to the three dots menu next to the script and select Run action the script runs successfully without error messages.
When I paste the same template that is used in the script directly in the Developer tools → TEMPLATE → Template editor I get another error message:
Template:
{% from ''easy_time.jinja'' import time_between %}{{ time_between(''input_datetime.in_slaap'', ''input_datetime.wakker'') }}
Error message:
TemplateSyntaxError: expected token ‘import’, got ‘easy_time’
When I replace each of the pairs of single quotation marks with one single quotation mark or with on double quotation mark in the template the problem is solved.
So these two templates are functioning correctly:
{% from "easy_time.jinja" import time_between %}{{ time_between("input_datetime.in_slaap", "input_datetime.wakker") }}
{% from 'easy_time.jinja' import time_between %}{{ time_between('input_datetime.in_slaap', 'input_datetime.wakker') }}
And this script also does function correctly:
set_slaapduur_current:
alias: Set current Slaapduur
sequence:
- action: input_datetime.set_datetime
target:
entity_id: input_datetime.slaapduur
data:
time: "{% from 'easy_time.jinja' import time_between %}{{ time_between('input_datetime.in_slaap',
'input_datetime.wakker') }}"
The problem however is that I did not enter these pairs of single quotation marks in the script myself.
These originally were either normal single or double quotation marks, but have been automatically changed to those pairs of single quotation marks.
It looks like this modification to the quotation marks is triggered by editing one of the scripts via: Settings → Automations & scenes → Scripts, select the script and in the top right-hand corner three dots menu select Edit in YAML. Then make a modification and save the script.
After that all scripts in scripts.yaml were modified and a lot of those pairs of single quotation marks have appeared.
It looks like this is a problem only when using datetime entities in the script (or may be only when using the EasyTime script?), because for instance this script does still function properly:
cast_youtube_to_cc_chromecast:
alias: Cast YouTube to CC Chromecast
sequence:
- action: media_player.play_media
target:
entity_id: media_player.cc
data:
media_content_type: cast
media_content_id: '{{ { ''app_name'': ''youtube'', ''media_id'': ( states( ''input_text.ytl''
).split( ''v='' )[1] ) } | to_json }}'
Can someone please confirm this issue?
If I am not the only one with this problem I will raise an issue about this on GitHub.
1 post - 1 participant
I had a heat pump installed a few years ago, which I wanted to surface the power usage figures from. I noticed that the installers have put in an Eastron sdm630, I also found that this feeds into a passivLiving hub. Below is the install diagram.
I have access to the PassivLiving hub via my network, and entering my ‘local IP address’/portal shows me several values like power usage, flow rate, etc. I looked up how to access this information in HA, and came across Multiscraper. Though I have messed up the config, it finds the entity I’ve added as it’s unavailable. Here is the code:
multiscrape:
- name: passiveLivingHub
resource: http://local-ip-address/portal/
scan_interval: 60
sensor:
- unique_id: air-temperature-pl-hub
name: Air Temperature PL-Hub
device-class: temperature
unit_of_measurement: °C
select: "tr:nth-child(10) > td:nth-child(8)"
value_template: "{{ value.replace('°C', '') }}"
Any help would be most appreciated.
1 post - 1 participant
Hi,
I am trying to add my Husqvarna Automower 310 Robot via Bluetooth via the “Husqvarna Automower BLE” integration.
I enter the Mac address as requested and start pairing the robot. It searches non-stop, never stopping. However, the robot indicates that it’s connected, and the Bluetooth monitor via HA indicates that the robot is connected, but no entity is added.
What should I do?
Thx
Last version version Home Assistant on Synology DS923+
Bluetooth USB : TPLink
1 post - 1 participant
Even though I cannot pinpoint the exact moment I believe my problems started with upgrade to OS 15.
Every now and then, my Home Assistant front end crashes and cannot be accessed. Neither externally, nor on internal network.
The back-end works fine:
Through SSH : ha core restart seems to be processing forever, I need to go the ha host reboot to get it back up.
After rebooting I end up with a clean log.
How could I look for the source?
Core 2025.4.2
Supervisor 2025.04.0
Operating System 15.2
User Interface 20250411.0
Generic x86-64, 5% of CPU used in average, 8Gb RAM (+/- 18% use)
1 post - 1 participant
Hi,
I have 2 spurious Zwave devices that I’d like to remove.
One is some kind of zombie left over from an aborted installation of the USB zwave hub that I’m using, showing up here as :“Node 2”.
The other is a wall remote which was faulty and has been returned to the manufacturer.
Looking everywhere I see no simple option to delete these devices?
Thanks,
Paul.
2 posts - 2 participants
I am stuck using a small screen now and finding the template editor really annoying that 25% of the very valuable screen real estate is taken up by this header:
I have tried modifying it via google chrome inspect but so far have not cracked it… anyone know how to get rid of this? or some other way to have the text editor in one screen and ouput/result in another (to even help with not being able to change the split from 50/50)?
1 post - 1 participant
Hello,
I’m working on a dashboard for mobile phones and am having issues with spacing that is driving me crazy. It seems when I use the Vertical Stack In Card I get different results on the spacing of the different cards.
For example, I’m trying to include Mushroom Title cards in each grouping of my devices. For my Alarm System and Door Locks that works fine and the spacing looks normal, but for my door contacts it puts each entity on top of each other with no spacing between each. I want it to look like my window group entities, but with the title like it is in the door group. Any ideas on how to do this? Here is the yaml for my door group card.
Thanks!
type: custom:vertical-stack-in-card
cards:
- type: custom:mushroom-title-card
title: Doors
subtitle: ""
title_tap_action:
action: none
subtitle_tap_action:
action: none
- type: horizontal-stack
cards:
- type: custom:mushroom-template-card
primary: Front Door
secondary: |-
{% if is_state('binary_sensor.front_door_contact_template', 'off') %}
Closed
{% elif is_state('binary_sensor.front_door_contact_template', 'on') %}
Open
{% else %}
{{ states('binary_sensor.front_door_contact_template') }}
{% endif %}
icon: >-
{% if is_state('binary_sensor.front_door_contact_template', 'off') %}
mdi:door
{% elif is_state('binary_sensor.front_door_contact_template', 'on' )
%}
mdi:door-open
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.front_door_contact_template
icon_color: >-
{% if is_state('binary_sensor.front_door_contact_template', 'off' ) %}
green
{% elif is_state('binary_sensor.front_door_contact_template', 'on' )
%}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
- type: custom:mushroom-template-card
primary: Garage Door
secondary: >-
{% if is_state('binary_sensor.mudroom_door_contact_template', 'off')
%}
Closed
{% elif is_state('binary_sensor.mudroom_door_contact_template', 'on')
%}
Open
{% else %}
{{ states('binary_sensor.mudroom_door_contact_template') }}
{% endif %}
icon: >-
{% if is_state('binary_sensor.mudroom_door_contact_template', 'off')
%}
mdi:door
{% elif is_state('binary_sensor.mudroom_door_contact_template', 'on' )
%}
mdi:door-open
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.mudroom_door_contact_template
icon_color: >-
{% if is_state('binary_sensor.mudroom_door_contact_template', 'off' )
%}
green
{% elif is_state('binary_sensor.mudroom_door_contact_template', 'on' )
%}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
- type: horizontal-stack
cards:
- type: custom:mushroom-template-card
primary: Deck Door
secondary: |-
{% if is_state('binary_sensor.deck_door_contact_template', 'off') %}
Closed
{% elif is_state('binary_sensor.deck_door_contact_template', 'on') %}
Open
{% else %}
{{ states('binary_sensor.deck_door_contact_template') }}
{% endif %}
icon: |-
{% if is_state('binary_sensor.deck_door_contact_template', 'off') %}
mdi:door
{% elif is_state('binary_sensor.deck_door_contact_template', 'on' ) %}
mdi:door-open
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.deck_door_contact_template
icon_color: |-
{% if is_state('binary_sensor.deck_door_contact_template', 'off' ) %}
green
{% elif is_state('binary_sensor.deck_door_contact_template', 'on' ) %}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
- type: custom:mushroom-template-card
primary: Basement Door
secondary: >-
{% if is_state('binary_sensor.basement_door_contact_template', 'off')
%}
Closed
{% elif is_state('binary_sensor.basement_door_contact_template', 'on')
%}
Open
{% else %}
{{ states('binary_sensor.basement_door_contact_template') }}
{% endif %}
icon: >-
{% if is_state('binary_sensor.basement_door_contact_template', 'off')
%}
mdi:door
{% elif is_state('binary_sensor.basement_door_contact_template', 'on'
) %}
mdi:door-open
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.basement_door_contact_template
icon_color: >-
{% if is_state('binary_sensor.basement_door_contact_template', 'off' )
%}
green
{% elif is_state('binary_sensor.basement_door_contact_template', 'on'
) %}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
- type: horizontal-stack
cards:
- type: custom:mushroom-template-card
primary: Single Garage Door
secondary: >-
Hold to Operate:
{% if is_state('binary_sensor.aqara_contact_garage_door_single',
'off') %}
Closed
{% elif is_state('binary_sensor.aqara_contact_garage_door_single',
'on') %}
Open
{% else %}
{{ states('binary_sensor.aqara_contact_garage_door_single') }}
{% endif %}
icon: >-
{% if is_state('binary_sensor.aqara_contact_garage_door_single',
'off') %}
mdi:garage
{% elif is_state('binary_sensor.aqara_contact_garage_door_single',
'on' ) %}
mdi:garage-open
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.aqara_contact_garage_door_single
icon_color: >-
{% if is_state('binary_sensor.aqara_contact_garage_door_single', 'off'
) %}
green
{% elif is_state('binary_sensor.aqara_contact_garage_door_single',
'on' ) %}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: call-service
service: switch.turn_on
target:
entity_id: switch.single_garage_door_relay
data: {}
double_tap_action:
action: none
multiline_secondary: false
- type: custom:mushroom-template-card
primary: Double Garage Door
secondary: >-
Hold to Operate:
{% if is_state('binary_sensor.aqara_contact_garage_door_double',
'off') %}
Closed
{% elif is_state('binary_sensor.aqara_contact_garage_door_double',
'on') %}
Open
{% else %}
{{ states('binary_sensor.aqara_contact_garage_door_double') }}
{% endif %}
icon: >-
{% if is_state('binary_sensor.aqara_contact_garage_door_double',
'off') %}
mdi:garage-variant
{% elif is_state('binary_sensor.aqara_contact_garage_door_double',
'on' ) %}
mdi:garage-open-variant
{% else %}
mdi:help-circle
{% endif %}
entity: binary_sensor.aqara_contact_garage_door_double
icon_color: >-
{% if is_state('binary_sensor.aqara_contact_garage_door_double', 'off'
) %}
green
{% elif is_state('binary_sensor.aqara_contact_garage_door_double',
'on' ) %}
red
{% else %}
orange
{% endif %}
layout: horizontal
tap_action:
action: more-info
hold_action:
action: call-service
service: switch.turn_on
target:
entity_id: switch.double_garage_door_relay
data: {}
double_tap_action:
action: none
2 posts - 2 participants
Good morning,
I have a couple automations that listen to an mqtt event from a Aeon ‘dual nano’ switch that lives at the front door and controls my porch and flood lights outside.
Short story long, I divorced the physical switch from the relay because I moved to individual wifi enabled bulbs. So I created an mqtt trigger to listen for the node to send 0 or 255 (on endpoint 1 or 2) and this works fine.
But a recent zwave JS update apparently changed the event a little and broke my automation. Easy fix, but while searching for a way to limit these changes causing problems (with regex or something) I discovered that HA created devides that can track these value changes.
I can watch the ‘value’ swap from 0 to 255 in real time. SO, I thought instead of capturing an mqtt even I could just use this device in my automation. So I disabled the mqtt trigger and used the device stat, value attribute watching for it to switch from 0 to 255 and vice versa to turn on/off the light group ‘porch’ and ‘floods’.
But this does not work, this entry does not trigger the automation, and I’m not sure why. Any help would be appreciated. Below shows part of the original and the new trigger.
1 post - 1 participant
I’ve been using the media_player.play_media action to sound alarms on my Squeezebox Boom for a few years now, but over the last couple of months playback has been failing. Instead of playing the requested media file, the player buzzes and the track name is displayed as " [tempplaylist_0004201e97d7]" or something similar.
The action looks like this:
- action: media_player.play_media
target:
entity_id: media_player.bedroom
data:
media_content_id: /local/parking-booking.mp3
media_content_type: music
Does anyone know what might have changed in the last few HA releases which might be causing this problem?
1 post - 1 participant
I am trying to expose the area’s temperature and humidity to voice assistant since Home Assistant does not do that. But I think I am getting myself in a chicken/egg situation.
The idea is:
{{
states.sensor |
selectattr('entity_id','in',area_entities('<ROOM_ASKED_FOR>')) |
selectattr('attributes.device_class','defined') |
selectattr('attributes.device_class','eq','temperature') | map(attribute='state') |
map('int',0)|sum
}}
The issue is that it feels to me a 2 step process, find out the room from the query, get the temperature/humidity/etc from the sensor and then compose the message. Has anyone attempted something similar?
Thanks in advance
1 post - 1 participant
My sprinkler system is integrated in HA. In order to run multiple sprinkler zones in succession, I use an input boolean which activates an automation. See below.
However, I want to configure it in a way where I can stop the entire automation mid-run if the input boolean is turned off. Is there a simple way to do that? Would I need a seperate automation? Any suggestions would be great.
alias: "Sprinklers: Frontyard (Right - Front)"
description: Runs Sprinkler Zones 1, 2 for 10 minutes
mode: single
triggers:
- entity_id:
- input_boolean.sprinklers_frontyard_right_front
to: "on"
trigger: state
conditions: []
actions:
- action: switch.turn_on
target:
entity_id: switch.rain_bird_sprinkler_1
data: {}
- delay: "00:10:00"
- action: switch.turn_off
target:
entity_id: switch.rain_bird_sprinkler_1
data: {}
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- action: switch.turn_on
target:
entity_id: switch.rain_bird_sprinkler_2
data: {}
- delay: "00:10:00"
- action: switch.turn_off
data: {}
target:
entity_id: switch.rain_bird_sprinkler_2
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- action: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id: input_boolean.sprinklers_frontyard_right_front
1 post - 1 participant
Am fairly new to HA and am really loving it
i got a lanbon L8 and was able to flash openHasp firmware on it.
the problem is the entities will not load and therefore i cant set automations or anything
here is my openhasp.yaml file
openhasp:
richards_office:
objects:
- obj: “p0b1” # temperature label on all pages
properties:
“text”: ‘{{ states(“sensor.downstairs_current_temperature_2”) }}°C’
- obj: “p1b2” # light-switch toggle button
properties:
“val”: ‘{{ 1 if states(“light.my_room”) == “on” else 0 }}’
“text”: ‘{{ “\uE6E8” if is_state(“light.my_room”, “on”) else “\uE335” | e }}’
event:
“up”:
- service: homeassistant.toggle
entity_id: “light.my_room”
- obj: “p1b3” # dropdown
event:
“changed”:
- service: persistent_notification.create
data:
message: I like {{ text }}
1 post - 1 participant
Hi, Everyone. Bit of an HA noob, here. I was running ZBT-1 Zigbee, but the radio seemed too weak. I purchased the Sonoff Zigbee Dongle Plus and am trying to setup in Zigbee Home Automation, but HA Green is not recognizing it.
Here’s what I’ve done so far:
I’ve tried two USB extender cables, just to rule out a cable problem. It didn’t help.
All tutorials I’ve found rely on HA Green auto discovery of the radio. I’ve reconnected a few times and restarted HA, but not luck.
What should I try next? TIA for the help.
2 posts - 1 participant
