Cumulus Support

Posted: **Sun 18 Jun 2023 8:40 pm**

SamiS wrote: ↑Sun 18 Jun 2023 8:32 pm 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?

Thanks for your time! Yes I remember that 1 minute log interval. I tried that too and nada. Attached the log file

ServiceConsoleLog.txt

Diags

20230618-163400.txt

This is whats throwing me off. Whats with the ffff??

2023-06-18 16:34:06.910 API tag: Processing API JSON tag request
2023-06-18 16:34:06.910 API tag: Source = [::ffff:192.168.1.9]:62853 Input string = ?locationJsEnc
2023-06-18 16:34:07.036 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 16:34:07.056 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 16:34:07.689 API tag: Processing API JSON tag request
2023-06-18 16:34:07.690 API tag: Source = [::ffff:192.168.1.9]:62857 Input string = ?locationJsEnc
2023-06-18 16:34:07.690 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 16:34:07.718 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 16:34:07.730 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 16:34:50.993 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 0

It's reading on startup but wont update. Just gets stuck after its running.

Posted: **Sun 18 Jun 2023 9:01 pm**

Hi,
This is still in your MXdiags:

Code: Select all

2023-06-18 16:35:00.318 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2023-06-18 16:35:00.539 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 0
2023-06-18 16:35:33.053 Updating station settings
2023-06-18 16:35:33.290 Writing Cumulus.ini file
2023-06-18 16:35:33.311 Completed writing Cumulus.ini file
2023-06-18 16:35:35.489 API tag: Processing API JSON tag request
2023-06-18 16:35:35.489 API tag: Source = [::ffff:192.168.1.9]:62877 Input string = ?locationJsEnc
2023-06-18 16:35:35.489 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 16:35:35.511 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 16:35:37.557 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 0
2023-06-18 16:35:37.727 API tag: Processing API JSON tag request
2023-06-18 16:35:37.727 API tag: Source = [::ffff:192.168.1.9]:62875 Input string = ?locationJsEnc
2023-06-18 16:35:37.727 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 16:35:37.737 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 16:36:00.395 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2023-06-18 16:37:00.481 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2023-06-18 16:38:00.229 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing

I'd try in Station settings > Common Options > to tick No sensor check

Code: Select all

Sensor check:
No sensor check
 Make Cumulus MX run even if you do not have the minimum sensors required (temp, press, wind)

Enjoy,
Paul

Posted: **Sun 18 Jun 2023 9:06 pm**

Cambium wrote: ↑Sun 18 Jun 2023 8:40 pm Thanks for your time! Yes I remember that 1 minute log interval. I tried that too and nada.

This is whats throwing me off. Whats with the ffff??

::ffff: is a reference to ipv6 protocol, and earlier I suggested that you should disable it if possible. But I think that there is more relevant messages on your last logfile:

2023-06-18 16:36:00.395 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2023-06-18 16:37:00.481 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2023-06-18 16:38:00.229 Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing

These messages show that your station is now definitely sending data to CMX in one minute interval. Cumulus just rejects it, because one or more of necessary sensor data is missing. Does your console show wind, humidity and temperature properly?

Posted: **Sun 18 Jun 2023 10:57 pm**

PaulMy wrote: ↑Sun 18 Jun 2023 9:01 pm
I'd try in Station settings > Common Options > to tick No sensor check

Enjoy,
Paul

Thanks for the suggestion. Done and nada still.

20230618-184233.txt

So the station IP is 192.168.1.6 but cumulus is showing its running at 192.168.1.9

Posted: **Mon 19 Jun 2023 12:53 am**

Hi,

So the station IP is 192.168.1.6 but cumulus is showing its running at 192.168.1.9

MXDiags shows:

Code: Select all

2023-06-18 18:48:22.086 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 0
2023-06-18 18:49:00.202 *** Data input appears to have stopped
2023-06-18 18:50:00.336 *** Data input appears to have stopped
2023-06-18 18:51:00.425 *** Data input appears to have stopped
2023-06-18 18:52:00.499 *** Data input appears to have stopped
2023-06-18 18:53:00.265 *** Data input appears to have stopped
2023-06-18 18:54:00.304 *** Data input appears to have stopped
2023-06-18 18:55:00.283 *** Data input appears to have stopped
2023-06-18 18:56:00.199 *** Data input appears to have stopped
2023-06-18 18:56:36.607 API tag: Processing API JSON tag request
2023-06-18 18:56:36.607 API tag: Source = [::ffff:192.168.1.9]:63842 Input string = ?locationJsEnc
2023-06-18 18:56:36.607 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 18:56:36.636 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 18:56:43.245 WS Client Disconnected: ::ffff:192.168.1.9, Total clients: 0
2023-06-18 18:56:57.698 API tag: Processing API JSON tag request
2023-06-18 18:56:57.698 API tag: Source = [::ffff:192.168.1.9]:63846 Input string = ?locationJsEnc
2023-06-18 18:56:57.698 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-18 18:56:57.716 WS Client Connect: ::ffff:192.168.1.9, Total clients: 1
2023-06-18 18:57:00.332 *** Data input appears to have stopped

