Decide how to handle different data types

[margau]

If we not have identical types in the same Channel, Grafana will burn down

[adnidor]

InfluxDB will burn down before Grafana.

Trying to write a value of a type not matching the previous types will result in an error

[margau]

Maybe we should give the option to define the Channel-Types per Sensor in the control panel? If the first value for a new Sensor is in the wrong type (which is possible trough debugging a sensor), the sensor-id is lost.

[hibas123]

Maybe we should give the option to define the Channel-Types per Sensor in the control panel? If the first value for a new Sensor is in the wrong type (which is possible trough debugging a sensor), the sensor-id is lost.

The data input should work as fast as possible. Any additional database access would create a large speed impact. I think the easiest way would be just to let the database create errors, what wouldn't impact the performance significantly. In case of an error, we could try an automatic type adjustment, and in case this is not working, the user should be informed. Although listing the type of the channel on the control panel would be a good idea.