Dynamically define source types

[valterc]

Hi, as a long term item, would it be possible to have an extension sensor as data source for E-Bike data fields?

[brentnd]

I haven't checked it myself but I think you could use the Type for LEV to do this right now.

LEV_ASSIST_MODE

There are several other LEV_* types you could support too.

DataType.Source vs DataType.Type was created to give a distinction for the types we'd expect as source but they're just strings. I'll make a note to try this out and add to Source if it works.

[valterc]

I noticed that the string values are identical between the DataType.Source and DataType.Type. I will try that too, thanks for the quick answer!

Btw, unrelated question: Let's say we have an extension sensor that at the time it was added to Karoo it indicated to emit some data types, let's say Device(extension, uid, listof(DataType.Source.SHIFTING_FRONT_GEAR)) and later, in an update to that extension we want to emit more datatypes from that extension sensor. How should that be done? Should we just emit more datatypes, or should we implement different extension sensors per each datatype?

[brentnd]

Right now, the sources defined at the time of scan are what that sensor can produce.

Adding an ability to make them dynamic definitely makes sense (we do this internally).

A new DeviceEvent should cover this in a compatible way that is opt-in.