I think you need to double check your IP addresses for both the Ecowitt and CMX.

CumulusMX will run on the IPaddress of your PC. Check your router for PC IPaddress. This is the IPaddress to be entered in WSView. This PC IPaddress will also appear in your CMX startup DOS screen

Code: Select all

Cumulus running at: http://localhost:8998/
                    http://10.0.0.76:8998/

Ecowitt device will have its own IPaddress. Also check your router for this device IPaddress. You can also get it from the WSView App under Device List. (I haven't used the Ecowitt for quite some time so going by memory and hadn't used the Ecowitt Local API version, just used the HTTP (Ecowitt)). This device IPaddress can be entered in the station settings or let CMX detect it automatically.

You had a similar issue about 18 months ago and you should review that thread and see if that helps you get it working again viewtopic.php?p=158965#p158965

Enjoy,
Paul

Posted: **Mon 19 Jun 2023 6:57 am**

PaulMy wrote: ↑Mon 19 Jun 2023 12:53 am I think you need to double check your IP addresses for both the Ecowitt and CMX.

CumulusMX will run on the IPaddress of your PC. Check your router for PC IPaddress. This is the IPaddress to be entered in WSView. This PC IPaddress will also appear in your CMX startup DOS screen

There is an earlier post in this thread that contains ServiceConsoleLog.txt that shows the pc ip address is 192.168.1.9 just as said and configured on ws view.

PaulMy wrote: ↑Mon 19 Jun 2023 12:53 am Ecowitt device will have its own IPaddress. Also check your router for this device IPaddress. You can also get it from the WSView App under Device List. (I haven't used the Ecowitt for quite some time so going by memory and hadn't used the Ecowitt Local API version, just used the HTTP (Ecowitt)). This device IPaddress can be entered in the station settings or let CMX detect it automatically.

The weather station console ip address is irrelevant when using HTTP (Ecowitt) as Cambium is doing here. When using this protocol, the computer running CMX is just running and listening if someone would send some data. There is no need to know weather station console ip address in this setup, because CMX does not connect to the station at all. We also already tried the gateway autoconfiguration yesterday, but it did not get us anywhere.

I’m quite a bit puzzled about the log lines about an api call regarding location.

Code: Select all

2023-06-18 18:56:36.607 API tag: Source = [::ffff:192.168.1.9]:63842 Input string = ?locationJsEnc
2023-06-18 18:56:36.607 API tag: Output string = {"locationJsEnc":"My Backyard"}

I have not seen anything even remotely similar on my ecowitt setup (although my backup station with http ecowitt is running quite a bit older build). For me this is starting to look like we need data logging or even debug logging and @mcrossley to interpret it. But I think Mark is currently on Holiday.

Posted: **Mon 19 Jun 2023 8:21 am**

Just jumping in because I noticed something missing in the discussion.

Cambium wrote: ↑Sun 18 Jun 2023 3:19 pm But under device list it shows this. It changed from 192.168.1.6 before

And you say it changed to 192.168.4.1 This seems to me - or resembles - the address of the Ecowitt server configured as access point (AP)

In the Device Setting on the gateway you need to switch the tick the Device AP Auto OFF option.
Did you?

Posted: **Mon 19 Jun 2023 11:30 am**

Really appreciate the team work here.

SamiS wrote: ↑Sun 18 Jun 2023 9:06 pm
::ffff: is a reference to ipv6 protocol, and earlier I suggested that you should disable it if possible. But I think that there is more relevant messages on your last logfile:

Just tried that and nada.

SamiS wrote: ↑Sun 18 Jun 2023 9:06 pm These messages show that your station is now definitely sending data to CMX in one minute interval. Cumulus just rejects it, because one or more of necessary sensor data is missing. Does your console show wind, humidity and temperature properly?

Yes console shows correct readings

PaulMy wrote: ↑Mon 19 Jun 2023 12:53 am
I think you need to double check your IP addresses for both the Ecowitt and CMX.

