Hmm, something is not right in your database. This will seem a roundabout
way to do things but could you try dropping and rebuilding the daily
summaries before running --update. The sequence of commands will be:
1. stop WeeWX
2. drop the daily summaries:
$ wee_database --drop-daily
3. rebuild
Thanks Gary,
I did as suggested, and received the following:
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database
'archive_mysql'
The update process does not affect archive data, but does alter the
database.
Continue (y/n)? y
Preparing
On Tuesday, 22 September 2020 at 07:52:28 UTC+10 ti...@skybase.net wrote:
> OK I thought the uvradiation field from the sensor corresponded to
> the radiation field in the DB given luminosity was a separate field in
> its own right.
>
No, the GW1000 API provides two UV related obs; one
Hi,
I'm sure the guidance you received was well intentioned but it is nothing
more than papering over the cracks and the issue will come back to bite in
the future. In particular, the next time you upgrade WeeWX you will be back
in the same predicament, better to fix the issue properly. I
Had a look around some existing posts regarding similar issues and with
some guidance from friends smarter than me, ended up changing this line
(1160):
weight = 60.0 * record['interval'] if self.version >= '2.0' else 1.0
to
weight = 60.0 * record['interval'] if self.version is not None and
Hi all,
Aweosmse software, have been using it since about 2015 without issue!
I'm running a Davis Vantage Vue w/usb connected to a raspberry pi.
I have just done a clean install of raspbian and have attempted an install
with 4.1.1 from apt repo using python3 but I'm hitting an error when it
I'm in no hurry. I still have to convert to weewx 4 and latest
Belchertown. Looking forward to it when it's ready.
Ernie
On Sat, Sep 19, 2020 at 6:33 PM Garry A Lockyer
wrote:
> I have not forgotton Ernest or others that may be interested in my
> Belchertown Wx Feeds extension. I have the
Hi Gary,
OK I thought the uvradiation field from the sensor corresponded to
the radiation field in the DB given luminosity was a separate field in
its own right.
I'll go make those changes to see what I get. I'll move the PM2.5
sensor back to ch1 and see if the data appears in the DB.
Hi Graham,
I have my PM sensor on ch2, it was on ch1 until a battery change and it
moved itself and I was too lazy to move it back.
The
[[field_map]]
is the default and I also tried the following...
[[field_map_extensions]]
uvradiation = radiation
pm2_52 = pm2_5
which
Hi,
There are numerous Froggit weather stations, but only a small portion of
those are listed in the supported page of Weewx.
Can I reasonably assume nearly any Froggit weather station will work with
Weewx? (and that it's just there hasn't been any feedback for that station
on the Weewx
ok thanks !
On Friday, September 18, 2020 at 3:55:02 PM UTC+2 ian...@kinnon.org wrote:
> The Froggit is a clone of Ecowitt stuff I believe and its
> the weewx-interceptor in ecowitt mode
> https://github.com/matthewwall/weewx-interceptor
>
> I think there are a couple of threads in this forum
Thanks Gary!
I first tried your new file, but got an error at line 223 --> "s =
smtplib.SMTP(self.smtp_host)". I looked at my old alarm.py file and saw
that it had _SSL after SMTP
"s = smtplib.SMTP_SSL(self.smtp_host)" So I put that in the new code and
then it sent my mail!
Here's the log
Great!
One more question. When I used alarm.py I somehow managed to get only the
"faulty" record to show in the email, not every other reading. Don't
remember how I did this. Could you tell me what to change in the code?
Alarm expression "extraTemp1 > 52 " evaluated True at 2020-09-21 14:40:00
Got a post of the logs? I have alarm.py working on 4.1.1. When I initially
set it up, I wasn't getting emails due to an error on the email side. Once
I resolved that, it's worked great.
On Saturday, September 19, 2020 at 3:57:45 AM UTC-4 pligg...@gmail.com
wrote:
>
> Tried this again today
Tim,
The GW1000 driver does not provide WeeWX field radiation, those folks that
want radiation from th GW1000 are deriving radiation from WeeWX field
luminosity. This is done through the WeeWX StdCalibrate service by placing
an entry in weewx.conf under [StdCalibrate] [[Corrections]] as
Good that it is working. I think alarm.py and alarm_multi.py diverged quite
some time ago and some of the common code should be brought back in sync. I
will have a look through in the coming days and post an updated
alarm-multi.py to hopefully prevent similar situations developing in the
Hello!
Thank you very much. :)
Now your very great Highcharts are working. :)
Regards, Astrid
--
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
Thanks Gary!
I first tried your new file, but got an error at line 223 --> "s =
smtplib.SMTP(self.smtp_host)". I looked at my old alarm.py file and saw
that it had _SSL after SMTP
"s = smtplib.SMTP_SSL(self.smtp_host)" So I put that in the new code and
then it sent my mail!
Here's the log
pm2_52 and wh41_ch2_batt (corresponding battery) and giving good values.
pm2_5 is absent and wh41_ch1_batt is None. is that sensor charged and working
(eg shows fine in WS View)?
and what is your [[field_map]] or [[field_map_extensions]]?
> On 21 Sep 2020, at 5:56 pm, Tim Tuck wrote:
>
> Hi
Hi Gary,
I've just been testing a new install of weewx 4.1.1 and I've found that
the GW1000 driver is not populating the radiation and pm2_5 fields of
the database. I'm viewing the database with DB browser for SQLite.
Running the driver on the command line I see the data being collected...
20 matches
Mail list logo
