Thanks, @kersing, for the heads-up—this is actually very helpful. I looked into integrations and searched related issues about normalization, and I came across this issue, which provides details on the rationale behind normalization.
Having a known data model/format will allow building integrations/apps using data coming from The Things Stack without caring about what device is providing that data, the units used…just caring about the capabilities/sensors that it has.
This makes sense. Sorry if this was obvious to everyone else—I’m still a noob on TTN, learning as I go.
My reference for trying to make sense of normalizeUplink() and its implementation in the PF was from the docs. Based on what I’ve learned, I’ll move forward with the following actions:
- Open an issue to suggest improvements to the documentation to better explain the context and expectations of
normalizeUplink(). - Open an issue for possible additions to the schema for the SenseCAP 2120’s UV Index and Rain Gauge fields, which are currently unsupported.
Thanks again for pointing me in the right direction!