Re: [weewx-user] Re: WeeWx not starting up automatically, and then not starting correctly on first run.

I know this thread has been dormant for some time, and I don't see that a solution has been determined, but I've got the same problem with my weewx install on an RPi3, and it's been a bit frustrating. The RPi is on battery backup, so glitches in AC don't impact it, but still, when for some rea

Re: [weewx-user] Re: WeeWx not starting up automatically, and then not starting correctly on first run.

what does the log say during this boot / stop / start procedure?? On Friday, 25 November 2016 17:01:55 UTC+2, Jon Adams wrote: > I know this thread has been dormant for some time, and I don't see that a > solution has been determined, but I've got the same problem with my weewx > install on

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Thanks for the fast response. Am Freitag, 25. November 2016 02:47:18 UTC+1 schrieb Tom Keffer: > > Please read the User's Guide, section 3rd party Vantage connectors > and > see if that answers your question. > Unfortunately y

[weewx-user] Where did my log file go?

Hello: I just updated to weewx 3.6.2 today and decided to clean up something that's been bothering me for a while since I reinstalled my Linux Mint 18. I had it set up previously to log weewx entries to a separate log file. It worked perfectly. I set it up today following these instructions:

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

The timestamp for the loop packets come from weewx. So, if the clock on the RPi is correct, then the loop packet timestamps should be correct. If you run weewx directly from the command line , you can monitor these timestamps and see if they ar

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I think I can remove the GETTIME command. archive_delay is still at 15 seconds. I come back later. Am Freitag, 25. November 2016 17:08:48 UTC+1 schrieb Tom Keffer: > > The timestamp for the loop packets come from weewx. So, if the clock on > the RPi is correct, then the loop packet timestamps

[weewx-user] Re: Where did my log file go?

Answered my own question here - the log file (/var/log/weewx.log) needed to be created manually. I gave root ownership, syslog read-write access, others read-only. Now it works fine. On Friday, November 25, 2016 at 10:44:53 AM UTC-5, Fraoch wrote: > > Hello: > > I just updated to weewx 3.6.2 t

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

You might not have changed the archive delay - but what is the archive interval set to?? On Friday, 25 November 2016 18:29:55 UTC+2, gustl319 wrote: > I think I can remove the GETTIME command. archive_delay is still at 15 > seconds. I come back later. > > > > Am Freitag, 25. November 2016 17:0

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I tried to atach the log file. hope you can read it -- 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, visi

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

as I said15. but here is my conf -- 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.go

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I don't think it is as simple as removing the GETTIME command. Weewx detects the lack of an onboard clock by making a call to the *driver* function getTime(). If has not been implemented, then it falls back to the system clock. Unfortunately, even if you remove the GETTIME command, the function g

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Am Freitag, 25. November 2016 18:58:30 UTC+1 schrieb Tom Keffer: > > I don't think it is as simple as removing the GETTIME command. > Just recognized that :-( > Weewx detects the lack of an onboard clock by making a call to the > *driver* function getTime(). If has not been implemented, then i

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

> > I just tried that. It just seems to have no efect. I'm not familiar with >> phyton. Must I run a compile script? >> > >> ​No. Just restart weewx. Python is an interpreted language. And, please don't just say "has no effect." Some details please. In particular* post the log!* -tk​ -- You rec

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

It had no effect because GETTIME was still missing. Now with a fake GETTIME and your code I get this. -- 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+

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

Just checked index.html Temp and Hum are the same as in the console. So far it looks good. Thanks a lot -- 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

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

I'm not following. I don't know how the Dekay libraries work, but I assume they emulate the Davis Vantage API. So, it must respond to a GETTIME command with something, but if the feather has no clock, what is it returning? >From your later note, it sounds like everything is working. What did you

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Dekay Lib: A GETTIME command is always responded with the same static time (Januar 1st 2016 1:00:00). On weewx: getConsoleTime() gets an answer on GETTIME and causes no errors. getTime() corrects the time to time.time() + 0.5 At the moment this works for me. But getConsoleTime() is also used

Re: [weewx-user] Re: WeeWx not starting up automatically, and then not starting correctly on first run.

I've attached the syslog. All times are local (MST) 083500: Pi powered on 083525: the syslog starts getting written to. 083525 (row 406): systemd starts weewx 083529 (row 521): Initializing weewx version 3.5.0 083529 (row 544): weewx can't find wired VantagePro on 192.168.1.45 083529 (row 547): we

Re: [weewx-user] Re: WeeWx not starting up automatically, and then not starting correctly on first run.

jon, your configuration requires a network connection to the vantage station, and weewx is bailing out when it finds no network (see lines 546 and 547 of the syslog you posted). by the time you try to start weewx directly, then network is functional. you need to tell systemd that weewx needs a

Re: [weewx-user] Dekay's DavisRFM69 lib without RTC

On Fri, Nov 25, 2016 at 11:04 AM, gustl319 wrote: > On Dekay Lib: > A GETTIME command is always responded with the same static time (Januar > 1st 2016 1:00:00). > On weewx: > getConsoleTime() gets an answer on GETTIME and causes no errors. > getTime() corrects the time to time.time() + 0.5 > > At

Re: [weewx-user] Re: WeeWx not starting up automatically, and then not starting correctly on first run.

On Friday, November 25, 2016 at 2:53:34 PM UTC-5, Jon Adams wrote: > > 083529 (row 547): weewx exits because it can't find a network (but there > was a network already set up?) > jon, your configuration requires a network connection to the vantage station, and weewx is bailing out when it fin

Re: [weewx-user] wee_reports only generating reports for most recent records in database

Hi, Thanks for your reply :) I tried it but it says "sudo: wee_reports: command not found". Do I have to 'install' it? On Friday, 25 November 2016 00:31:19 UTC, Tom Keffer wrote: > > You found a bug that was introduced in v3.6.0. Try the attached version of > wee_reports. > > -tk > > On Thu,

Re: [weewx-user] wee_reports only generating reports for most recent records in database

You should replace your existing version, then run it just like you ran your old version. Make sure you type './wee_reports' and not just ' wee_reports'. cd /usr/share/weewx sudo ./wee_reports /etc/weewx/weewx_archive_reps.conf 1480014000 You might have to change permissions on it: chmod +x wee_

Re: [weewx-user] wee_reports only generating reports for most recent records in database

Sorry. That would be sudo chmod +x wee_reports On Fri, Nov 25, 2016 at 1:18 PM, Thomas Keffer wrote: > You should replace your existing version, then run it just like you ran > your old version. Make sure you type './wee_reports' and not just ' > wee_reports'. > > cd /usr/share/weewx > sudo ./w

[weewx-user] davis - system stoped to collect and send data

Hi, I had lost my old config, had to go for old sd card. System started to collect old data - from last 4 days.Send it to the webpage - boleslawice.info, WU and other weather system and then stopped to collect data. Now I have something like: pi@raspberrypi:~ $ tail -f /var/log/syslog Nov 25 22:

[weewx-user] Weewx multiple language output

I’m running v3.6.1 deb on an RPi 2 with a Vantage Pro 2 and have built Dutch and English versions of the web pages, but I’m having problems with default languages (environment locale) and tags that return dateTime values. The OS environment locale is set to GB English by default, mainly for

Re: [weewx-user] davis - system stoped to collect and send data

Hello, Jacek I'm sorry, but I'm not quite following your question, but I'll try my best. The way weewx works, it looks for the last record in the database, then asks for the Vantage to dump all data since that record. It sounds like you are missing some intermediate data? That is, data that is o

Re: [weewx-user] Weewx multiple language output

Darned good question, and I'm not sure I know the answer. Because the Cheetah template engine allows you to include Python code, one thing you could try is to set the desired locale at the top of the template. Something like #import locale #locale.setlocale(locale.LC_ALL, 'fr_FR.utf8') ## Hopefu

Re: [weewx-user] davis - system stoped to collect and send data

I have been helping Jacek by email for the last week or so on an unrelated skin issue. I know he experienced some problems with his RPi around 21 November and since he was remote from the system there was little he could do. This morning I heard from him with a couple of log excerpts. It seems

[weewx-user] Xtide config in forecast skin on RPi 3

It appears I don't have the Xtide config correct: Nov 25 22:55:16 WeatherPi weewx[20308]: forecast: MainThread: XTide: >> starting thread > > Nov 25 22:55:16 WeatherPi weewx[20308]: forecast: XTideThread: XTide: >> generating tides from 2016-11-25 00:00:00 EST (148005) to 2016-12-23 >> 00:0