No handlers could be found for logger "user.ws6in1".

141 views
Skip to first unread message

Ξ

unread,
Jul 11, 2023, 4:43:06 AM7/11/23
to weewx-user
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?


Screenshot from 2023-07-11 11-41-07.png

Tom Keffer

unread,
Jul 11, 2023, 10:08:39 AM7/11/23
to weewx...@googlegroups.com
Looking through ws6in1, it looks like it expects WeeWX V4.0 or greater. You are using V3.7.1, 



--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/caf2eaa9-5b40-4a37-851a-2498b09ddc2dn%40googlegroups.com.

Ξ

unread,
Jul 11, 2023, 12:00:11 PM7/11/23
to weewx-user
Hi Tom,

Many thanks for the explanation, I'll keep the set up as long as it works since support for Arch for armv6 has been discontinued and I'll need either new hardware or to change to an OS that still has armv6 support, in either case that would require setting up everything anew and I just don't want to do deal with that right now.

Cheers,

Ivo

Ξ

unread,
Jul 11, 2023, 12:11:05 PM7/11/23
to weewx-user
> 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?

To answer my own question weewx/ws6in1 doesn't seem to do a backfill: today the electricity was down at the site between 07:00 and 16:30 and the graphs don't show anything in that time frame. The console runs on batteries and collects data, only the R-Pi was down

Screenshot from 2023-07-11 19-06-39.png


Bob Atchley

unread,
Jul 11, 2023, 2:35:10 PM7/11/23
to weewx-user
Hi Ivo,

ws6in1 should still work with v3.7.1 its more that I no longer have the capacity to support/test it, and with the imminent (?) release of weewx v5   which is not compatible with Python 2.x I thought it time to move on.
I can't see any ws6in1 errors in the logs you have provided so not sure what the problem is.  If sensor batteries fail that shouldn't affect the usb connection to the console, however sometimes the sensors need syncing back to the consul to work properly and I suspect that is the reason for the gaps in the graph.

Cheers

Bob

Ξ

unread,
Jul 11, 2023, 3:35:11 PM7/11/23
to weewx-user
also, oops, I've replied to the above but by hitting 'reply to author' so I guess now only Bob sees it :/

Bob Atchley

unread,
Jul 12, 2023, 3:30:31 AM7/12/23
to weewx-user
Hi Ivo,

Re reading your messages, I think I understand the issue - the ws6in1 driver will back fill missing data but only if it is available from the console.  The Bresser 5 in 1 console has a limited storage that gets filled and unfortunately once full it no longer stores new data.  If set to 5 minute recording (which I would recommend) it will stores about 50 days worth of data, so you need to periodically empty the buffer (I do this on the 1st of the month after backing up the database).  The Bresser 5 in 1 manual (or at least my copy) seems to have entirely removed the instructions on how to set up and clear the data buffer.  I'll add the instructions on how to do this to the ws6in1 driver and copy here hopefully later today/tomorrow.

Cheers

Bob

Bob Atchley

unread,
Jul 12, 2023, 4:14:47 PM7/12/23
to weewx-user
Hi Ivo,

The current Bresser manual seems to be dumbed down (given that it is aimed at weather enthusiasts this seems a strange decision) however the previous manual can still be found on line here:

I would recommend downloading a copy of this manual,  Page 20 of this manual provides the information you need under the section 'DATA LOG'.  The DATA button is on the back of the console.
I'll try and attach a screen shot

Bresser_5in1_DataLog.jpg

Hope this helps (obviously ignore "PC Software" bit as we are using weewx rather than the very limited software that can be downloaded)
It is a bit fidilly but it does the trick (typical weather station implementation with excellent capability but poor usability).

cheers

Bob

Ξ

unread,
Jan 6, 2024, 8:59:36 PM1/6/24
to weewx-user
Hello Bob,

Huge thank you for taking the time to get back to me on this even though I'm 'a bit' late to check back, but it's really appreciated!

Ivo
Reply all
Reply to author
Forward
0 new messages