i will for sure :)
On Tuesday, January 17, 2017 at 12:04:46 PM UTC+7, Andrew Milner wrote: > > Marc - if it freezes again you should post a new log - especially since > you have now made changes to both the forecast module (which should > eliminate forecast related error messages) and also to syslog.conf (which > hopefully removes even more logged messages). We don't want to be looking > at the wrong log for the current situation!! > > > > On Tuesday, 17 January 2017 06:33:46 UTC+2, Marc Aubry wrote: > >> Yes i did. >> Wait and see >> So far so good >> thanks >> >> >> On Tuesday, January 17, 2017 at 10:38:36 AM UTC+7, Andrew Milner wrote: >>> >>> Yes, that's what I was referring to ..... >>> >>> Have you tried amending the syslog.conf as I suggested in previous >>> posting to see if that is causing your weewx to freeze? >>> >>> >>> >>> On Tuesday, 17 January 2017 05:26:20 UTC+2, Marc Aubry wrote: >>> >>>> Hi andrew >>>> are your referring to this forecast error? >>>> >>>> Jan 16 22:40:27 weatherstation weewx[645]: forecast: OWMThread: OWM: >>>> forecast failure: global name 'periods' is not defined >>>> Jan 16 22:40:27 weatherstation weewx[645]: File >>>> "/home/weewx/bin/user/forecas .py", line 1173, in do_forecast >>>> >>>> I do not know where it' is coming from... >>>> My forecast install is standard as described in the forecast >>>> instrucrion. >>>> >>>> >>>> >>>> On Monday, January 16, 2017 at 6:37:29 PM UTC+7, Andrew Milner wrote: >>>>> >>>>> PS - in case you are unaware there are errors in the log connected >>>>> to the forecast module and forecast page ..... don't think they are a >>>>> direct cause of your problem though. >>>>> >>>>> >>>>> >>>>> On Monday, 16 January 2017 13:08:37 UTC+2, Marc Aubry wrote: >>>>> >>>>>> Hi >>>>>> The weewx has just stop reporting and i did a lsusb command and it >>>>>> look the same then before it stop reporting. >>>>>> so it is not a problem of usb port changing name or order. >>>>>> >>>>>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. >>>>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >>>>>> SMSC9512/9514 Fast Ethernet Adapter >>>>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>>> >>>>>> >>>>>> >>>>>> On Monday, January 16, 2017 at 9:48:58 AM UTC+7, Marc Aubry wrote: >>>>>>> >>>>>>> Hi, >>>>>>> Thanks for this info >>>>>>> i have listed the usb devices with lsusb >>>>>>> >>>>>>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. >>>>>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >>>>>>> SMSC9512/9514 Fast Ethernet Adapter >>>>>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>>>> >>>>>>> I guess that my weather station is Device 004: ID 10c4:8468 >>>>>>> I will wait the next time the weewx stop reporting to check if the >>>>>>> device number has changed. >>>>>>> I check in my weewx.conf file and i have no such thing as "device >>>>>>> link" i just have the following lines referring to the driver i'm using: >>>>>>> [WH23xx] >>>>>>> # This section is for Fine Offset WH23xx stations >>>>>>> # The model name such as Tycon, or TP2700 >>>>>>> model = WH2310 >>>>>>> # The driver to use >>>>>>> driver = user.wh23xx >>>>>>> >>>>>>> Do i have to add the following "port = /dev/mydevice" in the >>>>>>> weewx.conf file? >>>>>>> >>>>>>> thanks for your help >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sunday, January 15, 2017 at 8:58:57 PM UTC+7, Per Edström wrote: >>>>>>>> >>>>>>>> Apparently my USB-to-COM-port converter is not stable hence causing >>>>>>>> weewx to stop (when the device changes). SO I made a link to the >>>>>>>> current >>>>>>>> device for use in weewx.conf (details in a new thread here in the >>>>>>>> forum). >>>>>>>> It seems to work for now.. >>>>>>>> >>>>>>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
