Sensor ID is already registered

142

Thank you in advance :smiley:

143

@Markus1234 Could you please retry the registration? There isn’t one in our database for this chipID. You should check that all components are only listed once (only on SDS011, only one BME280, …)

144

Hello.
i have a Dust sensor connected to a wireless stick lora32 + Wifi + Blu.
how can i know my sensor id ?
also i can’t find the GP2Y1010AU0F dust sensor choices in the Sensor Type.
if the id it’s mean the chip id can you release my id please

145

Hello @ricki-z any news ?

146

Hi everyone,

I am from France and I also need help to delete my devices from your database for my final submission next week :
I need to create a new one with the same chip ID and two different sensors but I’ve got the same issues wich is "Sensor Id is already registered.

My chipID : 5C13
My registered devices : ESP32

Thank you in advance

info: I already contact the support but no reply for now

147

And again, for all new users in this forum:
We are a volunteered project, not a multimillion company. So we may need a little bit more time to answer questions.

2 Likes
148

@Meir_Belaich we can only support our firmware as we don’t know details of other implementations. So for the question regarding the chipID you should contact the developer of the firmware of your device.
In our firmware there is no support for the mentioned dust sensor.

149

Hello, @ricki-z
Thank you for your feedback.

Does the chipID refer to the sensor or the ESP32 module?
I also have a BME280 sensor available, so do I need the chipID of my BME280 or of my ESP32 LoRa wireless module?
Thank you.

150

@Meir_Belaich I’ve send you an answer to your mail.
But for all people reading this thread:
We need the chipID of the esp8266 or ESP32 module. For the Arduino ESP extensions there are functions for this.
If you use an Raspberry PI there is an entry for the serial number in /proc/cpuinfo that should be used.
For LoRaWAN/TheThingsNetwork users there should be a device ID when registering the device in the network that can be used.
In any case if you implement your own firmware or script this should send a HTTP header ‘X-sensor’ with a prefix for the system (‘esp8266-’, ‘esp32-’, ‘raspi-’, ‘TTN-’) followed by the chipID.
When you register your device at https://devices.sensor.community/ then you can select the system name and use the chipID.

1 Like
151

@ricki-z
Edit: NVM, Works now (don’t know if you did anything…)

Could I have released sensor for registration please?
chipID=esp8266-6788033
LOG:

Sending to sensor.community - SDS011
Request failed with error: 403
Details:{"detail":"Node not found in database."}

Thank you for your work for the community.

152

@Irek_Anonimowy I’haven’t done anything. Maybe you accidentally tried to add a component more than once at your first attempt. In this case the same error message is shown.

153

Can you please release chipID: 5583667?
Thank you!

154

Hi @ricki-z
Could you please release the sensor ID esp8266-14070151? It’s already registered, and I’d like to register it again.

Thanks a lot!

155

HI @marcoweber3 , I can’t see any data for this chipID at api-rrd.madavi.de. This site can be used to test the sensor before registering it. And for us it’s a help to prove the provided chipID.
So are you sure that the device is connected to your wifi network and that this is the right chipID?
(Former registration was by a different user …)

156

Hi @ricki-z,
Thanks for your reply. I’m sure the ID 14070151 is correct. I got this sensor from a friend about two or three years ago but only recently had time to set it up again. My friend no longer has access to the old account details.

The ESP is definitely connected to WiFi, but there seems to be an issue. I’ve attached a screenshot of the device status. There’s an error related to OTA—maybe you have some insight into what could be wrong?

1000031239
10000312391080×2660 307 KB

Could it also help to manually flash a new firmware version, since the device hasn’t been connected to the internet for a while?

Thanks for your help!

157

Hi @marcoweber3 . Yes you should flash teh latest stable version manually. Let’sEncrypt had a major change in the certificate chain, that disabled https connections in older firmware versions.
And could you please send me the name of your friend as a DM here? If it’s the person we have in our database then I can remove the existing registration.

158

Hi
could you please release ID 2385691, but for safety check if there are no active sensors with this ID

159

Hi. I have the same issue like others, the sensor is already used.
The number is 13463958.

Thank you for helping!

Br,

Feri