Since the EU Data Act became federal law, I am trying to collect my car data from two different connectors:
- the tronity connector
- the vw-eu-data-act connector from
Why is this necessary? The data sets are not equivalent. Example:
Currently the infamous EU Data Act Portal from Volkswagen provides no data on the connection status or the parking location of the car, but on the lockstate.
Tronity provides data on the connection status and parking location, but not on the lockstate.
However, within CarConnectivity there is currently no possibility to define a car that receives data from different connectors, as each connector defines its own vehicle class. My workaround is to run two instances of CarConnectivity and to aggregate in my MQTT client.
I am not really sure what the best method would be to provide such a merger here - but it would make sense to allow for such an aggregation.
Regards
pah
Since the EU Data Act became federal law, I am trying to collect my car data from two different connectors:
Why is this necessary? The data sets are not equivalent. Example:
Currently the infamous EU Data Act Portal from Volkswagen provides no data on the connection status or the parking location of the car, but on the lockstate.
Tronity provides data on the connection status and parking location, but not on the lockstate.
However, within CarConnectivity there is currently no possibility to define a car that receives data from different connectors, as each connector defines its own vehicle class. My workaround is to run two instances of CarConnectivity and to aggregate in my MQTT client.
I am not really sure what the best method would be to provide such a merger here - but it would make sense to allow for such an aggregation.
Regards
pah