You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But users can create (manually configured) senseboxes with empty sensortype via the OpenSenseMap UI.
When retrieving those sensors via the API, they wont not have the sensorType key
Possible Solution
Mark the sensortype as optional, even if there is only 1 sensor in the DB with empty sensortype
or set a default value like null or "undefined" or empty string
Steps to Reproduce (for bugs)
Manually configure a sensebox via the UI
Add a sensor to the box, leave its type empty
Query the area where the box is located
Context
Tried to download all senseboxes in an area.
The unmarshalling failed because of this 1 broken sensor.
The text was updated successfully, but these errors were encountered:
hf-kklein
changed the title
docs: sensortype is actually optional but docs state it's not
docs: sensortype is actually optional but docs state it's not
Dec 20, 2023
hf-kklein
changed the title
docs: sensortype is actually optional but docs state it's not
docs: sensortype is actually optional for manually configured senseboxes but docs state it's not
Dec 20, 2023
Expected Behavior
Docs should state the actual data to be expected from the API.
Current Behavior
Docs say, that sensortype is not optional:
https://docs.opensensemap.org/#api-Boxes-getBox
But users can create (manually configured) senseboxes with empty sensortype via the OpenSenseMap UI.
When retrieving those sensors via the API, they wont not have the
sensorType
keyPossible Solution
Steps to Reproduce (for bugs)
Context
Tried to download all senseboxes in an area.
The unmarshalling failed because of this 1 broken sensor.
The text was updated successfully, but these errors were encountered: