Re: [weewx-user] Re: New GW1000 Driver available for testing

I had not set it. I saw it mentioned as an option for weewxd. Your link clarified how to use it in the conf file. I've now set it and rebooted, I'll check the log in the morning. On Thursday, August 6, 2020 at 12:45:32 AM UTC-5 gjr80 wrote: > Bill, > > Did you try setting loop_on_init = 1 in

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, Did you try setting loop_on_init = 1 in weewx.conf (http://www.weewx.com/docs/usersguide.htm#General)? The pi zero problem was almost certainly a case of WeeWX starting before the network is up and it’s quite possible this latest problem has the same cause. Setting loop_on_init = 1

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, et al I though this might be specific to the Pi Zero W due to limited processing power. But tonight I had the same issue upon boot with a Pi 4B On Tuesday, August 4, 2020 at 2:24:23 PM UTC-5 Bill Arthur wrote: > Gary, > I'll grab and post the info this evening. > It looks like this

Re: [weewx-user] Re: New GW1000 Driver available for testing

I seem to recall this issue coming up a few times in the past, with mixed results. However, it is worth trying. Gary On Wednesday, 5 August 2020 16:12:25 UTC+10, Graham Eddy wrote: > > at the moment /etc/init.d/weewx says weewx depends on ‘localfs', > ‘remotefs', ‘syslog' and ‘time' for

Re: [weewx-user] Re: New GW1000 Driver available for testing

Yes, if it is a network startup issue as it appears, setting loop_on_init will work. Gary On Wednesday, 5 August 2020 15:33:30 UTC+10, Graham Eddy wrote: > > tried weewxd —loop-on-init? > > > On 5 Aug 2020, at 3:04 pm, Bill Arthur wrote: > > > >

Re: [weewx-user] Re: New GW1000 Driver available for testing

at the moment /etc/init.d/weewx says weewx depends on ‘localfs', ‘remotefs', ‘syslog' and ‘time' for startup. i notice in your syslog that ‘network' is reached *after* weewx starts → maybe we need to add ‘network’ to weewx’s dependencies: * edit /etc/init.d/weewx to add ‘$network’ to end of

Re: [weewx-user] Re: New GW1000 Driver available for testing

tried weewxd —loop-on-init? > On 5 Aug 2020, at 3:04 pm, Bill Arthur wrote: > > Gary, > Here's the log and stanza. As I suspected, wlan0 was not stable until after > WeeWx exited. > Perhaps this is specific to the Pi Zero W. -- You received this message because you are subscribed to the

Re: [weewx-user] Re: New GW1000 Driver available for testing

Google Groups does NOT like a file names syslog. Perhaps syslog.txt will get through. On Tuesday, August 4, 2020 at 2:24:23 PM UTC-5 Bill Arthur wrote: > Gary, > I'll grab and post the info this evening. > It looks like this happens only when booting, as if weewx starts before > the WiFi has

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, Here's the log and stanza. As I suspected, wlan0 was not stable until after WeeWx exited. Perhaps this is specific to the Pi Zero W. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, I'll grab and post the info this evening. It looks like this happens only when booting, as if weewx starts before the WiFi has stabilized. On Tuesday, August 4, 2020 at 3:30:09 AM UTC-5 gjr80 wrote: > Bill, > > For some reason the driver was unable to communicate with (one of) your >

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, For some reason the driver was unable to communicate with (one of) your GW1000(s). Before you get the log could you set debug = 3 in weewx.conf, restart WeeWX then post the log from startup through until the error. Would also help if you could post your [GW1000] stanza from WeeWX.conf.

Re: [weewx-user] Re: New GW1000 Driver available for testing

I hope I'm not making rookie mistakes, but I get the following when doing a fresh install on a Pi-zero. Nothing else is added, just weewx and the GW-1000 driver. I'll pull all the required logs tomorrow, but here is what I'm seeing on a reboot: Aug 4 02:00:48 OpiQ-12 dhcpcd[261]: wlan0:

Re: [weewx-user] Re: New GW1000 Driver available for testing

On Tuesday, 4 August 2020 07:44:37 UTC+10, Paul Anderson wrote: > > So I guess I'm a perdoid control freak > I hope that is not too painful :) The other point of concern is over blindly pasting the full [Accumulator] > stanza into weewx.conf when running as a service. Feel it's really easy for

Re: [weewx-user] Re: New GW1000 Driver available for testing

It's a beautiful day! Verified backed out my silly mod and tis works perfectly: # Options for extension 'GW1000' [GW1000] driver = user.gw1000 [[field_map]] inTemp = intemp inHumidity = inhumid pressure = absbarometer dateTime = datetime extraTemp2

Re: [weewx-user] Re: New GW1000 Driver available for testing

Duh sorry I missed your point Gary! So all I have to do is move my fields from battery field map up to field map in weeex.conf and all will be. Sorry sometimes I can't see the forest for the trees. -- You received this message because you are subscribed to the Google Groups "weewx-user" group.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Gary, So I guess I'm a perdoid control freak but when run as a service it's just to supplement data provided by my normal driver, and other services. I get paranoid over what the service has the ability to map too. Because I only have 4 WH31 , 1 WH 57, and the Gw 1000 itself it is way easier to

Re: [weewx-user] Re: New GW1000 Driver available for testing

Paul, The current field_map behaviour is deliberate, it probably doesn’t help that I have not documented the behaviour yet. The expected behaviour is: 1. If the user specifies nothing the default field map is used. (The default field map can be viewed by running the driver directly with the

Re: [weewx-user] Re: New GW1000 Driver available for testing

Forgot to say that user would need to add [[battery_field_map]] to weewx.conf as well On Mon, Aug 3, 2020 at 12:13 PM Paul R Anderson wrote: > Gary > V 10 as a service is almost 100% there. > However if you add a > [[field_map]] stanza to weewx.config, it gets honored correctly, > however

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary V 10 as a service is almost 100% there. However if you add a [[field_map]] stanza to weewx.config, it gets honored correctly, however with the current logic we don't get a battery_field_map added at all. One way to fix, altho you probably have a more eloquent solution is:

Re: [weewx-user] Re: New GW1000 Driver available for testing

that fixed mappings using gw1000 as service - thanks > On 4 Aug 2020, at 12:41 am, gjr80 wrote: > > I have released v0.1.0b10 on Github > . The changes include: > > - renamed --ip command line option to --ip-address > - reworked field map

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have released v0.1.0b10 on Github . The changes include: - renamed --ip command line option to --ip-address - reworked field map processing, field_map_extensions entries should no longer result in multiple mapping for GW1000 'fields' -

Re: [weewx-user] Re: New GW1000 Driver available for testing

Ok, thank you for the explanation. Good to hear that WeeWX has some controls for non-responding stations and that you were already thinking about utilizing them. On Sunday, August 2, 2020 at 11:41:15 PM UTC-4 gjr80 wrote: > Answers/comments below. > > Gary > > On Monday, 3 August 2020

Re: [weewx-user] Re: New GW1000 Driver available for testing

Answers/comments below. Gary On Monday, 3 August 2020 13:05:31 UTC+10, galfert wrote: > > If you only have one GW1000 is there an advantage to still specifying the > IP address in weewx.conf? Only in as much as it will save half a second during initialisation. > I'm wondering if

Re: [weewx-user] Re: New GW1000 Driver available for testing

If you only have one GW1000 is there an advantage to still specifying the IP address in weewx.conf? I'm wondering if specifying the IP address allows for more timely data access, as the driver doesn't need to find the GW1000. Also once the GW1000 is found by 'auto' setting, how long does it

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Bill, Yes that will cause problems. I have two GW1000 on my network and the when run as a driver/service the ip_address setting has always been honoured in my testing. Running the driver directly is a little different, I thought i had coded the driver such that it would take the IP address

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Gary, I believe I found my problem. Sorry to have caused any confusion. After I ran wee_install I saw the GW1000 stanzas at the end of weewx.conf and I falsely assumed it was configured. I had a ton of problems because I didn't run wee_config. On Saturday, August 1, 2020 at 12:41:19 AM UTC-5

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Gary, I wasn't able to make time to get the logs tonight. I'll try again tomorrow. But I did test running the driver directly. I have three GW-1000s, 192.168.0.104, 204 and 205. Out of ten runs it chooses 204 four times, 205 four times and 104 two times. # Options for extension 'GW1000'

Re: [weewx-user] Re: New GW1000 Driver available for testing

I installed this using wee_extension as described and all seems to be working correctly now - the barometer the didn't display properly in b7 is now displaying properly in graph on Weewx. Thanks Larry On Friday, July 31, 2020 at 3:54:51 AM UTC-5, gjr80 wrote: > > I have released v0.1.0b9

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, Does this occur every time or occasionally? Could you post your [GW1000] stanza, the output from my previous post should contain everything else I need to troubleshoot this issue. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, I doubt a fresh install will change things, either gw1000.py is there and being run or it isn’t. Could you do a few things for me please to try and troubleshoot. Could you run the driver directly with —live-data —debug=3 and post the console and log output. How does temperature on screen

Re: [weewx-user] Re: New GW1000 Driver available for testing

One other thing I noticed Even though I had set the ip_address in weewx.conf it chose to use a different one. This will be hard to troubleshoot unless you have several GW-1000s to work with. On Friday, July 31, 2020 at 2:53:30 PM UTC-5 Bill Arthur wrote: > The first time I set this up (on

Re: [weewx-user] Re: New GW1000 Driver available for testing

The first time I set this up (on a fresh install) I had low barometer and two digit wind direction. Wednesday I did a fresh install (on a Pi Zero) and the barometer and wind direction were OK but the outside temp was about 30 degrees low. I'm going to try another fresh install tonight. On

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have released v0.1.0b9 on Github . The main change is the (I hope) final resolution of the pressures issue. In short, the GW1000 Absolute Pressure is now mapped to WeeWX field pressure with WeeWX to calculate barometer and altimeter via

Re: [weewx-user] Re: New GW1000 Driver available for testing

Sounds like a good plan I like it! Restarted my test system here today with previous version of driver but only mapping pressure. Just checked and barometer, pressure and altimeter between that system and one of the VP2 stations I run still tracking within .1 millibar on all three parameters.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Perfect. I agree. Thank you On Thursday, July 30, 2020 at 9:57:53 PM UTC-4 gjr80 wrote: > To complete the trifecta b9 will (by default) map the GW1000 Absolute > Pressure to WeeWX field pressure and the StdWXCalculate service can then > be used to calculate WeeWX fields barometer and

Re: [weewx-user] Re: New GW1000 Driver available for testing

To complete the trifecta b9 will (by default) map the GW1000 Absolute Pressure to WeeWX field pressure and the StdWXCalculate service can then be used to calculate WeeWX fields barometer and altimeter. GW1000 Relative Pressure will be mapped through (again by default) to WeeWX field

Re: [weewx-user] Re: New GW1000 Driver available for testing

Only had my GW1000 and a few sensors since Last Saturday, just had some minor Thunderstorm activity, so first time seeing WH57 Lighting Detector work. Lightning Last Distance 0.6 miles Lightning Last Time 07/30/2020 06:53:04 PM Lightning Strikes Today 73 Seemed to detect strikes within maybe at

Re: [weewx-user] Re: New GW1000 Driver available for testing

I believe that this is exactly how Meteobridge also works. It just uses Absolute. I think this is probably the best solution. On Thursday, July 30, 2020 at 8:22:46 AM UTC-4 gjr80 wrote: > Looking at the WeeWX fousb driver it actually discards Relative Pressure > and uses Absolute Pressure as

Re: [weewx-user] Re: New GW1000 Driver available for testing

I can see it both ways as to how to deal with data from hardware versus having WeeWX calculate it. Some users that use WeeWX would surely go nuts if what they see on their display consoles does not match what they see in WeeWX. It would certainly make calibration very difficult. Certainly I

Re: [weewx-user] Re: New GW1000 Driver available for testing

Well aware that the manner in which the Rel Offset is determined does not apply the proper standard temperature profile. That's why I said it may have been more appropriate to map it to altimeter. Reasoning was at least it was a static numeric offset, coming closer to altimeter , and certainly not

Re: [weewx-user] Re: New GW1000 Driver available for testing

They won't cause any harm other than taking up room, you will need to manually delete the old ones. Gary On Thursday, 30 July 2020 23:40:22 UTC+10, gary@gmail.com wrote: > > I have reinstall b8 and now have both the old and new rain related entries > in weewx.conf > > >

Re: [weewx-user] Re: New GW1000 Driver available for testing

Same data just different field name. There would be no lasting damage unless you had hourRain, dayRain, weekRain monthRain, yearRain, stormRain or totalRain in you database schema. You would have noticed some temporary errors on pages if you were using tags such as $current.hourRain,

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have reinstall b8 and now have both the old and new rain related entries in weewx.conf [[stormRain]][[hourRain]][[dayRain]][[weekRain]][[monthRain]][[yearRain]][[totalRain]] [[rainevent]][[rainhour]][[rainday]][[rainweek]][[rainmonth]][[rainyear]][[raintotals]] On Thursday, July 30, 2020

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have the incorrect entries and will reinstall. Luckily, my rainfall occurred before installing this morning. On 7/30/2020 7:07 AM, gjr80 wrote: Good, just check that you have [Accumulator] entries for hourRain, dayRain etc and not rainhour, rainday etc. If you don’t download the b8

Re: [weewx-user] Re: New GW1000 Driver available for testing

> > The Customized upload in WU format only includes baromin. It is only when > you use Ecowitt format that you see baromrelin and baromabsin. > Don't know what happened this afternoon, must have been tongue tied switching between Ecowitt and WU. Yes the Relative Pressure out these stations

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, WU expects you to upload Sea Level Pressure. The best that is an equivalence to is Relative pressure if the station has been properly calibrated. The Customized upload in WU format only includes baromin. It is only when you use Ecowitt format that you see baromrelin and baromabsin. On

Re: [weewx-user] Re: New GW1000 Driver available for testing

George Alfert writes: > I disagree. Simply adding a constant offset to Absolute does not give you > Altimeter. I understand your point in that Altimeter is a similar thing > that uses a temperature constant, but Altimeter should be something that is > properly calculated from Absolute using a

Re: [weewx-user] Re: New GW1000 Driver available for testing

Paul, I disagree. Simply adding a constant offset to Absolute does not give you Altimeter. I understand your point in that Altimeter is a similar thing that uses a temperature constant, but Altimeter should be something that is properly calculated from Absolute using a proper formula. I'm sure

Re: [weewx-user] Re: New GW1000 Driver available for testing

Good, just check that you have [Accumulator] entries for hourRain, dayRain etc and not rainhour, rainday etc. If you don’t download the b8 extension package again and re-install. I had an upload issue with the package earlier today. Gary -- You received this message because you are subscribed

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have installed b8 successfully and note that nothing was changed in my weewx.conf except the addition of the extractors. On Thursday, July 30, 2020 at 2:08:46 AM UTC-4 gjr80 wrote: > I have released v0.1.0b8 on Github > which: > > - fixes an

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have released v0.1.0b8 on Github which: - fixes an incorrect mapping of GW1000 field relbarometer that will have resulted in incorrect barometer and altimeter fields in WeeWX - changes default field mappings of GW1000 fields rainhour, rainday,

Re: [weewx-user] Re: New GW1000 Driver available for testing

Thanks for the input Paul, I believe your are correct. As soon as you see Rel Offset being calculated as an altitude only offset it is pretty clear it is altimeter and that means the pressure you are offsetting from must be pressure. I am not sure why I put down barometer, perhaps it was the

Re: [weewx-user] Re: New GW1000 Driver available for testing

Should we map 'altimeter': 'relbarometer' ? Gw1000 produces 2 pressure readings: As defined by Ecowitt Calibration of barometric pressure settings *Absolute Pressure* "Absolute barometric pressure, can be calibrated at manufacturing time by comparing with a

Re: [weewx-user] Re: New GW1000 Driver available for testing

> Not sure why you think ‘uvi’ is mapped to ‘uv’, it is and always has been > mapped to ‘UV’. i misread the code and thought the case was wrong (it isn’t). i blame my spectacles. cheers -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To

Re: [weewx-user] Re: New GW1000 Driver available for testing

I must admit that I only looked at the wview-extended schema when developing the default field map and did not consider weewx.units.obs_group_dict, though it makes sense to use weewx.units.obs_group_dict where possible. Will change the default mapping for the three rain fields as suggested.

Re: [weewx-user] Re: New GW1000 Driver available for testing

i expect my new GW1000 (to augment my vp2) to arrive monday so have started planning… looking at gw1000 driver default_field_map, there seem to be a few mislabelled mappings into wview_extended.schema and weewx.units.obs_group_dict, they should be: gw1000 → weewx rainday → dayRain

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have added a page to the GW1000 driver wiki with details of the battery state information provided by the driver. The details on the page a a combination of details specified in the API, information posted on wxforum.net and anecdotal evidence

Re: [weewx-user] Re: New GW1000 Driver available for testing

I will put a battery state table in the driver wiki today. 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 weewx-user+unsubscr...@googlegroups.com. To view

Re: [weewx-user] Re: New GW1000 Driver available for testing

Battery status on different devices: https://www.wxforum.net/index.php?topic=37373.msg408190#msg408190 Matthias Am Dienstag, 28. Juli 2020 18:34:34 UTC+2 schrieb NanoG5Kite: > > Regarding Evowitt Battery Status. There are new Sensors like the WH 57 > which report the battery status from 0-5

Re: [weewx-user] Re: New GW1000 Driver available for testing

Regarding Evowitt Battery Status. There are new Sensors like the WH 57 which report the battery status from 0-5 (5=fully charged), but former sensors like the 7in1 with 0 or 1 (1=empty, to be replaced asap). There was a useful threat in the wxforum.net telleing which sensors show which kind of

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary First just a note that I was running v0.1.0b6 as a service and my GW1000 lost it's WIFI connection. Actual dropped WIFI connecting by the GW1000. Looking at the log I see that the driver worked perfectly, it logged a connection failure after 3 attempts, but weewx itself kept running so that

Re: [weewx-user] Re: New GW1000 Driver available for testing

My wind results have been corrected. On Tuesday, July 28, 2020 at 9:55:22 AM UTC-4 gjr80 wrote: > Bill, the incorrect wind direction decode likely accounts for your wind > direction discrepancies. Not sure about the pressure issues, as far as I am > aware pressure is being correctly decoded. I

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, the incorrect wind direction decode likely accounts for your wind direction discrepancies. Not sure about the pressure issues, as far as I am aware pressure is being correctly decoded. I will look into it further in the morning. Gary On Monday, 27 July 2020 20:03:01 UTC+10, Bill Arthur

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have released v0.1.0b7 on Github . b7 adds the battery states to the default field map which should see battery states appear in the loop packets. I expect there will still be some naming issues, especially with WH65 and WH32. b7 also fixes a n

Re: [weewx-user] Re: New GW1000 Driver available for testing

Thanks Ian, that confirms the last one. Gary On Tuesday, 28 July 2020 16:41:53 UTC+10, steeple ian wrote: > > Gary, > > This is my output (my GW1000 is 868MHz): - > > Using configuration file /home/weewx/weewx.conf > > Interrogating GW1000 at 192.168.1.234:45000 > > GW1000 frequency: 1 (Unknown)

Re: [weewx-user] Re: New GW1000 Driver available for testing

So with a modification to the parameters section I get: - Using configuration file /home/weewx/weewx.conf Interrogating GW1000 at 192.168.1.234:45000 GW1000 frequency: 1 (868Mhz) GW1000 sensor type: 1 (WH65) GW1000 decoded UTC: 2020-07-28 07:52:28 UTC (1595922748) GW1000 timezone: 39 On Tue,

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, This is my output (my GW1000 is 868MHz): - Using configuration file /home/weewx/weewx.conf Interrogating GW1000 at 192.168.1.234:45000 GW1000 frequency: 1 (Unknown) GW1000 sensor type: 1 (WH65) GW1000 decoded UTC: 2020-07-28 07:37:39 UTC (1595921859) GW1000 timezone: 39 On Tue, 28 Jul

Re: [weewx-user] Re: New GW1000 Driver available for testing

Yes, not surprised, am still working through sensor names and the API to get the code right. Fortunately, this disconnect does not affect the observational data only battery state field names and some of the 'informational' commands such as --system-params. Once I get the battery states into

Re: [weewx-user] Re: New GW1000 Driver available for testing

Thanks, I am guessing 868MHz will be 1 but we shall see. Gary On Tuesday, 28 July 2020 10:58:54 UTC+10, gary@gmail.com wrote: > > This is a 915 MHz unit > > Interrogating GW1000 at 10.10.100.125:45000 > > GW1000 frequency: 2 (Unknown) > GW1000 sensor type: 1 (WH65) > GW1000 decoded UTC:

Re: [weewx-user] Re: New GW1000 Driver available for testing

Though this is not a WH65 I have a GW1000, WS68, WH40, WH32-EP, WH32B On Monday, July 27, 2020 at 8:58:54 PM UTC-4 gary@gmail.com wrote: > This is a 915 MHz unit > > Interrogating GW1000 at 10.10.100.125:45000 > > GW1000 frequency: 2 (Unknown) > GW1000 sensor type: 1 (WH65) > GW1000 decoded

Re: [weewx-user] Re: New GW1000 Driver available for testing

This is a 915 MHz unit Interrogating GW1000 at 10.10.100.125:45000 GW1000 frequency: 2 (Unknown) GW1000 sensor type: 1 (WH65) GW1000 decoded UTC: 2020-07-27 20:57:43 UTC (1595883463) GW1000 timezone: 19 On Monday, July 27, 2020 at 8:53:36 PM UTC-4 gjr80 wrote: > v0.1.0b6 added the

Re: [weewx-user] Re: New GW1000 Driver available for testing

v0.1.0b6 added the --system-params command line option to the driver to display a number of GW1000 system parameters, eg: GW1000 frequency: 0 (433MHz) GW1000 sensor type: 0 (WH24) GW1000 decoded UTC: 2020-07-28 10:31:46 UTC (1595932306) GW1000 timezone: 94 Whilst I know which byte to look at

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill, I will send you the sensor mapping that you need to use later today when I am near my computer. Ian On Mon, 27 Jul 2020 at 11:03, Bill Arthur wrote: > Thanks Gary. > Your instructions worked perfectly. > > I'm still seeing a couple of things. Here are links to two reporting > stations.

Re: [weewx-user] Re: New GW1000 Driver available for testing

Thanks Gary. Your instructions worked perfectly. I'm still seeing a couple of things. Here are links to two reporting stations. They both receive data from the same GW-1000 The -1 station uses the old push method. The -5 station uses the new API method. I'm seeing differences in wind

Re: [weewx-user] Re: New GW1000 Driver available for testing

I have released v0.1.0b6 on Github . A summary of the significant changes can be found against the v0.1.0b6 release on Github. It has not (fully) addressed the issue of some battery states not making their way through to the loop packets,

Re: [weewx-user] Re: New GW1000 Driver available for testing

It´s in process on Github now... better to post there. https://github.com/gjr80/weewx-gw1000/issues/6 Am Sonntag, 26. Juli 2020 14:15:18 UTC+2 schrieb Vetti52: > > That's the output: > root@RaspBee:/usr/share/weewx/user# PYTHONPATH=/usr/share/weewx python3 > -m user.gw1000 --debug=3 --sensors >

Re: [weewx-user] Re: New GW1000 Driver available for testing

Using configuration file /etc/weewx/weewx.conf Interrogating GW1000 at 192.168.100.150:45000 GW1000 live sensor data: absbarometer: 1006.2, datetime: 1595765980, daymaxwind: 8.4, gustspeed: 0.7, inhumid: 76, intemp: 20.7, light: 24226.0, outhumid: 82, outtemp: 19.7, rainday: 10.2, rainevent:

Re: [weewx-user] Re: New GW1000 Driver available for testing

That's the output: root@RaspBee:/usr/share/weewx/user# PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 --debug=3 --sensors Using configuration file /etc/weewx/weewx.conf Interrogating GW1000 at 192.168.100.150:45000 Sensor Status WH65 sensor ID: f9 signal: 0 battery: 4 WS68

Re: [weewx-user] Re: New GW1000 Driver available for testing

Several samples posted on Github seems to be e.g. uv: 9.1 x 10 = 91,9w/m² Matthias Am Sonntag, 26. Juli 2020 10:00:15 UTC+2 schrieb gjr80: > > Can you please issue the following two commands(assuming a setyp.py > install) and post the console output and (WeeWX) log output from each: > > $

Re: [weewx-user] Re: New GW1000 Driver available for testing

Can you please issue the following two commands(assuming a setyp.py install) and post the console output and (WeeWX) log output from each: $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --debug=3 --sensors $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --debug=3 --live-data If possible,

Re: [weewx-user] Re: New GW1000 Driver available for testing

The setting 'radiation': 'solar_radiation', is copied from interceptor.py, which is propagated into radiation in weewx. When changing to gw1000 api driver, the data are lost. So I went back to the interceptor.py. You can see the little gap in the graph during my test of the gw1000 driver:

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hmm, seems GitHub has decided not to notify me of new issues/posts to issues on my own repos. I have noticed a few there now and will work through them IDC. Gary On Sunday, 26 July 2020 16:59:01 UTC+10, gjr80 wrote: > > I don't mind, Github is probably easier for tracking and hopefully keeps

Re: [weewx-user] Re: New GW1000 Driver available for testing

I don't mind, Github is probably easier for tracking and hopefully keeps one problem per issue unlike posts here which tend to grow many heads. All I ask is that some appropriate details of the problem are included (eg an explanation of the problem and a startup debug log extract - a list of

Re: [weewx-user] Re: New GW1000 Driver available for testing

https://github.com/gjr80/weewx-gw1000/issues Am Sonntag, 26. Juli 2020 08:39:19 UTC+2 schrieb NanoG5Kite: > > Is‘t it better to post possible errors on Githup? In addition to Radiation > I‘m also missing rain and current rain rate now. > Will open issues on Github now. > > Am Sonntag, 26. Juli

Re: [weewx-user] Re: New GW1000 Driver available for testing

Is‘t it better to post possible errors on Githup? In addition to Radiation I‘m also missing rain and current rain rate now. Will open issues on Github now. Am Sonntag, 26. Juli 2020 02:13:38 UTC+2 schrieb gjr80: > > Whilst there definitely is nothing in the API for retrieving what WeeWX > knows

Re: [weewx-user] Re: New GW1000 Driver available for testing

Whilst there definitely is nothing in the API for retrieving what WeeWX knows as 'radiation', there is a calibration setting labelled 'SolarRad Gain' in the WS View app (interestingly there is no gain setting for anything to do with 'light', luminosity, illuminance etc so it could be a

Re: [weewx-user] Re: New GW1000 Driver available for testing

Agreed completely :) Gary On Sunday, 26 July 2020 09:37:41 UTC+10, Greg Troxel wrote: > > gjr80 writes: > > > You will notice the highlight on the word radiation (but not the word > > field) in my original post, this was in reference to the WeeWX field > named > > radiation, not to something

Re: [weewx-user] Re: New GW1000 Driver available for testing

gjr80 writes: > You will notice the highlight on the word radiation (but not the word > field) in my original post, this was in reference to the WeeWX field named > radiation, not to something known as 'field radiation'. Sorry, reading in plain text so I did not actually notice that :-) > I

Re: [weewx-user] Re: New GW1000 Driver available for testing

On Sunday, 26 July 2020 08:55:08 UTC+10, Greg Troxel wrote: > > gjr80 writes: > > > Some folks derive field radiation from luminosity though I believe the > > relationship is somewhat complex. > > I'm not at all clear on what labels the various stations use. > > I would use "solar irradiance"

Re: [weewx-user] Re: New GW1000 Driver available for testing

gjr80 writes: > Some folks derive field radiation from luminosity though I believe the > relationship is somewhat complex. I'm not at all clear on what labels the various stations use. I would use "solar irradiance" or less pedantically "solar radiation". The term "field radiation" is

Re: [weewx-user] Re: New GW1000 Driver available for testing

I am not sure if this impacts on the WH65 issue mentioned below but I now have the driver distinguishing whether there is a WH65 or WH24 connected to the GW1000. This will (I hope) have a flow on affect on battery status fields but given the manner in which the API works I don't believe it will

Re: [weewx-user] Re: New GW1000 Driver available for testing

On Sunday, 26 July 2020 00:54:03 UTC+10, Vetti52 wrote: > > When running reconfigure with prompts, there are two changes, that > occured in my case without asking: > group_pressure turns to inHg, and group_speed and group_speed2 turn to > mile_per_hour > and ~2 respectively.You better diff old

Re: [weewx-user] Re: New GW1000 Driver available for testing

When running reconfigure with prompts, there are two changes, that occured in my case without asking: group_pressure turns to inHg, and group_speed and group_speed2 turn to mile_per_hour and ~2 respectively.You better diff old and new version before restarting. In addition, 'radiation':

Re: [weewx-user] Re: New GW1000 Driver available for testing

Bill About not being able to run the driver directly, If you have python 2 on your system, but have installed WeeWX to use python 3 you may not have installed the prerequisites for python 2. If you have a setup.py install and try to run: PYTHONPATH=/home/weewx/bin python -m user.gw1000

Re: [weewx-user] Re: New GW1000 Driver available for testing

That’s exactly what I am seeing. I am going to look at the interceptor map for WH65 and see where things appear to deviate. On Fri, 24 Jul 2020 at 19:43, Bill Arthur wrote: > I started as you and later added a WiFi-less console. I'm not sure where > to look for the WH65 designation. > No, I

Re: [weewx-user] Re: New GW1000 Driver available for testing

I started as you and later added a WiFi-less console. I'm not sure where to look for the WH65 designation. No, I didn't change the map. I was unable to run the driver directly to test, so I just launched it blindly... and it worked. I am seeing an anomaly with pressure, too. I'm looking at the

Re: [weewx-user] Re: New GW1000 Driver available for testing

That is the same array that I am using with gw1000 except I do not have a console. Does this show up as WH65? I have anomaly with the barometer but I cannot understand why. Have you changed the sensor map at all? On Fri, 24 Jul 2020 at 19:17, Bill Arthur wrote: > Hi Ian, > I have the Ambient

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Ian, I have the Ambient Weather WS-2902 array: temperature, rainfall, humidity, wind speed & direction, UV and solar. Indoor and pressure is from the GW-1000 On Friday, July 24, 2020 at 1:07:41 PM UTC-5 steep...@gmail.com wrote: > Hi Bill, > What sensors do you have connected? > > On Fri,

Re: [weewx-user] Re: New GW1000 Driver available for testing

Gary, No need for apologies. I'm glad that I was able to spot these things. And in a small way, I feel like I'm helping improve it for everyone. On Friday, July 24, 2020 at 8:44:57 AM UTC-5 gjr80 wrote: > My apologies all round Bill, a few typos and a wrong assumption about > package installs

Re: [weewx-user] Re: New GW1000 Driver available for testing

Hi Bill, What sensors do you have connected? On Fri, 24 Jul 2020 at 19:06, Bill Arthur wrote: > Ian, > Yes, just the simple Seasons skin for now. I now have 12 hours of data and > it's looking good. > I've compared it to my weather station console and the data all looks > correct. > > On

  1   2   >