Hi, attached is a photo of an alarm sensor I am using for a window. While it’s status is passed on to HA, if I “bypass” the sensor, the sensor no longer passes info on to HA. Hence, I am looking for recommendations for a Z-wave, Zigbee or Matter device that is super thin. This way, even if I bypass the sensor, I will have another sensor that will know the status of the window.
Thanks
4 posts - 3 participants
What do I have to do to be able to ask the user for details on an intent and then finish the intent? Is there anything I can do in the intent_script to get a session-ID, coie a new question, get the answer and continue?
To make things even more difficult most of my actions are handled in an external applicaton via REST-calls, but the mechanisms need to be present in HA I guess…
1 post - 1 participant
I am trying to make a tweak to the custom integration I’m working on, but can’t figure out how to make certain entities not visible or hidden like this…
1 post - 1 participant
Hi Folks, new to HA but really enjoying it so far! I want to make a sort of fun bonus interaction with my HA set up, where a particular spoken command will start a choose-your-own-adventure style interaction with a pre-determined script. Giving voice commands (e.g. “go left” or “go right”) willtrigger the ‘go left’ of ‘go right’ response, which could include playing sound files as well as generating speech. Is there a native HA addon that would handle this, or am I better off catching the logs from the voice assistant and piping them into a python script to handle the scripted interaction?
1 post - 1 participant
Hello 
. I could use some help troubleshooting Music Assistant if anyone would like to help please.
I have enabled a Music Provider (Spotify) and a number of Player providers (Multiple Google nest hubs and a Denon AVR entity via Media Players). When I choose a nest hub for instance, it powers on and I can even control the volume through the music assistant UI. However when I hit play, nothing happens. I get no sound and no progression on the song timeline either.
At one point there was an error that specifically stated “failed to play” in it, but I have not been able to reproduce this error to take a screenshot. Instead, here’s a screenshot showing a recent log file saying “task was destroyed but it is pending”. I did look this error up and there was not much in the way of fixing this error in relation to Music Assistant.
I would add more pics (like proof of the providers being enabled) but I am new and limited to one picture per the rules I guess. Any help is appreciated of course, thanks.
1 post - 1 participant
HI all,
I’m having trouble with card_mod and style formatting (learning this all for the first time) and I’m reading through a lot of docs, reddit posts etc. to figure this out but can’t seem to get it right. For the picture below, I’ve created a stack-in-card for a remote for my speakers and I’m trying to resize and reposition certain cards within this:
For the large speaker icon, that is the power button, and I’d like to cut it down to about what looks to be about 50-100px and my hope is that the green volume buttons that are vertically stacked to the right of that would line up with the next button on the right edge.
I’d also want to center the yellow input button so that it lands between the play and pause buttons. And finally brind the whole card size down to not take up so much space in terms of columns. I tried adding a grid column and row section to the config below but for some reason every time I saved it, it didn’t take.
type: custom:vertical-stack-in-card
cards:
- type: horizontal-stack
cards:
- type: custom:button-card
entity: scene.speaker_on_off
icon: mdi:speaker
color: lightblue
show_name: false
tap_action: action:toggle
card_mod:
style: |
ha-card {
height: 100px !important;
width: 50px;
border: 0px blue dashed !important;
}
- type: vertical-stack
cards:
- type: custom:mushroom-chips-card
chips:
- type: template
tap_action:
action: toggle
hold_action:
action: toggle
double_tap_action:
action: toggle
entity: scene.speaker_vol_down
icon: mdi:volume-minus
icon_color: green
- type: custom:mushroom-chips-card
chips:
- type: template
tap_action:
action: toggle
hold_action:
action: toggle
double_tap_action:
action: toggle
entity: scene.speaker_vol_up
icon: mdi:volume-plus
icon_color: green
- type: custom:mushroom-chips-card
chips:
- type: template
tap_action:
action: toggle
hold_action:
action: toggle
double_tap_action:
action: toggle
entity: scene.speaker_input
icon: mdi:import
icon_color: yellow
- type: custom:mushroom-chips-card
chips:
- type: template
entity: scene.speaker_last
tap_action:
action: toggle
icon: mdi:rewind
- type: template
entity: scene.speaker_play
tap_action:
action: toggle
icon: mdi:play-box
- type: template
entity: scene.speaker_pause
tap_action:
action: toggle
icon: mdi:pause-box
- type: template
entity: scene.speaker_next
tap_action:
action: toggle
icon: mdi:fast-forward
Any and all help here would be greatly appreciated!
1 post - 1 participant
I don’t know when this changed, but it was a recent update because it’s only recently happened on my system. But this new horizontal weather card is far inferior to the previous card that showed the days/hours vertically in a table that you can scroll up and down in.
This new card, the hourly doesn’t even show the day so it’s significantly less intuitive to use. I realize some folks may prefer this but I don’t know why changes like this always have to be “you will now do it this way whether you like it or not” rather than an option to see it the way it always was.
When did this change and has anyone figured out a way to change it back to the table? I can do a big markup card for it but it’s not nearly as nice as the previous card was.
1 post - 1 participant
Hi, my system is rebooting without any reason (for me).
I tried to disconnect the zigbee and z-wave dongle without succes.
I power the dongles wit a powers USB-hub, also without succes.
I can’t find something in the log’s. This is my log.1 file (the latest part):
2025-03-23 22:32:01.607 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 635, in state
numerical_value = int(value)
ValueError: invalid literal for int() with base 10: ''
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 638, in state
numerical_value = float(value)
ValueError: could not convert string to float: ''
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 117, in _handle_triggered_with_script
self._execute_update(run_variables, context)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 141, in _execute_update
self.async_set_updated_data(
~~~~~~~~~~~~~~~~~~~~~~~~~~~^
{"run_variables": run_variables, "context": context}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 515, in async_set_updated_data
self.async_update_listeners()
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 178, in async_update_listeners
update_callback()
~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/components/template/trigger_entity.py", line 59, in _handle_coordinator_update
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 1085, in __async_calculate_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1029, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 642, in state
raise ValueError(
...<5 lines>...
) from err
ValueError: Sensor sensor.openweathermap_forecast_cloud_coverage_3 has device class 'None', state class 'None' unit '%' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '' (<class 'str'>)
2025-03-23 22:32:02.594 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:03.601 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:04.605 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:05.608 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:06.612 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:07.615 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:08.619 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:09.626 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:10.629 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:11.633 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:12.636 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:13.794 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:14.671 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:15.646 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:16.650 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:17.768 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":36,"regen":1022,"wind":0.15}
2025-03-23 22:32:18.660 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:19.664 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":34,"regen":1023,"wind":0.15}
2025-03-23 22:32:20.667 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:21.671 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:22.674 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.44,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:23.677 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:24.685 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:25.688 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:26.692 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:27.695 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:28.698 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:29.702 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:30.705 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:31.713 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:32.716 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:33.719 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:34.725 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:35.726 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:36.730 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:37.733 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:38.740 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:39.744 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:40.747 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:41.751 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:42.754 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:43.757 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:44.761 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:45.768 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.30}
2025-03-23 22:32:46.772 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:47.775 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:48.778 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:49.782 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:50.785 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:51.789 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:52.796 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:53.799 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:54.803 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:55.806 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:56.810 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:32:57.813 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:32:58.816 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:32:59.823 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:00.185 INFO (MainThread) [homeassistant.components.automation.refresh_vloerverwarming_data_uit_iedere_1_min] Vloerverwarming: Refresh data (uit iedere 1 min.): Running automation actions
2025-03-23 22:33:00.186 INFO (MainThread) [homeassistant.components.automation.refresh_vloerverwarming_data_uit_iedere_1_min] Vloerverwarming: Refresh data (uit iedere 1 min.): Executing step call service
2025-03-23 22:33:00.252 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66049') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_w_2, state update may be delayed for devices on battery
2025-03-23 22:33:00.267 INFO (MainThread) [homeassistant.helpers.script.trigger_update_coordinator] Trigger Update Coordinator: Running template script
2025-03-23 22:33:00.267 INFO (MainThread) [homeassistant.helpers.script.trigger_update_coordinator] Trigger Update Coordinator: Executing step call service
2025-03-23 22:33:00.269 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'cloud_coverage' when rendering '{{ daily['weather.huis'].forecast[0].cloud_coverage }}'
2025-03-23 22:33:00.301 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66817') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_a_2, state update may be delayed for devices on battery
2025-03-23 22:33:00.353 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-65537') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_kwh_2, state update may be delayed for devices on battery
2025-03-23 22:33:00.403 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-67073') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_power_factor_2, state update may be delayed for devices on battery
2025-03-23 22:33:00.549 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66561') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_v_2, state update may be delayed for devices on battery
2025-03-23 22:33:00.827 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:01.831 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:02.060 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 635, in state
numerical_value = int(value)
ValueError: invalid literal for int() with base 10: ''
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 638, in state
numerical_value = float(value)
ValueError: could not convert string to float: ''
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 117, in _handle_triggered_with_script
self._execute_update(run_variables, context)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 141, in _execute_update
self.async_set_updated_data(
~~~~~~~~~~~~~~~~~~~~~~~~~~~^
{"run_variables": run_variables, "context": context}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 515, in async_set_updated_data
self.async_update_listeners()
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 178, in async_update_listeners
update_callback()
~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/components/template/trigger_entity.py", line 59, in _handle_coordinator_update
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 1085, in __async_calculate_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1029, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 642, in state
raise ValueError(
...<5 lines>...
) from err
ValueError: Sensor sensor.openweathermap_forecast_cloud_coverage_3 has device class 'None', state class 'None' unit '%' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '' (<class 'str'>)
2025-03-23 22:33:48.592 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOn>
2025-03-23 22:33:52.432 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOff>
2025-03-23 22:33:53.032 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":36,"regen":1022,"wind":0.15}
2025-03-23 22:33:54.035 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:55.039 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:56.042 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:33:57.046 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":34,"regen":1022,"wind":0.15}
2025-03-23 22:33:58.049 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:33:59.056 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:00.060 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:00.185 INFO (MainThread) [homeassistant.components.automation.refresh_vloerverwarming_data_uit_iedere_1_min] Vloerverwarming: Refresh data (uit iedere 1 min.): Running automation actions
2025-03-23 22:34:00.185 INFO (MainThread) [homeassistant.components.automation.refresh_vloerverwarming_data_uit_iedere_1_min] Vloerverwarming: Refresh data (uit iedere 1 min.): Executing step call service
2025-03-23 22:34:00.256 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66049') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_w_2, state update may be delayed for devices on battery
2025-03-23 22:34:00.266 INFO (MainThread) [homeassistant.helpers.script.trigger_update_coordinator] Trigger Update Coordinator: Running template script
2025-03-23 22:34:00.267 INFO (MainThread) [homeassistant.helpers.script.trigger_update_coordinator] Trigger Update Coordinator: Executing step call service
2025-03-23 22:34:00.268 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'cloud_coverage' when rendering '{{ daily['weather.huis'].forecast[0].cloud_coverage }}'
2025-03-23 22:34:00.313 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66817') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_a_2, state update may be delayed for devices on battery
2025-03-23 22:34:00.370 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-65537') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_kwh_2, state update may be delayed for devices on battery
2025-03-23 22:34:00.422 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-67073') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_power_factor_2, state update may be delayed for devices on battery
2025-03-23 22:34:00.468 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value Value(value_id='9-50-2-value-66561') for sensor.in_wall_dual_relay_switch_module_2x1_5kw_with_power_meter_electric_consumption_v_2, state update may be delayed for devices on battery
2025-03-23 22:34:01.063 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:01.918 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 635, in state
numerical_value = int(value)
ValueError: invalid literal for int() with base 10: ''
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 638, in state
numerical_value = float(value)
ValueError: could not convert string to float: ''
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 117, in _handle_triggered_with_script
self._execute_update(run_variables, context)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/template/coordinator.py", line 141, in _execute_update
self.async_set_updated_data(
~~~~~~~~~~~~~~~~~~~~~~~~~~~^
{"run_variables": run_variables, "context": context}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 515, in async_set_updated_data
self.async_update_listeners()
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 178, in async_update_listeners
update_callback()
~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/components/template/trigger_entity.py", line 59, in _handle_coordinator_update
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 1085, in __async_calculate_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1029, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 642, in state
raise ValueError(
...<5 lines>...
) from err
ValueError: Sensor sensor.openweathermap_forecast_cloud_coverage_3 has device class 'None', state class 'None' unit '%' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '' (<class 'str'>)
2025-03-23 22:34:02.068 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1023,"wind":0.30}
2025-03-23 22:34:03.070 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:04.074 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:05.077 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:06.084 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:07.620 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:07.629 INFO (MainThread) [homeassistant.helpers.intent] Triggering intent handler <OnOffIntentHandler - HassTurnOn>
2025-03-23 22:34:08.091 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:34:09.095 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:34:10.098 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:11.101 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:12.105 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:13.112 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:14.115 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:15.119 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:34:16.122 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:17.126 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:18.129 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:19.132 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:20.140 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:34:21.144 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:21.972 ERROR (MainThread) [frontend.js.modern.202503060] Uncaught error from Safari 18.3.1 on macOS 10.15.7
Error: Failed to execute 'define' on 'CustomElementRegistry': the name "auto-entities-editor" has already been used with this registry
message (node_modules/core-js/modules/web.dom-exception.stack.js:25:24)
src/scoped-custom-element-registry.js:45:10
module code (/local/plugins/lovelace-auto-entities/auto-entities.js:172:1117)
2025-03-23 22:34:22.147 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.44,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:23.150 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:24.189 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:25.157 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:27.539 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:34:27.547 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:34:27.794 ERROR (MainThread) [homeassistant.components.analytics] Error sending analytics to https://analytics-api.home-assistant.io/v1: ClientConnectorError(ConnectionKey(host='analytics-api.home-assistant.io', port=443, is_ssl=True, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Multiple exceptions: [Errno 111] Connect call failed ('0.0.0.0', 443), [Errno 111] Connect call failed ('::', 443, 0, 0)"))
2025-03-23 22:34:28.171 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:29.174 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:30.178 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:31.181 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:32.185 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:34:33.188 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":34,"regen":1022,"wind":0.30}
2025-03-23 22:34:34.195 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:35.199 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:36.211 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.56,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:37.205 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:38.209 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1023,"wind":0.15}
2025-03-23 22:34:39.213 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.30}
2025-03-23 22:34:40.216 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":34,"regen":1022,"wind":0.15}
2025-03-23 22:34:41.223 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
2025-03-23 22:34:42.227 DEBUG (MainThread) [homeassistant.components.serial.sensor] Received: {"temp":9.50,"licht":35,"regen":1022,"wind":0.15}
Can someone help me? Or find the problem.
Thank you 
1 post - 1 participant
HA supervised installed on a RPI4.
I have some esp32 devices with 1-wire temperature sensors. The esp’s update their published bluetooth name with sensor value so that it can be read without connecting to it. However, I am not able to find a way to read discovered bluetooth names in home assistant in a way that lets me make automations with it. Ideally I just want to get the list of bluetooth devices found in nodered, iterate through all bluetooth names, and get the ones I need (they all have a prefix that I can use to identify them), parse the name, and run some automation logic.
My only thought is to install mqtt, write a python script to scan bluetooth devices, then publish entities to mqtt from outside homeassistant. I already have the python script but really want to not use it. I’ve tried a handful of nodered ble integrations and they all appear to complain a modules not found.
Is there really no way to access this data in homeassistant or nodered?
1 post - 1 participant
Hello,
I am working on a project where I need to display real-time data from ‘‘Home Assistant’’ onto an ‘‘LCD screen’’. I am looking for an efficient and time-saving approach to achieve this.
Could someone suggest the best method to accomplish this with minimal delay and complexity?
4 posts - 4 participants
No matter what I do, my blueprint that I’ve got an input selector that takes a trigger, keeps complaining that something with triggers is malformed when I try to create an automation.
Message malformed: expected a dictionary @ data['triggers'][0]
Something of this sort. I can’t for the life of me figure out what the correct syntax is here, can anyone help? My current Blueprint is this:
blueprint:
name: Area Light Toggle
description: Toggle lights in an area on or off
domain: automation
input:
selected_remote_button:
name: Trigger Source
description: The name of the trigger to be used, e.g. a button on a remote
selector:
trigger:
selected_area:
name: Area
description: The area where the lights will be toggled
selector:
area:
# Is there some thing wrong here? I tried this, i tried triggers: !input selected_remote_button
# I tried triggers: - triggers: !input, i tried with entity_id, what's it supposed to be???
triggers:
- !input selected_remote_button
alias: Area Light Toggle
description: ""
variables:
selected_area_var: !input selected_area
conditions: []
actions:
/// actions ///
mode: single
9 posts - 4 participants
I have a Zooz Zen17 zwave relay connected via ZwaveJS to Home Assistant. Every time the zwave device restarts, ZwaveJS restarts, or Home Assistant restarts, the sensor entities are renamed.
For instance, they go from:
binary_sensor.gate_relay_window_door_is_open_2
to
binary_sensor.gate_relay_window_door_is_open_2_5
The original entity shows as “unavailable” and the new entity is now the one that updates from the relay. I can rename the entities to their original name and delete the now duplicate entity, but it every time either device restarts, the entity is renamed.
This device has 2 relays and 2 sensors. It only happens to the relay entities, not the sensor entities.
Any idea what would cause this?
1 post - 1 participant
Hello I’ve got a SNZB-3P sonoff motion and light sensor. I’m using it via zbee2qtt, the issue I have with the zbee2mqtt is the light sensor only changes state once motion is detected.
So to put it in perspective I want a light to switch on in my wardrobe when its dark. So if the state of the sensor is in the “light” state and I walk into the room when its dark the light wont switch on because the state of the sensor is set to “light”. However it will work if I renter the room because now the state has changed to dim, but a the same time the light sensor now changes to light state because the light is on. I can get around it by adding a time delay but it feels weird walking into a room and there’s a delay. The native sonoff app works as it should but that means I need to purchase another hub for one sensor. Just wondering if I can change the value of the sensor manually or there is any creative way to get around this.
Thanks in advance
Here is my yaml file as reference:
alias: WIR Auto Light
description: ""
triggers:
- trigger: state
entity_id:
- sensor.front_sensor_illumination
to: dim
conditions:
- condition: state
entity_id: binary_sensor.front_sensor_occupancy
state: "on"
actions:
- type: turn_on
device_id: 33f729336c4fe71232ecb9c5083c6043
entity_id: d635116d2c6292baaedc4cb9937300a7
domain: switch
- wait_for_trigger:
- type: not_occupied
device_id: ae157f23b5bc7183dec33d5bda1f7f8b
entity_id: 062e3f62323f8ff39104cafef512f529
domain: binary_sensor
trigger: device
for:
hours: 0
minutes: 0
seconds: 5
- type: turn_off
device_id: 33f729336c4fe71232ecb9c5083c6043
entity_id: d635116d2c6292baaedc4cb9937300a7
domain: switch
mode: single
2 posts - 2 participants
I am running HAOS 14.2 on a RPi5 and trying to update to the latest 15.0.
The update fails with the error message:
Failed to perform the action update/install. Error updating Home Assistant Operating System: Unknown error, see supervisor
I tried restarting HA core as well as rebooting the RPi - but continues to fail.
Supervisor log shows the following error:
2025-03-23 22:29:51.280 INFO (MainThread) [supervisor.os.manager] Fetch OTA update from https://os-artifacts.home-assistant.io/15.0/haos_rpi5-64-15.0.raucb
2025-03-23 22:29:55.017 INFO (MainThread) [supervisor.os.manager] Completed download of OTA update file /data/tmp/hassos-15.0.raucb
2025-03-23 22:29:55.078 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-193081' coro=<UDisks2Manager._interfaces_added() done, defined at /usr/src/supervisor/supervisor/dbus/udisks2/__init__.py:190> exception=DBusInterfaceError('D-Bus object /org/freedesktop/UDisks2/block_devices/dm_2d0 is not usable, introspection is missing required properties interface')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/dbus/udisks2/__init__.py", line 202, in _interfaces_added
self._block_devices[object_path] = await UDisks2Block.new(
^^^^^^^^^^^^^^^^^^^^^^^
object_path, self.dbus.bus
^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/supervisor/supervisor/dbus/udisks2/block.py", line 78, in new
await obj.connect(bus)
File "/usr/src/supervisor/supervisor/dbus/udisks2/block.py", line 69, in connect
await super().connect(bus)
File "/usr/src/supervisor/supervisor/dbus/interface.py", line 96, in connect
await super().connect(bus)
File "/usr/src/supervisor/supervisor/dbus/interface.py", line 50, in connect
await self.initialize(await DBus.connect(bus, self.bus_name, self.object_path))
File "/usr/src/supervisor/supervisor/dbus/interface.py", line 104, in initialize
raise DBusInterfaceError(
f"D-Bus object {self.object_path} is not usable, introspection is missing required properties interface"
)
supervisor.exceptions.DBusInterfaceError: D-Bus object /org/freedesktop/UDisks2/block_devices/dm_2d0 is not usable, introspection is missing required properties interface
2025-03-23 22:29:55.118 ERROR (MainThread) [supervisor.os.manager] Home Assistant Operating System update failed with: Failed mounting bundle: Failed to open /dev/dm-0: No such file or directory
1 post - 1 participant
So if you are in Texas, you know what I mean. A lot of the providers will give you a $100 usage credit if you use more than >=1000 kWh per month.
Problem is during the winter and spring months when you are most likely using slightly less than >=1000 kWh per month and do not get that $100 credit.
What I’ve done during the years I was on that plan is to download the CenterPoint meter reading dates.
They are posted online for each zone and once you know which zone you are, you can simply watch your electricity usage every month and make sure towards the last 5 days of the period to increase or decrease your electricity to save money.
That being said, does someone know if there’s a way to customize the end date of the monthly reset period for the kWh counter?
Right now it simply resets on the 1st of every month and you can customize that to a day you prefer.
Issue is that, I’d like to customize it for each month, separately.
for example, for my zone it’s:
jan 21
Feb 19
march 20
apr 21
may 20
june 19
jul 21
aug 19
sept 18
oct 17
nov 17
dec 18
That way I can set a card with the current usage and the reset date for this month so I can quickly glance at it without manually calculating and checking every month.
1 post - 1 participant
Is there any way to control the speed of the output? It talks really slowly and makes me feel like I am Stupid and that my brain is rotting away.
1 post - 1 participant
Hi,
I was looking for a configuration that saves temperature settings, lowers temperature for the night and the weekend (in an office building) and restores it in the morning. And most importantly: retains saved temperatures after HA restarts (so is different than using scene create/restore).
I found a solution here that is almost perfect (creating sensor template that saves temperatures of all devices having the same label):
template:
- trigger:
- platform: event
event_type: save_7_7_8_20
sensor:
- unique_id: d29aa7e2-62e1-4836-b94c-657666c9c4bb
name: save_7_7_8_20
state: data
attributes:
data: >
{% set entities =
label_devices('7_7_8_20')
| map('device_entities')
| sum(start=[])
| select('match', 'climate')
| list
%}
{% set ns = namespace(items=[], attrs=[]) %}
{% for obj in entities | expand %}
{% set ns.attrs = [('state', obj.state)] %}
{% if obj.domain == 'climate' %}
{% set ns.attrs = ns.attrs + [('temperature', obj.attributes.temperature)] %}
{% endif %}
{% set ns.items = ns.items + [ (obj.entity_id, dict.from_keys(ns.attrs)) ] %}
{% endfor %}
{{ dict.from_keys(ns.items) }}
Then I save in an automation using:
- event: save_7_7_8_20
and restore them using:
- action: scene.create
data:
scene_id: restore_7_7_8_20
entities: |
{{ state_attr('sensor.save_7_7_8_20', 'data') }}
- action: scene.turn_on
target:
entity_id: scene.restore_7_7_8_20
Everything worked until one of the sensors was unreachable. Instead of following state:
data: >-
{'climate.p_203': {'state': 'heat', 'temperature': 23.0},
'climate.hall_2': {'state': 'heat', 'temperature': 15.0},
'climate.hall': {'state': 'heat', 'temperature': 16.5}}
I got:
data: >-
{'climate.p_203': {'state': 'heat', 'temperature': 23.0},
'climate.hall_2': {'state': 'unavailable', 'temperature': undefined},
'climate.hall': {'state': 'heat', 'temperature': 16.5}}
And the restore function didn’t restore any of the climate settings in that group. Subsequent ‘save’ event overwrote that state with night temperatures (because all thermostats stayed in that state).
And now my question - how to rewrite the save function so that instead of unavailable/undefined there would be temperatures saved on the day before?
P.
1 post - 1 participant
By default, it seems HomeAssistant’s state_color for a “door” class sensor is yellow when the door is open, and blue/default when the door is closed. That makes sense for something like an exterior door, however in my case this is an interior door that is normally open, so I want that to be the blue/default colour while closed is yellow. Can flipping the state colour like this be done?
3 posts - 3 participants
So, I was trying to link my google home using a tutorial, when I forgot the authorized redirect URIs, and realized I typed in the wrong key. No big deal. I just go to refill the info. That’s what I thought, until it auto-submitted the bad info and tried to do the incorrect Oauth with it. I appear to not be able to press back and re-type the info, and I have reset my browser, my cache, and the HA setup a few times (with YAML). Can someone help?
1 post - 1 participant
Hi everyone,
I’m currently using Home Assistant in VirtualBox on a Linux server, but I’m experiencing a lot of issues due to unexpected crashes. The virtual machine stays up, but it’s completely inaccessible and unresponsive.
It might be caused by some integrations that are crashing Home Assistant, but I’m not sure. I’d like to switch to a Docker installation, also because when I restart the server, the service sometimes doesn’t start automatically and I have to manually access the server to launch it. With Docker, services usually start up automatically, which is a big plus.
Is it more complicated to handle DNS and other configurations with Docker?
Does it cause more problems when using Cloudflare for remote access?
Are there any major downsides to switching?
Thanks!
4 posts - 2 participants
