Frequently Asked Questions (FAQ)

Astrion Astrion - Knowledge Base & Tutorials
,
1

Frequently Asked Questions (FAQ)

Q1: Why doesn’t Astrion appear in HA integrations?
A: Astrion is a control terminal, not a device to integrate.

Q2: Remote can’t find HA server automatically.
A: Network issue: same Wi-Fi/subnet required. Manual entry possible.

Q3: New RosCard view not showing.
A: Pull down home screen → tap Refresh.

Q4: Can I use remote outside home network?
A: Possible via VPN/Nabu Casa; local network recommended.

Q5: Remote feels sluggish.
A: Refresh → Restart → Check OTA → Ensure strong Wi-Fi.

Q6: Changed HA password/token. How to re-login?
A: Settings → Home Assistant → Log Out → Re-login with new credentials.

Q7: How to perform factory reset?
A: Settings → System → Factory Reset (erases all settings, shortcuts, and HA connection).

2

:pushpin: Update FAQ – Astrion Remote v1.0.36 & RosCard v1.0.8

This FAQ covers the most common questions after updating to Astrion Remote v1.0.36 and RosCard v1.0.8.

:red_question_mark: What’s the main change in this update?

The biggest change is custom entity naming support.

You can now rename entities directly for Astrion / RosCard usage, allowing:

  • Cleaner labels on the remote
  • More user-friendly names
  • Better differentiation between similar devices

This affects how view data is loaded and stored.

:red_question_mark: My Astrion Remote doesn’t show the latest card layout or names. What should I do?

This is expected for some users after the update.
Please follow both steps below:

:white_check_mark: Step 1: Clear browser cache

  • Clear your browser data (cache + local storage)
  • Reload Home Assistant

:white_check_mark: Step 2: Re-save RosCard views

On your PC:

  1. Open Home Assistant
  2. Edit each RosCard card you use
  3. Click Save (no changes required)

This forces Home Assistant to store the new custom-name attributes correctly.

:warning: This step is important — custom naming is a structural change, so older saved views need to be refreshed once.

:red_question_mark: Why is re-saving cards necessary?

Because custom entity names are new attributes, older card data may not include them.

Re-saving ensures:

  • Consistent loading on Astrion
  • Correct display order
  • Proper synchronization between HA and the remote

This is a one-time action per card.

:red_question_mark: Does this affect button mappings or automations?

No.

  • Physical button mappings remain unchanged
  • Automations and scripts continue to work normally
  • Only display and metadata loading is affected

:red_question_mark: Do I need to factory reset the remote?

:cross_mark: No.
A factory reset is not required for this update.

Only follow the two steps above if you notice loading or display issues.

:red_question_mark: Where should I report issues after updating?

If problems persist after completing the steps above:

  • Please post in Astrion – Core Discussions
  • Include:
    • Firmware version
    • RosCard version
    • Card type (TV / Media / Light / Climate)
    • Screenshots if possible

This helps us troubleshoot faster.

:folded_hands: Thank you all for the detailed feedback — it directly helps shape Astrion and RosCard’s development.
More UI and button-customization improvements are already in progress.

3

Remote showing “Device is empty”

Step-by-step checklist (please follow in order)

If your Astrion Remote shows “Device is Empty” , it’s usually due to one of a few setup issues. Please check the following:

:one: Install RosCard as Custom Repository

  • Follow the Astrion Remote manual: Download Manual
  • Restart Home Assistant after installation
  • Refresh your dashboard in the browser

:two: Set Up Long-Lived Access Token

  • Go to Profile → Security → Long-Lived Access Tokens
  • Create a token that is active and not expired
  • Copy it fully into the remote app, then save and reconnect

:three: Ensure Same Local Network (LAN)

  • Home Assistant and the Astrion Remote must be on the same network
  • Use HA’s local IP (192.168.x.x)
  • Avoid VPN during setup

:four: Rename Dashboard View

  • Avoid “Default” or “Home” as the view name
  • Choose a unique name like Remote, Astrion, or Control

image
image1565×111 21.5 KB

  • Refresh the dashboard and reconnect

If it still shows “Device is Empty”

If the issue persists after checking all steps above, please reply with:

  1. A screenshot of the RosCard dashboard
  2. A screenshot of the Astrion Remote HA settings page
  3. Confirmation of whether HA and the remote are on the same LAN

We’ll be happy to help you resolve this quickly.