So apparently #Chirpstack can't convert float data from received packets and the best workaround is to convert the float to int in our #LoRaWAN sensors. This world is broken.
I give up.
@Szescstopni
I don't know neither LoRaWAN nor Chirpstack, but if you need to scale quantities to send them as ints, remember that multipying or dividing a float by a power of two only changes its exponent part, and therefore doesn't lose _any_ precision (in most cases)

@Szescstopni

... not quite sure to understand your issue, but working with #LoRaWAN sensors I never stumbled across floating values ...

Values like 1.532 Volt were always transmitted as 1532 Millivolt so you divided by 1000 after decoding

So not actually floating values but always integer and you had to divide by whatever ..

@manankanchu I haven't seen them on my sensors before, but a new sensor returns a float. Have to convert it to int before uploading. Just a minor inconvenience,

@Szescstopni

Would you mind telling me which sensor it is? manufacturer/type? ... thanks heaps!!

@manankanchu DFROBOT SEN0414 – I'm not working with it directly, a colleague is, remotely. I took a quick look at the code, but didn't check whether there's another function to return temperature as an int.

@Szescstopni

Thanks!!!

Ah, that's just the sensor, so I guess #LoRaWAN uplink is self developed, that's why ...

@manankanchu I need to get my hands on the sensor *and* the home-made board. Our work flow is very unorthodox :)

@manankanchu Everything is working now. Float is converted to int on the esp32, int is correctly converted to float on Chirpstack. I guess I must learn a bit more about the js flavor used by Chirpstack. The two working nodes were designed with great care and send data through forests over a few kilometres – something standard off-the-shelf devices fail to do.

CC @m4ver13