After the last week’s downtime (the SSL incident), I’ve updated my Airrohr-Sensor. It works like a charm and the data can be seen on map.sensor.community. Only the connection to OpenSenseMap seems to be broken.
I’ve double-checked the senseboxID and double-checked if OpenSenseMap is enabled in the config. In the debug log, I can find the following:
## Sending to sensor.community - BME280
Succeeded - api.sensor.community
## Sending to opensensemap:
Time for Sending (ms): 107
Any ideas on how to debug this issue? Is there a kind of log interface at OpenSenseMap?
Opensensemap indeed uses a Let’s Encrypt certificate which was renewed on March 16th without the X3 cross-signing so HTTPS uploads from the released firmware to opensensemap will fail.
Unfortunately the current SC-firmware (both release and beta) have HTTPS for the OpenSenseMap API hardcoded and it can’t be disabled in the UI.
Upgrading the SC firmware of a ‘Luftdaten’-setup to deal with this aspect seems the best idea, but reluctant to ‘fiddle’ with patched firmware, because knowing the limits of my capabilities: do not touch what is working …
Instead looking for a ‘general’ work-around:
is a small (Python**?**) script available with following 3 functions?
a. locally read the device by url-call http://ip-address/data.json
b. recompile the info from the resulting json-file for compatible upload to opensensemap
c. periodically perform that upload
Interested to participate in this kind of solution.
I understand the “do not touch what is working” sentiment. However this and other fixes and features are available in the current official release of the firmware NRZ-2024-135 since Apr 9 2024. That version works on more than 11000 installed sensors so you might consider installing the official firmware.
Normally yes but this specific beta version (NRZ-2021-134-B4) has a bug in the automatic updating so won’t auto-update. You’ll have to manually re-flash.