managed to get 1 card to show! but only 1 card at a time.
added it to my “admin” default dashboard.
If i add a second card and refresh both cards are not shown on the remote.
If i delete the second card and refresh the first card does not show.
if i then delete the first card, refresh, obviously no card is shown.
If i then add 1 card back in and refresh it shows on the remote.
If i then add a second card no cards show on the remote…
What i want to do is
Create a user for the remote (and token)
create a dashboard only for the remote that has only roscards on it.
i cant see how to do this… or have more than 1 card showing at a time
Thanks for the detailed description — that actually helps a lot. What you’re seeing is usually not a hardware or sync limitation, but rather how RosCard handles dashboard parsing and validation.
From your steps and version info, this behavior most commonly happens when one or more cards in the dashboard fail validation. When the remote syncs, it reads the dashboard configuration and only loads it if the structure is valid. If it detects an invalid or incomplete RosCard, it may skip rendering entirely — which is why it looks like all cards disappear when you add a second one.
MRRIZK’s method is very close to the recommended setup flow, and I’d suggest using it as a baseline. I’ll summarize a clean workflow here for clarity:
Change the default view name (important — the default unnamed view can sometimes prevent proper sync)
2. Create a dedicated user for Astrion
Create user (temporarily Admin role)
Log in as that user
Generate a Long-Lived Access Token
Set default dashboard = Remote
3. Add cards carefully
Add RosCards one at a time and verify:
each card is fully configured
no missing required fields
no YAML syntax errors
entities actually exist
If any card is invalid, the remote may reject the entire dashboard payload.
Why it behaves this way
The remote intentionally validates the full dashboard before rendering to prevent:
partial UI states
broken layouts
stuck interfaces
So instead of showing only valid cards, it fails safely and shows none.
Quick troubleshooting checklist
If adding a second card causes everything to disappear, check:
Entity IDs exist and are spelled correctly
Required card parameters are present
No empty fields or placeholder values
YAML formatting is valid
Card type is supported
Important note
Right now RosCard is optimized for structured, validated dashboards, not free-form experimental layouts. We know this can feel strict, but it ensures stability once the configuration is finalized.