Subway line ID in graphQL and MQTT do not match up

[PasiSalenius]

HSL area metro has a gtfsId like HSL:31M2 which in MQTT should match to a topic like
/hfp/journey/subway/+/31M2/1/+/+/#

The current MQTT topic's id: unique id of the vehicle seems to be the result of removing HSL: prefix from the gtfsId. This currently works for other HSL lines, just not for subway lines.

Here's an example of a current MQTT topic for a subway, containing an incorrect 1300M id
/hfp/journey/subway/metro77/1300M/2/XXX/undefined/undefined/60;25/10/93/51

[tuukka]

We are missing a suitable source for proper subway data for now. That is why the trip specific data is missing (undefined destination name, departure time and next stop) and we cannot say whether a vehicle is on e.g. route 31M2 or 31M2K.