After update no more data is sent to OpenSenseMap

1

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?

2

please check if you can send to opensensemap without HTTPS.
They may also use a let’sEncrypt cert.

1 Like
3

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.

I and a colleague have been running a patched version of the SC firmware for a week now on three different sensors and it is running very stable with the same performance characteristics as the original release. If people would like to test the patched firmware, binaries are available at https://github.com/opendata-stuttgart/sensors-software/actions/runs/8350876571/artifacts/1340730722
(builds for the PR at Replace DST Root CA X3 with ISRG Root X1 by Phaze-III · Pull Request #1015 · opendata-stuttgart/sensors-software · GitHub )

4

Upgrading the SC firmware of a ‘Luftdaten’-setup to deal with this aspect seems the best idea, but reluctant to ‘fiddle’ with patched firmware,
:wink: 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.

5

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.

6

Clear explanation which would like to follow.

According to header of the Local homepage presently have NRZ-2021-134-B4/NL (Aug 22 2021),
with setup for Firmware-version set to

  • Automatic update of firmware
  • Install beta-firmwares.

With those settings would expect that version NRZ-2024-135 automatically would have been installed, or missing something?

7

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.

8

Hey @Phaze-III
I’m having the very same issue - I got my device setup and working properly when it comes to sending the data to Sensor.community, but getting the

## Sending to opensensemap: 
Time for Sending (ms): 405

My current version is quite old - NRZ-2020-133/EN (Nov 30 2020) - but whatever I tried, I can’t get it to be detected properly on neither my Mac and Windows PC. It just appears as generic USB device, no matter how and what drivers I install. Is there any way to initiate the on-fly firmware update via WiFi?
I have

Firmware version Auto update firmware
Load beta firmware

ticks checked, but they don’t seem to work properly.

9

I’ve resolved the issue by finally being able to connect to the sensor and flash the firmware by cable.
Problem with my NodeMCU board was that even though it was explicitly written on it “Install CH340G drivers”, it appeared as FTDIBUS\COMPORT&VID_0403&PID_6001 which meant I needed proper FTDI drivers instead of CH340G :face_without_mouth:

2 Likes