Only ChirpStack supports DeviceProfiles. TTN and Loriot and IP don't have the concept. Formally a DeviceProfile was created for each Device pulled from TTN or Loriot. That code has been removed in the v2 branch.
The strategy that I suggest is to extract a minimum number of Device Profiles, whose identities are determined by the uniqueness of their networkSettings, when pulling a Loriot or TTN network. There might need to be some coordination in the Network Protocol model when pulling Device Profiles and Devices. Networks that don't have device profiles should return device profile properties in the devices, and the Network Protocol model should extract out the Device Profiles.
When the system attempts to push Device Profiles to a network that doesn't support them, the network protocol handler should contain an empty shell of a command. When pushing devices to networks that don't support network protocols, the network protocol handler should merge device profile settings into the device payload.
When a Device Profile is created/updated, and devices exist for that Device Profile, then those devices should be pushed out to networks that don't support Device Profiles.
Only ChirpStack supports DeviceProfiles. TTN and Loriot and IP don't have the concept. Formally a DeviceProfile was created for each Device pulled from TTN or Loriot. That code has been removed in the v2 branch.
The strategy that I suggest is to extract a minimum number of Device Profiles, whose identities are determined by the uniqueness of their networkSettings, when pulling a Loriot or TTN network. There might need to be some coordination in the Network Protocol model when pulling Device Profiles and Devices. Networks that don't have device profiles should return device profile properties in the devices, and the Network Protocol model should extract out the Device Profiles.
When the system attempts to push Device Profiles to a network that doesn't support them, the network protocol handler should contain an empty shell of a command. When pushing devices to networks that don't support network protocols, the network protocol handler should merge device profile settings into the device payload.
When a Device Profile is created/updated, and devices exist for that Device Profile, then those devices should be pushed out to networks that don't support Device Profiles.