[weewx-development] Re: Advice on a new driver and how to make it available

Hey Mike, I was wondering if you every got this working with you WS-2902. I followed this guide: http://landoflinux.com/linux_raspberry_pi_weather_station.html Seems to use the driver Susan developed. I get all the way down to "Checking connectivity to your weather station" but then it fails

[weewx-development] Re: Advice on a new driver and how to make it available

Hey Mike, I was wondering if you ever got your WS-2902 working with weewx? I followed this guide http://landoflinux.com/linux_raspberry_pi_weather_station.html Seems to be the same driver Susan developed. I get all the way down to "Checking connectivity to your weather station" but it always

[weewx-development] Re: Advice on a new driver and how to make it available

I've attached a zenmap log of a port scan. The only port it found open was 45000 with service asmp. The suspected OS (99% accuracy) is NodeMCU firmware. For what it's worth, the hostname is ESP_0BD7E0. I attempted to telnet to the open port telnet 192.168.1.16 45000 Trying 192.168.1.16...

[weewx-development] Re: Advice on a new driver and how to make it available

Ed at Ambient says the ws-2902 doesn't have a communications protocol. ;^) On Monday, September 11, 2017 at 11:49:29 AM UTC-7, Mike Frison wrote: > > > I've tried EasyWeather 3.1 Beta on a Windows PC and it can't find the 2902 > so I just sent email to Ambient support asking for protocol info.

[weewx-development] Re: Advice on a new driver and how to make it available

I've tried EasyWeather 3.1 Beta on a Windows PC and it can't find the 2902 so I just sent email to Ambient support asking for protocol info. I'll let you know what they say. Thanks, Mike

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

Does anyone know whether this can be adapted to the WS-2902/WH2900? It's a similar Fine Offset machine with wireless to console and WiFi to router connections and easy uploads to WU, ambientweather.net, and weathercloud. I have mine sending directly to WU with iptables on the router teeing

[weewx-development] Re: Advice on a new driver and how to make it available

Thanks Susan for the prompt correction of the driver and for the indication received. In fact I had already known the problems of My network. Unfortunately the station is installed in a country location not served by ADSL services and we share between neighbors a same connection to be able to

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

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

Re: [weewx-development] Re: Advice on a new driver and how to make it available

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 >

Re: [weewx-development] Re: Advice on a new driver and how to make it available

You need to store it somewhere, or host the repository on GitHub. Then make a wiki entry that points to its location. There are extensions that use both approaches on the wiki. For example, here's one that's hosted externally , and here's one hosted on GitHub

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

On Sunday, March 12, 2017 at 6:11:49 PM UTC-7, vk3...@gmail.com wrote: > > > Bob - I don't think that the line you mention needs to be changed. As far > as I now it is the name of the class (prefixed by the 'user.' folder which > becomes part of the nested class when it is imported) which does

Re: [weewx-development] Re: Advice on a new driver and how to make it available

Hi Susan, could you please bump the version number consistently? You've got 0.2 in install.py and 0.1 in HP1000.py. And could you bump it to 0.3? I used 0.2 internally for my own station for your last version, just so that I knew what version I was using... At the moment it could easily be

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

On Sunday, February 12, 2017 at 10:26:35 PM UTC-5, vk3...@gmail.com wrote: > > 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

[weewx-development] Re: Advice on a new driver and how to make it available

On Monday, February 20, 2017 at 9:45:55 PM UTC-5, vk3...@gmail.com wrote: > > I think I'm nearly ready to release this but I'd still like a comment on > hwo to best handle the new version (V3.7.0) > susan, you should not have to do anything special for weewx 3.7.0 - there are no changes in 3.7

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

Hi Susan, this is a very minor bug, but I found it while looking through my log files. There's a missing "%" on an strftime string. Yup, I did say minor! Here's the diff to HP1000.py: *** HP1000.py 2017-02-05 02:15:01.0 -0800 --- /usr/share/weewx/user/HP1000.py 2017-02-20

[weewx-development] Re: Advice on a new driver and how to make it available

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' :

[weewx-development] Re: Advice on a new driver and how to make it available

Hi Susan, I can't answer the questions about windDir and co, and I have to admit that I haven't had a chance yet to try out your latest, but I did take a look at it. There were two things that I noticed. The first is that you still have "driver = weewx.user.HP1000DRIVER" in the weewx.conf in

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

Hi Susan, I tried it out. All works fine, except, you have "driver = weewx.user.HP1000DRIVER" in the weewx.conf in your install.py. It should be "driver = user.HP1000". Otherwise, it seems to be working, on my Saturday evening. By the way, there are still some Mac-isms in your tar file,

[weewx-development] Re: Advice on a new driver and how to make it available

On Friday, January 20, 2017 at 12:40:51 AM UTC-5, dr__bob wrote: > > So a try, except bracketing the sendto would help. With a configurable > delay? With a configurable number of retries? But I've really got to > figure out why my cable modem apparently periodically restarts. > weewx is

[weewx-development] Re: Advice on a new driver and how to make it available

On Thursday, January 19, 2017 at 9:19:44 PM UTC-8, mwall wrote: > Also I'll add in the suggestion for the systemctl file. In the 'readme' I >> mention that you should put in references to make sure the network is up >> and running so the Weewx daemon will not cause problems on startup. >> >

[weewx-development] Re: Advice on a new driver and how to make it available

finally, and most importantly,... very nicely done!

[weewx-development] Re: Advice on a new driver and how to make it available

here is a bit more unsolicited advice: - split the code into two classes: HP1000Driver and HP1000Station. the station class should do all the work - that is where the network stuff happens, and that is where the decoding happens. then you can derive a TESTStation from HP1000Station to put

[weewx-development] Re: Advice on a new driver and how to make it available

On Thursday, January 19, 2017 at 11:54:26 PM UTC-5, vk3...@gmail.com wrote: > > 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

[weewx-development] Re: Advice on a new driver and how to make it available

On Thursday, January 19, 2017 at 8:54:26 PM UTC-8, vk3...@gmail.com wrote: > > > Dr Bob (name taken from the old Muppet sketch per chance???), > Indeed! I loved that show! :-) > I can put in a delay (with the delay length driven by an optional > parameter with a default of 5 seconds). I

[weewx-development] Re: Advice on a new driver and how to make it available

perhaps most important items as you make your work available to others: - add a copyright line to the top of readme, install.py, and the driver .py itself: Copyright 2017 Susan email address is optional. - if you want to distribute under a license, then include a file called

[weewx-development] Re: Advice on a new driver and how to make it available

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

[weewx-development] Re: Advice on a new driver and how to make it available

(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

[weewx-development] Re: Advice on a new driver and how to make it available

On Wednesday, January 11, 2017 at 10:01:58 PM UTC-5, vk3...@gmail.com wrote: > > At present the code includes 'testing code' that I've used to confirm that > the various unit transformations all work, and this is controlled by a > single class boolean variable. Is it better to leave this code in