[weewx-user] Problem with weewx 3.7.1 debian repository

[Juan Antonio Mosquera]

I have a problem after install...


Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Mar 23 18:23:37 raspberrypi weewx[17770]:   obj.start()
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Mar 23 18:23:37 raspberrypi weewx[17770]:   self.run()
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 31, in run
Mar 23 18:23:37 raspberrypi weewx[17770]:  
 self.genImages(self.gen_ts)
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 141, in genImages
Mar 23 18:23:37 raspberrypi weewx[17770]:  
 aggregate_interval=aggregate_interval)
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/manager.py", line 512, in getSqlVectors
Mar 23 18:23:37 raspberrypi weewx[17770]:   aggregate_type, 
aggregate_interval)
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weewx/manager.py", line 739, in _getSqlVectors
Mar 23 18:23:37 raspberrypi weewx[17770]:  
 _cursor.execute(sql_str, stamp)
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weedb/sqlite.py", line 29, in guarded_fn
Mar 23 18:23:37 raspberrypi weewx[17770]:   return 
fn(*args, **kwargs)
Mar 23 18:23:37 raspberrypi weewx[17770]: File 
"/usr/share/weewx/weedb/sqlite.py", line 211, in execute
Mar 23 18:23:37 raspberrypi weewx[17770]:   return 
sqlite3.Cursor.execute(self, *args, **kwargs)
Mar 23 18:23:37 raspberrypi weewx[17770]:   DatabaseError: 
database disk image is malformed
Mar 23 18:23:37 raspberrypi weewx[17770]: copygenerator: copied 0 files to 
/var/www/html/weewx/


Thanks!

-- 
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.

[weewx-user] Re: Version 3.7.1

[Neville Davis]

Installed fine (setup.py), no problems with replication MySQL (earlier 
discussion and mod to Pi MySQL config)

Nev

On Friday, March 24, 2017 at 1:02:28 AM UTC+10, Tom Keffer wrote:
>
> This version has fixes for some minor problems in V3.7.0.  Find it in the 
> usual places.
>
> -tk
>
> CHANGE LOG
>
> Fixed log syntax in wmr100 and wmr9x8 drivers.
>
>
> Emit Rapidfire cache info only when debug is level 3 or higher.  Thanks to
> user Darryn Capes-Davis.
>
> Fixed problem that prevented Rapidfire from being used with databases in
> metric units. Fixes issue #230.
>
> Set WOW `post_interval` in config dict instead of thread arguments so that
> overrides are possible.  Thanks to user Kenneth Baker.
>
> Distribute example code and example extensions in a single examples directory.
> Ensure that the examples directory is included in the rpm and deb packages.
>
> Fixed issue that prevented a port from being specified for MySQL 
> installations.
>
> MySQL error 2003 ("Can't connect to MySQL server...") now gets mapped to
> `weedb.CannotConnectError`. PR #234.
>
> By default, autocommit is now enabled for the MySQL driver. Fixes issue #237.
>
> Highs and lows from LOOP packets were not being used in preference to archive
> records in daily summaries. Fixed issue #239.
>
>

-- 
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.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[Thomas Keffer]

Unless there is something unusual about your adapter, no, that should not
be necessary.

-tk

On Thu, Mar 23, 2017 at 3:49 PM,  wrote:

> I have an rs232-->USB adapter which creates ttyUSB0 at startup. Should
> this be a rule in rules.d? Something I hadn't thought about.
> I'll remove the modemmanager. Thanks.
> Bob
>
> --
> 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.
>

-- 
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.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[bgrattan]

I have an rs232-->USB adapter which creates ttyUSB0 at startup. Should this be 
a rule in rules.d? Something I hadn't thought about.
I'll remove the modemmanager. Thanks.
Bob

-- 
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.

Re: [weewx-user] Re: weird yscale behaviour?

[Paolo Benvenuto]

proposed a pull request

Il giorno giovedì 23 marzo 2017 16:03:45 UTC+1, Tom Keffer ha scritto:
>
> I'm sorry.
>
> -tk
>
> On Thu, Mar 23, 2017 at 8:00 AM, Paolo Benvenuto  > wrote:
>
>> ymax is far bigger than it must be, it should be 22 (as when yscale is 
>> unset), it's 36!
>>
>>
>> don Paolo Benvenuto
>>
>> 2017-03-23 15:29 GMT+01:00 Thomas Keffer 
>> :
>>
>>> It works for me. What are you getting? And, what were you expecting?
>>>
>>> [image: Inline image 1]
>>>
>>> On Thu, Mar 23, 2017 at 7:24 AM, Paolo Benvenuto >> > wrote:
>>>
 Apparently it's in the correct position:


 [[day_images]]
 x_label_format = %k
 time_length = 133200# == 37 hours

 [[[daytemp]]]
 image_height = 400
 yscale = None, None, 2
 inTemp
 color = green




 Il giorno giovedì 23 marzo 2017 15:18:27 UTC+1, Tom Keffer ha scritto:
>
> Where in skin.conf are you setting yscale? See the specs for plot 
> [[[dayrain]]] for an example.
>
> -tk
>
> On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto  
> wrote:
>
>> In another graph where y ranges from 10 to 21 when yscale is not set, 
>> setting
>>
>> yscale = None, None, 2
>>
>> makes the graph have ymin = 10 and ymax = 30. None of the plotted 
>> lines raises above 21
>>
>> This is weirder...
>>
>>
>>
>> Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha 
>> scritto:
>>>
>>> Hi!
>>>
>>> In a temperature graph I'm setting
>>>
>>> yscale = None, None, 1
>>>
>>> I intend that this means that the "minimum tick interval" is 1 
>>> degree, but in the graphs where temperature ranges from -20 to 20 the 
>>> spacing between the lines is 5 degrees
>>>
>>> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't 
>>> weewx accept my value?
>>>
>>> And: is there a way to set the actual tick interval to 1 degree?
>>>
>>>
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> 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 weewx-user+...@googlegroups.com .
 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/topic/weewx-user/6gevHcrAoDk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com .
>>> 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 weewx-user+...@googlegroups.com .
>> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[Thomas Keffer]

1. Do you actually have a port /dev/ttyUSB0? This should have been set up
long before weewx was launched.

2. Unless you actually own a modem, you should remove the modem manager. It
will compete with the weewx process for control of /dev/ttyUSB0.

sudo apt-get remove modemmanager


-tk

On Thu, Mar 23, 2017 at 12:03 PM,  wrote:

> Tom,
>
> I have attached parts of the syslog file which cover your questions below.
> These are not filtered, but if you need more on either end I can send more.
> I tried to cut them down as close as I could by time because of the size. I
> did reboot at the times you ask about. I have only one instance of weewx
> that I know of.
> If I can do any more testing then please let me know as I will be happy to
> help in any way I can.  Thanks.
> Bob
>
> On Thursday, March 23, 2017 at 11:44:00 AM UTC-4, Tom Keffer wrote:
>>
>> Bob,
>>
>> Before chasing theories, let's make sure we understand exactly what's in
>> the log.
>>
>> 1. Did the computer reboot somewhere between 15:29:02 and 15:29:33 on
>> March 22?
>>
>> 2. At Mar 22 15:29:33 I am seeing three weewx processes: 810, 1025, and
>> 1006. I can imagine their being two just after the daemon fork, but there
>> should never be three. Did you have another weewx process running?
>>
>> 3. Did the computer reboot between March 23 10:02:00 and 10:05:01?
>>
>> General: if the computer was rebooting at the indicated times, we should
>> be seeing some evidence in the logs. Did you filter them in some way? If
>> so, please don't. In this case, we are looking at interactions between the
>> OS and weewx, so it's critical we see log entries from both.
>>
>> -tk
>>
>>
>>
>> On Thu, Mar 23, 2017 at 7:56 AM,  wrote:
>>
>>> Tom,
>>>
>>> I have attached the weewx.log portion which contains the info you
>>> requested. The system is Ubuntu 16.04.1 running on an Intel i5 (Intel NUC
>>> box). I tried rebooting again this morning and had some new results:
>>>
>>> root@nuc:~# service weewx status
>>> ? weewx.service - weewx weather system
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
>>> preset: enabled)
>>>Active: failed (Result: exit-code) since Thu 2017-03-23 10:05:01 EDT;
>>> 37s ago
>>>   Process: 1076 ExecStart=/home/weewx/bin/weewxd --daemon
>>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited, status=4)
>>>  Main PID: 1076 (code=exited, status=4)
>>> Mar 23 10:05:01 nuc weewx[891]: engine: pid file is /var/run/weewx.pid
>>> Mar 23 10:05:01 nuc systemd[1]:* weewx.service: Supervising process
>>> 1076 which is not our child. We'll most likely not notice when it exits.*
>>> Mar 23 10:05:01 nuc weewx[1076]: engine: Using configuration file
>>> /home/weewx/weewx.conf
>>> Mar 23 10:05:01 nuc weewx[1076]: engine: Loading station type Vantage
>>> (weewx.drivers.vantage)
>>> Mar 23 10:05:01 nuc weewx[1076]: import of driver failed: [Errno 2]
>>> could not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
>>> '/dev/ttyUSB0' (>> Mar 23 10:05:01 nuc weewx[1076]: engine: Unable to load driver: [Errno
>>> 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
>>> '/dev/ttyUSB0'
>>> Mar 23 10:05:01 nuc weewx[1076]:   Exiting...
>>> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Main process exited,
>>> code=exited, status=4/NOPERMISSION
>>> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Unit entered failed state.
>>> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Failed with result
>>> 'exit-code'.
>>> 
>>> ? weewx.service - weewx weather system
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
>>> preset: enabled)
>>>Active: failed (Result: timeout) since Thu 2017-03-23 10:08:16 EDT;
>>> 1min 14s ago
>>>   Process: 2348 ExecStart=/home/weewx/bin/weewxd --daemon
>>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited,
>>> status=0/SUCCESS)
>>>  Main PID: 2348 (code=exited, status=0/SUCCESS)
>>> Mar 23 10:06:46 nuc weewx[2352]: restx: PWSWeather: Data for station
>>> N4MRV will be posted
>>> Mar 23 10:06:46 nuc weewx[2352]: restx: CWOP: Data for station N4MRV-1
>>> will be posted
>>> Mar 23 10:06:46 nuc weewx[2352]: restx: WOW: Data for station 964806001
>>> will be posted
>>> Mar 23 10:06:46 nuc weewx[2352]: restx: AWEKAS: Data will be uploaded
>>> for user bgrattan
>>> Mar 23 10:06:46 nuc weewx[2352]: engine: Starting up weewx version 3.7.0
>>> Mar 23 10:06:46 nuc weewx[2352]: engine: Clock error is -1.64 seconds
>>> (positive is fast)
>>> Mar 23 10:06:46 nuc weewx[2352]: engine: Starting main packet loop.
>>> Mar 23 10:08:16 nuc systemd[1]: weewx.service: State 'stop-sigterm'
>>> timed out. Killing.
>>> Mar 23 10:08:16 nuc systemd[1]: weewx.service: Unit entered failed state.
>>> Mar 23 10:08:16 nuc systemd[1]: weewx.service: Failed with result
>>> 'timeout'.
>>>
>>> In the first listing, ttyUSB0 didn't load fast enough (haven't 

[weewx-user] Re: debian 3.7.1-1 error 404 on install - apt error?

[tempus]

Confirmed fixed.

Bob

On Thursday, March 23, 2017 at 7:57:44 AM UTC-7, mwall wrote:
>
> On Thursday, March 23, 2017 at 10:35:47 AM UTC-4, tempus wrote:
>>
>> 'Failed to fetch 
>> http://weewx.com/apt/pool/main/w/weewx/weewx_3.7.1-1_all.deb  404  Not 
>> Found'
>>
>
> this should be fixed now (23mar2017 10:50 us eastern time)
>
> sorry about the downtime
>

-- 
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.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[Thomas Keffer]

Glad that's working well for you, but I'd still like to know the answers to
my questions. It will help us diagnose future problems, or maybe even make
engineering changes.

-tk

On Thu, Mar 23, 2017 at 8:52 AM,  wrote:

> Matt,
>
> I added the " loop_on_init=true" to weewx.conf and that seemed to do it. I
> wasn't sure how to add the delay to weewx.service. I'll keep watch on it to
> be sure it restarts correctly. Thanks so much for the help, also Susan and
> Tom.
> Bob
>
> Last log:
>
> Mar 23 11:35:00 nuc weewx[853]: engine: Initializing weewx version 3.7.0
> Mar 23 11:35:00 nuc weewx[853]: engine: Using Python 2.7.12 (default, Nov
> 19 2016, 06:48:10) #012[GCC 5.4.0 20160609]
> Mar 23 11:35:00 nuc weewx[853]: engine: Platform
> Linux-4.8.0-41-generic-x86_64-with-Ubuntu-16.04-xenial
> Mar 23 11:35:00 nuc weewx[853]: engine: Locale is 'en_US.UTF-8'
> Mar 23 11:35:00 nuc weewx[853]: engine: pid file is /var/run/weewx.pid
> Mar 23 11:35:00 nuc weewx[1105]: engine: Using configuration file
> /home/weewx/weewx.conf
> Mar 23 11:35:00 nuc weewx[1105]: engine: Loading station type Vantage
> (weewx.drivers.vantage)
> Mar 23 11:35:00 nuc weewx[1105]: engine: Unable to load driver: [Errno 2]
> could not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
> '/dev/ttyUSB0'
> Mar 23 11:36:00 nuc weewx[1105]: engine: *retrying...*
> Mar 23 11:36:00 nuc weewx[1105]: engine: Using configuration file
> /home/weewx/weewx.conf
> Mar 23 11:36:00 nuc weewx[1105]: engine: Loading station type Vantage
> (weewx.drivers.vantage)
> Mar 23 11:36:00 nuc weewx[1105]: engine: StdConvert target unit is 0x1
> Mar 23 11:36:00 nuc weewx[1105]: engine: Archive will use data binding
> wx_binding
> Mar 23 11:36:00 nuc weewx[1105]: engine: Record generation will be
> attempted in 'hardware'
> Mar 23 11:36:00 nuc weewx[1105]: engine: Using archive interval of 900
> seconds (specified by hardware)
> Mar 23 11:36:00 nuc weewx[1105]: engine: Using binding 'wx_binding' to
> database 'weewx.sdb'
> Mar 23 11:36:00 nuc weewx[1105]: engine: Starting up weewx version 3.7.0
> Mar 23 11:36:00 nuc weewx[1105]: engine: Clock error is -1.61 seconds
> (positive is fast)
> Mar 23 11:36:00 nuc weewx[1105]: engine: Starting main packet loop.
>
>
>> --
> 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.
>

-- 
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.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[bgrattan]

Matt,

I added the " loop_on_init=true" to weewx.conf and that seemed to do it. I 
wasn't sure how to add the delay to weewx.service. I'll keep watch on it to 
be sure it restarts correctly. Thanks so much for the help, also Susan and 
Tom.
Bob

Last log:

Mar 23 11:35:00 nuc weewx[853]: engine: Initializing weewx version 3.7.0
Mar 23 11:35:00 nuc weewx[853]: engine: Using Python 2.7.12 (default, Nov 
19 2016, 06:48:10) #012[GCC 5.4.0 20160609]
Mar 23 11:35:00 nuc weewx[853]: engine: Platform 
Linux-4.8.0-41-generic-x86_64-with-Ubuntu-16.04-xenial
Mar 23 11:35:00 nuc weewx[853]: engine: Locale is 'en_US.UTF-8'
Mar 23 11:35:00 nuc weewx[853]: engine: pid file is /var/run/weewx.pid
Mar 23 11:35:00 nuc weewx[1105]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 23 11:35:00 nuc weewx[1105]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 23 11:35:00 nuc weewx[1105]: engine: Unable to load driver: [Errno 2] 
could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
'/dev/ttyUSB0'
Mar 23 11:36:00 nuc weewx[1105]: engine: *retrying...*
Mar 23 11:36:00 nuc weewx[1105]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 23 11:36:00 nuc weewx[1105]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Mar 23 11:36:00 nuc weewx[1105]: engine: StdConvert target unit is 0x1
Mar 23 11:36:00 nuc weewx[1105]: engine: Archive will use data binding 
wx_binding
Mar 23 11:36:00 nuc weewx[1105]: engine: Record generation will be 
attempted in 'hardware'
Mar 23 11:36:00 nuc weewx[1105]: engine: Using archive interval of 900 
seconds (specified by hardware)
Mar 23 11:36:00 nuc weewx[1105]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Mar 23 11:36:00 nuc weewx[1105]: engine: Starting up weewx version 3.7.0
Mar 23 11:36:00 nuc weewx[1105]: engine: Clock error is -1.61 seconds 
(positive is fast)
Mar 23 11:36:00 nuc weewx[1105]: engine: Starting main packet loop.


>

-- 
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.

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[Thomas Keffer]

Bob,

Before chasing theories, let's make sure we understand exactly what's in
the log.

1. Did the computer reboot somewhere between 15:29:02 and 15:29:33 on March
22?

2. At Mar 22 15:29:33 I am seeing three weewx processes: 810, 1025, and
1006. I can imagine their being two just after the daemon fork, but there
should never be three. Did you have another weewx process running?

3. Did the computer reboot between March 23 10:02:00 and 10:05:01?

General: if the computer was rebooting at the indicated times, we should be
seeing some evidence in the logs. Did you filter them in some way? If so,
please don't. In this case, we are looking at interactions between the OS
and weewx, so it's critical we see log entries from both.

-tk



On Thu, Mar 23, 2017 at 7:56 AM,  wrote:

> Tom,
>
> I have attached the weewx.log portion which contains the info you
> requested. The system is Ubuntu 16.04.1 running on an Intel i5 (Intel NUC
> box). I tried rebooting again this morning and had some new results:
>
> root@nuc:~# service weewx status
> ? weewx.service - weewx weather system
>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>Active: failed (Result: exit-code) since Thu 2017-03-23 10:05:01 EDT;
> 37s ago
>   Process: 1076 ExecStart=/home/weewx/bin/weewxd --daemon
> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited, status=4)
>  Main PID: 1076 (code=exited, status=4)
> Mar 23 10:05:01 nuc weewx[891]: engine: pid file is /var/run/weewx.pid
> Mar 23 10:05:01 nuc systemd[1]:* weewx.service: Supervising process 1076
> which is not our child. We'll most likely not notice when it exits.*
> Mar 23 10:05:01 nuc weewx[1076]: engine: Using configuration file
> /home/weewx/weewx.conf
> Mar 23 10:05:01 nuc weewx[1076]: engine: Loading station type Vantage
> (weewx.drivers.vantage)
> Mar 23 10:05:01 nuc weewx[1076]: import of driver failed: [Errno 2] could
> not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
> '/dev/ttyUSB0' ( Mar 23 10:05:01 nuc weewx[1076]: engine: Unable to load driver: [Errno 2]
> could not open port /dev/ttyUSB0: [Errno 2] No such file or directory:
> '/dev/ttyUSB0'
> Mar 23 10:05:01 nuc weewx[1076]:   Exiting...
> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Main process exited,
> code=exited, status=4/NOPERMISSION
> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Unit entered failed state.
> Mar 23 10:05:01 nuc systemd[1]: weewx.service: Failed with result
> 'exit-code'.
> 
> ? weewx.service - weewx weather system
>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>Active: failed (Result: timeout) since Thu 2017-03-23 10:08:16 EDT;
> 1min 14s ago
>   Process: 2348 ExecStart=/home/weewx/bin/weewxd --daemon
> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited,
> status=0/SUCCESS)
>  Main PID: 2348 (code=exited, status=0/SUCCESS)
> Mar 23 10:06:46 nuc weewx[2352]: restx: PWSWeather: Data for station N4MRV
> will be posted
> Mar 23 10:06:46 nuc weewx[2352]: restx: CWOP: Data for station N4MRV-1
> will be posted
> Mar 23 10:06:46 nuc weewx[2352]: restx: WOW: Data for station 964806001
> will be posted
> Mar 23 10:06:46 nuc weewx[2352]: restx: AWEKAS: Data will be uploaded for
> user bgrattan
> Mar 23 10:06:46 nuc weewx[2352]: engine: Starting up weewx version 3.7.0
> Mar 23 10:06:46 nuc weewx[2352]: engine: Clock error is -1.64 seconds
> (positive is fast)
> Mar 23 10:06:46 nuc weewx[2352]: engine: Starting main packet loop.
> Mar 23 10:08:16 nuc systemd[1]: weewx.service: State 'stop-sigterm' timed
> out. Killing.
> Mar 23 10:08:16 nuc systemd[1]: weewx.service: Unit entered failed state.
> Mar 23 10:08:16 nuc systemd[1]: weewx.service: Failed with result
> 'timeout'.
>
> In the first listing, ttyUSB0 didn't load fast enough (haven't seen this
> before). I restarted the service and it seems to start but crash on it's
> own (second listing). I restarted again and it seemed to take off and stay
> running. Susan's comment below seems to make sense that things that weewx
> needs aren't starting fast enough. Is there a way to initiate the restart
> but delay it to wait for what it needs?
> Thanks for your help and thanks to Susan who made the suggestion below.
> Bob
>
> On Wednesday, March 22, 2017 at 6:36:02 PM UTC-4, Tom Keffer wrote:
>
>> Hi, Bob
>>
>> What kind of operating system is this? I'm wondering if it is having a
>> reaction to the daemonizing strategy weewx uses.
>>
>> I would also like to see a bit more of the log, starting with the first
>> weewx log entry, through the 15:39:33 termination.
>>
>> -tk
>>
>> On Wed, Mar 22, 2017 at 12:52 PM,  wrote:
>>
>>> Andrew,
>>>
>>> I rebooted with debug on weewx and nothing showed up in syslog or
>>> weewx.log. I searched around for the "(/etc/systemd/system/*weewx.se
>>> rvice; disabled*; vendor 

Re: [weewx-user] Re: weewx doesn't start automatically after reboot

[mwall]

On Thursday, March 23, 2017 at 10:56:40 AM UTC-4, bgrattan wrote:
>
> Susan's comment below seems to make sense that things that weewx needs 
> aren't starting fast enough. Is there a way to initiate the restart but 
> delay it to wait for what it needs?
>

bob,

there are at least two strategies for dealing with unavailable resources:

1) configure your init system to deal with it.  in this case, you would 
modify the init system's configuration files to let it know that weewx 
should not be started until after the resource(s) are available.  for an 
rc/upstart system that would be /etc/init.d/weewx, for a systemd system 
that would be /etc/systemd/system/weewx.service. 

2) configure weewx to deal with it.  use the loop_on_init=true in 
weewx.conf to tell weewx that it should keep retrying during startup 
(normal behavior is to quit on startup when required resources are not 
available).

however, we should be sure that there is not a conflict between the way 
weewx daemonizes itself and the way systemd tries to 
assimilate^H^H^H^H^H^H^H^H^H^H manage weewx.  (sorry, the scars are still 
tender from fighting systemd on a cluster node with 24-cores and 10TB of 
disk)

m 

-- 
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.

Re: [weewx-user] Re: weird yscale behaviour?

[Thomas Keffer]

I'm sorry.

-tk

On Thu, Mar 23, 2017 at 8:00 AM, Paolo Benvenuto 
wrote:

> ymax is far bigger than it must be, it should be 22 (as when yscale is
> unset), it's 36!
>
>
> don Paolo Benvenuto
>
> 2017-03-23 15:29 GMT+01:00 Thomas Keffer :
>
>> It works for me. What are you getting? And, what were you expecting?
>>
>> [image: Inline image 1]
>>
>> On Thu, Mar 23, 2017 at 7:24 AM, Paolo Benvenuto 
>> wrote:
>>
>>> Apparently it's in the correct position:
>>>
>>>
>>> [[day_images]]
>>> x_label_format = %k
>>> time_length = 133200# == 37 hours
>>>
>>> [[[daytemp]]]
>>> image_height = 400
>>> yscale = None, None, 2
>>> inTemp
>>> color = green
>>>
>>>
>>>
>>>
>>> Il giorno giovedì 23 marzo 2017 15:18:27 UTC+1, Tom Keffer ha scritto:

 Where in skin.conf are you setting yscale? See the specs for plot
 [[[dayrain]]] for an example.

 -tk

 On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto 
 wrote:

> In another graph where y ranges from 10 to 21 when yscale is not set,
> setting
>
> yscale = None, None, 2
>
> makes the graph have ymin = 10 and ymax = 30. None of the plotted
> lines raises above 21
>
> This is weirder...
>
>
>
> Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha
> scritto:
>>
>> Hi!
>>
>> In a temperature graph I'm setting
>>
>> yscale = None, None, 1
>>
>> I intend that this means that the "minimum tick interval" is 1
>> degree, but in the graphs where temperature ranges from -20 to 20 the
>> spacing between the lines is 5 degrees
>>
>> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't
>> weewx accept my value?
>>
>> And: is there a way to set the actual tick interval to 1 degree?
>>
>>
>>
>> --
> 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+...@googlegroups.com.
> 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 weewx-user+unsubscr...@googlegroups.com.
>>> 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/6gevHcrAoDk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> 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 weewx-user+unsubscr...@googlegroups.com.
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Version 3.7.1

[Thomas Keffer]

This version has fixes for some minor problems in V3.7.0.  Find it in the
usual places.

-tk

CHANGE LOG

Fixed log syntax in wmr100 and wmr9x8 drivers.


Emit Rapidfire cache info only when debug is level 3 or higher.  Thanks to
user Darryn Capes-Davis.

Fixed problem that prevented Rapidfire from being used with databases in
metric units. Fixes issue #230.

Set WOW `post_interval` in config dict instead of thread arguments so that
overrides are possible.  Thanks to user Kenneth Baker.

Distribute example code and example extensions in a single examples directory.
Ensure that the examples directory is included in the rpm and deb packages.

Fixed issue that prevented a port from being specified for MySQL installations.

MySQL error 2003 ("Can't connect to MySQL server...") now gets mapped to
`weedb.CannotConnectError`. PR #234.

By default, autocommit is now enabled for the MySQL driver. Fixes issue #237.

Highs and lows from LOOP packets were not being used in preference to archive
records in daily summaries. Fixed issue #239.

-- 
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.

Re: [weewx-user] Re: weird yscale behaviour?

[Paolo Benvenuto]

ymax is far bigger than it must be, it should be 22 (as when yscale is
unset), it's 36!


don Paolo Benvenuto

2017-03-23 15:29 GMT+01:00 Thomas Keffer :

> It works for me. What are you getting? And, what were you expecting?
>
> [image: Inline image 1]
>
> On Thu, Mar 23, 2017 at 7:24 AM, Paolo Benvenuto 
> wrote:
>
>> Apparently it's in the correct position:
>>
>>
>> [[day_images]]
>> x_label_format = %k
>> time_length = 133200# == 37 hours
>>
>> [[[daytemp]]]
>> image_height = 400
>> yscale = None, None, 2
>> inTemp
>> color = green
>>
>>
>>
>>
>> Il giorno giovedì 23 marzo 2017 15:18:27 UTC+1, Tom Keffer ha scritto:
>>>
>>> Where in skin.conf are you setting yscale? See the specs for plot
>>> [[[dayrain]]] for an example.
>>>
>>> -tk
>>>
>>> On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto 
>>> wrote:
>>>
 In another graph where y ranges from 10 to 21 when yscale is not set,
 setting

 yscale = None, None, 2

 makes the graph have ymin = 10 and ymax = 30. None of the plotted lines
 raises above 21

 This is weirder...



 Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha
 scritto:
>
> Hi!
>
> In a temperature graph I'm setting
>
> yscale = None, None, 1
>
> I intend that this means that the "minimum tick interval" is 1 degree,
> but in the graphs where temperature ranges from -20 to 20 the spacing
> between the lines is 5 degrees
>
> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't
> weewx accept my value?
>
> And: is there a way to set the actual tick interval to 1 degree?
>
>
>
> --
 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+...@googlegroups.com.
 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 weewx-user+unsubscr...@googlegroups.com.
>> 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/
> topic/weewx-user/6gevHcrAoDk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: debian 3.7.1-1 error 404 on install - apt error?

[mwall]

On Thursday, March 23, 2017 at 10:35:47 AM UTC-4, tempus wrote:
>
> 'Failed to fetch 
> http://weewx.com/apt/pool/main/w/weewx/weewx_3.7.1-1_all.deb  404  Not 
> Found'
>

this should be fixed now (23mar2017 10:50 us eastern time)

sorry about the downtime

-- 
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.

[weewx-user] Re: debian 3.7.1-1 error 404 on install - apt error?

[tempus]

I just had a 'sudo apt-get dist-upgrade' failure due to a 
'weewx_3.7.1-1_all.deb' missing file. A list of files unrelated to weewx 
failed to upgrade on a production server because 'weewx_3.7.1-1_all.deb' 
couldn't be found.  Re-running with '--fix-missing' allowed the unrelated 
upgrades to be installed with this error message:

'Failed to fetch 
http://weewx.com/apt/pool/main/w/weewx/weewx_3.7.1-1_all.deb  404  Not 
Found'

I will try again in a few hours.

Bob

On Thursday, March 23, 2017 at 2:08:55 AM UTC-7, Duncan Wilson wrote:
>
> Hi, i have just successfully built 2 Intel Edison Debian Weewx devices 
> connected to WU. When i tried to build the third i got an error at the 
> final stage of installing from debian install page:
>
> sudo apt-get install weewx 
>
>
> root@ubilinux:~# sudo apt-get install weewx
>
> Reading package lists... Done
>
> Building dependency tree
>
> Reading state information... Done
>
> The following extra packages will be installed:
>
>   libfreetype6 libjbig0 libjpeg62-turbo liblcms2-2 libpng12-0 libtiff5
>
>   libwebp5 libwebpdemux1 libwebpmux1 python-cheetah python-configobj
>
>   python-imaging python-pil python-serial python-six python-usb
>
> Suggested packages:
>
>   liblcms2-utils python-markdown python-pygments python-memcache
>
>   python-configobj-doc python-pil-doc python-pil-dbg python-wxgtk3.0
>
>   python-wxgtk sqlite ftp httpd python-pip
>
> The following NEW packages will be installed:
>
>   libfreetype6 libjbig0 libjpeg62-turbo liblcms2-2 libpng12-0 libtiff5
>
>   libwebp5 libwebpdemux1 libwebpmux1 python-cheetah python-configobj
>
>   python-imaging python-pil python-serial python-six python-usb weewx
>
> 0 upgraded, 17 newly installed, 0 to remove and 109 not upgraded.
>
> Need to get 1,197 kB/3,369 kB of archives.
>
> After this operation, 11.1 MB of additional disk space will be used.
>
> Do you want to continue? [Y/n] y
>
> Err http://weewx.com/apt/ squeeze/main weewx all 3.7.1-1
>
>   404  Not Found
>
> E: Failed to fetch 
> http://weewx.com/apt/pool/main/w/weewx/weewx_3.7.1-1_all.deb  404  Not 
> Found
>
>
> E: Unable to fetch some archives, maybe run apt-get update or try with 
> --fix-missing?
>
> root@ubilinux:~#
>
> i cant work out why it worked twice 12 hours ago but on the third attempt 
> it failed. Any hints? I have replicated the error by building a 4th device 
> and it stops with same error. I have run with --fix-missing but get the 
> same error re the weewx page.
>
>
>
>
>

-- 
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.

Re: [weewx-user] Re: weird yscale behaviour?

[Paolo Benvenuto]

Apparently it's in the correct position:


[[day_images]]
x_label_format = %k
time_length = 133200# == 37 hours

[[[daytemp]]]
image_height = 400
yscale = None, None, 2
inTemp
color = green




Il giorno giovedì 23 marzo 2017 15:18:27 UTC+1, Tom Keffer ha scritto:
>
> Where in skin.conf are you setting yscale? See the specs for plot 
> [[[dayrain]]] for an example.
>
> -tk
>
> On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto  > wrote:
>
>> In another graph where y ranges from 10 to 21 when yscale is not set, 
>> setting
>>
>> yscale = None, None, 2
>>
>> makes the graph have ymin = 10 and ymax = 30. None of the plotted lines 
>> raises above 21
>>
>> This is weirder...
>>
>>
>>
>> Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha 
>> scritto:
>>>
>>> Hi!
>>>
>>> In a temperature graph I'm setting
>>>
>>> yscale = None, None, 1
>>>
>>> I intend that this means that the "minimum tick interval" is 1 degree, 
>>> but in the graphs where temperature ranges from -20 to 20 the spacing 
>>> between the lines is 5 degrees
>>>
>>> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't 
>>> weewx accept my value?
>>>
>>> And: is there a way to set the actual tick interval to 1 degree?
>>>
>>>
>>>
>>> -- 
>> 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+...@googlegroups.com .
>> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weird yscale behaviour?

[Thomas Keffer]

It works for me. What are you getting? And, what were you expecting?

[image: Inline image 1]

On Thu, Mar 23, 2017 at 7:24 AM, Paolo Benvenuto 
wrote:

> Apparently it's in the correct position:
>
>
> [[day_images]]
> x_label_format = %k
> time_length = 133200# == 37 hours
>
> [[[daytemp]]]
> image_height = 400
> yscale = None, None, 2
> inTemp
> color = green
>
>
>
>
> Il giorno giovedì 23 marzo 2017 15:18:27 UTC+1, Tom Keffer ha scritto:
>>
>> Where in skin.conf are you setting yscale? See the specs for plot
>> [[[dayrain]]] for an example.
>>
>> -tk
>>
>> On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto 
>> wrote:
>>
>>> In another graph where y ranges from 10 to 21 when yscale is not set,
>>> setting
>>>
>>> yscale = None, None, 2
>>>
>>> makes the graph have ymin = 10 and ymax = 30. None of the plotted lines
>>> raises above 21
>>>
>>> This is weirder...
>>>
>>>
>>>
>>> Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha
>>> scritto:

 Hi!

 In a temperature graph I'm setting

 yscale = None, None, 1

 I intend that this means that the "minimum tick interval" is 1 degree,
 but in the graphs where temperature ranges from -20 to 20 the spacing
 between the lines is 5 degrees

 Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't
 weewx accept my value?

 And: is there a way to set the actual tick interval to 1 degree?



 --
>>> 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+...@googlegroups.com.
>>> 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 weewx-user+unsubscr...@googlegroups.com.
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weird yscale behaviour?

[Thomas Keffer]

Where in skin.conf are you setting yscale? See the specs for plot
[[[dayrain]]] for an example.

-tk

On Thu, Mar 23, 2017 at 6:41 AM, Paolo Benvenuto 
wrote:

> In another graph where y ranges from 10 to 21 when yscale is not set,
> setting
>
> yscale = None, None, 2
>
> makes the graph have ymin = 10 and ymax = 30. None of the plotted lines
> raises above 21
>
> This is weirder...
>
>
>
> Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha scritto:
>>
>> Hi!
>>
>> In a temperature graph I'm setting
>>
>> yscale = None, None, 1
>>
>> I intend that this means that the "minimum tick interval" is 1 degree,
>> but in the graphs where temperature ranges from -20 to 20 the spacing
>> between the lines is 5 degrees
>>
>> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't
>> weewx accept my value?
>>
>> And: is there a way to set the actual tick interval to 1 degree?
>>
>>
>>
>> --
> 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.
>

-- 
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.

[weewx-user] Re: debian 3.7.1-1 error 404 on install - apt error?

[Duncan Wilson]

Many thanks for the quick reply. I am assuming it is best for me to rebuild 
the 2 others i did last night as 3.7.1 ?

As they say - what are the chances of that happening! Great timing on my 
part!

Am a recent convert to Weewx - fantastic tool - thanks.

d



On Thursday, 23 March 2017 11:53:04 UTC, mwall wrote:
>
> duncan,
>
> as gary noted, we had a few last-second issues with the 3.7.1 release last 
> night; we had to remove the 3.7.1 release from the apt repository.
>
> meanwhile, you can install 3.7.0 by specifying the version number:
>
> apt-get install weewx=3.7.0
>
> m
>

-- 
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.

[weewx-user] Re: weird yscale behaviour?

[Paolo Benvenuto]

In another graph where y ranges from 10 to 21 when yscale is not set, 
setting

yscale = None, None, 2

makes the graph have ymin = 10 and ymax = 30. None of the plotted lines 
raises above 21

This is weirder...


Il giorno giovedì 23 marzo 2017 14:21:14 UTC+1, Paolo Benvenuto ha scritto:
>
> Hi!
>
> In a temperature graph I'm setting
>
> yscale = None, None, 1
>
> I intend that this means that the "minimum tick interval" is 1 degree, but 
> in the graphs where temperature ranges from -20 to 20 the spacing between 
> the lines is 5 degrees
>
> Ok, the 1 I set is the minimum, and thus 5 is ok, but... why doesn't weewx 
> accept my value?
>
> And: is there a way to set the actual tick interval to 1 degree?
>
>
>
>

-- 
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.

[weewx-user] Re: Raspbian (Jessie), weewx 3.71, WMR100 - stopped working

[Mike Mitchell]

As a last resort last night, I tried resetting the WMR100NA--unplugging it, 
removing and reinstalling the batteries, and plugging it back in and I got 
a nice surprise this morning--I see my weather reports posted to WU and 
APRS! I guess I went a little overboard on the upgrading to resolve this, 
but at least I am on the latest version of Raspbian and weewx now. I still 
need to resolve some issues with publishing to apache2 (but I am a lot less 
concerned about that.

-- 
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.

[weewx-user] Re: Weewx Automatic Update

[mwall]

On Thursday, March 23, 2017 at 7:50:06 AM UTC-4, david wrote:
>
> When I started using Weewx a few weeks ago (v3.6.2) it would automatically 
> update my web page. Then along came v3.7.0 which I updated to and that was 
> a 
> disaster. To fix that problem I did a clean reinstall of v3.6.2 and since 
> then there has been no automatic updating of my web page. 
>
> Any ideas as to how I can get my web page to automatically update again. 
>

impossible to say definitively without seeing the logs.

what kind of hardware?  are you updating a local web page or something 
remote?  using ftp, rsync or some other mechanism?

sorry that 3.7.0 was a stinker for you - there issues with wmr100 and 
wmr9x8 drivers, and mysql, all fixed in 3.7.1.

if you hit some other problem, please provide the details so we can fix it.

m

-- 
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.

[weewx-user] Re: debian 3.7.1-1 error 404 on install - apt error?

[mwall]

duncan,

as gary noted, we had a few last-second issues with the 3.7.1 release last 
night; we had to remove the 3.7.1 release from the apt repository.

meanwhile, you can install 3.7.0 by specifying the version number:

apt-get install weewx=3.7.0

m

-- 
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.

[weewx-user] Weewx Automatic Update

[david]

When I started using Weewx a few weeks ago (v3.6.2) it would automatically
update my web page. Then along came v3.7.0 which I updated to and that was a
disaster. To fix that problem I did a clean reinstall of v3.6.2 and since
then there has been no automatic updating of my web page.

Any ideas as to how I can get my web page to automatically update again.

TIA

.-.-.-.-.-.-.

David Taylor, Puniho
'the place to be; beneath the Mountain, beside the Sea'
http://www.pwx.kiwi
~
whose computer uses linux/open source software, featuring
Mageia release 5 (Official) for i586, kernel 4.4.50-desktop-2.mga5
~

-- 
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.

[weewx-user] debian 3.7.1-1 error 404 on install - apt error?

[gjr80]

Hi, 

There were a couple of last minute hiccups with the 3.7.1 release. Give it 24 
hours or wait for the release announcement and all should be fine. 

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.

[weewx-user] debian 3.7.1-1 error 404 on install - apt error?

[Duncan Wilson]

Hi, i have just successfully built 2 Intel Edison Debian Weewx devices 
connected to WU. When i tried to build the third i got an error at the 
final stage of installing from debian install page:

sudo apt-get install weewx 


root@ubilinux:~# sudo apt-get install weewx

Reading package lists... Done

Building dependency tree

Reading state information... Done

The following extra packages will be installed:

  libfreetype6 libjbig0 libjpeg62-turbo liblcms2-2 libpng12-0 libtiff5

  libwebp5 libwebpdemux1 libwebpmux1 python-cheetah python-configobj

  python-imaging python-pil python-serial python-six python-usb

Suggested packages:

  liblcms2-utils python-markdown python-pygments python-memcache

  python-configobj-doc python-pil-doc python-pil-dbg python-wxgtk3.0

  python-wxgtk sqlite ftp httpd python-pip

The following NEW packages will be installed:

  libfreetype6 libjbig0 libjpeg62-turbo liblcms2-2 libpng12-0 libtiff5

  libwebp5 libwebpdemux1 libwebpmux1 python-cheetah python-configobj

  python-imaging python-pil python-serial python-six python-usb weewx

0 upgraded, 17 newly installed, 0 to remove and 109 not upgraded.

Need to get 1,197 kB/3,369 kB of archives.

After this operation, 11.1 MB of additional disk space will be used.

Do you want to continue? [Y/n] y

Err http://weewx.com/apt/ squeeze/main weewx all 3.7.1-1

  404  Not Found

E: Failed to fetch 
http://weewx.com/apt/pool/main/w/weewx/weewx_3.7.1-1_all.deb  404  Not Found


E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

root@ubilinux:~#

i cant work out why it worked twice 12 hours ago but on the third attempt 
it failed. Any hints? I have replicated the error by building a 4th device 
and it stops with same error. I have run with --fix-missing but get the 
same error re the weewx page.




-- 
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.