Simulator

[kruegercharles]

How to use

1. Activate Simulator in Internal Settings
2. Pick a route and send a Pair Request
3. The Pairing has to be confirmed from the simulator. For testing purposes the confirmation can be send via the terminal as well (see below under "Publish")
4. Start ride. The MQTT messages during the ride can be read via the terminal, if subscribed (see below under "Subscribe").

For the detailed protocol see below.

Use MQTT within terminal

The MQTT-Messages can be send & received via the terminal, if mosquitto is installed.
On MacOS: brew install mosquitto

Publish

Replace deviceID with the deviceID shown in the internal settings. The ID resets whenever the app restarts.

mosquitto_pub -h priobike.vkw.tu-dresden.de -p 20036 -t "simulation" -m "{\"type\":\"PairStart\", \"deviceID\":\"ee1e9\"}" -P JsAF0keyKjrJT9LwiUKV0YRdemhUFxhF -u app

Subscribe

No need to use a deviceID.

mosquitto_sub -h priobike.vkw.tu-dresden.de -p 20036 -i "client-id" -v -t "simulation" -P Qe6irlBho9JJXbWHQQ1PB6qxHjtAHEJ9 -u simulator

Communication protocol

Step 1: If the user activated the simulator and then tries to start a ride, a pair request is sent to the simulator.
{"type":"PairRequest","deviceID":"90610","deviceName":"Priobike"}

Step 2: The server has to confirm the pairing.
{"type":"PairStart", "deviceID":"90610"}

Step 3: The app sends the first point of the route to position the simulator at the start of the route.
{"type":"FirstCoordinate","deviceID":"90610","longitude":"9.993682","latitude":"53.551086","bearing":"0.0"}

Step 4: The user has to start to ride.
Step 4.1: The app sends all the points of the route.
[{"type":"RouteDataStart","deviceID":"90610"},{"lon":9.993682,"lat":53.551086},...,{"lon":9.976977980510583,"lat":53.56440493672994}]

Step 4.2: The app sends all the traffic lights on the route.
{"type":"TrafficLight","deviceID":"90610","tlID":"hamburg/333_42","longitude":"9.9861116","latitude":"53.5476128","bearing":"109.60459330886522"}

During the ride:
The app sends an update of the current position once a second.
{"type":"NextCoordinate","deviceID":"90610","longitude":"9.993686","latitude":"53.551085","bearing":"29.79114808786065"}

The app sends updates for the state of the traffic lights whenever an update is detected.
{"type":"TrafficLightChange","deviceID":"90610","tlID":"hamburg/333_42","state":"green"}

The ride ends whenever the simulator or the app sends a StopRide.
{"type":"StopRide","deviceID":"90610"}

[PaulPickhardt]

Reviewed the code. Still need to test it with the simulator.

@kruegercharles pls check my comments and decide, if changes are necessary or provide a very brief explanation to my questions.

Also check Buttonoverflows after applying my suggestions.

[kruegercharles]

Reviewed the code. Still need to test it with the simulator.

@kruegercharles pls check my comments and decide, if changes are necessary or provide a very brief explanation to my questions.

Also check Buttonoverflows after applying my suggestions.

How can I fix Button-Overflows? It seems to me like this is a problem of the design of the app. I could change the Button to IconTextButton but I'm not sure if this would be in line with the design. Also, I cannot think of a way to shorten the text 😅