I would suggest you work on eliminating the under voltage errors before trying to work out why you cannot communicate with the weather station. The implication is that the RPi is having trouble coping with whatever you have got connected via usb and/or network. This is not unusual and indicates you may need either a larger power supply or a powered usb hub to cope with your usb loads.
On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote: > > My Pi stopped reporting at 19.20 today and despite rebooting twice, it > does not seem to be able to wake up the console......is there a way/log I > can query to find out why it might have stopped at 19.10....it was working > fine for 2 or 3 days. Here is the syslog... > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available > Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console > Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable to > wake up Vantage console (<class 'weewx.WakeupError'>) > Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: > Unable to wake up Vantage console > Jan 28 21:44:02 raspberrypi weewx[510]: **** Exiting... > Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: > connected: 10.1.1.155::40108 (TCP) > Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: > authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) > Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: Failed > to add printer: server-error-service-unavailable > Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage detected! > (0x00050005) > Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised > (0x00000000) > Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 88.191.250.97 > Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4 > Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server > 103.106.66.123 > Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server > 103.106.65.219 > Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.159.70.33 > Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5 > Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.86.206.43 > Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4 > Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3 > Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 103.242.68.69 > Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server > 130.217.226.49 > Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server > 122.252.188.99 > Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.78.240.38 > Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.46.179.18 > Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server > 2407:f100:0:1::2 > Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server > 130.217.226.51 > Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed > Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed > Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min > 19.972590s random time. > Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding > 37min 57.400920s random time. > Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin > timestamp 0xdff93f8c.e12c4d6d does not match aorg 0000000000.00000000 from > ser...@203.159.70.33 <javascript:> xmt 0xdff93f94.5a13b23a > Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin > timestamp 0xdff93f8c.e1319bed does not match aorg 0000000000.00000000 from > ser...@37.187.18.4 <javascript:> xmt 0xdff93f94.62dbcbad > Jan 28 21:47:56 raspberrypi kernel: [ 251.674064] Under-voltage detected! > (0x00050005) > Jan 28 21:48:02 raspberrypi kernel: [ 257.914050] Voltage normalised > (0x00000000) > > > On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote: >> >> Not a problem, you pointed me in the right direction which was all I >> needed......thanks again! >> >> On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote: >>> >>> My apologies if I lead you astray, I did mentioning dumping but did not >>> list the command. Was out at the time and on the mobile. >>> >>> Gary >>> >> -- 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.
