Relation between chipid and sensor->id

1

A SeCo-sensor has a chipid. Which is part of the MAC-address of the ESP.
When uploading data to SensorCommunity I assume this chipid is the unique id. In the SensorCommunity-DB this chipid is related to sensor-id. Am I correct?

The SensorCommunity API gives sensor->id. But not chipid.
When I send data to my own endpoint I only see chipid. Which makes sense because the relation between chipid and sensor->id is in the SensorCommunity-environment.

Is there nonetheless a way to relate these id’s?

I would like to send data of a bunch of sensors to both the SensorCommunity-endpoint and my own endpoint to prevent data loss when one or the other is down.

2

Welcome,
Have you read the guide on the website ?
Have you configured the device well in the interface ?
Have you registered on devices.sensor.community ?

If yes, the data is sent to sensor.community and also to madavi.
In the sensor interface (reachable from your router) you can make the sensor send the same data to your own endpoint.

3

And if you hae registered the sensors at devices.sensor.community then you can see the sensorIDs there. Or you can get them on the map, these are also the same sensorIDs as used for our API or our archive. So for you as the owner of the device all IDs are known.

4

I will clarify my question.
Yes, I have a working sensor, sending its data to SensorCommunity and to our own endpoint.
But the data that arrives at our own endpoint only has the chipid as unique identifier.
I would like to have many sensors (not only my own) to send their data to our endpoint. Thus creating a bypass when SensorCommunity fails.
We at RIVM have https://samenmeten.rivm.nl. Some 80% of the sensordata comes from the SensorCommunity-API. But this API has not the chipid in its json.
So I can tell people to also send their data to our endpoint but then I can not relate this data to the original data we extact from the SensorCommunity-API.
Best option would be to have the chipid included in the SensorCommuniyt-API. Is that a realistic option?
Or do you maybe see other options?
Best regards,
Derko

5

Hello,
the chipID is part of the MAC address that is sent with every wifi packet. So someone could scan for the devices (starting at the position shown on the map.)
For many users this is a privacy issue.
But if you ask the users to add your endpoint then why not asking them for their chipID<->sensorID mapping?