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
what dependencies does this ticket have?
c-beam backend must implement this, sure. But what do we need hardware wise. Afaik the current bar status signs don't have any network connection and the RJ45 cables that they use are only used because we have enough of them.
Another implementation could be to use the running missions to detemrine if there is someone at the bar. Sure using the actual bar signs would be the better way.
My falcon is 99% ready to sit on top of the bar and has a built in raspbery pi. It could be used for a bar sign service. ping me if you need an account.
The falcon will leave hyperspace in a couple of days and request docking permissions.
I thought in a completely different direction. But nice to see that the bar event already gets pushed through the network.
Is there some generic mqtt client to listen to all that or will it be integrated just into the c-beam app?
Are the perpetual statuses "open" and "closed" pushed to mqtt too? With "opening" and "closing", only transition statuses would be displayable, which is like seeing an hourglass all the time.
last-call / bar open push messages
The text was updated successfully, but these errors were encountered: