Yes, although it's not necessary to do the first 'mv.' If the version on your desktop is truly the original engine, then
sudo /etc/init.d/weewx stop cd /usr/share/weewx/weewx sudo cp ~/Desktop/engine.py engine.py sudo /etc/init.d/weewx start If you're not sure, you can download the v3.6.0 version of engine.py from here <https://raw.githubusercontent.com/weewx/weewx/v3.6.0/bin/weewx/engine.py>. -tk On Sun, Oct 16, 2016 at 3:49 PM, Tim Phillips <[email protected]> wrote: > I put the original engine.py on my desktop, so the process of getting that > back to the location would be?: > > sudo /etc/init.d/weewx stop > sudo cd /usr/share/weewx/weewx > sudo mv engine.py engine.py.orig > sudo cp ~/Desktop/engine.py engine.py > sudo /etc/init.d/weewx start > > Drag/drop using the UI doesn't work due to permissions. I added sudo to > the commands earlier since I got denied with permission errors there > earlier as well. Assuming that IS the way it's supposed to be? > > > On Sun, Oct 16, 2016 at 1:29 PM, Thomas Keffer <[email protected]> wrote: > >> Put the original engine back. They are the same, but the modified version >> will put a lot of entries into your log. >> >> -tk >> >> On Sun, Oct 16, 2016 at 1:07 PM, Tim Phillips <[email protected]> >> wrote: >> >>> Do I need to put the original engine.py back into the folder or do I >>> leave what you gave me in there? >>> >>> >>> >>> On Sun, Oct 16, 2016 at 11:29 AM, Thomas Keffer <[email protected]> >>> wrote: >>> >>>> Your value of archive_delay is set to 300 seconds. Change it to 15 >>>> seconds and all your problems will go away. >>>> >>>> archive_delay = 15 >>>> >>>> -tk >>>> >>>> On Sun, Oct 16, 2016 at 11:18 AM, Tim Phillips <[email protected]> >>>> wrote: >>>> >>>>> New log attached after replacing the engine.py per instructions. Lots >>>>> of "syslog" files attached in this thread, so I've renamed this log with >>>>> appropriate changes- "new engine.py" in the file name >>>>> >>>>> Tim. >>>>> >>>>> >>>>> On Sunday, October 16, 2016 at 9:58:18 AM UTC-7, Tim Phillips wrote: >>>>>> >>>>>> Just followed your instructions and will post the new log file >>>>>> after it's had a chance to run a while as suggested. >>>>>> >>>>>> On Sunday, October 16, 2016 at 6:59:57 AM UTC-7, Tom Keffer wrote: >>>>>>> >>>>>>> On Sun, Oct 16, 2016 at 6:18 AM, mwall <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> On Sunday, October 16, 2016 at 8:19:38 AM UTC-4, Tom Keffer wrote: >>>>>>>>> >>>>>>>>> Me too. What do you think of my theory that the console is >>>>>>>>> (occasionally) waiting more than 5 minutes to emit a LOOP packet? >>>>>>>>> >>>>>>>> >>>>>>>> the log indicates that the driver is getting data regularly. take >>>>>>>> a look at the entries between some of the 10 minute add records. >>>>>>>> >>>>>>>> there is a yield just before each "next read in X second". when >>>>>>>> the data are stale, the yielded packet contains only dateTime, usUnits, >>>>>>>> channel, sensor_id, rssi, sensor_battery, but no weather data. >>>>>>>> >>>>>>> >>>>>>> That should be enough to give the engine a chance to break the loop. >>>>>>> >>>>>>> Tim: I have attached an instrumented version of >>>>>>> engine.py >>>>>>> that should shed some light on this mystery. Please set your old >>>>>>> version of >>>>>>> engine.py >>>>>>> aside, and replace it with this one. Assuming you download this >>>>>>> version into >>>>>>> ~/Downloads >>>>>>> , the process would be: >>>>>>> >>>>>>> cd /usr/share/weewx/weewx >>>>>>> mv engine.py engine.py.orig >>>>>>> cp ~/Downloads/engine.py engine.py >>>>>>> >>>>>>> >>>>>>> Make sure debug=1, then restart weewx, then send the log from the >>>>>>> restart, through the first couple of reports (should take about 20 >>>>>>> minutes). The log will be big, so just attach it as a file. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "weewx-user" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/weewx-user/W8C-1CuFsik/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> 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. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "weewx-user" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/weewx-user/W8C-1CuFsik/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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. > -- 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.
