this decodes fine to: 0x00,0x00,0x00,0x00,0x00,0x20,0x57,0xf9,0x8c,0x18,0x00,0x15,0xd4,0xa4,0xd5,0xb3,0x70,0x43,0xda,0x86,0xcf,0x03,0x18
Have you tried to match that up against device documentation to decode each byte? Once you had a decoder, beat it into format chirpstack requires and include it in the device profile for that particular family of devices. Then, adding new devices using this device profile would get their data decoded.
If that’s not working (ie. hex data isn’t valid per device documentation), then you’d come on the forums and provide your existing code, any errors from the logs, and information on device you’re dealing with. It REALLY helps to start with a commercially available device that is known to work with chirpstack, if you want to avoid stress.
P.S. I’ve been away from chirpstack forums in a holding pattern, waiting for the great news that came recently. However, I don’t know what to do with “docker” so will need to find some time to figure that whole thing out (under ubuntu - if anyone can point me to a good tutorial).