Error: Node not found in

1

Hi!

I searched the forum, but couldn’t find any hints on how to solve the following error:

PM10: 3.50
PM2.5: 3.03
----
## Sending to sensor.community - SDS011
Request failed with error: 403
Details:{"detail":"Node not found in database."}
Temperature (°C): 24.36
Pressure (hPa): 98292.53
Humidity (%): 47.97
----
## Sending to sensor.community - BME280
Request failed with error: 403
Details:{"detail":"Node not found in database."}
## Sending to madavi.de:
Succeeded - api-rrd.madavi.de
Time for Sending (ms): 191

After reflashing the firmware, it seems that Data is send correctly, but only to madavi:

https://api-rrd.madavi.de:3000/grafana/d/GUaL5aZMz/pm-sensors?orgId=1&theme=light&var-chipID=esp8266-6631327&from=now-6h&to=now&timezone=browser&var-type=BME280&var-query0=sensors

Before that I got the error from madavi:

Request failed with error: 308

The Sensor-ID is: esp8266-6631327

Can someone help?

Greetings
Till

2

Have you registered the sensor on devices.sensor.community ?
What is the SensorID ?

3

Yes. The Sensor-UID is: esp8266-663127
The two registered Sensors are: 95411(SDS011) and 95412 (BME280)

When I log in to devices.sensor.community it says:

Zu diesem Sensor liegen keine aktuellen Daten vor.
4

Are you sure it is the SensorID from the map ? We are so high now ? And are you sure the sensor is still connected to internet ? Can you check the access through your router with the DHCP client list ?

5

I’m reading the ID from devices.sensor.community when im logged in. I’ll attach my screenshots.

I initially was suspecting the WIFI. We wanted to install the sensor at our school (I’m a teacher) to measure the air quality around our school with students. We have some limitations in our school-WIFI, so after those error messages I brought the sensor home for testing. Here I have the same error messages. (The gap from tonight is caused from the WIFI shutting down, but now in the morning it is transmitting to madavi but still not to sensor community → same error).

Maybe I’ll try buying another node mcu…

Bildschirmfoto 2025-07-15 um 06.45.05
Bildschirmfoto 2025-07-15 um 06.45.052332×872 182 KB

Bildschirmfoto 2025-07-15 um 06.45.59
Bildschirmfoto 2025-07-15 um 06.45.59992×2012 150 KB

6

@ricki-z Can you help ? It is above my knowledge…

7

Could something have been deactivated in devices.sensor.community ? or in the database ?

8

Hello @Till the screenshot shows a chipID 6631327.
I’ve changed the device registration to this chipID.

9

Thanks a lot! It’s working now and we could figure out the last necessary settings in our firewall.

One last question: You said, that “you changed the device registration to this chipID”. Was something wrong with my registration? Because I hope that I didn’t type in anything incorrectly…

10

[quote=“Till, post:1, topic:6970”]
The registration was for chipID 663127 (see the screenshot of the page at devices.sensor.community).
But the status page of the sensor shows 6631327 as the chipID (screenshot of the status page).
So there was only a missing “3”.