Cumulus Support

Error 500 (error) Error processing Ecowitt settings: Object reference not set to an instance of an object.

This appears everytime I try to enable my Ecowitt - previously running fine. With a new install I typically have to disable, close CMX, reopen, enable to get it to display correct data. Right now I can't do that.

Guy

Could you post a zipped MXDiags file please as this will help the diagnosis.

I am using HTTP Ecowitt on Windows with no problems whatsoever.

Oh wow! That seems to have been broken since v3.16.0 - b3182, unless a library update changed how JSON encoding is handled.

Your Ecowitt extra sensor settings up and including settings up to "Leak" should be saved OK, settings after that will not.

grwkak wrote: ↑Thu 16 Jun 2022 9:59 pm This appears everytime I try to enable my Ecowitt - previously running fine. With a new install I typically have to disable, close CMX, reopen, enable to get it to display correct data. Right now I can't do that.

Can you explain that some more. When upgrading you should not need to do any configuration change or close/reopen etc.

When I update I close the browser interface/display, close CMX. Then copy files to the correct directory (all the files from the CMX download).

After that I restart CMX - often if I view the extra sensors in the browser I see false readings from sensors I do not have with obviously incorrect readings (say -88F).

So I disable the extra sensors, save settings, close CMX, restart, and enable extra sensors then it seems to work properly.

Guy

Diag attached

For those "phantom" extra sensors, have you followed the general advice and disabled discovery for any sensors you do not have in the WS View[+] app?
There is a known issue where the station can sometimes send invalid data for sensors that are not present but have discovery enabled.

Just saw this reply! Will try this.

Guy