Bill, Well it is good that it is working as it should. As for binding = archive and what is displayed in the log during startup, well the code is pretty cut and dry. If binding is set to archive it should be displaying archive, so that suggests that whilst it looks like binding = archive there may be some other invisible characters in there that are interfering. What editor do you use to edit weewx.conf, is it a proper text or code editor?
I guess it is up to you if you want to look at this any further, when I see things that are working for the wrong reason I like to look closer as you don't know what else might be being masked by a potential issue. If you do want to look any further the next thing I would do would be post a wee_debug report <http://weewx.com/docs/utilities.htm#wee_debug_utility>, that will give us a clear picture of your config (which we haven't seen yet). If you do post a wee_debug report do check it for sensitive info such as user names, passwords, API keys etc before posting, wee_debug does a good job at obfuscating these things but it is not perfect. Gary On Thursday, 27 February 2020 13:17:01 UTC+10, Bill Arthur wrote: > > Gary, > > Almost 24 hours later.... cwxn 0.5a is chugging along. It's outputting > wxnow.txt every five minutes. I'm good with that. > Maybe cwxn binding is actually set for archive but it's just not > displaying properly in the log. Output at exactly five minutes makes me > think it is. > > Now we just need some rain. > > Bill > > On Wednesday, February 26, 2020 at 12:15:44 AM UTC-6, Bill Arthur wrote: >> >> >> Instead of spinning my wheels over binding=archive, I updated cwxn.py. >> It seems to be working fine. Syslog reports version 0.5a and "binding is >> loop" Wxnow.txt is updating and new data is making it to findu >> >> >> >> >> >> >> On Tuesday, February 25, 2020 at 10:50:30 PM UTC-6, Bill Arthur wrote: >>> >>> >>> >>> One more thing... >>> The original problem was that when I had added binding=archive my output >>> was static for a day. Now, I have binding=archive in weewx.conf and my >>> output is updating regularly.. But we seem to have a different problem now, >>> with binding=archive not showing up in the syslog. >>> >>> >>> >>> On Tuesday, February 25, 2020 at 10:20:13 PM UTC-6, Bill Arthur wrote: >>>> >>>> I've configured it (after stopping) with binding=archive in >>>> /etc/weewx/weewx.conf.. saved. viewed to confirm. restarted. syslog says >>>> binding=loop. rebooted. same results. >>>> stopped weewx. deleted line.saved. viewed to confirm. restarted. read >>>> syslog. syslog says binding=loop. stopped. set binding=archive. saved. >>>> viewed to confirm. restarted. syslog says binding=loop.. rebooted. read >>>> syslog. no change. >>>> >>>> >>>> I don't believe it has any effect, but i should tell you that I am not >>>> directly connected to the RasPi, I've working through VNC. >>>> >>>> On Tuesday, February 25, 2020 at 10:01:57 PM UTC-6, Bill Arthur wrote: >>>>> >>>>> Gary, >>>>> >>>>> I saved and restarted, then I rebooted. I've confirmed correct >>>>> /etc/weewx/weewx.conf location listed in the /var/log/syslog file. I'm >>>>> not >>>>> aware of any other weewx.conf file >>>>> >>>>> I've set it back and I'm trying it again. Will advise >>>>> >>>>> On Tuesday, February 25, 2020 at 9:28:41 PM UTC-6, gjr80 wrote: >>>>>> >>>>>> Some obvious things. You did save weewx.conf? You did restart Weewx? >>>>>> Is there more than one weewx.conf on your system and are you editing the >>>>>> right one(it happens). When you start Weewx look at the log during WeeWX >>>>>> startup and it will tell you the full path to weewx.conf, that is the >>>>>> file >>>>>> you need to edit. >>>>>> >>>>>> 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d3f11a70-083a-4b14-8131-e8ff4829e039%40googlegroups.com.
