Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thank you, I will give that a try!

On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:

> Reseat means to remove the logger from the Envoy and then reinstall the 
> logger in the Envoy. Sometimes you can get a dodgy connection between pins 
> on the logger and the socket in the Envoy (or console) and remaking the 
> connection by reseating can sometimes fix this.
>
> Gary 
>
> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>
>> Sorry, I don't quite understand what you mean by "reseat"?
>>
>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>>
>>> You can try reseating the logger.
>>>
>>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>>
 Neither TEST nor NVER returns anythingso, I guess I have a 
 connectivity problemwhich seems strange as  I did a straight swap out 
 of the Envoys!

 On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:

> If the cursor went down the screen, then the console is sending 
> something back. Make sure you press  a few times, then "TEST", all 
> in capital letters.
>
> You can also type "NVER". Again, all in capital letters. This will 
> return the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>
>> The screen shows blank when I get to the point above.after 
>> hitting enter a few times, it just sends the cursor down the 
>> screen..I 
>> tried typing TEST but no response...just a dark screen in the CL window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and then send 
>>> TEST as per the wiki article 
>>> ?
>>>  
>>> You should get a response from the Envoy.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo killall screen
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 11:00:42

 Press CTRL-A Z for help on special keys


 On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
 wrote:

> Monmul, we have not definitively heard whether or not you are able 
> to do the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command 
> with 'sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: 
>> Initializing weewx version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using 
>> Python 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 
>> 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
>> system: weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: 
>> Initializing engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Reseat means to remove the logger from the Envoy and then reinstall the 
logger in the Envoy. Sometimes you can get a dodgy connection between pins 
on the logger and the socket in the Envoy (or console) and remaking the 
connection by reseating can sometimes fix this.

Gary 

On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:

> Sorry, I don't quite understand what you mean by "reseat"?
>
> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>
>> You can try reseating the logger.
>>
>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>
>>> Neither TEST nor NVER returns anythingso, I guess I have a 
>>> connectivity problemwhich seems strange as  I did a straight swap out 
>>> of the Envoys!
>>>
>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>>>
 If the cursor went down the screen, then the console is sending 
 something back. Make sure you press  a few times, then "TEST", all 
 in capital letters.

 You can also type "NVER". Again, all in capital letters. This will 
 return the firmware version number.

 If neither of those work, then you have a connectivity problem.


 On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after hitting 
> enter a few times, it just sends the cursor down the screen..I tried 
> typing TEST but no response...just a dark screen in the CL window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then send 
>> TEST as per the wiki article 
>> ?
>>  
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 Monmul, we have not definitively heard whether or not you are able 
 to do the test listed under *Establishing connectivity 
 *
  in 
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the command 
 with 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
> system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
> weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
> /var/run/weewx.pid
> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
> system: weewx.
> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
> system.
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: 
> Initializing engine
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 
> weewx.drivers.vantage: Driver version is 3.2.1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 
> weewx.drivers.vantage: Option loop_request=1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Sorry, I don't quite understand what you mean by "reseat"?

On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:

> You can try reseating the logger.
>
> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>
>> Neither TEST nor NVER returns anythingso, I guess I have a 
>> connectivity problemwhich seems strange as  I did a straight swap out 
>> of the Envoys!
>>
>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>>
>>> If the cursor went down the screen, then the console is sending 
>>> something back. Make sure you press  a few times, then "TEST", all 
>>> in capital letters.
>>>
>>> You can also type "NVER". Again, all in capital letters. This will 
>>> return the firmware version number.
>>>
>>> If neither of those work, then you have a connectivity problem.
>>>
>>>
>>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>>
 The screen shows blank when I get to the point above.after hitting 
 enter a few times, it just sends the cursor down the screen..I tried 
 typing TEST but no response...just a dark screen in the CL window.


 On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send 
> TEST as per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are able 
>>> to do the test listed under *Establishing connectivity 
>>> *
>>>  in 
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the command 
>>> with 'sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
 system: weewx.
 Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
 system.
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
 engine
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Driver version is 3.2.1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Option loop_request=1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
 from fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
 lease
 Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #0 failed
 Feb 26 16:31:40 WeatherPi weewx[17971] 

Re: [weewx-user] Rest Service for OpenSenseMap

[Tom Keffer]

Not sure why you did an override of the get_request() method but, other
than that, your extension looks great!

No special "QC" needed to list something in the wiki. Just edit the home
page and list it yourself.

On Sat, Feb 27, 2021 at 10:35 AM sbar...@gmail.com 
wrote:

> Hi,
>
> For those interested, I have just made a Weewx rest extension to publish
> your measures to OpenSenseMap (https://opensensemap.org).
>
> The aim being to publish measures from a PM sensor, that I intend to add
> to my weewx station.
>
> The extension is available on GitHub :
> https://github.com/sbsrouteur/weewx-opensensemap
>
> I do not know if the code quality will qualify for being listed in the
> weewx wiki for extension.
>
> Just hope it helps.
>
> Regards,
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f90d3460-2e3a-4e6e-9f9c-8804425ef600n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBOPKWNSW5Da3o3%3DwfbXoQTB%2B31wnaYgy3Pxni6hDxN3A%40mail.gmail.com.

[weewx-user] Re: SQLite schema report

[vince]

I'd suggest your commentary is more than a little bit unfair and 
inaccurate, and I'll leave it at that.

Weewx by default uses an underlying sqlite3 database and puts its readings 
into an 'archive' table that has a large number of fields for the actual 
weather measurements.

CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
`usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `altimeter` REAL, 
`appTemp` REAL, `appTemp1` REAL, `barometer` REAL, `batteryStatus1` REAL, 
`batteryStatus2` REAL, `batteryStatus3` REAL, `batteryStatus4` REAL, 
`batteryStatus5` REAL, `batteryStatus6` REAL, `batteryStatus7` REAL, 
`batteryStatus8` REAL, `cloudbase` REAL, `co` REAL, `co2` REAL, 
`consBatteryVoltage` REAL, `dewpoint` REAL, `dewpoint1` REAL, `ET` REAL, 
`extraHumid1` REAL, `extraHumid2` REAL, `extraHumid3` REAL, `extraHumid4` 
REAL, `extraHumid5` REAL, `extraHumid6` REAL, `extraHumid7` REAL, 
`extraHumid8` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` 
REAL, `extraTemp4` REAL, `extraTemp5` REAL, `extraTemp6` REAL, `extraTemp7` 
REAL, `extraTemp8` REAL, `forecast` REAL, `hail` REAL, `hailBatteryStatus` 
REAL, `hailRate` REAL, `heatindex` REAL, `heatindex1` REAL, `heatingTemp` 
REAL, `heatingVoltage` REAL, `humidex` REAL, `humidex1` REAL, `inDewpoint` 
REAL, `inHumidity` REAL, `inTemp` REAL, `inTempBatteryStatus` REAL, 
`leafTemp1` REAL, `leafTemp2` REAL, `leafWet1` REAL, `leafWet2` REAL, 
`lightning_distance` REAL, `lightning_disturber_count` REAL, 
`lightning_energy` REAL, `lightning_noise_count` REAL, 
`lightning_strike_count` REAL, `luminosity` REAL, `maxSolarRad` REAL, `nh3` 
REAL, `no2` REAL, `noise` REAL, `o3` REAL, `outHumidity` REAL, `outTemp` 
REAL, `outTempBatteryStatus` REAL, `pb` REAL, `pm10_0` REAL, `pm1_0` REAL, 
`pm2_5` REAL, `pressure` REAL, `radiation` REAL, `rain` REAL, 
`rainBatteryStatus` REAL, `rainRate` REAL, `referenceVoltage` REAL, 
`rxCheckPercent` REAL, `signal1` REAL, `signal2` REAL, `signal3` REAL, 
`signal4` REAL, `signal5` REAL, `signal6` REAL, `signal7` REAL, `signal8` 
REAL, `snow` REAL, `snowBatteryStatus` REAL, `snowDepth` REAL, 
`snowMoisture` REAL, `snowRate` REAL, `so2` REAL, `soilMoist1` REAL, 
`soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, `soilTemp1` REAL, 
`soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, `supplyVoltage` REAL, 
`txBatteryStatus` REAL, `UV` REAL, `uvBatteryStatus` REAL, 
`windBatteryStatus` REAL, `windchill` REAL, `windDir` REAL, `windGust` 
REAL, `windGustDir` REAL, `windrun` REAL, `windSpeed` REAL);

