Better Practice Non-Technical User Asset/Attribute Design

I am a non technical functional application user. Currently we have a project that utilses a LoRaWAN controller to collect various inputs including RS485 data from a weather station with around 10 data types. We have decided to use a new Asset for the weather data rather than over complicating the LoRaWAN node asset with numerous different attributes from different sources. We have pointed the data from the payload attribute link directly to a weather asset that has no physical LoRaWAN node.

I was wondering if there are other non technical users who may have developed standard better practice approaches to functionally using the system?

thanks
Scott

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.