You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are 2 mattermost channels in which door updates appear:
~kelder: here, messages like door was open, redfast00 tried to lock door via the API get posted
~verbose-mattermore: here, messages like "open" command from Mattermost handled, The door is now open and logging messages get posted
This approach was easy to implement (it's stateless, so we don't have to keep any state between requests in the mattermore backend), but is not that friendly for humans:
if you see a message in ~kelder and want to know if the action succeeded, you have to look in ~verbose-mattermore
it's hard to see when the door was manually opened: you have to look in ~verbose-mattermore and then discard all updates that are because of users electronically opening the door
Just changing the door was open, redfast00 tried to lock door into door was open, redfast00 locked the door is a bad approach: locking the door can fail (for example, if the door is misaligned and the dead bolt hits the strike plate), this would not be correct.
A possible approach is to use a state machine and a background task, but I'll leave it up to you on how you want to solve it.
The text was updated successfully, but these errors were encountered:
Currently, there are 2 mattermost channels in which door updates appear:
door was open, redfast00 tried to lock door via the API
get posted"open" command from Mattermost handled
,The door is now open
and logging messages get postedThis approach was easy to implement (it's stateless, so we don't have to keep any state between requests in the mattermore backend), but is not that friendly for humans:
Just changing the
door was open, redfast00 tried to lock door
intodoor was open, redfast00 locked the door
is a bad approach: locking the door can fail (for example, if the door is misaligned and the dead bolt hits the strike plate), this would not be correct.A possible approach is to use a state machine and a background task, but I'll leave it up to you on how you want to solve it.
The text was updated successfully, but these errors were encountered: