📘 RosCard for Home Assistant

Astrion Astrion - Development & Advanced
21

They seems to be using AI to translate and summarise the conversations, but a lot of it does seem to be normal “give a positive response breaking down the points” kind of thing.

There are some actual project devs here and when enough people start asking about one thing they pop in, look through the AI summaries of what people are talking about and start asking actual questions and providing real information.

At the moment I think they’re mostly working on the HA integration to work alongside Roscard to add two way control, I think that was the last thing the actual devs gave a hand typed outline for.

22

The RD team are now conducting preliminary research on infrared functionality. Once the research is complete, we will post the version plan on the forum soon.

23

@Nicola_Reina @Faceman yes, gentlman! we do use the AI to refine some post, but mostly we will observe and check, thank you very much for your advices.

24

Are there any plans to document the API and allow power users / open source developers to create their own ROS-compatible cards?

For example, I have several DREO pedestal fans with many configurable properties that don’t exist on a typical ceiling fan. Since it’s a niche product I wouldn’t expect the Sanytron provided card to display all these unique properties. However, it would be a great feature if I could create a customized version of the Fan card or create my own cards from scratch.

I’ll also note that it’s somewhat confusing to have a public RosCard repo that only includes minified source code while still using the MIT license. If this code is MIT-licensed and freely reusable & modifiable, why not include the readable version of the code in the repo?

25

Hi @stealthwang,

First of all, welcome to the community, and thank you for raising these questions.

The short answer is yes, we do have plans to make the platform more open and extensible, but we are still working through the architecture and documentation required to support this properly.

Regarding custom cards:

Your DREO fan example is exactly the type of use case we have discussed internally. We recognize that many Home Assistant devices expose attributes and capabilities that do not fit neatly into generic categories such as Fan, Climate, Media Player, Light, or Cover. Allowing advanced users to create their own ROS-compatible cards—or extend existing ones—would provide significantly more flexibility for niche devices and custom installations.

This is currently on our long-term roadmap, but we do not yet have a public SDK, API specification, or card development framework available. Before opening this to third-party developers, we need to ensure:

  • Card compatibility across remote firmware versions

  • Performance and memory stability on the remote

  • Security and sandboxing considerations

  • A stable API that will not constantly change between releases

As for the RosCard repository:

You are correct that the current repository primarily contains production/minified code. The original intention was to simplify distribution and deployment while protecting the stability of the release process during the early stages of the project.

We understand that this can feel inconsistent with the spirit of an MIT-licensed project, especially for developers who want to learn from, modify, or contribute to the codebase. This feedback is fair, and we have discussed internally whether additional source code, documentation, examples, or developer resources should be published in the future.

At the moment, our development team is focused primarily on:

  • Core feature development

  • Bug fixes and compatibility improvements

  • Expanding card capabilities

  • Activity and navigation workflows

  • Home Assistant integration enhancements

However, developer extensibility is definitely an area we are interested in exploring as the platform matures.

Thank you again for the thoughtful feedback. Comments like yours help us prioritize what power users and developers would like to see next. I’ll make sure this request is recorded and shared with our R&D team for future roadmap discussions.

Best regards,

Charles
Sanytron Team