Awesome. Just got version 4 installed, hit this same error, and found the
solution in short order.
Thanks!
On Thursday, January 23, 2020 at 5:30:41 PM UTC-8, gjr80 wrote:
>
> Ha, first version worked fine! Second version was fine too. Checked under
> both python 2 and 3.
>
> Gary
>
> On
It was a joke. A play on words as a quote from the Matrix.
--
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 this
Just installed version 4 on my PI 4, and hit this error. Came to google
groups and you'd already fixed it. Awesome.
On Thursday, January 23, 2020 at 5:16:52 PM UTC-8, Thomas Keffer wrote:
>
> Rats. Try this version.
>
> On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer > wrote:
>
>> Try replacing
Ha, first version worked fine! Second version was fine too. Checked under
both python 2 and 3.
Gary
On Friday, 24 January 2020 11:16:52 UTC+10, Thomas Keffer wrote:
>
> Rats. Try this version.
>
> On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer > wrote:
>
>> Try replacing your version of
Updated to db1b41e, problem solved.
Thanks!
Paul
--
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 this
Grumble!
Try this one.
On Wed, Jan 22, 2020 at 7:16 PM gjr80 wrote:
> Hmm, looks like the extra log line is itself producing an error:
>
> Jan 23 13:10:14 stretch40 weewx[1174] INFO weewx.manager: Added record
> 2020-01-23 13:10:00 AEST (1579749000) to database 'weewx.sdb'
> Jan 23 13:10:14
You need to do one of two things...
- put the WS-2902A console behind the WeeWx system so that it can see the WU
packets and actually intercept them. This is done by creating a separate
network hotspot for the WS-2902A to connect to.
- or you need d to do DNS poisoning so that the WS-2902A
Hi Michael,
it is nearly a year now that you had this question, perhaps it is still
interesting for you: As far as I know the wind sensor does not transmit the
UV index. Years ago a seperate UV sensor was available, but it was fragile
and it can't be bought any more.
Before I used weewx, the
Thanks for the input! My impression was that I was attempting to perform
the latter by updating my pihole's /etc/hosts file. I added records to
resolve both `time.windows.com` and `rtupdate.wunderground.com` to the ip
running weewx (those domains are the domains regularly being requested by
Mr. Anderson, what good is an IP address if you are unable to speak [to other
users]?
--
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
Anybody got the IP address? That should work.
On Tuesday, January 21, 2020 at 10:34:18 AM UTC-6, Paul Grunwald wrote:
>
>
> me (pgrunwald change)
> 9:33 AM (less than a minute ago)
> https://notopening.com/site/wxforum.net
>
> Anyone know what is going on?
>
>
--
You received this message
I can confirm that the DNS is resolving to my weewx ip. This leads me to
believe that the problem lies with either my nginx configuration or my
weewx interceptor configuration.
I mentioned that the pi that's running weewx is also running owncloud,
exposing ports 80/443 in an nginx webserver. I
Yes, you are correct. I missed the line where you mentioned changing the host
file on your DNS server. That should have worked. Test that DNS is really being
served by using a different system on the network to ping the WU server name
and see if it resolves to the IP address of the WeeWx
That got it!
Gary
Jan 24 09:10:51 stretch40 weewx[777] INFO weewx.engine: Starting main
packet loop.
Jan 24 09:15:16 stretch40 weewx[777] INFO weewx.manager: Added record 2020-
01-24 09:15:00 AEST (1579821300) to database 'weewx.sdb'
Jan 24 09:15:16 stretch40 weewx[777] INFO weewx.manager:
OK, now we know what went wrong, but we don't know why.
What version of ConfigObj are you using?
*python2 -c "import configobj; print(configobj.__version__)"*
-tk
On Thu, Jan 23, 2020 at 3:22 PM gjr80 wrote:
> That got it!
>
> Gary
>
> Jan 24 09:10:51 stretch40 weewx[777] INFO
5.0.6
gary@stretch40:~/src/weewx$ python2 -c "import configobj;
print(configobj.__version__)"
5.0.6
Gary
On Friday, 24 January 2020 09:37:04 UTC+10, Thomas Keffer wrote:
>
> OK, now we know what went wrong, but we don't know why.
>
> What version of ConfigObj are you using?
>
> *python2 -c
Just as I suspected. The patch that fixed things for configobj v4.7.2,
broke v5.0.6.
Can't help but feel that I'm approaching this all wrong. Got to give it a
deep think.
-tk
On Thu, Jan 23, 2020 at 3:38 PM gjr80 wrote:
> 5.0.6
>
> gary@stretch40:~/src/weewx$ python2 -c "import configobj;
>
Am Donnerstag, 23. Januar 2020 02:55:50 UTC+1 schrieb gjr80:
>
> Hallo Georg,
>
> When i saw *Mittwoch* in your reply I thought then that you should look
> at that thread from early January, it has both English and German, well
> Google-German!
>
> The readonly database issue is a sure sign
95% of what I do is read, and mostly old posts. Seldom on the bleeding
edge.
On Thu, Jan 23, 2020 at 2:54 PM galfert wrote:
> Mr. Anderson, what good is an IP address if you are unable to speak [to
> other users]?
>
> --
> You received this message because you are subscribed to the Google
Try replacing your version of weewx/defaults.py with the attached and
see if that helps.
Bit of a hack. I'll keep searching for something more elegant.
On Thu, Jan 23, 2020 at 3:54 PM Thomas Keffer wrote:
> Just as I suspected. The patch that fixed things for configobj v4.7.2,
> broke v5.0.6.
Rats. Try this version.
On Thu, Jan 23, 2020 at 5:07 PM Thomas Keffer wrote:
> Try replacing your version of weewx/defaults.py with the attached and
> see if that helps.
>
> Bit of a hack. I'll keep searching for something more elegant.
>
> On Thu, Jan 23, 2020 at 3:54 PM Thomas Keffer wrote:
21 matches
Mail list logo
