Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce actors besides sensors. #126

Open
Idorobots opened this issue Jan 6, 2024 · 0 comments
Open

Introduce actors besides sensors. #126

Idorobots opened this issue Jan 6, 2024 · 0 comments

Comments

@Idorobots
Copy link
Member

Idorobots commented Jan 6, 2024

Reading values is cool and all, but it would be really nice to be able to finally do something with those values.

A sensor is a set of readings that can be configured individually and retrieved in bulk via the API. Readings display on the UI via the associated widgetConfig.

An actor should be a set of endpoints that can be configured individually and triggered individually via the API. Depending on the type of the endpoint a different schema of data will be required. It should be possible to retrieve endpoints' current state via the API as well. Endpoints should also have an associated widgetConfig of a widget able to display the endpoints state.

Some examples:

  • on/off relay switch - accepts the state (either open or closed) and triggers an external relay switch,
  • display - accepts text to display on an attached screen (maybe a bitmap as well?),
  • network-attached IR blaster - with configurable remote controller widgets,
  • servo - accepts rotation angle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant