Lots of info. Thanks. I have a website domain already and use a
raspberry pi for this. I apparently just can't seem to get it to show
other than on the local network.
On Thursday, January 5, 2023 at 12:13:20 PM UTC-5 pannetron wrote:
> If you host a public website from a personal Linux se
"iams...@gmail.com" writes:
> I've looked into getting a UPS for the Pi, which really appears to be
> nothing more than a $15 ext phone battery, but it seems to me this is a
> weewx problem that should be addressed. Alternately, I can contact Davis to
> see what they say.
> "
It seems, from l
Sometimes the logger inside your Vp2 base station gets into a weird state.
You can try weewx_device —dump to try and recover you missing data, but I
often just end up running —clear and eat the loss See
.https://www.weewx.com/docs/hardware.htm#vantage_notes
On Friday, January 6, 2023 at 6:17:05
If weewx causes the corruption, I sure don't see how. It operates well
within the published API provided by Davis.
Graham is probably right: a power spike from when power comes on is likely
the problem. It's coming through either the VP2 power supply or, more
likely, the Pi's.
Try at least a surg
Would also look at adding a DS1307 or DS3231 RTC Module to RPI zero. This
should maintain the time when the RPI zero loses power.
On Friday, January 6, 2023 at 7:59:16 AM UTC-5 tke...@gmail.com wrote:
> If weewx causes the corruption, I sure don't see how. It operates well
> within the publishe
Are you saying that you have a registered domain name (and that is as far
as you have gone), or that you have a web server that is already
successfully serving other pages to the public internet?
What exactly is that raspberry pi doing? If it is serving web pages, is
it the same machine that
On Friday, January 6, 2023 at 4:59:16 AM UTC-8 Tom Keffer wrote:
> Graham is probably right: a power spike from when power comes on is likely
> the problem. It's coming through either the VP2 power supply or, more
> likely, the Pi's.
>
> Try at least a surge suppressor.
>
We took a crazy set o
Thanks all for the feedback! The engineer in me wants to debug this, but
assuming a UPS does the trick, probably best left alone. I do appreciate
all the effort put into weewx and since the interface is purely through the
api, seems like it must be a logger problem. I am going to take a look at
the
I'm trying to make a new start but this time in the Netherlands.
Bought a WS 2818 and commissioned it without any problems.
A thin client t620 with a small linux mint that works fine and is connected
to the internet.
But the USB dongle won't pair with the console.
Temporarily installed weewx on a
I managed this by modifying Axelle's code above in process_record():
ts = time.localtime()
if ts.tm_hour not in (0,6,12,18) or ts.tm_min != 0:
logdbg("This is not hour to tweet: %d" % ts.tm_hour)
return
That should tweet at 00:00, 06:00, 12:00 and 18:00. I'm not sure if this
Is it possible to use this to post the daily archived values for a given
day? Ideally I'd like to set it to automatically tweet once a day (say at
10am local time) giving the stats for the previous day, e.g.:
06/01/2023: Max temperature: 12.3C, Min temperature: 2.3C, Max wind gust:
35 mph, Tota
Is it possible to use this Twitter extension to post the daily archived
values for a given day? Ideally I'd like to set it to automatically tweet
once a day (say at 10am local time) giving the stats for the previous day,
e.g.:
06/01/2023: Max temperature: 12.3C, Min temperature: 2.3C, Max wind
12 matches
Mail list logo