If you look at the beginning of the line, you'll see the unique key is the 
dateTime (seconds since the unix epoch).

There are also a number of additional sqlite3 tables created, one per item 
above, with the dateTime for the record, the max/min for that measurement, 
when the max/min occurred, and also for things that are accumulated a 
running total.

CREATE TABLE archive_day_inTemp (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);

These tables are not connected in any way at the database level, they're 
individual tables.  They're also using the dateTime of the record as the 
primary key for the records in the table.

Weewx handles the heavy lifting for keeping the summary tables up to date 
from the data in the archive table.   When you see people who ask how to 
clear bad data from their (archive table in the) database, they are 
generally told to 'drop daily' (which deletes the summary tables) and 
'rebuild daily' (which regenerates the summary tables from the 
hand-modified archive table).

That help any ? 

I guess I'm kinda speechless re: using a drawing tool to visualize a 
database nor really what you're trying to do.   Perhaps the tool you want 
to use is google and going through the sqlite3 documentation online to 
better understand how to reverse engineer and examine a sqlite3 database, 
but I guess that's a bit harsh.  I'll assume that you're overthinking 
things a bit and looking for complexity where it doesn't exist.


   - archive table has all the 'meat'
   - summary archive_whatever tables have the pre-computed summaries of 
   max/min/sums of each element for later use
   


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c154915f-80da-40ca-ad9a-2d7d484d0890n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

You can try reseating the logger.

On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:

> Neither TEST nor NVER returns anythingso, I guess I have a
> connectivity problemwhich seems strange as  I did a straight swap out
> of the Envoys!
>
> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>
>> If the cursor went down the screen, then the console is sending something
>> back. Make sure you press  a few times, then "TEST", all in capital
>> letters.
>>
>> You can also type "NVER". Again, all in capital letters. This will return
>> the firmware version number.
>>
>> If neither of those work, then you have a connectivity problem.
>>
>>
>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>
>>> The screen shows blank when I get to the point above.after hitting
>>> enter a few times, it just sends the cursor down the screen..I tried
>>> typing TEST but no response...just a dark screen in the CL window.
>>>
>>>
>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>>
 That’s a better start, did you hit enter a few times and then send TEST
 as per the wiki article
 ?
 You should get a response from the Envoy.

 Gary

 On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
> /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com
> wrote:
>
>> Monmul, we have not definitively heard whether or not you are able to
>> do the test listed under *Establishing connectivity
>> *
>>  in
>> the Wiki.That is an essential first step.
>>
>> Use either screen or minicom. You may have to preface the command
>> with 'sudo'. For example,
>>
>>
>> *sudo screen /dev/ttyUSB0 19200*
>>
>> -tk
>>
>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>
>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather
>>> system...
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing
>>> weewx version 4.4.0
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is
>>> 'en_NZ.UTF-8'
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather
>>> system: weewx.
>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather
>>> system.
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing
>>> engine
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Driver version is 3.2.1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Option loop_request=1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
>>> from fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6
>>> lease
>>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #0 failed
>>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #1 failed
>>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #2 failed
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
>>> from fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:45 

Re: [weewx-user] Saving database etc to external drive

[Les Niles]

I just put everything on the SSD, so there’s no SD card to fail.  It turned out 
to be really easy (running Debian Buster):

1. With the RPi set up on an SD card, shut down, plug in the SSD, and start up 
the RPi.  Don’t try to mount it or anything; if the system tries to mount it 
automatically, tell it no. 
2. Figure out what “device” is associated with the SSD.  It’s probably /dev/sda 
as long as you don’t have any other storage like a USB stick. (If you do, take 
it out.) Running “fdisk /dev/sda” is a good way to check — a “p” command should 
show a storage device of the correct size.
3. Shut down weewx, any database, and any other services that aren’t necessary 
for running the OS.  Probably the best thing is to boot into single-user mode, 
but I didn’t bother with that.  The important thing is to make sure weewx (and 
mysql, if you use it) are shut down.  
4. Copy the image of the SD card to the SSD.  dd bs=1M if=/dev/mmcblk0 
of=/dev/sda should do it, assuming your SD card is /dev/mmblk0 and the SSD is 
/dev/sda. 
5. Then shut down, remove the SD card, and start the RPi back up.  It should 
just boot from the SSD, and look just like it did before.  The last step is to 
launch raspi-config and run “Expand Filesystem" from the Advanced menu to 
resize the filesystem to use the available space on the SSD.  For some reason I 
had to do this twice; the first time only got about 90% of the space.  Note 
that you need to reboot after each resize.  

This worked for me on an RPi 3 B+, and should be fine on a 4.  It may not work 
on pre-3 versions.  Also, you should probably do an update/full-upgrade before 
starting, in part to make sure you have the latest firmware.  

  -Les



> On 27 Feb 2021, at 16:16, Ken Asmus  wrote:
> 
> I am a very new user of Raspberry Pi and a LINUX neophyte!
> 
> I have WeeWx running now on my RPI4 and it is working fine.
> 
> I have read in numerous locations about the limited life of the micro SD 
> cards. So I acquired and mounted an external SSD drive to my RPI4.
> 
> But how do I save the database and any other files that are are being swapped 
> to the SD card to the SSD to decrease wear on the SD card?
> 
> Any guidance will be appreciated.
> 
> Thanks
> Ken
> 
> 
> -- 
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6f74a17e-080a-4889-8475-35bd3b25e9acn%40googlegroups.com
>  
> .

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2982F601-E15E-46D2-A5FF-3B772CDD3866%402pi.org.

[weewx-user] Re: Saving database etc to external drive

[vince]

On Saturday, February 27, 2021 at 4:16:03 PM UTC-8 ken@gmail.com wrote:

> I am a very new user of Raspberry Pi and a LINUX neophyte!
>
>
If you're willing to invest some of your time and do some free self-paced 
training, one course that over 675,000 people have taken 
is https://www.edx.org/course/introduction-to-linux - it will definitely 
help make Linux less of an unknown.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0edc7836-682f-48ca-a4e9-51bd07cf7a66n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Neither TEST nor NVER returns anythingso, I guess I have a connectivity 
problemwhich seems strange as  I did a straight swap out of the Envoys!

On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:

> If the cursor went down the screen, then the console is sending something 
> back. Make sure you press  a few times, then "TEST", all in capital 
> letters.
>
> You can also type "NVER". Again, all in capital letters. This will return 
> the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>
>> The screen shows blank when I get to the point above.after hitting 
>> enter a few times, it just sends the cursor down the screen..I tried 
>> typing TEST but no response...just a dark screen in the CL window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and then send TEST 
>>> as per the wiki article 
>>> ?
>>>  
>>> You should get a response from the Envoy.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo killall screen
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 11:00:42

 Press CTRL-A Z for help on special keys


 On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
 wrote:

> Monmul, we have not definitively heard whether or not you are able to 
> do the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command 
> with 'sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
>> weewx version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
>> system: weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
>> engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
>> lease
>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #1 failed
>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #2 failed
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
>> lease
>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #3 failed

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

If the cursor went down the screen, then the console is sending something
back. Make sure you press  a few times, then "TEST", all in capital
letters.

You can also type "NVER". Again, all in capital letters. This will return
the firmware version number.

If neither of those work, then you have a connectivity problem.


On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after hitting
> enter a few times, it just sends the cursor down the screen..I tried
> typing TEST but no response...just a dark screen in the CL window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then send TEST
>> as per the wiki article
>> ?
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>>>
 Monmul, we have not definitively heard whether or not you are able to
 do the test listed under *Establishing connectivity
 *
  in
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the command with
 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather
> system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing
> weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is
> 'en_NZ.UTF-8'
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is
> /var/run/weewx.pid
> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system:
> weewx.
> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather
> system.
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing
> engine
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading
> station type Vantage (weewx.drivers.vantage)
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Driver version is 3.2.1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Option loop_request=1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
> from fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #0 failed
> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #1 failed
> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #2 failed
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
> from fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #3 failed
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage:
> Unable to wake up console
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of
> driver failed: Unable to wake up Vantage console ( 'weewx.WakeupError'>)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:
>    Traceback (most recent call last):
> Feb 26 16:31:48 

[weewx-user] Saving database etc to external drive

[Ken Asmus]

I am a very new user of Raspberry Pi and a LINUX neophyte!

I have WeeWx running now on my RPI4 and it is working fine.

I have read in numerous locations about the limited life of the micro SD 
cards. So I acquired and mounted an external SSD drive to my RPI4.

But how do I save the database and any other files that are are being 
swapped to the SD card to the SSD to decrease wear on the SD card?

Any guidance will be appreciated.

Thanks
Ken

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6f74a17e-080a-4889-8475-35bd3b25e9acn%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

The screen shows blank when I get to the point above.after hitting 
enter a few times, it just sends the cursor down the screen..I tried 
typing TEST but no response...just a dark screen in the CL window.


On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send TEST as 
> per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are able to do 
>>> the test listed under *Establishing connectivity 
>>> *
>>>  in 
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the command with '
>>> sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
 weewx.
 Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
 engine
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Driver version is 3.2.1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Option loop_request=1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #0 failed
 Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #1 failed
 Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #2 failed
 Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #3 failed
 Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
 Unable to wake up console
 Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
 driver failed: Unable to wake up Vantage console (>>> 'weewx.WakeupError'>)
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
 Traceback (most recent call last):
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
   File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
 self.console = loader_function(config_dict, self)
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
 Feb 26 16:31:48 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

That’s a better start, did you hit enter a few times and then send TEST as 
per the wiki article 
?
 
You should get a response from the Envoy.

Gary

On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>
>> Monmul, we have not definitively heard whether or not you are able to do 
>> the test listed under *Establishing connectivity 
>> *
>>  in 
>> the Wiki.That is an essential first step.
>>
>> Use either screen or minicom. You may have to preface the command with '
>> sudo'. For example,
>>
>>
>> *sudo screen /dev/ttyUSB0 19200*
>>
>> -tk
>>
>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>
>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>>> system...
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx 
>>> version 4.4.0
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>>> 'en_NZ.UTF-8'
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
>>> weewx.
>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
>>> engine
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Driver version is 3.2.1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Option loop_request=1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #0 failed
>>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #1 failed
>>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #2 failed
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #3 failed
>>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
>>> Unable to wake up console
>>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
>>> driver failed: Unable to wake up Vantage console (>> 'weewx.WakeupError'>)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> Traceback (most recent call last):
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> self.console = loader_function(config_dict, self)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> return VantageService(engine, config_dict)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> Vantage.__init__(self, 

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Also, i'll try to just document the base and extended schema's to give a 
good base model. 
p.s., I'm using Visio as it's the tools i've used for years. If you have a 
suggestion for another tool, let me know and i'll see if i can 
load/install/use that tool. 

On Saturday, February 27, 2021 at 2:33:01 PM UTC-8 David Prellwitz wrote:

> Vince - I did all of that and the schema view is bare, i.e., it's still a 
> whole lot of nothing  other than the field names - and it's not complete 
> (or even close). I've run a Visio Data Model on Weewx.sdb (my running copy) 
> and found 114 separate tables; many matching field names. All with the same 
> PK and little - if any - SK/FK to differentiate what device/station 
> generated that instance of data. And, all without (relationship) links. All 
> without documentation or a word anywhere as to what some or most of the 
> tables are for and/or pertaining to. 
>
> So, rather than slogging through a morass of blogs, texts and various 
> thousands of pages to try to figure out what most of those tables are for, 
> i'm okay with adding notes and documentation to my Visio workspace and 
> publish that info as i complete each piece. I just need people to send me, 
> or provide links to, any specific documents describing these tables. 
> Better, if something exists that shows some/most of this info, please 
> provide it. 
>
> On Thursday, February 25, 2021 at 2:17:50 PM UTC-8 vince wrote:
>
>> echo ".schema" | sqlite3 mydatabasename.sdb
>>
>> or look at 
>> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py 
>> for the default schema for current v4 weewx.
>>
>> On Thursday, February 25, 2021 at 1:48:45 PM UTC-8 david.a@gmail.com 
>> wrote:
>>
>>> Looking through both SQLite and Weewx documentation, i can't find a 
>>> reference to a tool or report that will take a existing SQLdb and display 
>>> the underlying DB's structure? I can see that wee-debug will give a listing 
>>> of fields and key's, but there's no references to the relationships 
>>> established for the exiting db. I ask because i'd like to understand how 
>>> the existing data maintains keys. i.e., if data is stored with the only 
>>> primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? 
>>> That would allow me to store multiple occurrences of epochDT, but different 
>>> devices. that would allow me to store data from devices as raw data and 
>>> data from WF (or other weather services) corrected data concurrently. It 
>>> would also solve the often-mentioned "What's raw data and what has WF 
>>> 'conditioned' data in my SQLdb?" issues.
>>> /David
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a4d7e4d2-60bb-48cc-9faa-ee8843699fbfn%40googlegroups.com.

[weewx-user] Re: SQLite schema report

[David Prellwitz]

Vince - I did all of that and the schema view is bare, i.e., it's still a 
whole lot of nothing  other than the field names - and it's not complete 
(or even close). I've run a Visio Data Model on Weewx.sdb (my running copy) 
and found 114 separate tables; many matching field names. All with the same 
PK and little - if any - SK/FK to differentiate what device/station 
generated that instance of data. And, all without (relationship) links. All 
without documentation or a word anywhere as to what some or most of the 
tables are for and/or pertaining to. 

So, rather than slogging through a morass of blogs, texts and various 
thousands of pages to try to figure out what most of those tables are for, 
i'm okay with adding notes and documentation to my Visio workspace and 
publish that info as i complete each piece. I just need people to send me, 
or provide links to, any specific documents describing these tables. 
Better, if something exists that shows some/most of this info, please 
provide it. 

On Thursday, February 25, 2021 at 2:17:50 PM UTC-8 vince wrote:

> echo ".schema" | sqlite3 mydatabasename.sdb
>
> or look at 
> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py 
> for the default schema for current v4 weewx.
>
> On Thursday, February 25, 2021 at 1:48:45 PM UTC-8 david.a@gmail.com 
> wrote:
>
>> Looking through both SQLite and Weewx documentation, i can't find a 
>> reference to a tool or report that will take a existing SQLdb and display 
>> the underlying DB's structure? I can see that wee-debug will give a listing 
>> of fields and key's, but there's no references to the relationships 
>> established for the exiting db. I ask because i'd like to understand how 
>> the existing data maintains keys. i.e., if data is stored with the only 
>> primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? 
>> That would allow me to store multiple occurrences of epochDT, but different 
>> devices. that would allow me to store data from devices as raw data and 
>> data from WF (or other weather services) corrected data concurrently. It 
>> would also solve the often-mentioned "What's raw data and what has WF 
>> 'conditioned' data in my SQLdb?" issues.
>> /David
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8ae243bf-0fa0-4844-a582-38f40fefe522n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo killall screen
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 11:00:42

Press CTRL-A Z for help on special keys


On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:

> Monmul, we have not definitively heard whether or not you are able to do 
> the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command with '
> sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx 
>> version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 2.7.13 
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
>> weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #0 failed
>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #1 failed
>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #2 failed
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #3 failed
>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
>> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>> Traceback (most recent call last):
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   self._setup()
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
>> Feb 26 16:31:48 WeatherPi 

[weewx-user] Rest Service for OpenSenseMap

[sbar...@gmail.com]

Hi, 

For those interested, I have just made a Weewx rest extension to publish 
your measures to OpenSenseMap (https://opensensemap.org).

The aim being to publish measures from a PM sensor, that I intend to add to 
my weewx station.

The extension is available on GitHub 
: https://github.com/sbsrouteur/weewx-opensensemap

I do not know if the code quality will qualify for being listed in the 
weewx wiki for extension.

Just hope it helps.

Regards,


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f90d3460-2e3a-4e6e-9f9c-8804425ef600n%40googlegroups.com.

Re: [weewx-user] wee_reports picks up extensions.py delay

[Paul Dunphy]

 Thanks for the quick reply, Tom.  This makes sense.  I had the 45 
seconds in there from some debugging 6-8 months ago and I really don't 
need it anymore.  Just removed it.


- Paul VE1DX

On 2021-02-27 12:09 p.m., Tom Keffer wrote:
Unfortunately, wee_reports has to load extensions.py, because there 
might be some user extensions in there, which it might need for the 
reports (for example, an xtypes extension). So, whatever is in there, 
is going to get executed.


I no longer think an arbitrary 45 second sleep is such a good idea. 
The engine already has something that causes it to wait until the time 
is greater than the timestamp on weewx.conf, so that should give some 
measure of protection against clock slew. But, the best way to 
approach the problem is through systemd time synchronizations.


If you really want to sleep, then it's probably best done with a WeeWX 
extension that's bound to the STARTUP event.




On Sat, Feb 27, 2021 at 7:56 AM WindnFog > wrote:


Here's an oddity.  To delay weewx from starting for 45 seconds
after a reboot, I used Tom's 2019 suggestion of putting a delay of
45 in /usr/share/weewx/user/extensions.py . . . and this works
well, except it also kicks in when you run wee_reports:

*sudo wee_reports
^CTraceback (most recent call last):
  File "/usr/share/weewx/wee_reports", line 16, in 
    import user.extensions
  File "/usr/share/weewx/user/extensions.py", line 20, in 
    time.sleep(45)
KeyboardInterrupt*   <--- I ctrl-C'ed out of this after 25-30 seconds.

Is there any way to change the code so that wee_reports doesn't
execute the time.sleep(45) command?

- Paul VE1DX
-- 
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
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/1c121d0d-e909-425e-b532-7d79fc2d9954n%40googlegroups.com

.

--
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/kMMYGq5gC6E/unsubscribe 
.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDqK-0aNM6SjaHYgx9eiAR465rTUotYYe6pJ-05-%3De0zQ%40mail.gmail.com 
.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b9d0931c-5878-7ddf-8698-6c66e7ef61ae%40gmail.com.

Re: [weewx-user] wee_reports picks up extensions.py delay

[Tom Keffer]

Unfortunately, wee_reports has to load extensions.py, because there might
be some user extensions in there, which it might need for the reports (for
example, an xtypes extension). So, whatever is in there, is going to get
executed.

I no longer think an arbitrary 45 second sleep is such a good idea. The
engine already has something that causes it to wait until the time is
greater than the timestamp on weewx.conf, so that should give some measure
of protection against clock slew. But, the best way to approach the problem
is through systemd time synchronizations.

If you really want to sleep, then it's probably best done with a WeeWX
extension that's bound to the STARTUP event.



On Sat, Feb 27, 2021 at 7:56 AM WindnFog  wrote:

> Here's an oddity.  To delay weewx from starting for 45 seconds after a
> reboot, I used Tom's 2019 suggestion of putting a delay of 45 in
> /usr/share/weewx/user/extensions.py . . . and this works well, except it
> also kicks in when you run wee_reports:
>
>
>
>
>
>
>
> *sudo wee_reports^CTraceback (most recent call last):  File
> "/usr/share/weewx/wee_reports", line 16, in import
> user.extensions  File "/usr/share/weewx/user/extensions.py", line 20, in
> time.sleep(45)KeyboardInterrupt*   <--- I ctrl-C'ed out of
> this after 25-30 seconds.
>
> Is there any way to change the code so that wee_reports doesn't execute
> the time.sleep(45) command?
>
> - Paul VE1DX
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1c121d0d-e909-425e-b532-7d79fc2d9954n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDqK-0aNM6SjaHYgx9eiAR465rTUotYYe6pJ-05-%3De0zQ%40mail.gmail.com.

[weewx-user] wee_reports picks up extensions.py delay

[WindnFog]

Here's an oddity.  To delay weewx from starting for 45 seconds after a 
reboot, I used Tom's 2019 suggestion of putting a delay of 45 in 
/usr/share/weewx/user/extensions.py . . . and this works well, except it 
also kicks in when you run wee_reports:







*sudo wee_reports^CTraceback (most recent call last):  File 
"/usr/share/weewx/wee_reports", line 16, in import 
user.extensions  File "/usr/share/weewx/user/extensions.py", line 20, in 
time.sleep(45)KeyboardInterrupt*   <--- I ctrl-C'ed out of this 
after 25-30 seconds.

Is there any way to change the code so that wee_reports doesn't execute the 
time.sleep(45) command?

- Paul VE1DX

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1c121d0d-e909-425e-b532-7d79fc2d9954n%40googlegroups.com.

Re: [weewx-user] Running Klimalogg and Fine Offset in one weewx session?

[Maarten Weerman]

Hello Rainer,

Thanks a lot for that very helpful post, it works now.



Rainer Lang  schrieb am Mo., 22. Feb. 2021, 21:23:

> the Klimalogg Pro database consists of two databases (default names:
> weewx.sdb and weewx-kl.sdb) - they will have of course be located in a
> different directory from your standard weewx installation if you keep the
> database names.
> The installation will not run with the weewx-kl.sdb only - even though the
> archived data will be in weewx-kl.sdb.
> I found that out the hard way thinking for a restore only the weewx-kl.sdb
> was necessary. Luckily the KLP has a 50,000 record internal storage which
> could be reloaded when starting from scratch again.
>
> You will have to run two separate instances of weewx and for each your
> SQLITE_ROOT should be different -  (if for you session = instance, then not
> one session).
>
> As they are/will be located in different directories fed by two separate
> weewx instances (with their own weewx.conf - e.g. fineoffset.conf and
> klp.conf), you don't need to rename the databases - but you can.
> maybe for a better recognition you should do this. (The weewx multi
> description uses the rename approach, see below)
>
> If in your wording session = one weewx installation on one server, then
> you are correct.
>
> By the way - I'm running both myself (weewx with GW1000 and weewx with
> Klimalogg Pro) - so far still on two separate RPi4s, but one of my next
> activities will be to move them onto one RPi4.
>
> There is a setup description on GitHub for running two stations and two
> weewx instances on one server - recently updated.
>
> https://github.com/weewx/weewx/wiki/weewx-multi
>
>
> On 22.02.2021 17:17, Maarten Weerman wrote:
>
> Hi all,
>
> I have weewx 4.4.0 already running with a Fine Offset Station and it works
> fine. I also have a TFA Klimalogg station with two external sensors. I've
> read out that it is possible to get data with a weewx Klimalogg driver and
> that it is also possible two run two stations in one weewx session.
>
> I have some questions: I've read that the table structure of the klimalogg
> database is different from the "normal" weewx.sdb database. Does that have
> any effect when running two stations in one weewx?
>
> And regarding the existing weewx.sdb table, do i have to rename it in e.g.
> "fineoffset.sdb" or can i keep the current name weewx.sdb? I still want to
> use my existing weewx.sdb database table for data from my Fine Offset
> Station and just add the "Klimalogg.sdb" database for the Klimalogg Pro.
>
> Best regards
>
> Georg
>
>
>
>
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAKEu0RNRcUiT%2B-bNQbsPnaMtZEisjuXDcHm9T0eju1L%2BnTDXcA%40mail.gmail.com
> 
> .
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/24a63a77-b826-1784-513c-0e3d775bb720%40gmail.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAKEu0ROVKWtF2t61RSV8hodomp0G%2BEuE0%2BHgcP__%3DY1P0Gp5AQ%40mail.gmail.com.

Re: [weewx-user] Bootstrap skin update preview

[Auchtermuchty Weather]

I found the answer when I looked at the code for WeeWx v4.4.0.  Old code 
simply has:

import Image

This needs amending to:

try:
from PIL import Image, ImageDraw
except ImportError:
import Image, ImageDraw

I had old code on a newly build SD card.


On Friday, 26 February 2021 at 12:17:28 UTC Auchtermuchty Weather wrote:

> I see the colour on first cell only problem is fixed, I like the new 
> images. I'll give it a go.
>
> BTW I had problems installing an earlier version as:
>
>1. import Image cause an error, and the way to resolve it (apt-get) in 
>the FAQ didn't work on a brand new Raspbian installation.  I suspect 
>systems that have been upgraded already had the necessary library.  This 
>URL seems to cover the necessary gound:  Why can't Python import Image 
>from PIL? - Stack Overflow 
>
> 
>2. Again probably because I started with a new Raspbian image, I 
>didn't have the necessary font loaded.  I put my solution to this in 
>'issues'.
>
> I've got a spare SD card, I think I might start over to install this as 
> I've messed around somewhat.  I copied the database over from my live 
> system to get realistic data rather than turn on the simulator.
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/546ad529-0a7e-48f1-b1fb-2ff70a2844d5n%40googlegroups.com.