Is anyone else having problems getting a response from Sensor.Community when you request to transfer your AQI sensor to a new owner? My old sensor has disappeared completely from the Sensor.Community after I requested to transfer ownership, but no email has been received by the new email account. My sensor now lives in purgatory somewhere! Has anyone else had a similar problem and any suggestions for how to proceed? Thanks in advance for your help!
Could you please send the chipID and the old and the new email address to tech (at) sensor.community.
I think that there was a typo in the target email address. So the registration was moved to this email but the confirmation couldn’t be sent.
Dear Colleges, I reply to this post because I have the same issue
Mij sensor was handed over with the following mailaddress:
gervanderrijt@onsbrabantnet.nl.
however I was not able to make/ register an account at sensor.community with this address.
a message as confirmation needed was displayed after entering the password.
Registering with gervanderrijt@kpnmail.nl was succesful !!
But there I can not see a sensor.
Adding a new sensor starts registration but is not seen afterwards.
Suggesting my sensor to be added at my account gervanderrijt@kpnmail.nl
or my registration with my primary mailaddress gervanderrijt@onsbrabantnet.nl made possible so the sensor can be seen on the map
The sensor is working, locally and puts data at grafana
Can you help me with the Registration or coupling of the sensor to the valid address ??
with kind regards,
Ger van der Rijt
@gervanderrijt Hi, I’ve moved the sensor to your newest account.
Thank you for this action,
removed old data and filled in the new location
can you check if everything is ok now ?
regards, Ger
Hi @gervanderrijt , we can’t really check something. The position can only be checked by you. And if the sensor is shown on the map then everything should be fine.
Thanks for your reply,
can you explain the reason for the data send return timeout ?
Home » Apparaatstatus
| Parameter | Waarde |
|---|---|
| Firmware-versie | NRZ-2024-135 |
| ST:1 | |
| SDK:2.2.2-dev(38a443e) | |
| Core:2.7.3-3-g2843a5ac=20703003 | |
| lwIP:STABLE-2_1_2_RELEASE | |
| glue:1.2-30-g92add50 | |
| BearSSL:5c771be | |
| Free Memory | 28464 |
| Heap Fragmentation | 4 % |
| Last OTA | 23 hours, 29 min, 33s |
| NTP Sync | 216 |
| NTP Info | 185.51.192.61 (1.pool.ntp.org) reachable: Yes |
| Tijd (UTC) | Sun Aug 11 12:59:48 2024 |
| Uptime | 8 days, 23 hours, 42 min, 53s |
| Reset Reason | Software/System restart |
| SDS011 | 18-11-16(0827) |
| enkel foutmeldingen | |
| WiFi | 0/-85/0 |
| OTA Return | 200 |
| Sensor.Community | 352 |
| Madavi.de | 7 |
| Data Send Return | read Timeout |
| SDS011 | 25 |
| Aantal metingen | 5219 |
| Tijdsduur opsturen metingen | 3677 ms |
Thank you in advance
The error message is only showing the error of the last failed transmission. As long as the count of failed transmissions is only a small part of the count of measurements everything is okay.
This may happen as sometimes too many sensors are trying to send data to our servers of if your internet connection is down for a moment.