Botched FW upgrades almost never result in "partial" instabilities... It will almost always result in a bricked device.
On Saturday, November 12, 2016 at 7:11:43 PM UTC-6, Radar wrote: > > changed the 3 calls and is running right now > > it could be that the bridge didn't take the firmware right it is over 3 > years old so might not be able to fix it > > On Saturday, November 12, 2016 at 9:05:44 AM UTC-6, mwall wrote: >> >> On Saturday, November 12, 2016 at 9:37:25 AM UTC-5, Radar wrote: >>> >>> it might be >>> this is from running it with ./weewxd ../weewx.conf >>> --log-label=weewx-3.6.1 >>> >> >> well, i'd rather not debug your syslog configuration (i find that >> exercise particularly frustrating on recent ubuntu systems) >> >> so as a quick hack, change the 3 calls to logdbg to loginf in the >> decode_ip_packet method of SniffServer in interceptor.py >> >> then run again. that should tell us what is in the data that won't >> stringify. >> >> 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.
