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

2017-03-20 Thread vk3anz
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: UPDATE: wee_debug: add support for *BSD sysinfo and load information

2017-03-20 Thread Bill Richter
I'm guessing you get notified on the pull requests. I think I have my repository back in sync and the pull request should only touch wee_debug. Tested on Fedora 25 and FreeBSD 11. I put the ENVIRON check at --verbosity=2. On Monday, March 20, 2017 at 5:54:10 AM UTC-7, mwall wrote: > > bill

[weewx-development] Re: UPDATE: wee_debug: add support for *BSD sysinfo and load information

2017-03-20 Thread Bill Richter
Yes, I noticed that as well, as the deprecated % issue. I followed the existing way. I'll give the conversion a try and submit a new pull request. I think I've got my local repository in sync with the master now. I'm an SVN user, struggling with git. On Monday, March 20, 2017 at 5:54:10 AM

[weewx-development] Re: candidate for Standard skin replacement

2017-03-20 Thread Bill Richter
Very cool. Especially the new Sensor status. I sure would like to see Rain total for year [Oct] added under High/Low Rain Total. Though I'm not sure if it should only show on the yearly tab or on each Day, Week, Month and Year. I like the latter option. On Sunday, January 29, 2017 at 7:41:50

Re: [weewx-development] Re: continuation of discussion on wxMesh MQTT

2017-03-20 Thread mwall
On Monday, March 20, 2017 at 11:12:55 AM UTC-4, Wysiwyg wrote: > > also during the weekend I noticed that at reboot, as weewx start before my > ethernet connexion is fully setup, it seems I get a crash (the driver is > not able to connect). > > Is it possible to use this weewx.WeeWxIOError during

Re: [weewx-development] Re: continuation of discussion on wxMesh MQTT

2017-03-20 Thread Wysiwyg
Hi Tom, Thanks for advices ! After a deeper look in python mqtt documentation, it seems that "loop_start()" thing take care to make sure we are still connected to broker. if not, it will reconnect. but it may make sense to check before sending anyway. also during the weekend I noticed that at

[weewx-development] Re: UPDATE: wee_debug: add support for *BSD sysinfo and load information

2017-03-20 Thread mwall
bill, thanks for posting this. we probably should refactor the platform stuff in wee_debug. instead of checking for a specific *platform*, it should check for specific *features*. for example, it can easily spit out standard platform stuff: platform.python_version() platform.platform() platfo

[weewx-development] UPDATE: wee_debug: add support for *BSD sysinfo and load information

2017-03-20 Thread Bill Richter
I've created a pull request for this update. But sadly, I'm having a horrible time getting my local github repository in sync with the weewx master. I can't remember how I did this before and I couldn't find instructions on the weewx site for creating submitting fixes, but I remember a pull r