CMX reading on start up but station not updating [SOLVED]

[Cambium]

Station wasn't updating today, then started working before, now its not again. Reinstalled it yesterday trying to get it running smoothly.

Under station type I chose HTTP Ecowitt, is that right?

How do I check the ini folder error?

What would give me this ini message when starting it up?

Why would data stop retriveing after some time?

Would normal and real time settings have anything to do with it in configuration settings, I have both checked?

20230617-190455.txt

SS.jpg

[PaulMy]

Hi,
Your have it now in your Program Files folder.

Code: Select all

2023-06-17 19:04:55.272  ========================== Cumulus MX starting ==========================
2023-06-17 19:04:55.272 Command line: "C:\Program Files (x86)\CumulusMX\CumulusMX.exe"  

From the WiKi

Code: Select all

There is one place, where you must not store MX, and that is "avoid the 'Program File' hierarchy".

viewtopic.php?p=162744#p162744


Enjoy,
Paul

[Cambium]

Something is stopping the readings after some time. Getting this message popping up. Trying different settings with the config wizard but nothing seems to work. I have everything set right, path, mac, interval, ect, ect

SS1.jpg

20230618-081633.txt

[SamiS]

Basically all the data you get is coming from ecowitt.net when doing catch-up on start. The logfile shows that CMX is trying to connect to address 0.0.0.0 which is obviously not possible since it is not a valid ip address. Actually it should not be trying to connect to anything if you have properly selected the HTTP (Ecowitt) as station type. Do you have ”Allow Cumulus to configure your Ecowitt gateway for you” enabled?

Also one thing to check is that your computer’s ip address hasn’t changed. If it has, you must change it to your weather console’s custom upload server.

[Cambium]

Do you have ”Allow Cumulus to configure your Ecowitt gateway for you” enabled?

I didn't, now I do. Still not updating

Also one thing to check is that your computer’s ip address hasn’t changed. If it has, you must change it to your weather console’s custom upload server.

Looks like the console is 1.6 and the PC is 1.9. Which do I add for these options?

Ecowitt Gateway devices IP address:
Local Cumulus address:

I also notice on the Cumulus screen its showing the :8998/ after the IP address. I dont remember seeing that when it was working right. Only under local host

[SamiS]

I didn't, now I do. Still not updating

Ok, so it did not help.

Also one thing to check is that your computer’s ip address hasn’t changed. If it has, you must change it to your weather console’s custom upload server.

Looks like the console is 1.6 and the PC is 1.9. Which do I add for these options?

Ecowitt Gateway devices IP address:
Local Cumulus address:

You must configure you pc:s ip address to your weather station console’s custom upload server. First press the setup gear button, then use arrows to go to weather server, then use arrows and go to customized setup, and there you should be able to setup your server (pc) ip and path that should be /station/ecowitt

If this still does not help, please post a new version of your mxdiags logfile.

[Cambium]

You must configure you pc:s ip address to your weather station console’s custom upload server. First press the setup gear button, then use arrows to go to weather server, then use arrows and go to customized setup, and there you should be able to setup your server (pc) ip and path that should be /station/ecowitt

If this still does not help, please post a new version of your mxdiags logfile.

Appreciate the help! New diags attached.

I noticed it says this in the diags. Why would it say #& at the end of the IP?

"2023-06-18 11:05:16.577 Ecowitt Gateway Custom Server config: Server=http://192.168.1.#&, Port=0, Path=/station/ecowitt, Interval=0, Protocol=Ecowitt, Enabled=0
2023-06-18 11:05:16.577 Ecowitt Gateway Custom Server config does not match the required config, reconfiguring it...
2023-06-18 11:05:16.655 Error setting Ecowitt Gateway Custom Server config: Destination array was not long enough. Check destIndex and length, and the array's lower bounds.
2023-06-18 11:05:16.655 Ecowitt Gateway Custom Server configuration complete"

Here's what I have under the WS View settings.


But under device list it shows this. It changed from 192.168.1.6 before

20230618-110514.txt

[freddie]

Think you need to remove the "/" after the 8998.

[Cambium]

Think you need to remove the "/" after the 8998.

Thanks freddie. I removed that and still having issues. I also tried to uncheck 'Enable Gateway Config:" I think its that setting that is the issue I will reenable it

Cumulus definitely not retrieving the data only on start up

Attached new diags

20230618-114546.txt

I reenabled it and it automatically entered 0.0.0.0

[SamiS]

Appreciate the help! New diags attached.

I noticed it says this in the diags. Why would it say #& at the end of the IP?

"2023-06-18 11:05:16.577 Ecowitt Gateway Custom Server config: Server=http://192.168.1.#&, Port=0, Path=/station/ecowitt, Interval=0, Protocol=Ecowitt, Enabled=0
2023-06-18 11:05:16.577 Ecowitt Gateway Custom Server config does not match the required config, reconfiguring it...
2023-06-18 11:05:16.655 Error setting Ecowitt Gateway Custom Server config: Destination array was not long enough. Check destIndex and length, and the array's lower bounds.
2023-06-18 11:05:16.655 Ecowitt Gateway Custom Server configuration complete"

Here's what I have under the WS View settings.


But under device list it shows this. It changed from 192.168.1.6 before


20230618-110514.txt

First I would suggest disabling the gateway autoconfiguration on CMX settings and restart it. There seems to be some issue with autoconfig, the weird ip ending with #& is related to this.

Then I agree with freddie, you should remove the / after 8998 on ws view.

The ip address confusion is a bit strange. Is your weather console maybe connected to a ”guest” wifi ssid instead of the main network? Also it seems that there is something odd going with ipv6. If your weather console allows disabling it, it could help.

[PaulMy]

Hi,
Again from memory I think the Server IP / Hostname: in WS View should be just the IP address 192.168.1.9 so also remove the :8998
The port needs to be set as you've done 8998 for the default CMX startup.

Code: Select all

Manual Configuration: In WS View configure the Custom Server to use:-
Protocol: Ecowitt
Server: CMX IP Address
Path: /station/ecowitt
Port: 8998
Interval: 20

Enjoy,
Paul

[Cambium]

First I would suggest disabling the gateway autoconfiguration on CMX settings and restart it. There seems to be some issue with autoconfig, the weird ip ending with #& is related to this.

Done

Then I agree with freddie, you should remove the / after 8998 on ws view.

Done

The ip address confusion is a bit strange. Is your weather console maybe connected to a ”guest” wifi ssid instead of the main network? Also it seems that there is something odd going with ipv6. If your weather console allows disabling it, it could help.

Not a guest. Do you guys think its the Cumulus latest update maybe has something off?

[SamiS]

Not a guest. Do you guys think its the Cumulus latest update maybe has something off?

If there were problems with the newest build and ecowitt http protocol, there would be much more problem messages. For me it seems the problem is somehow related to your own environment.

However after checking the images you sent before, I agree with Paul. Ws View should have only the plain ip address without :8998 since the port is defined on its own textfield.

[Cambium]

Ws View should have only the plain ip address without :8998 since the port is defined on its own textfield.

Done.

I'm trying everything, nothing is working to get Cumulus to update while running.

Let me backup the data I have, then try to uninstall then reinstall Cumulus.

[SamiS]

I looked at the previous thread from the time you first setup your system, and it seemed to be very tricky also. There was some discussion about how your system only worked if you used 60 seconds update interval. So that is maybe one thing to try on ws view. Personally I don’t believe that reinstallation will solve your problem. Do you have logfile captured after the last settings change?