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.
For Debian, Ubuntu, Mint, including Raspberry Pi, see:
http://weewx.com/docs/debian.htm
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
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d932a614-2bab-4b0b-bb98-51d014513254n%40googlegroups.com.