I discovered what the issue was. Badges using the entity filter don’t convert into new style badges using equivalent viability rules. You need to remove the entity filter using the complete Dashboard Yaml editor and readd to use visibility.
What about new notification groups? I am using yaml until now to group my mobile app notification services. I tried to mimic the same in UI, but these notification entities for mobile apps don’t show up in the dropdown. Is there any limitation?
I am not sure what happened there. It didnt take much time :-/
2024-08-08 09:49:53.883 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.8.0
2024-08-08 09:49:53.885 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/odroid-n2-homeassistant:2024.7.4 to ghcr.io/home-assistant/odroid-n2-homeassistant:2024.8.0
2024-08-08 09:49:53.885 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/odroid-n2-homeassistant with tag 2024.8.0.
2024-08-08 09:51:55.818 INFO (SyncWorker_9) [supervisor.docker.manager] Stopping homeassistant application
2024-08-08 09:52:19.650 INFO (SyncWorker_9) [supervisor.docker.manager] Cleaning homeassistant application
2024-08-08 09:52:20.379 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2024-08-08 09:52:20.776 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/odroid-n2-homeassistant with version 2024.8.0
2024-08-08 09:52:20.776 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-08-08 09:52:47.758 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-08-08 09:52:48.070 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2024-08-08 09:52:50.852 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)
2024-08-08 09:52:52.728 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'addons'
2024-08-08 09:52:53.078 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
2024-08-08 09:53:27.576 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'homeassistant'
2024-08-08 09:53:27.924 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
2024-08-08 09:53:52.403 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='STARTING', offline_db_migration=False)
2024-08-08 09:53:58.454 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)
2024-08-08 09:53:58.454 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
2024-08-08 09:53:58.454 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.8.0
2024-08-08 09:53:58.582 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/odroid-n2-homeassistant:2024.7.4']
1 Like
think those logs are just for the Core upgrade finishing…the DB will update the schema separately…you’ll see a Notification when it starts (and is in logs for Core too)
If you’re ok with modifying the manifest file for AMP… the comment in this bug report fixed it for me (upgrades alexa.py):
1 Like
Am I the only one who upgraded and still see the old badges with no way to add new ones as shown here? Quite sure I’m missing something but could not figure out what…
yes, these groups work with notify entities, and mobile_app doesn’t have these (yet) so cant be used with notify groups
I had also updates for my nanoleaf products.
It worked for me after I tried it a second time per each device. And only if I selected one at the same time.
that was it… the browser cache. Didn’t think about it 
thank you
Why are you commenting here? Post on the author’s GitHub.
Read your logs
Is it working in other countries other than .com?
you’re replying to me about Alexa Media Player and quoting Tom about a Daikin Integration…what are you actually wondering about
if it’s re Alexa Media Player all the details are in the Github issue I linked to for various amazon regions…
Nothing in there. Not in the core logs, not in the MySQL addon logs. I guess I store too much data (400 days configured now), and it just takes a long time since it’s a full table rebuild probably.
The logs will tell you whether it has started.
Apologies, not sure what happened there
1 Like
thanks, the linked ticket is mine 
1 Like
I think I can safely report this as a bug.
Tested the following automation script, created in the UI from scratch, in a fresh browser session (tried different Chromium-based browsers in public and private sessions as well as two HAOS instances, one lightly loaded). Once SAVE is clicked the screen goes blank as in the image of my original message.
alias: HVAC Therm
description: ""
trigger:
- platform: state
entity_id:
- climate.hvac_therm
attribute: current_temperature
condition: []
action:
- if:
- condition: template
value_template: "{{ is_state('input_boolean.hvac','on') }}"
then: null
mode: single