Closed rhythnic closed 5 years ago
Fixed for LoRa V2. I'm working on a similar bug. Going to use this issue. The bug is that device profiles created in the UI are not synced to LoRa V1.
Here is a successful device profile post to V1. It's the device profile from LoRa v2.
{"deviceProfile":{"classBTimeout":0,"classCTimeout":0,"deviceProfileID":"9dd538e8-a231-4a35-8823-eecbffb9d4a9","factoryPresetFreqs":[],"macVersion":"1.0.0","maxDutyCycle":0,"maxEIRP":0,"pingSlotDR":0,"pingSlotFreq":0,"pingSlotPeriod":0,"regParamsRevision":"A","rfRegion":"US902","rxDROffset1":0,"rxDataRate2":0,"rxDelay1":0,"rxFreq2":0,"supportsClassB":false,"supportsClassC":false,"supportsJoin":false},"name":"BobMouseTrapDeviceProfileLv2","networkServerID":"5","organizationID":"56"}
Here's the failing one from the UI:
{"deviceProfile":{"deviceProfileID":3,"macVersion":"1.0.0","regParamsRevision":"A"},"name":"CATA Device Profile","networkServerID":"5","organizationID":"56"}
Obviously there are a lot of missing properties. Need to figure out if the UI is not passing them up or there is a server bug. @dschrimpsher FYI
Changes thus far are on branch issue-245
The issue was that deviceProfileID was a number and not a string.
Device profile creation fails on LoRa because top-level properties are not in payload. Response to UI succeeds because response goes back before the device profiles are created on LoRa Server.