Did some searches here, and didn’t find anything like this, but I’ve set some visibility conditions to my dashboard, and the remote doesn’t seem to act on them. The dashboard itself hides and shows like it should, but the remote still displays all cards all the time.
Is there a setting or a trick I’m missing on this?
Welcome to the forum, and thank you for the report.
At the moment, RosCard does not fully support Home Assistant’s Lovelace visibility conditions in all scenarios. The Astrion Remote primarily retrieves card definitions and entity data from Home Assistant, but some frontend-specific behaviors—such as conditional visibility rules—may not currently be evaluated the same way as they are in the standard Home Assistant dashboard.
To help us determine whether this is a limitation or a bug, could you please provide:
• Your RosCard version (recommended: v1.1.3 or newer)
• Your Astrion firmware version (recommended: v1.1.5)
• The type of visibility condition being used
Entity state
User-based visibility
Template-based visibility
Other custom conditions
• A screenshot of the card visibility configuration in Home Assistant
We are actively collecting feedback on dashboard synchronization, visibility logic, and conditional card rendering, as these areas have been requested by several users.
If this turns out to be a missing feature rather than a configuration issue, I’ll make sure it is recorded for our development team and included in our future roadmap discussions.
Thank you again for helping us improve RosCard and Astrion.
@sparkinman You’re right. Same here. The visibility condition works correctly within Home Assistant, but it does not appear to be applied on the remote, where the card remains visible regardless of the condition.
I guess your goal is to use visibility conditions to show only the information you want on the remote screen, rather than displaying every card all the time.
The display on the remote isn’t a direct Lovelace display, it’s built by the app running on the remote itself and the dashboard UI in HA you put your cards into is just used as an easy way to get a graphical interface for editing and adding functions without requiring custom made configuration software.
They will probably add a hide function eventually since it seems useful, but at the moment the remote isn’t updated live, it would require a manual re-sync to grab that data and apply the change so it’s use would be limited until it supports either a push-change function on the HA side to force update the remote, or a polling schedule on the remote would could affect battery life.
later in the software timeline they’ve laid out is a more well featured integration (a proper device integration rather than just a set of cards that the remote checks on update) that would be live and could allow for more advanced features like automatic show/hide or ordering of cards.
Thank you @Desmond_Dong and @Faceman for the discussion and for helping clarify the current behavior.
@Desmond_Dong, your understanding is correct. The purpose of visibility conditions in Home Assistant is to allow users to show only the information they want on the remote at a given time, rather than displaying every card continuously.
@Faceman also provided a very good explanation of how the current architecture works. At the moment, the Astrion remote does not render the Lovelace dashboard directly. Instead, RosCards act as a bridge between Home Assistant and the Astrion application, allowing the remote to build its own optimized interface and control logic.
Because of this design, Home Assistant visibility conditions are not currently being fully interpreted by the remote application. As a result, cards that are hidden within Home Assistant may still appear on the remote.
We agree that support for visibility conditions would be very useful, especially for:
• Context-aware dashboards
• Activity-based interfaces
• Room-specific controls
• Cleaner and less cluttered remote screens
Our long-term roadmap includes a deeper Home Assistant integration that will allow tighter synchronization between Home Assistant and Astrion. Features such as dynamic card visibility, improved state synchronization, automatic page navigation, and more advanced UI behavior are all areas we are actively evaluating.
Thank you again for bringing this up. Feedback like this helps us prioritize future improvements, and we’ll add this request to our feature review list.