TL;DR:
After the v1.0.38 / RosCard v1.0.8 update, some existing entity bindings can break due to an internal ID change. Removing and re-adding the affected entity (or RosCard) refreshes the binding and resolves the issue — which matches what you observed.
Hi Mark,
Thank you for the update — and great catch 
Your solution and observations are exactly aligned with what we’ve been seeing internally.
To add some background for clarity:
Why this happened
In the RosCard v1.0.8 update (paired with Astrion Remote v1.0.38), we introduced support for custom device and scene names based on user feedback.
To enable this cleanly, we changed the internal device identification method from:
- Entity ID–based ➜ Card ID–based
Because of this change:
- Existing bindings created before the update are not backward compatible
- In some setups, a stale or unavailable entity can block other cards from loading correctly
Why removing and re-adding fixed it
When you:
- Removed the problematic entity
- Re-added it (or re-saved the dashboard / RosCard)
Home Assistant regenerated the bindings using the new Card ID logic, which immediately restored normal behavior. This is exactly why your Climate card appeared again.
Recommended recovery steps (for anyone else reading)
If cards fail to display after updating:
- Ensure Astrion Remote is v1.0.38 and RosCard is v1.0.8
- Re-save cards from the dashboard
- If needed:
- Remove and re-add the affected entity
- Or delete and re-download RosCard
- If an entity shows as Unavailable, remove it first — it may block others
Thanks again for testing and reporting back — this kind of feedback helps us refine both the product and our upgrade guidance for other users.