Scenes called from Astrion remote report missing/unavailable in Home Assistant

Astrion Astrion - Development & Advanced
1

Hi,

I’ve run into a repeatable issue using an Astrion remote with Home Assistant scenes.

Symptoms:

- Triggering certain scenes from the remote causes Home Assistant to log:

  • Referenced entities scene.test are missing or not currently available

  • Referenced entities scene.all_off_incl_bedrooms are missing or not currently available

  • Referenced entities scene.all_off_excluding_bedrooms are missing or not currently available

Important detail:

- These scenes do exist in Home Assistant.

- The same scenes can be triggered directly via the Home Assistant API / scene.turn_on service and return 200 OK.

- So the scene definitions themselves do not appear to be broken.

Current suspicion:

- The Astrion remote / action path is doing a stricter entity availability check (or stale entity resolution) for scene entities than a normal Home Assistant service call.

- Scene entities may be treated as unavailable/missing by the remote path even though Home Assistant can activate them normally.

Current workaround:

- Instead of having the remote trigger the scene entity directly, create a script wrapper in Home Assistant and have the remote call the script.

- Example: script.activate_scene_all_off_incl_bedrooms → scene.turn_on → scene.all_off_incl_bedrooms

Questions:

1. Is this a known issue with Astrion + Home Assistant scene entities?

2. Is there a recommended way to trigger scenes from Astrion without using wrapper scripts?

3. Does Astrion cache entity availability in a way that could cause this?

Happy to provide more detail if needed.

Thanks.

2

Hi @C_HA_User, welcome to the community :waving_hand: — and thank you for the very detailed write-up, that really helps :+1:

:magnifying_glass_tilted_left: What You’re Seeing

From your description, your analysis is actually very close to what’s happening.

  • :white_check_mark: Scenes exist and work via scene.turn_on

  • :cross_mark: When triggered via Astrion, HA reports “missing or unavailable”

This typically points to a difference in how the entity is being resolved or referenced, rather than the scene itself being broken.

:warning: Most Likely Cause

In most cases we’ve seen, this is related to one of the following:

1. Entity ID mismatch / formatting

Astrion relies on the exact entity_id string.

Please double-check:

  • No hidden characters / spaces

  • Correct naming (especially underscores vs hyphens)

  • Entity ID hasn’t changed after scene edits/reloads

2. Entity registry refresh / sync timing

Astrion syncs entities from Home Assistant, and in some cases:

  • Newly created or modified scenes

  • Or scenes reloaded via YAML

may not be immediately recognized until a refresh.

:backhand_index_pointing_right: Try:

  • Re-syncing the remote

  • Or slightly modifying the card layout and syncing again

3. Scene availability handling in HA

Unlike most entities, scene entities don’t always behave like “stateful” entities:

  • They may not always report as “available” in the same way

  • Some integrations treat them differently internally

This can lead to stricter validation paths (like you suspected).

:white_check_mark: About Your Workaround

Your workaround is actually 100% valid and recommended :+1:

Using a script wrapper like:

script.activate_scene_all_off_incl_bedrooms

→ which calls:

scene.turn_on

is currently the most robust and reliable approach, because:

  • Scripts are always treated as callable services

  • Avoids edge cases with scene availability

:red_question_mark: Your Questions Answered

1. Is this a known issue?

:backhand_index_pointing_right: It’s not a universal issue, but we have seen similar behavior depending on:

  • How scenes are defined (YAML vs UI)

  • Entity refresh timing

  • HA version differences

2. Recommended way without scripts?

:backhand_index_pointing_right: Direct scene binding should work in most cases, but:

  • If you encounter this issue → script wrapper is the safest method

  • Especially for critical automations like “all off”

3. Does Astrion cache entity availability?

:backhand_index_pointing_right: Astrion does maintain a synced entity list from HA, so:

  • If entities change or reload

  • There can be temporary mismatches until next sync

:light_bulb: Suggested Next Steps

To help narrow it further, you could try:

  • Recreate one test scene via UI

  • Sync Astrion again

  • Test with a very simple scene (e.g. toggle one light)

If that works, it may point to:

  • Specific scene complexity

  • Or how those scenes were originally defined

:rocket: Moving Forward

We agree this should behave more consistently, and we’ll continue improving:

  • Scene handling robustness

  • Entity sync reliability

  • Error feedback clarity

:white_check_mark: Summary

  • Your scenes are valid :white_check_mark:

  • Issue likely related to entity resolution / sync :red_exclamation_mark:

  • Script wrapper = best current workaround :+1:

Really appreciate the detailed report — this is exactly the kind of feedback that helps us improve reliability

3

@C_HA_User maybe you can try our new updates v1.1.2.1

1 Like
4

Incredibly fast fix. Thank you so much!

5

You are welcome, Christopher