*This is driving me CRAZY!* I thought I found the problem with a UPS monitor daemon running (I had unplugged the USB cable from the CyberPower box) - I stopped the process and set it to not start at boot. Then it looked like weewx was talking to the console but we had some kind of database problem since I've been down for several days. It was updating my web page with old data. Now I'm getting errors like it can't talk to the logger. I did manage to do a logger text dump but after fiddling around that won't work now. I'm really frustrated and it's time to leave it alone and come back later.
Sigh. On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote: > > On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John Canfield wrote: >> >> The enigma for me then is why does weewx report the console woke up? A >> USB problem is the first thing I thought of as well but the Fitlet does >> report when ttyUSB0 is attached to a new port. Grrrr. >> >> Thanks Vince, I need all of the help I can get even though I'm not a >> weewx newbie - I was one of Tom's beta testers with one of his first >> releases. >> >> >> > I think the minicom approach of trying to connect to the console 'without' > weewx is a good one, it's just that the device might not match the one > you're trying to use. > > Try disconnecting the usb then reconnecting it, then use 'dmesg' to see > what device it allocated. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
