Looking through ws6in1 <https://github.com/BobAtchley/weewx-ws6in1>, it looks like it expects WeeWX V4.0 or greater. You are using V3.7.1,
On Tue, Jul 11, 2023 at 1:43 AM Ξ <[email protected]> wrote: > Hello, > > A year ago I installed WS 6in1 for Bresser 5-in1 (thread for reference > https://groups.google.com/u/1/g/weewx-user/c/VPrfgr5uZq4/m/pNE9U0RRAQAJ), > which was running without problems until June 13 when it stopped sending > reports. > > When I went at the site I noticed the outside batteries had to be > replaced, so I did that, but it didn't help, then I've noticed weewx was > failing to start with an exit code something along the lines of "device not > found". > > Frankly not having a clue what to do since I hadn't done any changes or > modifications in the past year since I made it work I decided swapping the > USB cable, but I've noticed it was detecting the station: > > kernel: usb 1-1.3: new full-speed USB device number 9 using dwc_otg > kernel: usb 1-1.3: New USB device found, idVendor=1941, idProduct=8021, > bcdDevice= 0.00 > kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > kernel: usb 1-1.3: Product: CCLEL C8488 > kernel: usb 1-1.3: Manufacturer: Silicon Laboratories Inc. > kernel: usb 1-1.3: SerialNumber: CCLEL c8488 > kernel: hid-generic 0003:1941:8021.0004: hiddev96,hidraw0: USB HID v1.11 > Device [Silicon Laboratories Inc. CCLEL C8488] on > usb-20980000.usb-1.3/input0 > > Yet, weewx was failing with No handlers could be found for logger > "user.ws6in1": > > Jul 10 17:05:03 alarmpi weewx[415]: engine: Finished loading service > weewx.engine.StdReport > Jul 10 17:05:03 alarmpi weewx[415]: engine: Starting up weewx version 3.7.1 > Jul 10 17:05:03 alarmpi weewx[415]: engine: Station does not support > reading the time > Jul 10 17:05:03 alarmpi weewx[415]: manager: Daily summary version is 4.0 > Jul 10 17:05:03 alarmpi weewx[415]: manager: Daily summary version is 4.0 > Jul 10 17:05:03 alarmpi weewx[415]: manager: Daily summary version is 4.0 > Jul 10 17:05:03 alarmpi weewx[415]: manager: Daily summary version is 4.0 > Jul 10 17:05:10 alarmpi weewxd[415]: No handlers could be found for logger > "user.ws6in1" > Jul 10 17:05:52 alarmpi weewx[415]: engine: Main loop exiting. Shutting > engine down. > Jul 10 17:05:52 alarmpi weewx[415]: restx: Shut down WeatherCloud thread. > > Again, not having a clue what that could possibly mean or what to do I > decided to play with the console buttons: pressing TIME SYNC; RESET; DATA - > but weewx kept shutting down with *No handlers could be found for logger > "user.ws6in1".* > > Maybe it's worth noting that USB DATA kept blinking on the screen during > all this time (at least I've notied it after the RESET and all that). > > I've decided to leave the premises and much to my surprise I saw the > station had started sending reports a couple of hours later: > > Jul 10 19:55:30 alarmpi weewx[215]: manager: Daily summary version is 4.0 > Jul 10 19:55:30 alarmpi weewx[215]: manager: Daily summary version is 4.0 > Jul 10 19:55:31 alarmpi weewx[215]: manager: Daily summary version is 4.0 > Jul 10 19:55:31 alarmpi weewx[215]: manager: Daily summary version is 4.0 > Jul 10 19:56:40 alarmpi weewxd[215]: No handlers could be found for logger > "user.ws6in1" > Jul 10 20:04:49 alarmpi weewx[215]: engine: Starting main packet loop. > Jul 10 20:05:43 alarmpi weewxd[215]: LOOP: 2023-07-10 20:04:51 EEST > (1689008691) altimeter: 1023.27580096, appTemp: 22.2702851465, barometer: > 1013.0, cloud> > Jul 10 20:05:43 alarmpi weewxd[215]: LOOP: 2023-07-10 20:04:56 EEST > (1689008696) altimeter: 1023.27580096, appTemp: 22.2702851465, barometer: > 1013.0, cloud> > Jul 10 20:05:43 alarmpi weewxd[215]: LOOP: 2023-07-10 20:05:08 EEST > (1689008708) altimeter: 1023.27580096, appTemp: 22.2702851465, barometer: > 1013.0, cloud> > Jul 10 20:15:20 alarmpi weewx[215]: manager: Added record 2023-07-10 > 20:15:00 EEST (1689009300) to database 'weewx.sdb' > > Notice there's still there the No handlers could be found for logger > "user.ws6in1" but now it works! > > So after this rather long intro two questions: > 1. What does that message mean and is it something I should worry/care > about? (No handlers could be found for logger "user.ws6in1) > > 2. Since the station has a configurable data log, if communication between > it and weewx/ws6in1 is interrupted for a significant time period, let's say > 5 days, does weewx/ws6in1 catch up/fetch the missing data? > > > [image: Screenshot from 2023-07-11 11-41-07.png] > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/caf2eaa9-5b40-4a37-851a-2498b09ddc2dn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/caf2eaa9-5b40-4a37-851a-2498b09ddc2dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECC3nxB_CmKme0OBjjGDthjzrux7OqSB8JKRzU4Qaanjg%40mail.gmail.com.
