Hi Gary Thanks, working now.
Do you know if I can more weewx instances running using the same port 8000? Gert On Thursday, May 21, 2020 at 1:57:30 AM UTC+2, gjr80 wrote: > > Hi, > > Not an error as such but an informational log entry that the interceptor > driver did not recognise PASSKEY. It just happens that this unfortunately > causes the passkey to be logged in full and unobfuscated. I have submitted > a PR <https://github.com/matthewwall/weewx-interceptor/pull/64> to > Matthew to fix the issue, I am sure he will get around to it in due course. > In the interim, you can fix the problem by applying the change to > interceptor.py > <https://github.com/matthewwall/weewx-interceptor/pull/64/commits/00bdecdc1822d7deaa7c41f20dfc4c30a349936d> > > that is included in the PR. > > Gary > > On Thursday, 21 May 2020 07:36:02 UTC+10, Gert Andersen wrote: > >> Hi >> >> Weewx4.0 >> Interceptor 0.54 >> Ubuntu 20.04 >> GW1000 >> >> I get this error: >> INFO user.interceptor: unrecognized parameter >> b'PASSKEY=5E7384C4921D13C0A8572F8XXXXXXXXXXX >> all the time. I have registered the device with Ecowitt.net. >> >> Can I do anything about that? >> >> One more question, can I have more weewx instances listen to same >> interceptor port or is the port locked with the first instance? >> >> Thanks >> Gert >> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/bf492a51-489a-4f33-bb5b-26382710d660%40googlegroups.com.
