Sensors must be positioned / bound to parking parking space position in order to generate parking occupancy events and be available via APIs. While a sensor is not positioned you can only see its raw messages. The look like a sequence of hexadecimal numbers and are not too useful.
...
Device Monitoring - for getting information about sensor health;
Occupancy - for monitoring which allows you to know which sensors are vacant and which are not;
HTTP outgoing calls - for getting occupancy data using HTTP triggers about sensor occupancy states changes;
https://nwaveio.atlassian.net/wiki/pages/resumedraft.action?draftId=1864761385
| Tip |
|---|
Even if you make your first steps in Nwave Console using Test Devices, you should set their positions before using them. |
How To set sensor position
Nwave provides a special tool for sensor positions management. It is called SPlace. You have two types of SPlace using:
Web-version on http://splace.nwave.io/
Android App https://play.google.com/store/apps/details?id=io.nwave.splacing2
Installing SPlace for Android
Android App is much more functional than Web Version. With It, you are able to set up and calibrate sensors using Bluetooth. But you need to install Nwave Device Management App first.
Position setting
As you can see in the Nwave ecosystem document, Nwave stores sensors' positions in the hierarchy. Before setting a sensor position, you need to create or select an existing project, zone, level and group and assign labels to spaces (EV, ADA/Disabled, etc).
...