Summary / Zusammenfassung / A brief description of the error. to Reproduce / Steps to Reproduce
Many buttons in the radio don’t work, so that in some cases no information can be sent to the vehicle
Go to ‘…’ / Go to ‘…’
Click on ‘…’ / Click on ‘…’
Scroll down to ‘…’ / Scroll down to ‘…’
See error / Error visible
Expected Behavior / Expected Behavior
Actual Behavior / Actual Behavior
Impact on Usage / Impact on Usage
Minor: Small / cosmetic impact. / Small / cosmetic impact.
Moderate: It disrupts some workflows. / Affects some workflows.
Critical: I can’t use the platform at all. / The platform is not usable.
I had a TH1 with a TSF-W…in the same location then an RWM was triggered…I addressed the vehicle by radio as it should be..so first select the channel, then the callsign..the vehicle also responded, but I couldn’t send anything to it with the radio buttons. There are also sometimes similar difficulties in the RD.
When asked in the chat, Simon1234 said he also has such problems, I think the buttons aren’t properly mapped.
What also stands out is that a NEF sends a request to speak twice, and when an RTW requests a NA (emergency patient) and I confirm this, all possible responses to it are sent.
If an RTW requests a NA, you can press the “Doctor arrives (not)” button only a few seconds after the RTW has spoken. If you wait longer, nothing happens—then you can only trigger “Understood, End”
Do vehicles respond to follow-up operations or urgent follow-up operations? Does this have any impact? Do individual vehicles become available earlier?
For example: HLF-1 and HLF-2 are alerted to a fire, nearby there is an emergency medical services operation, HLF-2 is called for a follow-up operation as a first responder.
Usually they also do report in with status 8/1 expressing a desire to speak, making it clear they’re ready for the next assignment. But sometimes they just head back to the station.
In my experience, an urgent follow-up deployment doesn’t make any difference