The server and API are functioning properly and almost all of the API methods are working exactly as described in the API guide. However, regardless of input parameters, the getGeoObject process returns an empty list as its payload ("[ ]"). We seem to be making successful contact with the endpoint (the return message also contains "statusCode: 200", indicating a successful return), but regardless of the geoObjects present in our environment, we cannot see any of them.
We've primarily been running it with {"longitude":0,"latitude":0,"attitude":"friendly","radius":10000} parameters, but have tried all the combinations of parameters we could think of. {"longitude":0,"latitude":0,"attitude":"any","radius":10000}, {"longitude":0,"latitude":0,"radius":10000}, etc...
We are deploying this in Node-RED, but the flow seems to be working properly given that we are getting a successful return statement.
When the getGeoObject request is sent, there are a few errors thrown on the computer that is running the server. Additionally, the PowerShell script running the server seems to be identifying some of the UIDs of the objects within getGeoObject's search radius but is then throwing a "list index out of range" error.
The server and API are functioning properly and almost all of the API methods are working exactly as described in the API guide. However, regardless of input parameters, the getGeoObject process returns an empty list as its payload ("[ ]"). We seem to be making successful contact with the endpoint (the return message also contains "statusCode: 200", indicating a successful return), but regardless of the geoObjects present in our environment, we cannot see any of them.
We've primarily been running it with {"longitude":0,"latitude":0,"attitude":"friendly","radius":10000} parameters, but have tried all the combinations of parameters we could think of. {"longitude":0,"latitude":0,"attitude":"any","radius":10000}, {"longitude":0,"latitude":0,"radius":10000}, etc...
We are deploying this in Node-RED, but the flow seems to be working properly given that we are getting a successful return statement.
When the getGeoObject request is sent, there are a few errors thrown on the computer that is running the server. Additionally, the PowerShell script running the server seems to be identifying some of the UIDs of the objects within getGeoObject's search radius but is then throwing a "list index out of range" error.
Any advice would be much appreciated!!
getGeoObject Return:
Server Computer Errors:
