I included how I ran the command in the second part just incase its 
something I am doing

Ok here is the first part 

test driver

Using configuration file /etc/weewx/weewx.conf
debug level is '1'

IP address obtained from station config
Port number obtained from station config
Battery state filtering ('False') using the default

Interrogating GW2000 at 192.168.1.110:45000

2023-03-22 23:19:02 UTC (1679527142): 'dateTime': '1679527142', 
'daymaxwind': '4.1', '
'64', 'extraTemp1': '20.8', 'inHumidity': '66', 'inTemp': '20.6', 
'lightning_distance'
ning_last_det_time': '1679527051', 'lightning_strike_count': 'None', 
'lightningcount':
ity': '3210.0', 'outHumidity': '96', 'outTemp': '15.1', 'p_dayRain': '2.6', 
'p_monthRa
_rain': 'None', 'p_rainRate': '15.0', 'p_stormRain': '5.1', 'p_weekRain': 
'5.6', 'p_ye
, 'pressure': '944.3', 'relbarometer': '944.3', 'soilMoist1': '44', 
'soilMoist2': '22'
: '68', 'usUnits': '17', 'UV': '0', 'uvradiation': '0.0', 'wh31_ch1_batt': 
'0', 'wh31_
 'wh51_ch1_batt': '1.6', 'wh51_ch1_sig': '4', 'wh51_ch2_batt': '1.6', 
'wh51_ch2_sig':
_batt': '1.5', 'wh51_ch7_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 
'windDir': '240
 '1.7', 'windSpeed': '0.9', 'ws90_batt': '3.2', 'ws90_sig': '4'
2023-03-22 23:19:22 UTC (1679527162): 'dateTime': '1679527162', 
'daymaxwind': '4.1', '
'64', 'extraTemp1': '20.8', 'inHumidity': '66', 'inTemp': '20.6', 
'lightning_distance'
ning_last_det_time': '1679527051', 'lightning_strike_count': '0', 
'lightningcount': '5
': '3080.0', 'outHumidity': '96', 'outTemp': '15.0', 'p_dayRain': '2.6', 
'p_monthRain'
in': '0.0', 'p_rainRate': '15.0', 'p_stormRain': '5.1', 'p_weekRain': 
'5.6', 'p_yearRa
ressure': '944.3', 'relbarometer': '944.3', 'soilMoist1': '44', 
'soilMoist2': '22', 's
8', 'usUnits': '17', 'UV': '0', 'uvradiation': '0.0', 'wh31_ch1_batt': '0', 
'wh31_ch1_
51_ch1_batt': '1.6', 'wh51_ch1_sig': '4', 'wh51_ch2_batt': '1.6', 
'wh51_ch2_sig': '4',
t': '1.5', 'wh51_ch7_sig': '4', 'wh57_batt': '5', 'wh57_sig': '4', 
'windDir': '273', '
3', 'windSpeed': '1.0', 'ws90_batt': '3.2', 'ws90_sig': '4'


second part root@mail:/home# PYTHONPATH=/usr/share/weewx python3 -m 
user.gw1000 --live-data
Using configuration file /etc/weewx/weewx.conf
debug level is '1'

IP address obtained from station config
Port number obtained from station config
Battery state filtering ('False') using the default

Interrogating GW2000 at 192.168.1.110:45000

Displaying data using the WeeWX METRIC unit group.

GW2000 live sensor data (2023-03-22 23:27:59 UTC (1679527679)): 
'absbarometer': '944.500000', 'annual_reset': '0.000000', 'day_reset': 
'0.000000', 'daymaxwind': '14.760000', 'gain0': '1.000000', 'gain1': 
'1.000000', 'gain2': '1.000000', 'gain3': '1.000000', 'gain4': '1.000000', 
'gain5': '1.000000', 'gain6': '1.000000', 'gain7': '1.000000', 'gain8': 
'1.000000', 'gain9': '1.000000', 'gustspeed': '5.040000', 'humid1': 
'64.000000', 'inhumid': '65.000000', 'intemp': '20.700000', 'light': 
'2800.000000', 'lightningcount': '10.000000', 'lightningdettime': 
'22-Mar-2023 23:27', 'lightningdist': '12.000000', 'outhumid': '98.000000', 
'outtemp': '14.500000', 'p_rainday': '0.440000', 'p_rainevent': '0.690000', 
'p_rainmonth': '1.010000', 'p_rainrate': '1.260000', 'p_rainweek': 
'0.740000', 'p_rainyear': '1.010000', 'rain_source': '2.000000', 
'relbarometer': '944.500000', 'soilmoist1': '44.000000', 'soilmoist2': 
'24.000000', 'soilmoist7': '73.000000', 'temp1': '20.800000', 'uv': 
'0.000000', 'uvi': '0.000000', 'week_reset': '0.000000', 'wh31_ch1_batt': 
'0.000000', 'wh31_ch1_sig': '4.000000', 'wh51_ch1_batt': '1.60', 
'wh51_ch1_sig': '4.000000', 'wh51_ch2_batt': '1.60', 'wh51_ch2_sig': 
'4.000000', 'wh51_ch7_batt': '1.50', 'wh51_ch7_sig': '4.000000', 
'wh57_batt': '5.000000', 'wh57_sig': '4.000000', 'winddir': '279.000000', 
'windspeed': '2.160000', 'ws90_batt': '3.20', 'ws90_sig': '4.000000'
On Thursday, March 23, 2023 at 10:07:09 AM UTC+11 gjr80 wrote:

> There are a couple of checks you can do to confirm the gateway device is 
> working and WeeWX is receiving the expected data. The first check is to run 
> the driver directly with the --live-data command line option. This will 
> display the data received by the gateway device before the data is mapped 
> to any WeeWX field. This proves the gateway device is correctly talking to 
> the sensors. The second check is to again run the driver directly but this 
> time with the --test-driver command line option. This will result in the 
> driver emitting loop packets to the console. This again proves the gateway 
> device is talking to the sensors, but also proves the mapping of gateway 
> device data to WeeWX fields. If you like, it shows what data the driver 
> will send to WeeWX. The final check is to run WeeWX directly. This check 
> proves the sensors are communicating with the gateway device, the driver is 
> mapping the gateway device data to WeeWX fields and that WeeWX is receiving 
> the loop packet data from the gateway device driver. When running WeeWX 
> directly you should see rainfall data appearing in WeeWX rain related 
> fields, eg rain and rainRate. If this is not the case then it is unlikely 
> that any WeeWX generated outputs (reports, uploads etc) will contain rain 
> related data.
>
> Running the latter two of above checks are covered in the Gateway driver 
> readme 
> <https://github.com/gjr80/weewx-gw1000/blob/master/README.md#installation-as-a-weewx-driver>.
>  
> Running the driver directly with the --live-data command line option is 
> not covered in the readme, but it is identical to running the driver 
> directly with the --test-driver command line option you just need to 
> substitute the --live-data command line option. You can also use the 
> --help command line option when running the driver directly to display 
> details of each available command line option.
>
> Gary
>
> On Thursday, 23 March 2023 at 05:40:27 UTC+10 [email protected] wrote:
>
>> Hey again Garry. I am trying to work out if this is a weewx or weather34 
>> issue. I can see as mentioned above the rain (or what I believe is the rain 
>> figures) in the loop but when I went to my cwop page after I went home it 
>> shows no rain either and that gets fed from Weewx. The wunderground page 
>> that gets fed directly from the GW2000 shows the rain.
>>
>> I am happy to post any logs etc if that helps or look at anything if you 
>> can point me in that direction.
>>
>> On Wednesday, March 22, 2023 at 12:17:58 PM UTC+11 Peter Peter wrote:
>>
>>> Thanks Gary. I was trying to beat you back here but alas I didnt. I did 
>>> a search on the gw2000 and found some posts and like you suggested here ran 
>>> Weewx directly and can see both the rain in the loop and rec so that parts 
>>> seems ok. I will do a bit more research and see what I can find. I have 
>>> been trying the Weather34 skin/web stuff and thats how I noticed it and 
>>> then went and looked at other stuff. It gives me something to tinker with
>>>
>>> On Wednesday, March 22, 2023 at 11:47:10 AM UTC+11 gjr80 wrote:
>>>
>>>> On Wednesday, 22 March 2023 at 10:05:31 UTC+10 [email protected] wrote:
>>>>
>>>> Hey all.
>>>>
>>>> I have been running Weewx together with my Ecowitt and using the GW1000 
>>>> setup. My base unit is actually a GW2000C_V2.2.3C
>>>>
>>>> When I initially set it up I ran it in simulator mode and all seemed ok
>>>>
>>>> I have been waiting for rain and we have some today but it appears 
>>>> Weewx isnt picking up the rain info. The last update of the rain data in 
>>>> relation the the graphics was over a week ago and thats when I changed 
>>>> from 
>>>> Simulator to real. At that stage I deleted the database and let it start.
>>>>
>>>>  
>>>> What sensor is connected to your GW2000 and reporting rain? I'm 
>>>> guessing it is a WS90? The GW2000 (and other Ecowitt gateway devices) 
>>>> simultaneously support traditional tipping type rain gauges (eg WH40) as 
>>>> well as piezo based WS90. A default install of the Ecowitt Gateway driver 
>>>> will map tipping rain gauge data through to WeeWX. If using a piezo based 
>>>> sensor (eg WS90) then the piezo rain data is passed through to WeeWX, but 
>>>> it must be manually mapped to suitable WeeWX fields. If you do indeed have 
>>>> a WS90 (and no other rain gauge) try adding a [[field_map_extensions]] 
>>>> stanza to [GW1000] in weewx.conf as follows:
>>>>
>>>> [GW1000]
>>>>     ....
>>>>     [[field_map_extensions]]
>>>>         rain = p_rain
>>>>         stormRain = p_rainevent
>>>>         rainRate = p_rainrate
>>>>         dayRain = p_rainday
>>>>         weekRain = p_rainweek
>>>>         monthRain = p_rainmonth
>>>>         yearRain = p_rainyear 
>>>>  
>>>> Stop WeeWX if it is running and try running WeeWX directly 
>>>> <http://weewx.com/docs/usersguide.htm#Running_directly>, you should 
>>>> see rainfall data appearing in the usual WeeWX rain fields. If you do 
>>>> indeed see rainfall data then stop WeeWX and restart it as a daemon.
>>>>
>>>> If you don't have a WS90 or have multiple rain gauges then some 
>>>> additional changes will be required. If this is the case, or the above 
>>>> does 
>>>> not work, post back here.
>>>>  
>>>>
>>>> The only thing I notice in the debug syslog entry that may be related 
>>>> is 
>>>> DEBUG user.gw1000: Unknown field address '7B' detected. Remaining data 
>>>> '00' ignored.
>>>>
>>>>  
>>>> You can safely ignore this; the GW2000 firmware includes an additional 
>>>> field that was not identified in the Ecowitt Gateway API documentation on 
>>>> which the v0.5.0b5 Ecwoitt Gateway driver is based. Consequently v0.5.0b5 
>>>> ignores, but debug logs, the unknown field. Ecowitt has since documented 
>>>> this unknown field as indicating whether or not radiation compensation is 
>>>> applied when reporting outside temperature for WH65/WH69/WS80/WS90 devices.
>>>>  
>>>> Gary
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4e61b691-c44b-4169-bf33-31a6ea10f0c8n%40googlegroups.com.

Reply via email to