[weewx-user] Re: WMR300 testing LAST Driver

Hi everybody , I have installed a Weewx on a Raspbian Stretch last version. Raspberry pi used is B2.0 with BCM2835 rev. 000e. The station is WMR300 . It took me a long time to find this driver 0.19rc5 . With 0.19rc3 was working for around 1.5 2 hours and exiting without error in syslog. Now

[weewx-user] Re: WMR300 testing LAST Driver

I have 10 days uptime with this driver version. I think all is stable now :-D Thank's a lot for your work. El sábado, 17 de marzo de 2018, 13:53:04 (UTC+1), Ruben Navarro Huedo escribió: > > I am trying it now. > > I will tell result in some hours. > > Mar 17 13:51:31 MeteoElche weewx[9026]: wm

[weewx-user] Re: WMR300 testing LAST Driver

I am trying it now. I will tell result in some hours. Mar 17 13:51:31 MeteoElche weewx[9026]: wmr300: content: d2 80 00 3f ee ee ee 00 0a 00 e9 00 00 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 20 04 7f 7f 7f 7f 7f 7f 7f 00 08 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f fd 7f ff 7f ff 7f ff

[weewx-user] Re: WMR300 testing LAST Driver

Following up on my last post, I decided to bump the failure rate and ran raid-check every day. This revealed gaps up to 2 minutes between heartbeats, which confirmed the diagnosis, so I have added the code to send a restart and it seems to be keeping it alive. I have attached what I hope is a w

[weewx-user] Re: WMR300 testing LAST Driver

OK, Finally another hang-up. 3 weeks to the day after the previous one. As I suspected, it is due to the WMR300 console behaving as if it has not seen the heartbeat packets and so stops transmitting. The code then is stuck forever in genLooopPackets waiting for the next packet, which never come

[weewx-user] Re: WMR300 testing LAST Driver

It is set to 5 minutes both values. I cleared the console log but stability problem continues with RC5. El domingo, 11 de febrero de 2018, 7:01:59 (UTC+1), Cameron D escribió: > > Hello Ruben, > I cannot see where you have already said this, but can you report the > logging frequency of the WMR30

[weewx-user] Re: WMR300 testing LAST Driver

Two problems with RC5 so far... 1. There is still something wrong in the history code, with more bogus history records being reported.. I have not yet worked out if it was a fault in my original code or in the recent adaptation. Even though I am saving every minute, I still have to wait about

[weewx-user] Re: WMR300 testing LAST Driver

> > > Hi Matthew, > 1. I might load RC5 onto my system and see how it behaves, ... > Traps for young players (and not so young) - I spent yesterday mulling over weird debug logs only to finally discover it was due to syslog rate-limiting always discarding the critical part. -- You received th

[weewx-user] Re: WMR300 testing LAST Driver

On Sunday, 11 February 2018 16:01:59 UTC+10, Cameron D wrote: > > > There is an odd section at the start of the console's history log, where > it has saved data from before the clock was set up. > And I'll try mine as well, because I have just noticed that my system > also has some junk in th

[weewx-user] Re: WMR300 testing LAST Driver

Hello Ruben, I cannot see where you have already said this, but can you report the logging frequency of the WMR300 console and the archive interval you have set in weewx. >From the logs it look like WMR300 is set to 5 minutes. There is an odd section at the start of the console's history log, wh

[weewx-user] Re: WMR300 testing LAST Driver

1.- NO...all information is here. I can do all necessary tests for you. El sábado, 10 de febrero de 2018, 15:36:05 (UTC+1), Cameron D escribió: > > > > On Saturday, 10 February 2018 22:58:32 UTC+10, mwall wrote: >> >> On Saturday, February 10, 2018 at 3:26:22 AM UTC-5, Cameron D wrote: >>> >>> Hi

[weewx-user] Re: WMR300 testing LAST Driver

On Saturday, 10 February 2018 22:58:32 UTC+10, mwall wrote: > > On Saturday, February 10, 2018 at 3:26:22 AM UTC-5, Cameron D wrote: >> >> Hi all, >> I am back after a long period of doing other things and have started >> merging Matthew's latest code into my version of the driver, which >> use

[weewx-user] Re: WMR300 testing LAST Driver

On Saturday, February 10, 2018 at 3:26:22 AM UTC-5, Cameron D wrote: > > Hi all, > I am back after a long period of doing other things and have started > merging Matthew's latest code into my version of the driver, which > uses only PyUSB v1 > I am looking to create a unified version that works w

