tony.r
(Tony)
April 24, 2024, 12:19pm
1
Hi All,
I bought a RAK2560 and a water level sensor ULB16 and then connected to LoRa network server (chirpstack). I have received the following payload,
0102018e
{“bytes”:[1,2,1,142],“fPort”:1,“recvTime”:“2024-04-24T12:08:45.718Z”,“variables”:{}}
I have used this payload decoder
RAKwireless_Standardized_Payload
and the result was,
{ data: { analog_in_1: 4.01 } }
This was the result in WisToolBox.
the result are not matching, Can someone help me to find the solution?
Best Regards
Tony R
crmrosa
(claudio roberto machado da rosa)
April 25, 2024, 8:40am
2
tony.r
(Tony)
April 25, 2024, 11:19am
3
Hi @crmrosa ,
Thank you !
I have tried RAKwireless_Standardized_Payload.js and the result was not correct.
is this a valid payload (0102018e) from Sensor Hub (RAK2560) for ULB16 water level sensor?
can you please guide to decode data from sensor hub for ULB16 water level sensor in chirpstack?
crmrosa
(claudio roberto machado da rosa)
April 29, 2024, 1:51pm
4
I don´t have this Sensor Hub to test it, but I am using the Standardized Payload Decoder for a Wisblock with RAK1904, RAK1906(temperature, humidity, barometric pressured, etc…), and it is working very well…
This is a strange behavior, because in the product documentation we can see the sensors list as: RAK1901 and RAK1902: RAK2560 WisNode Sensor Probe Datasheet | RAKwireless Documentation Center . Then the Standardized Payload load support both.
The Chirpstack decoder is in the Standardized Payload page: RAKwireless_Standardized_Payload/WisBlock-TagoIO-Chirpstack.js at main · RAKWireless/RAKwireless_Standardized_Payload · GitHub
I think that we will need someone from RAK Staff to explain how the payload is prepared in the RAK2560, maybe it is not support Standarized Payload Decoder.
Claudio