I did through router and thats what it is. As I said, the software reads the data on startup but its just not updating at all. This morning it even logged in the NOAA daily data which is great! It's just the update not working while CMX is open.

PaulMy wrote: ↑Mon 19 Jun 2023 12:53 am
You had a similar issue about 18 months ago and you should review that thread and see if that helps you get it working again viewtopic.php?p=158965#p158965

I remember that and went back to that thread. It was the log interval that time which I tried this time. Another time it was a cumulus ini folder issue, I can't even find that folder now. Hmmm

HansR wrote: ↑Mon 19 Jun 2023 8:21 am
In the Device Setting on the gateway you need to switch the tick the Device AP Auto OFF option.
Did you?

There is no option for that.

Attached new diags after trying some other things.

20230619-072643.txt

Posted: **Tue 20 Jun 2023 11:02 am**

Changed the thread title. So it continues to read the data on start up but station not updating at intervals..

It's picking up the 5 minute intervals the station is recording but only on catch up at start up.. It's just not picking it up in real time.

Any other ideas I can check?

20230620-063528.txt

Posted: **Tue 20 Jun 2023 2:24 pm**

It seems that you have enabled again the autoconfiguration of the gateway. Logfiles have clearly shown that it is failing, so you should keep it off. However it most likely is not the reason for your problems, but not a solution either. It also seems that your station ip has changed from 192.168.1.9 to .8?

I’m quite sure, that if someone just would understand what is behind these strange api call logs, then we could come up with a solution.

Code: Select all

2023-06-20 06:46:28.551 API tag: Source = [::ffff:192.168.1.8]:59688 Input string = ?locationJsEnc
2023-06-20 06:46:28.690 WS Client Connect: ::ffff:192.168.1.8, Total clients: 1
2023-06-20 06:46:28.701 API tag: Output string = {"locationJsEnc":"My Backyard"}
2023-06-20 06:46:32.937 API tag: Processing API Text tag request
2023-06-20 06:46:32.941 API tag: Source = [::ffff:192.168.1.8]:59685 Input string = {"month": <#recordsbegandate format="%M">, "year": <#recordsbegandate format="yyyy">}
2023-06-20 06:46:32.964 API tag: Output string = {"month": 6, "year": 2012}
2023-06-20 06:46:32.972 WS Client Disconnected: ::ffff:192.168.1.8, Total clients: 0

But since we have checked all the usual things, I think that only @mcrossley can help find the cure when he returns from his holiday.

Posted: **Tue 20 Jun 2023 9:01 pm**

SamiS wrote: ↑Tue 20 Jun 2023 2:24 pm It seems that you have enabled again the autoconfiguration of the gateway. Logfiles have clearly shown that it is failing, so you should keep it off. However it most likely is not the reason for your problems, but not a solution either. It also seems that your station ip has changed from 192.168.1.9 to .8?

Sorry, yes, I been trying different things, I unchecked it now.
Yes, the IP changed, I did change it on the WS view too so not an issue. I have to find a way to make it static

SamiS wrote: ↑Tue 20 Jun 2023 2:24 pm I’m quite sure, that if someone just would understand what is behind these strange api call logs, then we could come up with a solution.

Agree.

Looking forward to @mcrossleys help.

Thanks for the effort guys! Really appreciate it.

Posted: **Thu 22 Jun 2023 8:54 pm**

So new thing now the NOAA Data saying High was 62.2°F yesterday but the June log file definitely shows it reaching into the 70s.

CMX seems glitchy. And still not updating as its running.

Jun23log.txt

NOAAMO0623.txt

20230622-164829.txt

Posted: **Fri 23 Jun 2023 4:43 am**

Could you create a CMX logfile with debug and data logging on please.
(try to keep the catch up as short as possible as the issue apparently is not in that phase)

Posted: **Fri 23 Jun 2023 7:57 am**

CMX seems glitchy.

I find it rock solid. I think you have a setup problem.

Posted: **Fri 23 Jun 2023 8:04 am**

Cambium wrote: ↑Mon 19 Jun 2023 11:30 am
HansR wrote: ↑Mon 19 Jun 2023 8:21 am
In the Device Setting on the gateway you need to switch the tick the Device AP Auto OFF option.
Did you?
There is no option for that.

Are you sure you have a GW1100 as here it is

Cumulus Support

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

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: Today.ini reading

Re: CMX reading on start up but station not updating

Re: CMX reading on start up but station not updating

Re: CMX reading on start up but station not updating

Re: CMX reading on start up but station not updating

Re: CMX reading on start up but station not updating

Re: CMX reading on start up but station not updating

Re: Today.ini reading