Sorry about that. I see now that he has added two packages to the requires
section; apparently rather than installing them.
> On Jun 2, 2019, at 8:48 PM, gjr80 wrote:
>
> I am not sure what was done either. However, the setup.py that was included
> in the post is a modified version of the
I am not sure what was done either. However, the setup.py that was included
in the post is a modified version of the WeeWX setup.py, I can only surmise
it was modified and used. Agree 100% that for setup.py you need to manually
install any additional packages, the recommended way to do that is
I’m not so sure he modified anything. The packages need to be installed
manually when using setup.py for installation.
See: http://www.weewx.com/docs/setup.htm
In particular, look at the Install Prerequisites section.
> On Jun 2, 2019, at 8:33 PM, gjr80 wrote:
>
> Hi,
>
> It looks like you
Hi,
It looks like you have modified the WeeWX installer and it has not done
what you want. I cannot help with that but I suggest the easiest way to fix
your requests import error is to manually install the python requests
library. To install requests try (untested):
1. install pip:
$ sudo
you have web server running on port 80
this will help https://github.com/matthewwall/weewx-interceptor
On Sunday, June 2, 2019 at 4:03:37 PM UTC-5, Thomas Chapin wrote:
>
> Hoping someone smarter than I can help...
>
> Like others, I was fried when after 3 months told by Acurite that they
> were
The “today" result works as desired when I am ahead of the UTC date (as I am at
the moment and will be for the next 33 minutes)
[root@moses bin]# date
Mon Jun 3 09:25:10 AEST 2019
[root@moses bin]# /home/weewx/bin/wunderdates3 --epsilon=125 --station
ISYDNEY155 --test --verbose | (head -n 9 ;
Rod,
Thanks again for the added validation of what I saw earlier.
Never minding for now the issues with last week's data, what I am now most
concerned to know is whether there is any point throughout the PRESENT day
(your local time) that the latest wunderdates is showing the wrong results?
Well, it turns out that the East of the UTC date line bug only occurs for the
latest week. (I’d assumed that testing involving requests for the last few days
would show the behaviour, but that turned out to be wrong.)
At the moment, I’m a day ahead of UTC. Here is the output for requests for
Did you read the following post?
https://groups.google.com/forum/#!searchin/weewx-user/smarthub%7Csort:date/weewx-user/0e2E3F7EG7Y/mVv7oUZ1BgAJ
On Sunday, June 2, 2019 at 5:03:37 PM UTC-4, Thomas Chapin wrote:
> Hoping someone smarter than I can help...
>
> Like others, I was fried when
Hoping someone smarter than I can help...
Like others, I was fried when after 3 months told by Acurite that they were
discontinuing smartHub and I could pay another $129 for its replacement...I
read about Weewx and Rasberry Pi.
Finally bought the Pi and got started. Quickly underestimated the
Rod,
I've spent quite a bit of time working on a "cleaner" workaround for the WU
bugs.
But just when I thought I had landed on the "reasonable" approach, I hit a snag.
As a reminder, with the latest approach, all is fine for stations west of the
UTC date line. What I am working on now is a
yes - 8813 was of course a typo in my post, I'm using the default 1883 for
mosquitto which was fine all the time.
The problem was I didn't know what MQTT topic to subscribe Belchertown to.
Using weather/loop made it work. Thanks.
(also - Rich's snippet that sets log_success = false for MQTT is
Ah, now that's interesting. Thanks.
John
WB5THT
On 6/2/2019 11:48 AM, John wrote:
I seem to have found another solution, just disable weewx from
updating the console's clock. It is a setting in the weewx
configuration file.
On Sunday, June 2, 2019 at 8:55:45 AM UTC-5, John Canfield wrote:
What you are seeing is the data from the ISS every 2.5 seconds (Loop Data)
and every 5 minutes you see the archive data which is being written to the
archive database.
On Sunday, June 2, 2019 at 11:35:37 AM UTC-4, gch...@juno.com wrote:
>
> Hi there. I'm a newbie to WeeWx. I have a Davis
I seem to have found another solution, just disable weewx from updating the
console's clock. It is a setting in the weewx configuration file.
On Sunday, June 2, 2019 at 8:55:45 AM UTC-5, John Canfield wrote:
>
> Yes, it does have something to do with timestamps. Boy was I chasing my
> tail for
to stop the LOOP packet being printed every couple seconds: in weewx.conf,
remove weewx.engine.StdPrint from report_services. you almost certainly do not
want to do this while testing and running weewx in foreground, as seeing the
LOOP packets is important to debugging
when you are happy weewx
On Sun, Jun 2, 2019, 8:35 AM gch...@juno.com wrote:
> Hi there. I'm a newbie to WeeWx. I have a Davis Instruments Vantage Pro2.
>
> Firstly, let me say, that it seems to be working perfectly. However ...
>
> Since this is my first time using it, I decided to try "Installation using
>
Hi there. I'm a newbie to WeeWx. I have a Davis Instruments Vantage Pro2.
Firstly, let me say, that it seems to be working perfectly. However ...
Since this is my first time using it, I decided to try "Installation using
setup.py." This says to "Download the source archive weewx-X.Y.Z.tar.gz
Hello,
Looking for Vaisala configuration tool for WXT520 weather transmitter.
Thanks
Andrej
--
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
Yes, it does have something to do with timestamps. Boy was I chasing my
tail for several days - bought a new Davis logger and even bought the
WiFi logger to try. I was on the verge of rebuilding the entire Fitlet
and then stumbled on a solution (a blind chicken finds a piece of corn
once in a
Hallo
ich habe eine Froggit WH3000 und leider ständig Probleme mit WU. Wie kann
ich meine Wetterdaten zb. per Weewx selbst auf eine eigene Website spielen.
Mein Router ist eine FRITZBOX. Wie macht man da das mit dem weiterleiten
der ip Adresse?
mfg
Otmar Schuster
El viernes, 26 de octubre
Hi Gary,
All working thanks to your hints.
It did not like these two lines in graphs.html: -
I dropped the ../ in front and hey presto! I knew it would be something so
obvious that I had not spotted.
Thanks once again.
Ian
On Sun, Jun 2, 2019 at 7:27 AM steeple ian wrote:
>
Gary,
Thanks for your detailed response. It is on my test server which it is no
public facing. I will give it another go using your hints. If I continue to
fail I will install on my public server to let you have a look.
Thanks again,
Ian
On Sun, 2 Jun 2019 at 02:38, gjr80 wrote:
> Ian,
>
>
23 matches
Mail list logo
