-
Notifications
You must be signed in to change notification settings - Fork 13
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
Switch to the MQTT-backed transport #81
Comments
Can we get For station panels we can split frontend, and use webstomp. |
Hmm, at the moment it is not available over MQTT. I will make it happen and write about it tonight. Note, however, that this feature request is for milestone 3.0, so - in the future. At the moment our top priorities are route-multi-subscription and the performance issues #76. It is getting unusable on my phone, and sometimes even on my computer. |
@iamandrewluca, I forgot about this, but stumbled upon it today. The ETAs are now exposed to the public via MQTT as well, here's how it works: Payload example:
The format is a draft and will be changed, based on feedback. The payloads may contain other elements - don't count on those. |
This could be relevant, since the bus telemetry also uses MQTT: roataway/gtfs-data#5 |
Currently we use an API that was not documented officially, the one that runs on top of WebSTOMP. The new API, documented in api-documentation is using MQTT and is more reliable (it runs on a separate server, and it works even when RabbitMQ is down).
The payload formats are the same, and the subscription logic is the same too.
What is different:
.
separators, MQTT uses slashes/
transport.telemetry.*
becomestransport/telemetry/*
The text was updated successfully, but these errors were encountered: