Trying to use /vehicles/{vehicleID}/compatibility, I got a list of available and unavailable signals.
A large part of signals reported as available are in fact, reported as non-existant when queried to by using /vehicles/{vehicleID}/signals?signals={signalName} and this returns a 400 error.
{
"error_description": "Signals does not exist",
"error": "signals_unexistant"
}
The ones that are working are actuallly the ones returned by /vehicles/{vehicleID}/status.
I don't see any link between the confidence variable and the real availablity of signals. All available signals are marked as confidence: true, here, execpt one (FuelLevel).
status is also returning ComputedAccActivity, and ComputedFuelLevel as available signals, which are not mentionned by compatibility
I have tested this only on one vehicle, so I don't know if it's a problem with the API or the vehicle/brand/model
Trying to use
/vehicles/{vehicleID}/compatibility, I got a list of available and unavailable signals.A large part of signals reported as available are in fact, reported as non-existant when queried to by using
/vehicles/{vehicleID}/signals?signals={signalName}and this returns a 400 error.The ones that are working are actuallly the ones returned by
/vehicles/{vehicleID}/status.I don't see any link between the
confidencevariable and the real availablity of signals. All available signals are marked as confidence: true, here, execpt one (FuelLevel).status is also returning
ComputedAccActivity, andComputedFuelLevelas available signals, which are not mentionned by compatibilityI have tested this only on one vehicle, so I don't know if it's a problem with the API or the vehicle/brand/model