Ecowitt Lightning Sensor Config in CMX

[stefanbagnato]

Freddie, makes sense. However, my server is on its own vlan since it also hosted my public facing website. My wired and wireless traffic are also separated, but this is the only issue I've had. I added a route in pfsense for traffic to the wireless network going to the server's IP on port 8998 to be forwarded. Waiting to see if that works.

[dazza1223]

yh that is strange as min not working and my set up more simply then yours?

[freddie]

Freddie, makes sense. However, my server is on its own vlan since it also hosted my public facing website. My wired and wireless traffic are also separated, but this is the only issue I've had. I added a route in pfsense for traffic to the wireless network going to the server's IP on port 8998 to be forwarded. Waiting to see if that works.

You could define a virtual interface for your server for the public facing website and another one for your internal stuff. That way you would have separate IP addresses for external and internal traffic. You could have more relaxed vlan configuration then.

[stefanbagnato]

Freddie, makes sense. However, my server is on its own vlan since it also hosted my public facing website. My wired and wireless traffic are also separated, but this is the only issue I've had. I added a route in pfsense for traffic to the wireless network going to the server's IP on port 8998 to be forwarded. Waiting to see if that works.

You could define a virtual interface for your server for the public facing website and another one for your internal stuff. That way you would have separate IP addresses for external and internal traffic. You could have more relaxed vlan configuration then.

Most definitely. But I have sooo much custom configuration in there, I don't know what I want to mess with anything now haha. The route is working because I can see the connections. But, since I fixed (for now) the false positive strikes issue, I need to wait for more storms to come through to confirm the data makes it to CMX.

[freddie]

The route is working because I can see the connections. But, since I fixed (for now) the false positive strikes issue, I need to wait for more storms to come through to confirm the data makes it to CMX.

Great news you've got the route working. You should be able to confirm receipt of data from your MXdiags file, with entries like this:

Code: Select all

2021-10-05 15:19:44.805 ProcessExtraData: Payload = PASSKEY=<redacted>&stationtype=GW1100A_V2.0.2&dateutc=2021-10-05+15:19:10&tempinf=67.1&humidityin=55&baromrelin=29.672&baromabsin=29.211&temp1f=53.6&tf_ch1=54.7&batt1=0&tf_batt1=1.36&freq=868M&model=GW1100A

[stefanbagnato]

Freddie, do I need to wait for a strike to occur first?

[freddie]

Freddie, do I need to wait for a strike to occur first?

I'm not sure as I don't have a lightning detector. You'll have to look at what is being logged in your MXdiags. I'm pretty sure the GW sends its data every 20 seconds (or whatever you've configured it to be) regardless of strikes - as it is only passing on the data received from the sensors.

There are other users on here with lightning detectors (@mapantz?) so perhaps wait for one of those to reply?

[stefanbagnato]

I'm not sure as I don't have a lightning detector. You'll have to look at what is being logged in your MXdiags. I'm pretty sure the GW sends its data every 20 seconds (or whatever you've configured it to be) regardless of strikes - as it is only passing on the data received from the sensors.

There are other users on here with lightning detectors (@mapantz?) so perhaps wait for one of those to reply?

Yes I'll have to wait for additional responses. A quick look at the latest log file doesn't reveal any "new" entries related to this, though.

[stefanbagnato]

Hm still not working. Had 2 more FPs this morning (way better than the few dozen I was having), and they did not show in CMX. Checked the logs and nothing.

[freddie]

Are you seeing any messages like this in your logs?

Code: Select all

2021-10-05 15:19:44.805 ProcessExtraData: Payload = PASSKEY=<redacted>&stationtype=GW1100A_V2.0.2&dateutc=2021-10-05+15:19:10....

Is the GW your primary weather station, or are you using it just for additional sensors like me?

[stefanbagnato]

Are you seeing any messages like this in your logs?

Code: Select all

2021-10-05 15:19:44.805 ProcessExtraData: Payload = PASSKEY=<redacted>&stationtype=GW1100A_V2.0.2&dateutc=2021-10-05+15:19:10....

Nope, not a single line.

Is the GW your primary weather station, or are you using it just for additional sensors like me?

It's just for the additional lightning sensor. Everything else (besides the Airlink) is on the VP2.

[freddie]

Are you seeing any messages like this in your logs?

Code: Select all

2021-10-05 15:19:44.805 ProcessExtraData: Payload = PASSKEY=<redacted>&stationtype=GW1100A_V2.0.2&dateutc=2021-10-05+15:19:10....

Nope, not a single line.

Is the GW your primary weather station, or are you using it just for additional sensors like me?

It's just for the additional lightning sensor. Everything else (besides the Airlink) is on the VP2.

Looks to me as if your GW can't talk to MX then. Either the config on the GW side is incorrect or there is a networky problem between GW and MX. Something like not being on the same network segment or router firewall rules, etc. etc

[dazza1223]

yh im seeing the same thing in my logs nothing like that line at all

[freddie]

Had a thought last night: I'm assuming you have both made the necessary changes in the MX "Extra Sensor Setting" page in the interface?

ecowitt2.jpg

[dazza1223]

yep all the same as yours

Configure your Ecowitt station, or GW-1000 device to send data to Cumulus and the extra sensor data will be used in addition to your primary stations data

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

You must restart Cumulus after enabling/disabling this feature