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

Have an API queryable space open state stored in slack server #18

Closed
sjefferson99 opened this issue Apr 19, 2024 · 4 comments
Closed

Have an API queryable space open state stored in slack server #18

sjefferson99 opened this issue Apr 19, 2024 · 4 comments
Assignees
Labels
🔮 enhancement New feature or request
Milestone

Comments

@sjefferson99
Copy link
Member

Where the SmibHID will have leds to reflect space open status for the space open and close buttons, this state should be tracked centrally and be available for any endpoints interacting with space open or closed rather than tracking locally. SmibHID can then regularly poll to ensure it's in sync and update the LED states accordingly.

@sjefferson99 sjefferson99 added the 🔮 enhancement New feature or request label Apr 19, 2024
@sam57719
Copy link
Collaborator

Probably as part of the Central DB issue

@sjefferson99
Copy link
Member Author

I was thinking something like this. I've written the current code with this in mind although nothing specific implemented. Vague ideas are could have a HID at either end of the space and the async code could easily implement a 30 second poll state watcher and consume a state change push from the slack server. This way you could have every physical button and slack button working off one state so you could use any you want without confusion. Could also query the state for other purposes.

If we implemented a motion sensor or other presence detection, I think it might be best to have it as supplementary information So state is open or close, but also there is motion sense recently, then logic or simply human reviewing can be built on top as needed.

@sjefferson99 sjefferson99 added this to the v1.1 milestone Apr 30, 2024
@sam57719
Copy link
Collaborator

sam57719 commented May 2, 2024

being implemented as part of #11 / #48

@sjefferson99 sjefferson99 added ♊ duplicate This issue or pull request already exists and removed ♊ duplicate This issue or pull request already exists labels May 2, 2024
@sjefferson99
Copy link
Member Author

Done in #48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔮 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants