New HP2551 Setup

[water01]

This is driving me nuts!!. New HP2551 weather station installed and talking great to the panel.

Panel is WiFi attached to local network on 192.168.1.120. Data is streaming to Ecowitt.net since 17.00 on the 20/04/24. and the Custom server is pointing at 192.168.1.121 /station/ecowitt/ on port 8998 using 16 sec as the interval.

Right Cumulusmx (decided to use the Beta build on MX 4 (B4020)) set up on a Windows 11 PC ethernet attached to the same network(192.168.1.121).

Thought (and I still think!!) I had everything set up right, but MX starts up and runs and then data stops!! Arrrgh!!

MXDiags with debug and data logging attached, can anyone see what I have done wrong?

Also I have set the start date to 20/04/2024 and put the API and App key in with the MAC code but it will not pick up data from 20/04?

[HansR]

I see :

Code: Select all

2024-04-24 21:57:14.999 Ecowitt Gateway Custom Server config: Server=192.168.1.121, Port=8998, Path=/station/ecowitt, Interval=15, Protocol=Ecowitt, Enabled=1

and later:

Code: Select all

2024-04-24 21:57:16.970 WS Client Connect: ::ffff:192.168.1.121, Total clients: 1

2024-04-24 21:58:13.457 WS Client Connect: ::ffff:192.168.1.121, Total clients: 1
2024-04-24 21:58:13.459 WS Client Disconnected: ::ffff:192.168.1.121, Total clients: 1

Some IPv4 / IPv6 mix?

[water01]

Could be but how do you stop it using Ipv6. Switched the protocol off on the Network adapter which seemed to me to be the obvious place but it made no difference, still getting those weird IP ffff bits added to the IP address.

I will check the router.

[broadstairs]

Searching I found this

It’s IPv4 expressed through IPv6 so that the application only needs to support one IP stack.

Being able to reference IPv4 addresses through IPv6 notation means I can work on getting IPv6 support really solid in my application, and not have to worry about duplicating effort.

These days some distributions disable IPv4 compatibility by default (e.g. Debian), and also Windows does this by default. To accommodate this as a programmer you should bind two sockets: one IPv4 socket, and one IPv6 socket with the IPV6_V6ONLY flag (which forces it to bind IPv6–only with no IPv4 compatibility, no matter the state of /proc/sys/net/ipv6/bindv6only).

so I'm guessing CMX the culprit here. Perhaps checking the state of that /proc/sys/net/ipv6/bindv6only might give some clues. Maybe Mark can enlighten us?

Stuart

[HansR]

so I'm guessing CMX the culprit here. Perhaps checking the state of that /proc/sys/net/ipv6/bindv6only might give some clues. Maybe Mark can enlighten us?

I guess so. There has been an issue as a result of which Mark forced the connection to be IPv4.
He may have missed one or two

[SamiS]

When browsing through the logfile, I see no evidence that CMX has received any data from the station (192.168.1.120) at all. So maybe you have not allowed CMX to listen inbound connections in Windows Firewall.

[mcrossley]

I see :

Code: Select all

2024-04-24 21:57:14.999 Ecowitt Gateway Custom Server config: Server=192.168.1.121, Port=8998, Path=/station/ecowitt, Interval=15, Protocol=Ecowitt, Enabled=1

and later:

Code: Select all

2024-04-24 21:57:16.970 WS Client Connect: ::ffff:192.168.1.121, Total clients: 1

2024-04-24 21:58:13.457 WS Client Connect: ::ffff:192.168.1.121, Total clients: 1
2024-04-24 21:58:13.459 WS Client Disconnected: ::ffff:192.168.1.121, Total clients: 1

Some IPv4 / IPv6 mix?

Red herring I think, that is the browser client connecting to the Dashboard - that does have IPv6 enabled.

[mcrossley]

Maybe try switching on debug and data logging, but I suspect it will just show that the data stops coming in.

Wasn't there somebody else having issues with the data stopping being sent from the station? But I think that was Ecowitt saying the binary (telnet) API wasn't supported on that station, despite it being advertised as supporting it and it being implemented.

[SamiS]

Maybe try switching on debug and data logging, but I suspect it will just show that the data stops coming in.

Do I miss something when not seeing data coming in at all except catch-up from cloud?

[HansR]

@water01: You have

Code: Select all

/station/ecowitt/

defined as the custom server. Is the last slash necessary? I don't have that in my configuration. Shouldn't that be

Code: Select all

/station/ecowitt

Mmm.... the logfile clearly says Path=/station/ecowitt so It does not look like that is a problem.

[freddie]

Maybe try switching on debug and data logging, but I suspect it will just show that the data stops coming in.

Do I miss something when not seeing data coming in at all except catch-up from cloud?

Data from cloud, but no data from station. Implies something amiss with the console API functionality, as MX can reach the internet for the cloud data so must have network access.

[SamiS]

Maybe try switching on debug and data logging, but I suspect it will just show that the data stops coming in.

Do I miss something when not seeing data coming in at all except catch-up from cloud?

Data from cloud, but no data from station. Implies something amiss with the console API functionality, as MX can reach the internet for the cloud data so must have network access.

Yeah, but as I said earlier, inbound connections to application must be specifically allowed in firewall. But windows does not block applications from connecting to internet. So if incoming data is missing, first check the firewall. However I do not know exactly how services are presented on firewall configuration, since I do not yet have W11 on my hands.

[mcrossley]

Yeah, but as I said earlier, inbound connections to application must be specifically allowed in firewall. But windows does not block applications from connecting to internet. So if incoming data is missing, first check the firewall. However I do not know exactly how services are presented on firewall configuration, since I do not yet have W11 on my hands.

This. Add in in-bound TCP rule on port 8998.

[freddie]

Yeah, but as I said earlier, inbound connections to application must be specifically allowed in firewall. But windows does not block applications from connecting to internet. So if incoming data is missing, first check the firewall. However I do not know exactly how services are presented on firewall configuration, since I do not yet have W11 on my hands.

This. Add in in-bound TCP rule on port 8998.

Oh, I thought MX pulled the data from the console. Apologies for misunderstanding.

[SamiS]

Oh, I thought MX pulled the data from the console. Apologies for misunderstanding.

No worries, easy to mix up, since the station type HTTP Ecowitt is a passive listener (configured as custom server upload on the console), but on the other hand when using station type Ecowitt Local API, then CMX is actively polling the station/gateway.