Thanks Gary . I had it set to auto in gw1000 . But I did recently set up
router to assign it same ip address so I will make that change in weewx
config now..
I appreciate the work you have done on GW1000 driver .
Larry
On Saturday, March 26, 2022 at 6:12:06 PM UTC-5 gjr80 wrote:
> An
Thanks tke - Yes I had v 0.4.1 so I just updated it to 4.2 .
Larry
On Saturday, March 26, 2022 at 4:01:07 PM UTC-5 tke...@gmail.com wrote:
> Check the version of your gw1000 driver. It's in the comment section near
> the top of the file gw1000.py.
>
> You want v0.4.2. I thin
learn a new skill on how to debug. And
also to make sure I check all devices when working on router or power
failures.
Larry
On Saturday, March 26, 2022 at 3:23:26 PM UTC-5 Larry wrote:
> Vince -
> I found the logs - this is from the logs at the point in time where the
> weew
.
Larry
Mar 23 08:10:17 weewx weewx[531] INFO weewx.manager: Added record
2022-03-23 08:10:00 CDT (1648041000) to database 'weewx.sdb'
Mar 23 08:10:17 weewx weewx[531] INFO weewx.manager: Added record
2022-03-23 08:10:00 CDT (1648041000) to daily summary in 'weewx.sdb'
Mar 23 08:10:19 weewx weewx
Peter this is what I see with that command - so maybe problem is with
driver ?
I will read up on how to get better debug report
Thanks -Larry
pi@weewx:~ $ /etc/init.d/weewx status -1
● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx; generated)
Active
I have weewx running on dedicated raspberry pi zero W and has been very
stable no problems for long time. I am using a Ecowitt GW1002 that uses
GW1000 and I have the gw1000 api driver installed. It was running on
previous raspbian buster .
The last update to Weewx 4.7 really messed everything
My weewx using GW-1000 on Pi Zero W worked fine for years until last
update of Weewx. I couldn't seem to get all the issues figured out so I
just made a fresh install of newest Bullseye lite ( no desktop) and set it
all up for Weewx , Apache2, and the latest GW-1000 driver . I couldnt' get
Done ! I am showing up on the weewx map now .
On Sunday, October 4, 2020 at 3:57:52 PM UTC-5 gjr80 wrote:
> The only requirement of the URL is that it is unique in the station
> registry. So I guess if you are making up an arbitrary URL be creative. WU
> URLs are fine, they are used by
nstall.
> If you don't have -y you get a prompt to install y/n
>
> On Tuesday, 29 September 2020 at 04:54:29 UTC+10 Larry wrote:
>
>> I did a fresh Buster and Weewx install on my Pi Zero W yesterday and it
>> all worked out fine .
>> Only problem I had was with gett
old version was on
Jessie with so many updates , config changes, etc . It is working fine with
my Ecowitt newest api driver.
Larry
On Monday, September 28, 2020 at 2:35:19 AM UTC-5 graha...@gmail.com wrote:
> i’d like to see a total cost figure put on cut & paste errors - it would
>
the
driver.
Larry
On Wednesday, September 23, 2020 at 5:27:03 AM UTC-5 gjr80 wrote:
> Larry,
>
> So I guess the GW1000 driver picked up the GW1000 again? If the WSView app
> doesn't pick p the GW1000 then the driver probably doe snot have much
> chance either. I believe there have be
- not sure what made it crash .
Larry
On Tuesday, September 22, 2020 at 9:33:06 PM UTC-5 Larry wrote:
> I have had three crashes of Weewx on my Raspberry Pi Zero W in past few
> weeks .
> Here is the log I have now - not sure if it is the right one you would
> need to gather any clues.
I have had three crashes of Weewx on my Raspberry Pi Zero W in past few
weeks .
Here is the log I have now - not sure if it is the right one you would need
to gather any clues.
Any help on what I should do is appreciated
Thanks
Larry
sudo tail -f /var/log/syslog
Sep 22 21:23:34 pizerowx
I am not the best Linux user but happy when I can figure out why things
don't work right !
By the way I believe there are other instructions in the wiki for package
with the same issue - maybe it was in the battery sensors wiki section I
saw that.
Thanks
Larry
On Saturday, September 12
I think there is an error in the wiki
or for package installs:
$ cp /etc/weewx/skins/Seasons/current.inc
/*home*/weewx/skins/Seasons/current_orig.inc
should be
or for package installs:
$ cp /etc/weewx/skins/Seasons/current.inc
/*etc*/weewx/skins/Seasons/current_orig.inc
Larry
I think there is an error in the wiki
or for package installs:
$ cp /etc/weewx/skins/Seasons/current.inc
/*home*/weewx/skins/Seasons/current_orig.inc
should be
or for package installs:
$ cp /etc/weewx/skins/Seasons/current.inc
/*etc*/weewx/skins/Seasons/current_orig.inc
Larry
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
Yep, can't believe I missed that! Been fixing too many WOW guide issues ;-0
--
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
User's Guide
> <http://weewx.com/docs/usersguide.htm>.
>
> Gary
>
> On Tuesday, 27 August 2019 08:51:58 UTC+10, Larry Lewis wrote:
>>
>> We moved and installed a new weather station at our new home, when the
>> Davis Vantage Pro2 was connected it all started work
removed and reinstalled Weewx both using pyinstall & apt-get and still
the same, data seems fine so how can I coerce the system to show the dots
as joined lines as they were before?
Thanks,
Larry
--
You received this message because you are subscribed to the Google Groups
"weewx-us
thanks Thomas and Vince for the input. I am still a Linux novice and the
advice is truly appreciated.
On Sunday, January 27, 2019 at 12:22:13 PM UTC-5, vince wrote:
>
> On Saturday, January 26, 2019 at 5:50:58 PM UTC-8, Larry DeBlaay wrote:
>>
>> The following packages have
o apt-get install weewx
>
>
> On 27/01/2019, Larry DeBlaay wrote:
>> The following packages have unmet dependencies:
>> weewx : Depends: python-configobj (>= 4.5) but it is not installable
>> Depends: python-cheetah (>= 2.0) but it is not installable
>>
The following packages have unmet dependencies:
weewx : Depends: python-configobj (>= 4.5) but it is not installable
Depends: python-cheetah (>= 2.0) but it is not installable
Depends: python-imaging (>= 1.1.6) but it is not installable or
python-pil (>= 5.1.0)
On Monday, 10 September 2018 13:22:37 UTC+10, gjr80 wrote:
>
> Um, v3.6.0 was released with the crontab-like report facility back in
> October 2016. The feature has been in every release since.
>
>
Just installed v3.8.2 and have not seen in the conf file or dox ... can yo
point me to the right
very 30 minutes rather than 5 ;-)
Thanks
Larry
--
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.
For
AM UTC-5, rhsch...@gmail.com wrote:
>
> Larry, any tips from Davis support? I'm running into same symptoms,
> albeit with a Belfryboy clone logger.
>
> Bought the logger in Aug 2017 and it's since been working like a champ
> connecting my VP2 6152 (F/W v3.62) with my
I would give Davis a call. Their tech support can be very helpful.
>
> -tk
>
> On Sat, Sep 2, 2017 at 12:39 PM, Larry Walker <pwe...@gmail.com
> > wrote:
>
>> I'm trying to help someone set up their Vantage Pro2 with WeeWx. When I
>> try to TEST the co
I'm trying to help someone set up their Vantage Pro2 with WeeWx. When I
try to TEST the communications with:
minicom -b 19200 -D /dev/ttyUSB0
It connects, but when I type TEST, it says:
SECURED-LOGGER FAILED
In fact, no matter what I type, it says: SECURED-LOGGER FAILED
(This is a new 6510USB
28 matches
Mail list logo
