Davis VP2+GW1000 problem extra sensor

[Shamy]

Hello,
Today I received the GW1000 gate and I have a "small" problem.
My main station is Davis Vantage Pro 2, Ecowitt was supposed to be an extra sensor, but there is a bug because, when connected in Cumulus settings, it does not display this data. If I change the type of station to Ecowitt (HTTP), then the data shows up, but I want Davis to be the main station...

In the extra sensor card, two values are displayed, but they are constant - and wrong - 23.3C and 16.1C (all day, all night - outdoor temp is 2deg.C, besides, I don't have any additional sensors in Davis.

The IP addresses are correct. What am I doing wrong?

Edit: my Cumulus version is 3.22.4 b3215

[Mapantz]

I didn't enable 'Allow Cumulus to configure your Ecowitt gateway for you" and manually set up the gateway to send the data to CMX. Works perfectly for me using that method.

[Shamy]

Thanks for an answer.
I enabled this option because there was just no data. Now I unchecked it, restarted Cumulus, validated the data in the gateway and still the same

[mcrossley]

Enable debug and data logging, then restart CMX. After 10 mins of running post the latest MXdiags file. You can switch off the logging after that

[Shamy]

Okay, I am sending the latest file in attachment

[mcrossley]

Cumulus is not receiving any data from your Ecowitt.

Does your Windows Firewall have an in-bound rule to allow traffic from the Ecowitt to be sent to TCP port 8998 on Windows?

I also notice you have an error in one of your monthly log files...

Code: Select all

Error parsing log file record: Nieprawidłowy format ciągu wejściowego.
LoadRecent: Error at line 3801 of data\gru22log.txt : Nieprawidłowy format ciągu wejściowego.

[Shamy]

You were right, add an exception to this port in the windows firewall and it shows the data (Humidity and Dew point)
But temperature is still 23.3 I guess it's a Davis error, because I only have one sensor. Can it be changed somehow?

[mcrossley]

Now you have data coming through, switch on debug and data logging for 5 mins and post the MXdiags file again.

[mcrossley]

Do you have any extra sensors on your Davis kit?

[Shamy]

Ok, file below

Do you have any extra sensors on your Davis kit?

No, only one main temp. sensor

[mcrossley]

The extra sensor temperature is coming through OK as 36.1°F which is 2.3°C

So, it maybe it is being logged as 10x the value? Which is strange as no one else has reported that as an issue.

OK, mystery solved, your Davis is sending two extra temperature values. 23.3C for sensor #1, and 16.1C for sensor #2. These are overriding the Ecowitt values.

If as you say you do not have these sensors, then I suggest a complete power down of your console - power lead out and batteries out - and see if that fixes it.

[iandrews]

I've just got a GW1100 gateway (Mainly to allow for lightning, and soil temp and moisture) to go alongside my Davis Pro2.

(I have been playing around with Extra sensors recently and a pi running rtl_433 to get some temp / humidity sensors into Cumulus MX, but that's separate to this).

Anyway I have configured the GW1100 to send data to Cumulus, and under extra sensors I have ticked Soil moisture and User Temperature, and can see that data in Cumulus. What I am wondering is (with the Davis Pro as the main station) can I see the temp / humidity of the GW1100 in the extra sensors area. If I do http://192.168.x.y/get_livedata_info the data string returned shows the temp / humidity data in intemp / inhumi so assume in Cumulus if I had my main station type as a Ecowitt that would be the Indoor temp / humidity values, but is there any (planned) functionality in Cumulus to view this under an extra sensor.

[mcrossley]

Not at present, sorry.

[iandrews]

Not at present, sorry.

That's ok.

Just knocked together a powershell script to read the temp / humidity from the GW1100, and then use the Ecowitt HTTP command to put the data into Cumulus as Sensor9 (already using Sensor 1 - 8).

Code: Select all

$responseget=""
$responseput=""
$responseget = try {Invoke-RestMethod -Uri "http://192.168.x.y/get_livedata_info" } catch { $_.Exception.Response }
if ($responseget.psobject.Properties.name -contains "wh25") {
    [decimal]$wh25temp=$responseget.wh25.intemp
    $wh25temp=($wh25temp*1.8)+32
    $wh25hum=$responseget.wh25.inhumi
    $wh25hum=$wh25hum.Substring(0,$wh25hum.Length-1)
    write-host $wh25temp
    write-host $wh25hum
    $body = @{
    'temp9f'=$wh25temp
    'humidity9'=$wh25hum
    }
    $responseput=try {Invoke-WebRequest http://192.168.x.z:8998/station/ecowittextra -Method POST -Body $body } catch { $_.Exception.Response }
    if ($responseput.StatusCode -Eq "200") {
        write-host "Putting Data was OK"
    } else {
        write-host "Error Putting Data"
    }
#    Start-Sleep -s 5 
} else {
    write-host "Error Getting Data"
}

Maybe needs a bit more work such as writing to a log file, and then set up in a loop with say a 60 sec wait time, or just need to schedule it to run say every 1 or 2 mins.