Cumulus Support

Running CMX with Davis VPw2 station using WiFiLogger, and adding Ecowitt extra sensors via HTTP settings in WS View.
Just realized that the Extra sensor page in the Dashboard shows data for Soil Temperature, Leaf Temperature/Wetness, and Lightning and I don't have these sensors. The only extra sensors I have are Air Quality and Soil Moisture and these do appear to show correct in CMX.

Is this a possible a settings issue?

Screen capture attached.

Enjoy,
Paul

I've got my GW1000 sending data to my CMX set up too.

I have 2 multi-channel temp/humidity sensors, soil moisture and lightning checked.

All seems OK on mine?!

Paul can you switch on debug and data logging then post the log file please.

MXdiags is set to logging so I have several files.
The issue is now disappeared with only Lightning showing as -1 km and I believe it has always shown this.

My computer periodically shuts down unscheduled (Your PC needs to Shut Down...) and then automatically restarts. I have StartWatch and at a PC reboot then CMX auto starts as well and have not seen any issue with this.

CMX had been running for a while when I noticed the bogus sensor data last night, and that bogus data continued until another PC shutdown at about 7:00 am this morning and from a restart the bogus data is no longer showing. Thinking back I am sure most of the time the bogus data had not been showing and the ExtraLog files, going back to late July do not show the bogus values except the period 02/08/21 10:50 to 04/08/21 07:00.

Attached ExtraLog202108.txt shows the period that the bogus data is in the log.
Attached MXdiags from before until PC shutdown 20210803-181145, and from that restart to current 20210804-070338. (from looking at MXdiags I just realized I had forgotten to untick Realtime for my Ecowitt extra sensor script I've added to Extra Web Files, and now only at normal interval)

Thanks,
Paul

p.s.
This is one extract I noticed in MXdiags when bogus data logged and before PC shutdown:
2021-08-04 06:45:07.925 ProcessExtraData: Processing posted data
2021-08-04 06:45:07.925 ProcessExtraData: Payload = PASSKEY=522298689EAB74C44CB3881F6F696FBD&stationtype=GW1000B_V1.6.8&dateutc=2021-08-04+10:45:08&tempinf=76.6&humidityin=55&baromrelin=30.082&baromabsin=29.161&soilmoisture1=43&pm25_ch1=12.0&pm25_avg_24h_ch1=14.1&soilbatt1=1.5&pm25batt1=4&freq=915M&model=GW1000
2021-08-04 06:45:07.925 ProcessExtraData: Record date = 2021-08-04 10:45:08
2021-08-04 06:45:07.925 ProcessExtraData: StationType = GW1000B_V1.6.8, Model = GW1000, Frequency = 915MHz
2021-08-04 06:45:07.925 ProcessExtraData: Complete
2021-08-04 06:45:08.514 Done uploading standard Data file

This is extract from MXdiags when bogus data not logged and after PC reboot and CMX restart:
2021-08-04 07:04:34.503 ProcessExtraData: Processing posted data
2021-08-04 07:04:34.503 ProcessExtraData: Payload = PASSKEY=522298689EAB74C44CB3881F6F696FBD&stationtype=GW1000B_V1.6.8&dateutc=2021-08-04+11:04:33&tempinf=76.5&humidityin=55&baromrelin=30.079&baromabsin=29.158&soilmoisture1=43&pm25_ch1=14.0&pm25_avg_24h_ch1=14.1&soilbatt1=1.5&pm25batt1=4&freq=915M&model=GW1000
2021-08-04 07:04:34.503 ProcessExtraData: Record date = 2021-08-04 11:04:33
2021-08-04 07:04:34.503 ProcessExtraData: StationType = GW1000B_V1.6.8, Model = GW1000, Frequency = 915MHz
2021-08-04 07:04:34.503 ProcessExtraData: Complete

Both look fine to me.

Do you have the log file for 2nd August @ 10:50 when the "bad" data was logged?

Hi Mark,
Attached are the MXdiags from before the bad data was logged in ExtraLog202108 to current.
I've looked and wasn't able to see anything bad in the many ProcessExtraData entries, just the expected inside temp/hum/press and the AirQuality and SoilMoisture, and battery status.

The initial bad data does appear to be about the time of an unexpected PC shutdown/restart, and continued past at least one other shutdown/restart.

As the ExtraLog shows now, all is ok.

Thanks,
Paul

I cannot see anything either in the Ecowitt data, or the VP2 data.

But it looks Cumulus was stopped abruptly at 10:49. Perhaps something got corrupted because it was not a controlled shutdown.

Thanks Mark,
I will keep an eye for when the next shutdown occurs.

Enjoy,
Paul