Perhaps a bit more detail on what you tried, what worked and what didn't.
Also what were the sources of your information that you tried (URLs etc.)
and where did you get up to?
Susan
On Thursday, April 26, 2018 at 7:55:34 AM UTC+10, Jim Myers wrote:
>
> I have followed steps from two different ob
The protocol used to talk to the console is based on what I could see being
used by the EasyWeatherIP app (the version I looked at was running on my
iMac under MacOS).
If there is similar software that can talk to your console (or even a later
version of the software I used) then there is a cha
Hello Francesco,
The log has identified a bug which has now been fixed and a new file
uploaded to GitHub. Basically I had refactored some of the network access
code (to avoid duplicating the code for both the historic and current
record access) and I had not transferred over a variable initiali
Hello Francesco,
I'm sorry to hear that you are having a problem.
Can you let me know the error messages that you are getting - they should
be in the SYSLOG?
Susan
On Saturday, September 2, 2017 at 12:28:10 AM UTC+10, Francesco Scaramella
wrote:
>
> Hi Susan!! I saw that it was available on G
Hi Tom,
The question I was asking was in the last line: does anyone know the
underlying cause of these broken pipes?
I could do as you suggest but I don't get this error when running weeWx on
my iMac, only on the Raspberry Pi - with the same WiFI network and weather
station. I'm using a standa
This relates to the latest update of my HP1000 (and clone) driver where
I've added in code to read historical records from the weather station.
Configuration: weeWx 3.6.2 running on a Raspberry Pi 3 with the latest
patches.
To read the historical records, the driver makes a number of network
r
I've further updated my driver (in the github repository) to read
historical records from the weather station when weeWx starts up. It uses
te 'genStartupRecords' function to do this.
If the weeWx database is empty (the timestamp passed to the driver is None)
then it will try to read all of the
Hello Bob,
I found the same information (in answer to my Q3) and I've used that. The
HP1000 (and clones) provide different information in various records: form
the NOWRECORD (the current observation data) it provides the UVI directly,
but the HISTORY_DATA record has the UV value but in uW/cm^2.
I'm upgrading my HP1000 (and clone) driver so that it reads all of the
"history" records from the weather station since the last one in the
database (using the 'genStartupRecords' function) when Weewx connects to
the weather station.
I have managed to work out what is required for all of the ava
I've just updated the HP1000/WS1001/other-clones driver in the GIT
repository.
If you have the 'netifaces' Python package installed then the driver will
work out the network broadcast mask for itself. If the package is not
installed then it will work as before.
The actual process is:
- if the
Thanks. First time using github (as a contributor) and first time writing
to a wiki (yep - Luddite First Class: that's me!)
I hope others find this useful.
Susan
>
Hopefully the last request: I have what I believe should be the V1.0 gz
file.
What do I do with it now to make it available?
I've not done this sort of thing before and (at least in this aspect) I'm a
total novice.
Thanks
Susan
Horrendous goof on my part - I hope I have deleted that last post. Somehow
a syntax error crept in but this one should be OK.
I've also updated the version number to 0.3 in both the source file and the
instal file.
Bob - I don't think that the line you mention needs to be changed. As far
as I
Last (I hope) test version before release.
Cleaned up the code, the install process and the variable names etc.
Susan
hp1000.tar.gz
Description: Binary data
Thanks for the advice - I had added the WindGustDir code in (all of 1
line!) but it is trivial to take it out again.
Susan
On Tuesday, February 21, 2017 at 2:01:20 PM UTC+11, mwall wrote:
>
> On Sunday, February 12, 2017 at 10:26:35 PM UTC-5, vk3...@gmail.com wrote:
>>
>> Just noticed that the b
Yep - Spotted that myself on Sunday. Thanks.
Also took the advice about removing the extraneous lines form the
install.py file - much better now. (I copied this from one of the example
files pretty much without understanding the relation ship between these
lines and the code in the main file to
Thanks for the feedback. I'll plead 'guilty' to not bumping the version
number, but I've just downloaded and expanded the file I attached above and
the line in the 'install.py' file that I think drives all this is:
'retry_wait' : 5,
'driver' : 'user.HP1000
Just noticed that the beta of V3.7.0 is available.
In the release notes from Tom he noted that any missing 'windGustDir' is to
be determined by Weewx with this version.
Please note that the last version of my driver (posted above) does assign
'windDir' to 'windGustDir'.
Therefore, is it better fo
The latest version is attached. I *think* this is nearly read to go.
I know that there are some things outstanding (such as the coding style)
but I think I have the functionality sorted, including the network failure
restarts but I'd appreciate it if others can test this out - I've tried
variou
Thanks for the comments and suggestions.
I read the comments on Friday (my time) and then spent today (Sunday)
making some revisions:
- changed the name to HP1000
- added the loop delay parameter (default of 15 seconds) and associated code
- added the default/error checking around reading in the
Thanks for all of the feedback - brilliant!
Mike - I was a bit wary of claiming too much 'copyright' as I must admit
I've "borrowed" quite a bit from your "pmon" extension.
I noticed that using the "wee_extension" install method only put into the
config file the lines in 'config' section of the '
I have attached the tar.gz file that I *think* will work as an extension
but I've only managed to test it on my iMac with Weewx installed via the
'setup.py' method.
Can some mind soul(s) please try this out (in a test environment in case it
generates black holes etc.) before I put it into the re
(Busy weekend - I hope to get a 'first cut' version out shortly)
I'm using the SETUP packet to get the units. At the moment I only read that
packet when the driver start (i.e. if you change anything on the console
you would need to 'bounce' Weewx to pick them up) but in principle there is
nothi
I have written a new driver for my XC0422 weather station (which I believe
is a WS1001 and HP1000 clone). It talks directly to the console via the
WiFi connection using TCP sockets with no packet sniffing or other
interception techniques. I'm looking for some advice on some final
'finishing tou
/etc/systemd/system/weewx.service works well
Susan
Thanks for the information about Red Hat and what is supposed to go where.
I either didn't understand the information that I was reading (more than
likely) or perhaps there are some differences between how Red Had and
Debian/Ubuntu/Raspbian are supposed to be managed.
And yes - I had tried to e
I have tried to use the instructions in the Wiki about using systemd to
manage WeeWx on my Raspbian (2016-11-25) with mixed success.
Using the SysV file in /etc/init.d (with the addition of a dependency on
$network) it worked well but I could not stop or start the daemon
interactively.
When I
Thanks Gary.
I'll check a few things out when I get home but I had not realised that I
needed to provide the 'delta' rain value for each loop packet. I was
passing back the 'daily rain so far' value so I'll look into changing that
and see what happens.
Susan
(Don't know how to edit my post)
The WU time scale for the rain is that it started to rain about 0400 and
finished about 0530.
Susan
(I'm fairly new to Weewx and Python but not programming. I'm trying to go
through the code to see if I can work this out for myself, but this is a
'parallel' line of enquiry.)
I have written a new driver (to access a XC0422/HP1000/WS1001 clone WiFI
workstation over the network) and it seems to
30 matches
Mail list logo
