Seems to have fixed itself. I guess time heals all wounds? But now getting this message: Aug 28 00:44:40 raspberrypi weewx[4022]: interceptor: MainThread: unrecognized parameter absbaromin=26.82
On Sunday, August 27, 2017 at 10:21:54 PM UTC-4, mwall wrote: > > On Sunday, August 27, 2017 at 10:01:28 PM UTC-4, Bill Volz wrote: >> >> I'm having trouble getting the weewx to listen for the incoming info from >> a ws-1001-wifi. Here's what in syslog: >> >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is >> listen >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: mode is >> listen >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen >> on 192.168.0.196:8081 >> Aug 27 21:43:26 raspberrypi weewx[2809]: interceptor: MainThread: listen >> on 192.168.0.196:8081 >> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno >> 99] Cannot assign requested address (<class 'socket.error'>) >> Aug 27 21:43:26 raspberrypi weewx[2809]: import of driver failed: [Errno >> 99] Cannot assign requested address (<class 'socket.error'>) >> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: >> [Errno 99] Cannot assign requested address >> Aug 27 21:43:26 raspberrypi weewx[2809]: engine: Unable to load driver: >> [Errno 99] Cannot assign requested address >> Aug 27 21:43:26 raspberrypi weewx[2809]: **** Exiting... >> Aug 27 21:43:26 raspberrypi weewx[2809]: **** Exiting... >> >> > has the network been initialized by the time that weewx starts? > > syslog will tell you > > you can also test: for example, does weewx work when you start it > manually, but not when started by the system at system startup? > > m > > -- 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. For more options, visit https://groups.google.com/d/optout.
