Just to be clear I was just pointing out that the two places to look for info on what weeWX is doing is the console output when running weeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly> (this shows the data coming from the station) and the log (this shows config (during startup) and any errors that may be logged). I was not necessarily expecting to see any errors in your log.
Seeing as you are using a Vantage station you should be seeing loop packets every 2 odd seconds. Given the small screen capture showing just 2 loop packets only that were 5 seconds apart with the wakeup message between that would cause me to look more closely to see if you are somehow dropping loop packets. How often does that wakeup message appear and does it result in a dropped loop packet each time, if it occurs once a day it probably makes little difference, every second loop packet perhaps more of a difference (depends on your config). If you wanted to look into it further my suggestion was to provide a larger screen capture when running weeWX directly so we could gauge the extent of the issue (those wakeup log entries should also appear in the log - how often do they occur). Of course if you are not concerned about the wakeup /missing loop packets then you need do nothing :) Gary On Sunday, 6 January 2019 15:39:44 UTC+10, monmul wrote: > > This is all I could find on the syslog....no errors given so I will ignore > the LOOP etc > > Jan 6 18:25:20 Weatherpi weewx[831]: engine: Loading station type Vantage > (weewx.drivers.vantage) > Jan 6 18:25:20 Weatherpi weewx[831]: import of driver failed: [Errno 11] > Resource temporarily unavailable (<type 'exceptions.OSError'>) > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No <ACK> received from > console > Jan 6 18:25:20 Weatherpi weewx[831]: engine: Unable to load driver: > [Errno 11] Resource temporarily unavailable > Jan 6 18:25:20 Weatherpi weewx[831]: **** Exiting... > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 0.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 1.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 2.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 3.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No <ACK> received from > console > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No <ACK> received from > console > Jan 6 18:25:20 Weatherpi avahi-daemon[468]: Joining mDNS multicast group > on interface eth0.IPv6 with address fe80::1cc0:5dfe:d383:8c98. > Jan 6 18:25:20 Weatherpi avahi-daemon[468]: New relevant interface > eth0.IPv6 for mDNS. > > > On Sunday, 6 January 2019 17:52:24 UTC+13, gjr80 wrote: >> >> On Sunday, 6 January 2019 14:20:09 UTC+10, monmul wrote: >>> >>> Hmmm! I would have to pass on that one....I am not sure I even know what >>> it means.....is it something I set up when following the instructions about >>> installing nginx? >>> >>> Ok, you posted a screen capture with a couple of loop packets (the lines >> starting with LOOP: ). This was part of the output you would have seen when >> you ran weewx directly using sudo weewxd /etc/weewx/weewx.conf. Since >> you only showed us a couple of loop packets things could be running fine, >> its hard to say with such a small snapshot. The loop packets were 5 seconds >> apart, if you station emits loop packets every 5 seconds then this is fine, >> if it emits loop packets every 2 seconds then maybe there is an issue. >> Having a look at a good couple of archive periods of output would give a >> better feel for things rather than just a couple of loop packets. We would >> also see some archive records (they occur once per archive period) and >> start with REC: on screen. Would also be handy to know the station >> type/model. >> >> You might want to have a read through Loop packets vs. archive records >> <http://weewx.com/docs/customizing.htm#_________LOOP_packets_vs._archive_records_______> >> >> in the Customization Guide <http://weewx.com/docs/customizing.htm> - it >> will give you a bit of background. Also, have a look at your log (likely >> /var/log/syslog) from when you start weeWX, you will see a whole pile of >> info there as to how your station and weeWX are configured. teh log is good >> for seeing startup config and events as they happen (including errors). >> Screen output from running weeWX directly is handy for seeing the actual >> data weeWX gets off the station. >> >> nginx will have nothing to do it, nginx is purely serving web pages/data >> to your browser, the sleeping/retrying etc is weeWX interacting with your >> weather station. >> >> >>> One other thing....I have not done anything about setting up the NTP >>> Daemon thing....do I need to do that also? >>> >> >> Horses for courses. If it were me I would get NTP setup and working >> properly. Correct time is critical for weeWX to operate trouble free, some >> really bad and unusual things happen if weeWX and your station have >> significantly different times. That being said, once you have the correct >> time set all will likely be well until you have to reboot or turn your RPi >> off or there is a power interruption. RPis (as distinct from a desktop type >> PC or laptop) are a common source of concern as they have no battery backed >> clock for when the power is off, they have a fake hardware clock that can >> come up in the past. Various improvements have been applied to weeWX over >> the years to make it better handle temporal displacements and it is >> probably the best it has been but as a minimum I would get NTP up and >> running and I would also consider an add-on battery backed RTC module, they >> are just a couple of dollars on ebay or the like. >> >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
