He still has an issue with his uv install, likely the same path issue the rest of us had. Nothing the integration owners can help with.
Now it is logical to have “plurals” for trigger-based sensors as well - this code causes error:
template:
- triggers:
- trigger: state
entity_id: input_boolean.test_boolean
actions:
- action: persistent_notification.create
data:
message: |-
action!
value: {{trigger.to_state.state}}
binary_sensor:
- name: testing_2024_10_plurals
state: >
{% if trigger.to_state.state == 'on' -%}
off
{%- else -%}
on
{%- endif %}
ERROR (MainThread) [homeassistant.config] Invalid config for ‘template’ at conf/test/template_sensors/test_2024_10_plurals.yaml, line 2: ‘triggers’ is an invalid option for ‘template’, check: triggers
Invalid config for ‘template’ at conf/test/template_sensors/test_2024_10_plurals.yaml, line 7: ‘actions’ is an invalid option for ‘template’, check: actions
Otherwise we have one syntax for automations, another syntax for templates.
Having issues with DashCast when upgrading core to 2024.10 - reverting to 2024.9.3 fixes it immediately. Confirmed I have the latest version of DashCast installed, and also tried re-installing it post-upgrade of core.
Once I perform the 2024.10 update, the action to cast a dashboard disappears; leaving only the cast a camera feed option. Sounds like some others are seeing some general casting weirdness, which is the only reason I post this here.
Been using DashCast to cast a WallPanel dashboard with variables for each Nest Hub name in my config to simplify.
It’s a work in progress. That will come eventually.
I updated last night, fixed some minor repairs, but no sign of my section heading being converted to the new headings card - they are all still the same as last release and I have several dashboards all using them.
That’s exactly how I did it. A little round-about, but it gets the job done. I’ve got a helper:
input_boolean.dashboard_einkaufsliste_visible
And these are the cards:
type: heading
heading: Einkaufsliste 🛒
heading_style: title
tap_action:
action: perform-action
perform_action: input_boolean.toggle
target:
entity_id: input_boolean.dashboard_einkaufsliste_visible
badges:
- type: entity
show_state: true
show_icon: true
entity: todo.google_keep_einskaufsliste
color: amber
type: todo-list
entity: todo.google_keep_einskaufsliste
visibility:
- condition: state
entity: input_boolean.dashboard_einkaufsliste_visible
state: "on"
I somewhat can’t believe that HA is getting more and more user friendly, more beautiful UI’s and yet still user is not able to see real “last_changed” when entity was changed not by HA restart.
Maybe it’s worth to take a look at it globally and finally be able to solve intentional value of last changed “while HA was online”?
Hello, after this update of 2024.10 my HA restarting any issue:
2024-10-03 09:15:16.612 ERROR (MainThread) [supervisor.homeassistant.api] Timeout on call http://172.30.32.1:8123/api/core/state.
2024-10-03 09:16:05.509 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed
2024-10-03 09:16:05.545 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Cannot connect to host 172.30.32.1:8123 ssl:False [Connect call failed (‘172.30.32.1’, 8123)]
2024-10-03 09:16:08.697 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting…
2024-10-03 09:16:08.711 INFO (SyncWorker_7) [supervisor.docker.manager] Starting homeassistant
2024-10-03 09:16:08.789 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-10-03 09:16:10.626 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-10-03 09:16:10.765 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-10-03 09:16:14.455 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state=‘NOT_RUNNING’, offline_db_migration=False)
2024-10-03 09:16:15.069 INFO (MainThread) [supervisor.auth] Auth request from ‘core_mosquitto’ for ‘homeassistant’
2024-10-03 09:16:15.074 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
2024-10-03 09:16:34.491 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state=‘RUNNING’, offline_db_migration=False)
2024-10-03 09:16:34.491 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
Fascinating job! Cheers to everyone involved!!
Maybe you share some details of your flow and the „template“ you use (Mustache?). I assume you are using an action node?
If needed post an issue in the repo where something similar was reported.
yes restart and hangs issue here too after update within 5 minutes, restore if i can 2 releases in a row update breaks something or system… onto the waiting for a fix. I would submit issue but cant even get into logs in time.
Hi, Solarlog integration (on a SolarLog 500) now returns “string index out of range” - and is no longer functioning.
Deletion and re-configuration didn’t work either - what to do?
This, i have the same issue…
This version seems to have added animations to dashboard entity window popups. How do I disable them?
Or are popups for some other reason much slower to open than before?
thanks the new version of Alexa Media Player
this please! I use mushroom title card, which alows it and it would be great to switch to native card
thanks the new version of Alexa Media Player
Entity card’s history graph color has changed, it’s now tinted to purple from previous blue.
Is there a setting for it or is this coming from theme? Any ideas how to revert it?
Anyone else found the casting is broken again in this release?
I get the error Chromecast is connecting…
Switching back to the previous release it works fine
I noticed this this morning. It was hanging on the “Connected” or “Not Connected” screen. I restarted HA Core and the device I was trying to cast to and it worked again.