[weewx-user] Re: WMR300 testing LAST Driver

Hi all, I am back after a long period of doing other things and have started merging Matthew's latest code into my version of the driver, which uses only PyUSB v1 I am looking to create a unified version that works with both V0 and V1 APIs. My system has been running without crashing for about

[weewx-user] Re: WMR300 testing LAST Driver

After 54 hours RC5 Crashed again :-( With NO message on syslog. El jueves, 8 de febrero de 2018, 12:34:57 (UTC+1), Ruben Navarro Huedo escribió: > > I don't know what changed, but it is running now 48 hours with RC5 and all > is fine. > > El martes, 6 de febrero de 2018, 13:52:29 (UTC+1), mwall

[weewx-user] Re: WMR300 testing LAST Driver

I don't know what changed, but it is running now 48 hours with RC5 and all is fine. El martes, 6 de febrero de 2018, 13:52:29 (UTC+1), mwall escribió: > > On Tuesday, February 6, 2018 at 7:29:04 AM UTC-5, Ruben Navarro Huedo > wrote: >> >> Mismas versiones que yo pero en mi caso no es estable. >

[weewx-user] Re: WMR300 testing LAST Driver

You have my station at your disposal. If interested you can access my rasp using SSH. Send me personal mail and i will send you details. runahue at gmail.com El martes, 6 de febrero de 2018, 13:52:29 (UTC+1), mwall escribió: > > On Tuesday, February 6, 2018 at 7:29:04 AM UTC-5, Ruben Navarro Hu

[weewx-user] Re: WMR300 testing LAST Driver

On Tuesday, February 6, 2018 at 7:29:04 AM UTC-5, Ruben Navarro Huedo wrote: > > Mismas versiones que yo pero en mi caso no es estable. > >> >>> ruben, thank you for checking the versions. i think we have the usb instabilities under control no

[weewx-user] Re: WMR300 testing LAST Driver

Gracias. Mismas versiones que yo pero en mi caso no es estable. El martes, 6 de febrero de 2018, 9:02:44 (UTC+1), Alberto Sánchez escribió: > > Linux 4.4.50-v7+ > > > > pi@raspberrypi:~ $ dpkg -l | grep usb > > ii libusb-0.1-4:armhf2:0.1.12-25 >

[weewx-user] Re: WMR300 testing LAST Driver

Linux 4.4.50-v7+ pi@raspberrypi:~ $ dpkg -l | grep usb ii libusb-0.1-4:armhf2:0.1.12-25 armhfuserspace USB programming library ii libusb-1.0-0:armhf2:1.0.19-1 armhfusersp

[weewx-user] Re: WMR300 testing LAST Driver

¿Que version de kernel Alberto y de librerias usb? uname -a para el kernel y dpkg -l | grep usb para las librerias El lunes, 5 de febrero de 2018, 19:17:37 (UTC+1), Alberto Sánchez escribió: > > Hi mwall, > > 12 days testing RC5 without errors. > > Thanks > > http://www.elurerauntsi.com/weather

[weewx-user] Re: WMR300 testing LAST Driver

Hi mwall, 12 days testing RC5 without errors. Thanks http://www.elurerauntsi.com/weather/index.html -- 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 weewx-user+u

[weewx-user] Re: WMR300 testing LAST Driver

i can't see anything on the log. Last i can see is: Jan 25 01:19:14 MeteoElche wpa_supplicant[382]: wlan0: WPA: Group rekeying completed with 00:0c:42:bc:80:94 [GTK=CCMP] Jan 25 01:20:14 MeteoElche weewx[6486]: manager: Added record 2018-01-25 01:20:00 CET (1516839600) to database 'weewx.sdb' J

[weewx-user] Re: WMR300 testing LAST Driver

0.18 is "stable" version for me. I have had very long uptime with this version and kernel 4.4.50-v7+ Using last kernel (4.9.*) raspberry freezes completly after some hours. i will try search for the crash on the log. pi@MeteoElche:/usr/share/weewx/weewx/drivers $ dpkg -l | grep usb ii libusb-0.

[weewx-user] Re: WMR300 testing LAST Driver

On Thursday, January 25, 2018 at 2:01:50 PM UTC-5, Ruben Navarro Huedo wrote: > > Testing last RC and after some hours it crashes :-( > Returning to Stable driver version and all fine. > thank you for the feedback, but could you add a little bit more information so i can actually do something ab

[weewx-user] Re: WMR300 testing LAST Driver

Testing last RC and after some hours it crashes :-( Returning to Stable driver version and all fine. -- 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 weewx-user+un

[weewx-user] Re: WMR300 testing LAST Driver

No i am not doing it. I will try and will tell you the result. El miércoles, 24 de enero de 2018, 15:25:24 (UTC+1), sina...@gmail.com escribió: > > Asking you twice, could you upload your data to wunderground with > rapidfire feature. If you are already doing give me id please -- You rece

[weewx-user] Re: WMR300 testing LAST Driver

Jan 24 10:43:00 raspberrypi weewx[875]: wmr300: catchup complete: count=0 last_index=6576 latest_index=6577 Jan 24 10:43:01 raspberrypi weewx[875]: wmr300: dump history Jan 24 10:43:01 raspberrypi weewx[875]: wmr300: reading records since 2018-01-24 10:43:01 CET (1516786981) (last_index=6576 late

[weewx-user] Re: WMR300 testing LAST Driver

Asking you twice, could you upload your data to wunderground with rapidfire feature. If you are already doing give me id please -- 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

[weewx-user] Re: WMR300 testing LAST Driver

Testing Running 1:30 hours fine. El miércoles, 24 de enero de 2018, 6:12:18 (UTC+1), mwall escribió: > > On Tuesday, January 23, 2018 at 2:13:07 PM UTC-5, Ruben Navarro Huedo > wrote: >> >> >> Again "LOOP" and shutdown :-( >> > > ruben, > > please try v0.19rc5 > > > https://raw.githubusercon

[weewx-user] Re: WMR300 testing LAST Driver

On Tuesday, January 23, 2018 at 2:13:07 PM UTC-5, Ruben Navarro Huedo wrote: > > > Again "LOOP" and shutdown :-( > ruben, please try v0.19rc5 https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py m -- You received this message because you are subscribed to the Goog

[weewx-user] Re: WMR300 testing LAST Driver

Again "LOOP" and shutdown :-( Jan 22 16:31:18 MeteoElche weewx[15491]: wmr300: reading records since 2018-01-22 16:31:18 CET (1516635078) (last_index=21390 latest_index=21391) Jan 22 16:31:18 MeteoElche weewx[15491]: wmr300: catchup complete: count=0 last_index=21390 latest_index=21391 Jan 22 1

[weewx-user] Re: WMR300 testing LAST Driver

hey, can you upload to wunderground with rapidfire? Im too far from my wmr300 I cant remote control and give me wu ıd please, thanks a lot 22 Ocak 2018 Pazartesi 14:48:27 UTC+3 tarihinde Ruben Navarro Huedo yazdı: > > Hello: > > Testing last WMR300 driver: > > Jan 22 12:45:42 MeteoElche weewx[150

[weewx-user] Re: WMR300 testing LAST Driver

Now is running fine with no modification: Jan 23 13:20:52 MeteoElche weewx[16384]: restx: WeatherCloud: service version is 0.10 Jan 23 13:20:52 MeteoElche weewx[16384]: restx: WeatherCloud: Data will be uploaded for id=82ffe1c4671ee036 Jan 23 13:20:52 MeteoElche weewx[16384]: engine: Starting up

[weewx-user] Re: WMR300 testing LAST Driver

On Monday, January 22, 2018 at 10:31:05 AM UTC-5, Ruben Navarro Huedo wrote: > > A lot of thank's to you. > It has started but i think we have a loop: > not an infinite loop. but your hardware is not responding the way other hardware has responded. please post the entire log from the time that

[weewx-user] Re: WMR300 testing LAST Driver

A lot of thank's to you. It has started but i think we have a loop: Jan 22 16:30:03 MeteoElche weewx[15491]: wmr300: reading records since 2018-01-22 16:30:03 CET (1516635003) (last_index=21390 latest_index=21391) Jan 22 16:30:03 MeteoElche weewx[15491]: wmr300: catchup complete: count=0 last_in

[weewx-user] Re: WMR300 testing LAST Driver

On Monday, January 22, 2018 at 6:48:27 AM UTC-5, Ruben Navarro Huedo wrote: > > Hello: > > Testing last WMR300 driver: > > Jan 22 12:45:42 MeteoElche weewx[1500]: wmr300: dump history > Jan 22 12:45:42 MeteoElche weewx[1500]: wmr300: reading records since > 2018-01-22 12:45:42 CET (1516621542) (