Cumulus Support

Hi
ever since I moved to 3117 I'm getting the following error: maybe I missed something in the update ....
renamed my old CumulusMX folder to CumulusMX3116
created a new CumulusMX directory CumulusMX - copied all the CumulusMX 3117 files from the zip into the CumulusMX folder,
copied Cumulus.ini and the data directory from the CumulusMX3116 into the CumulusMX folder.
In my understanding I did everything right.
Everything continued working well except for the error messages for the CO2 sensors (keep on showing "loading ..." in the interface
and no sensors and values shown).
Another observation:
when I try to edit a log entry in the data log viewer, it gives the message "Error! Response code: 404 There was an unknown error!"

As a side remark - the interface shows "Cumulus MX 3.9.2 b3097" in the bottom line - I would expect to see "3.10.2 b3117". But that might be a beauty thing.

environment: Raspberry Pi 4, Debian 10 (not the CumulusMX image for RPi), mono 6.12.0.122

Gyvate wrote: ↑Mon 08 Mar 2021 9:19 am ever since I moved to 3117 I'm getting the following error:
CO2-Ajax-error-extra sensors-20210308.JPG

Can you post the results of this URL please...

http://localhost:8998/api/extra/co2sensor.json

Gyvate wrote: ↑Mon 08 Mar 2021 9:19 am As a side remark - the interface shows "Cumulus MX 3.9.2 b3097" in the bottom line - I would expect to see "3.10.2 b3117". But that might be a beauty thing.

It will reflect the version of the program that you are connected to, it is dynamic data not static.

Which implies you are still running v3.9.2

mcrossley wrote: ↑Mon 08 Mar 2021 10:57 am

Gyvate wrote: ↑Mon 08 Mar 2021 9:19 am ever since I moved to 3117 I'm getting the following error:
CO2-Ajax-error-extra sensors-20210308.JPG

Can you post the results of this URL please...

http://localhost:8998/api/extra/co2sensor.json
{"Title": "Unexpected Error","ErrorCode": "KeyNotFoundException","Description": "Key Not Found: co2sensor.json"}

Gyvate wrote: ↑Mon 08 Mar 2021 9:19 am As a side remark - the interface shows "Cumulus MX 3.9.2 b3097" in the bottom line - I would expect to see "3.10.2 b3117". But that might be a beauty thing.

It will reflect the version of the program that you are connected to, it is dynamic data not static.

Which implies you are still running v3.9.2

theory and reality ...
how would this be possible after I did this in my opinion clean new install (see description above) and only copied the Cumulus.ini and the content of the data directory - or does the data directory contain information that says b3097 ?

below the OS message after start
pi@raspberrypi:~/CumulusMX $ sudo mono CumulusMX.exe
Cumulus MX v.3.10.2 build 3117
Working Dir: /home/pi/CumulusMX/
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Open the admin interface by entering this URL in a browser.
Today.ini = data/today.ini
Last update=2021-03-07T12:31:00
Connected to station
Normal running
3/7/2021 12:32:36 PM
Type Ctrl-C to terminate

but the browser interface still shows "Cumulus MX 3.9.2 b3097" in the bottom line ...
strange ...

The error message - "Key Not Found: co2sensor.json" - means that the version of Cumulus MX you are running does not support that URL, again it means you are not running b3117.

The version and build number on the dashboard pages comes direct from the executable.

Could you have another old copy of Cumulus still running in the background?

mcrossley wrote: ↑Mon 08 Mar 2021 1:36 pm The error message - "Key Not Found: co2sensor.json" - means that the version of Cumulus MX you are running does not support that URL, again it means you are not running b3117.

The version and build number on the dashboard pages comes direct from the executable.

Could you have another old copy of Cumulus still running in the background?

I did a reboot - and now it shows 3117, the data log entries can be edited and the ajax error has disappeared.
the option: stop second instance was tagged though - but you never know

However,
- the CO2 data in the extra sensor table are all 0 now - before there had been values different from 0.
- the lightning date/time is just 1.1.1970 (EPOCH 0), 999 km - whereas it should be 03/04/2021 (MM/DD/YYYY) 16:02:47. 27 km, daily count 0
- for airQuality only one sensor is shown - before two were shown. the WH45 sensors are active - the WSView app shows values ...
all other extra sensor data are shown

best you turn on debugging and restart, give it 5-10 minutes, shutdown, zip up mxdiags folder, and post here.

otherwise we are merely guessing what the problem is.

issue solved - without knowing exactly what the reason was - a new install from scratch (migrating the data folder and Cumulus.ini) did the job.
All extra sensor data back.