Cant add second card to remote

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

Environment

  • Astrion Software Version: 1.1.0

  • Astrion firmware: 2025111419

  • RosCard version: 1.0.8

  • Home Assistant version:

    Core 2026.2.2

    Supervisor 2026.02.2

    Operating System 17.1

    Frontend 20260128.6

  • Network type (local / VPN / remote): Local

Below is the steps that worked for me. Replace with whatever works for you

  • Log into HA with your Admin account
  • Create a new Dashboard called Remote
  • Rename the default view to something. This needs to be done otherwise it wont sync. I used the Masonry view layout
  • Create a user called Astrion with Admin rights (Needs to be admin intially to have rights to create token)
  • Log into HA as Astrion
  • Create long live-lived access token
  • Set the default dashboard as Remote for Astrion
  • Log back in as your normal admin account
  • Add RosCards to the Remote Dashboard

What I have noticed is that if your RosCard’s are misconfigured or not configured at all they will not appear when you sync the remote.

Hope this helps

2 Likes

Hi 45Commanso,

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:


Recommended Setup Method (Stable Multi-Card Configuration)

1. Create a dedicated dashboard

  • Name it something like Remote

  • 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.

We are actively evaluating ways to:

  • provide clearer sync error feedback

  • show validation logs

  • indicate which card failed

Hi Charles

Thank you for the detailed response. I’m out of the country at present but will try the above upon my return.

it would be useful for others if you updates your documentation with these clear steps.

Thanks