ERROR unecpecteddevice id

64 views
Skip to first unread message

BORIS

unread,
Dec 11, 2023, 10:29:54 AM12/11/23
to weewx-user
When starting a new installation I get the following error.

boris@boris-NUC-Jamjo:~$ sudo tail -f /var/log/syslog
Dec 11 16:21:16 boris-NUC-Jamjo weewx[770] INFO user.kl: press the USB button to start communication
Dec 11 16:21:28 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Reject scan trigger since one is already pending
Dec 11 16:21:28 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Failed to initiate AP scan
Dec 11 16:21:29 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Reject scan trigger since one is already pending
Dec 11 16:21:29 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Failed to initiate AP scan
Dec 11 16:21:30 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Reject scan trigger since one is already pending
Dec 11 16:21:30 boris-NUC-Jamjo wpa_supplicant[638]: wlo2: Failed to initiate AP scan
Dec 11 16:21:31 boris-NUC-Jamjo weewx[770] INFO user.kl: press the USB button to start communication
Dec 11 16:21:46 boris-NUC-Jamjo weewx[770] INFO user.kl: press the USB button to start communication
Dec 11 16:22:01 boris-NUC-Jamjo weewx[770] INFO user.kl: press the USB button to start communication
Dec 11 16:22:16 boris-NUC-Jamjo weewx[770] INFO user.kl: press the USB button to start communication
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:23 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:24 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present
Dec 11 16:22:25 boris-NUC-Jamjo weewx[770] ERROR user.kl: generateResponse: intercepted message from device 01bd with length: e5
Dec 11 16:22:25 boris-NUC-Jamjo weewx[770] ERROR user.kl: unexpected device ID (id=01bd); use parameter 'serial' if more than one USB transceiver present

What is wrong?
/Boris

Rainer Lang

unread,
Dec 11, 2023, 11:03:56 AM12/11/23
to weewx...@googlegroups.com

only from the context (and when you know) one can guess that you are talking about KlimaLogg and the the KlimaLogg extension.
And the messages refer to the tranceiver USB stick through which the KlimaLogg console communicates with weewx
Are you aware of how the two devices cooperate ?

Did you press the USB button for the console to initiate the communication while weewx was waiting ?
Did you choose the proper Logger in the console ?
That doesn't look like a weewx issue but a user issue handling their hardware
😎
what does the [kl] stanza in your weewx.conf look like ?

Normally we reply here only if you provide a log from a new start of weewx - and from the start of the logging
such snippets are not helpful - most likely, provided you have set debug = 1 or debug = 3 in weewx.conf and restarted,
in the earlier syslog messages at startup some hints can be found

providing such a complete log has the chance to be more insightful - looking forward to seeing it ...

--
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/e098085b-7b58-44b6-b0d3-fd740edd6d7en%40googlegroups.com.

BORIS

unread,
Dec 11, 2023, 1:57:30 PM12/11/23
to weewx-user
Hello Rainer,
Did you press the USB button for the console to initiate the communication while weewx was waiting ?  Yes
Did you choose the proper Logger in the console ? I am not sure what you mean with that.

I followed the instruction for installation as given from:
Platform Packages

For Debian, Ubuntu, Mint, including Raspberry Pi, see:
http://weewx.com/docs/debian.htm

I cannot access the installation now and will provide more detailed log later with debug set to 1.
I may have forgotten to add the Klimalogg installation at  GitHub - matthewwall/weewx-klimalogg: klimalogg pro driver for weewx
/Boris

Rainer Lang

unread,
Dec 11, 2023, 2:03:00 PM12/11/23
to weewx...@googlegroups.com

that's the weexwx end - but to me this looks like an issue at the console end.
Each transceiver stick has a unique ID which should be mentioned in weewx.conf
(and which will be reported in the syslog, when debug = 1)
Also the console needs to be paired with the transceiver stick - that's KlimaLogg manual.
You may have selected the wrong logger in the console - then the weewx extension will not recognize the transceiver

Reply all
Reply to author
Forward
0 new messages