Re: [weewx-user] Re: Weatherlink IP replacement

[Robin Hunt]

Thanks for all the responses, much appreciated!

On Thu, Nov 19, 2020 at 9:31 AM Karen K  wrote:

> I asked the support of Davis Instruments about local asscess. The answer
> was:
>
> "Both the EnviroMonitor IP and WeatherLink Live are strictly cloud based
> and you would not be able to access through your LAN."
>
> Nevertheless, I actually see no alternative to the WeatherLink Live
> device.
>
> Nicolas Peninguy schrieb am Mittwoch, 18. November 2020 um 21:13:36 UTC+1:
>
>> Hello,
>>
>> Le 11/18/20 à 2:07 PM, galfert a écrit :
>> > Davis pretty much discontinued the Weatherlink IP around the time they
>> > released the WeatherLink Live. My recommendation is to go with the
>> > WeatherLink Live.
>>
>> It took me some time to find relevant information on the Internet, so
>> may be this will be of some interest for someone.
>>
>> This thing embeds an HTTP server with a local API described here:
>>
>> https://weatherlink.github.io/weatherlink-live-local-api/
>>
>> There are some good things, like broadcast of live data or discovery
>> through mDNS.
>>
>>
>> BUT:
>>
>> Currently there is no local access to archive data, nor device health
>> data: https://github.com/weatherlink/weatherlink-live-local-api/issues
>>
>> This thing will be useless if for whatever reason using Davis
>> weatherlink.com service is not wanted or possible.
>>
>>
>> Regards,
>>
>> Nicolas
>>
>> --
> 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/xzkGqLi0Tdk/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/2c921c94-42df-4b3e-b74d-e8a6ac6f4982n%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/CAM08vJMg1OURMjryYssNO0QLVe%3D%3DgcUbFkr1h1Hsjt6UNPYTFw%40mail.gmail.com.

Re: [weewx-user] Re: Weatherlink IP replacement

[Karen K]

I asked the support of Davis Instruments about local asscess. The answer 
was:

"Both the EnviroMonitor IP and WeatherLink Live are strictly cloud based 
and you would not be able to access through your LAN."

Nevertheless, I actually see no alternative to the WeatherLink Live device. 

Nicolas Peninguy schrieb am Mittwoch, 18. November 2020 um 21:13:36 UTC+1:

> Hello,
>
> Le 11/18/20 à 2:07 PM, galfert a écrit :
> > Davis pretty much discontinued the Weatherlink IP around the time they 
> > released the WeatherLink Live. My recommendation is to go with the 
> > WeatherLink Live.
>
> It took me some time to find relevant information on the Internet, so 
> may be this will be of some interest for someone.
>
> This thing embeds an HTTP server with a local API described here:
>
> https://weatherlink.github.io/weatherlink-live-local-api/
>
> There are some good things, like broadcast of live data or discovery 
> through mDNS.
>
>
> BUT:
>
> Currently there is no local access to archive data, nor device health 
> data: https://github.com/weatherlink/weatherlink-live-local-api/issues
>
> This thing will be useless if for whatever reason using Davis 
> weatherlink.com service is not wanted or possible.
>
>
> Regards,
>
> Nicolas
>
>

-- 
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/2c921c94-42df-4b3e-b74d-e8a6ac6f4982n%40googlegroups.com.

[weewx-user] Integrating internal temp/humidity sensors to Weatherflow Tempest, possible?

[Chotechai Piyavongsiri]

I'm now using WH24 as my external all-in-one sensors which sends data to my 
Ecowitt GW1000. It has been working well with my weewx. Lately, the 
humidity sensor in WH24 reported erratic values, so I purchased Ecowitt 
external sensor WH32 to replace temp/humidity values reported from WH24, 
via Ecowitt GW1000.

I also install Weatherflow Tempest for a few months now running on a 
testing server with a separate weewx.

If I'm going to retire my WH24 and use my Tempest as my main external 
sensors, my questions are:
- can I integrate the GW1000 indoor temp/humidity sensors data with Tempest 
so that I still have internal temp/humidity reported on my weewx
- if not, any indoor sensor I could use with Tempest.
- what weewx driver will allow my weewx to display both Tempest and indoor 
data in real time (or, say 16s, interval).

Thank you.

-- 
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/e45ffc19-b166-44aa-b149-72cdf7ea0a87n%40googlegroups.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Greg from Oz]

You would test it the same way as if you configured using /dev/ttyUSB0 for 
example. 
You just use /dev/weather instead of /dev/ttyUSB0.
There is nothing special about it really. I just use this method as I have 
several usb devices on my server and I name them to reflect the application 
I am using so it is easier to know what device has been configured for that 
application.


On Thursday, 19 November 2020 at 00:54:50 UTC+11 lecoqacr...@gmail.com 
wrote:

> What is a good way to test the symlink rule to verify that it was created 
> correctly? There is the new file in /dev/weather but is there a more 
> complete way to test? thank you
>
> On Tuesday, November 17, 2020 at 7:29:08 PM UTC-6 Greg from Oz wrote:
>
>> I set my fineoffset rule to:
>>
>> SUBSYSTEM=="usb", ATTRS{idVendor}=="1941", ATTRS{idProduct}=="8021", 
>> MODE="0666", GROUP="plugdev", SYMLINK+="weather"
>>
>> That way it is always /dev/weather regardless of the ttyUsb it is 
>> attached to.
>>
>> ll /dev/weather 
>> lrwxrwxrwx 1 root root 15 Nov 17 09:26 /dev/weather -> bus/usb/002/002
>>
>> On Wednesday, 18 November 2020 at 12:14:53 UTC+11 tke...@gmail.com wrote:
>>
>>> Are you sure? Depending on what permissions the usb port has, you may 
>>> need to use sudo to run lsof:
>>>
>>> *sudo lsof /dev/ttyUSB0*
>>>
>>> Come to think of it, you may have to do that with minicom, too.
>>>
>>> Personally, I change the udev rule that governs permissions for usb 
>>> devices to give everyone access to the port. The rule that governs this is 
>>> most likely in the directory /lib/udev/rules.d, but which file it is in 
>>> depends on the operating system. I believe on Raspbian, it's in file 
>>> 91-permissions.rules, but it may be in 50-udev-default.rules.  Wherever 
>>> you find it, you want to change this
>>>
>>> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664"
>>>
>>> to this
>>>
>>> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
>>>
>>>
>>> -tk
>>>
>>> On Tue, Nov 17, 2020 at 3:07 PM bgra...@umw.edu  wrote:
>>>

 Thanks everyone, I think I have a bad logger (6540).
 On Tuesday, November 17, 2020 at 9:41:56 AM UTC-5 bgra...@umw.edu 
 wrote:

> root@raspberrypi:/home/pi# ll /dev/ttyUSB0
> crw-rw 1 root dialout 188, 0 Nov 16 17:48 /dev/ttyUSB0
>
>
> root@raspberrypi:/home/pi# lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
> /run/user/1000/gvfs
>   Output information may be incomplete.
>
> On Monday, November 16, 2020 at 8:43:34 PM UTC-5 tke...@gmail.com 
> wrote:
>
>> If it were a permissions problem, it would have said so. Same if 
>> modemmanager controlled the port. Still, it doesn't hurt to try lsof and 
>> see if anything else is using the port.
>>
>> *lsof /dev/ttyUSB0*
>>
>>
>>
>>
>> On Mon, Nov 16, 2020 at 5:36 PM Greg from Oz  
>> wrote:
>>
>>> Is the user running this in the dialout group? 
>>>
>>> On Tuesday, 17 November 2020 at 12:30:14 UTC+11 tke...@gmail.com 
>>> wrote:
>>>
 The only thing I can think of to try is to reseat the logger. 

 Unless, you actually have the serial version of the VantagePro and 
 are using a serial-to-usb converter. They are notoriously flakey. If 
 you 
 have a spare one, try that.

 If none of that works, call Davis.

 On Mon, Nov 16, 2020 at 5:04 PM bgra...@umw.edu  
 wrote:

> Yes, I did hit enter many times. Since dmesg said that the usb had 
> attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had 
> connected. I’m at a loss because everything was working...  Thanks.
>
> On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com 
> wrote:
>
>> OK, but did you hit  a few times before typing "TEST"? If 
>> so, you have a connectivity problem, not a WeeWX problem.
>>
>> But, you probably already knew that!
>>
>> -tk
>>
>> On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  
>> wrote:
>>
>>>
>>> I don’t remember the minicom string but it was the one posted to 
>>> test TEST. When I opened minicom it just sat there no echo on TEST 
>>> or VER. 
>>> No reply. Several reboots no results. /dev/ttyUSB0 is there but 
>>> does not 
>>> respond. Dmesg Seems to have found it.
>>> I checked all plugs and connections. Removed batteries from 
>>> console to reboot. Even tried new RS232/USB dongle. I have a main 
>>> ubuntu 
>>> linux pc running from the ISS so I know that’s working and sending 
>>> data. 
>>> The rpi is setup as a second console which was running weather34. 
>>> Thanks 
>>> Tom and Graham (you helped me in the days of wview).
>>> Bob
>>> 

Re: [weewx-user] Re: errors from power outage

[GCC Observatory]

The fix mentioned in that thread fixed the problem... thanks!

On Wednesday, November 18, 2020 at 5:59:07 PM UTC-5 tke...@gmail.com wrote:

> See if this thread 
>  
> helps.
>
> On Wed, Nov 18, 2020 at 2:52 PM GCC Observatory  
> wrote:
>
>> ah... that makes more sense...
>>
>> here's the output - I don't notice anything out of the norm:
>>
>>
>> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
>> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, 
>> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL, 
>> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL, 
>> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL, 
>> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation` 
>> REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL, 
>> `soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, 
>> `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL, 
>> `soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, 
>> `leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus` 
>> REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL, 
>> `heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL, 
>> `referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus` 
>> REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL, `appTemp` 
>> REAL, `windrun` REAL, `cloudbase` REAL, `owTemp0` REAL, `owTemp1` REAL, 
>> `owTemp2` REAL);
>> CREATE TABLE archive_day_barometer (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_pressure (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_altimeter (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> 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);
>> CREATE TABLE archive_day_outTemp (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_inHumidity (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_outHumidity (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_windSpeed (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_windDir (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_windGust (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_windGustDir (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_rainRate (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_rain (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
>> KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
>> INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_dewpoint (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_windchill (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_heatindex (dateTime INTEGER NOT NULL UNIQUE 
>> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
>> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
>> CREATE TABLE archive_day_ET (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
>> KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, 

Re: [weewx-user] Re: errors from power outage

[Tom Keffer]

See if this thread
 helps.

On Wed, Nov 18, 2020 at 2:52 PM GCC Observatory 
wrote:

> ah... that makes more sense...
>
> here's the output - I don't notice anything out of the norm:
>
>
> CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY,
> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL,
> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL,
> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL,
> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL,
> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation`
> REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL,
> `soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL,
> `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL,
> `soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL,
> `leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus`
> REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL,
> `heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL,
> `referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus`
> REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL, `appTemp`
> REAL, `windrun` REAL, `cloudbase` REAL, `owTemp0` REAL, `owTemp1` REAL,
> `owTemp2` REAL);
> CREATE TABLE archive_day_barometer (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_pressure (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_altimeter (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> 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);
> CREATE TABLE archive_day_outTemp (dateTime INTEGER NOT NULL UNIQUE PRIMARY
> KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count
> INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_inHumidity (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_outHumidity (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_windSpeed (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_windDir (dateTime INTEGER NOT NULL UNIQUE PRIMARY
> KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count
> INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_windGust (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_windGustDir (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_rainRate (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_rain (dateTime INTEGER NOT NULL UNIQUE PRIMARY
> KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count
> INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_dewpoint (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_windchill (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_heatindex (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_ET (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY,
> min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count
> INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_radiation (dateTime INTEGER NOT NULL UNIQUE
> PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum
> REAL, count INTEGER, wsum REAL, sumtime INTEGER);
> CREATE TABLE archive_day_UV 

Re: [weewx-user] Re: errors from power outage

[GCC Observatory]

ah... that makes more sense...

here's the output - I don't notice anything out of the norm:


CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
`usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, 
`pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL, 
`inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL, 
`windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL, 
`dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation` 
REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL, 
`soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, 
`leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL, 
`soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, 
`leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus` 
REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL, 
`heatingTemp` REAL, `heatingVoltage` REAL, `supplyVoltage` REAL, 
`referenceVoltage` REAL, `windBatteryStatus` REAL, `rainBatteryStatus` 
REAL, `outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL, `appTemp` 
REAL, `windrun` REAL, `cloudbase` REAL, `owTemp0` REAL, `owTemp1` REAL, 
`owTemp2` REAL);
CREATE TABLE archive_day_barometer (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_pressure (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_altimeter (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
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);
CREATE TABLE archive_day_outTemp (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_inHumidity (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_outHumidity (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_windSpeed (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_windDir (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_windGust (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_windGustDir (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_rainRate (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_rain (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_dewpoint (dateTime INTEGER NOT NULL UNIQUE PRIMARY 
KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_windchill (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_heatindex (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_ET (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY, 
min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_radiation (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum 
REAL, count INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_UV (dateTime INTEGER NOT NULL UNIQUE PRIMARY KEY, 
min REAL, mintime INTEGER, max REAL, maxtime INTEGER, sum REAL, count 
INTEGER, wsum REAL, sumtime INTEGER);
CREATE TABLE archive_day_extraTemp1 (dateTime INTEGER NOT NULL UNIQUE 
PRIMARY KEY, min REAL, mintime 

Re: [weewx-user] Re: errors from power outage

[John Kline]

There should be an echo in front of that .schema.
Also, you don’t need the sudo.

echo .schema | sqlite3 /var/lib/weewx/weewx.sdb

> On Nov 18, 2020, at 2:44 PM, GCC Observatory  wrote:
> 
> I'm not aware of the ".schema" command you mention...
> 
>> On Wednesday, November 18, 2020 at 5:19:31 PM UTC-5 vince wrote:
>> Try ".schema | sudo sqlite3 /var/lib/weewx/weewx.sdb" and see if you get all 
>> the various tables that are expected there, if I recall the path to the 
>> database correctly there
>> 
>>> On Wednesday, November 18, 2020 at 1:09:50 PM UTC-8 gccobse...@gmail.com 
>>> wrote:
>>> I thought so too, but I redropped and rebuilt the dailies and still the 
>>> same...
>>> 
>>> 
 On Wednesday, November 18, 2020 at 4:01:13 PM UTC-5 vince wrote:
 The lack of the archive_day_wind table tells me perhaps your 
 --rebuild-daily didn't complete 
 
> 
> -- 
> 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/55fd7f56-4db8-4934-af38-3767382f8c66n%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/5B507542-A177-443A-968A-61EF48A1348B%40johnkline.com.

[weewx-user] Re: errors from power outage

[GCC Observatory]

I'm not aware of the ".schema" command you mention...

On Wednesday, November 18, 2020 at 5:19:31 PM UTC-5 vince wrote:

> Try "*.schema | sudo sqlite3 /var/lib/weewx/weewx.sdb*" and see if you 
> get all the various tables that are expected there, if I recall the path to 
> the database correctly there
>
> On Wednesday, November 18, 2020 at 1:09:50 PM UTC-8 gccobse...@gmail.com 
> wrote:
>
>> I thought so too, but I redropped and rebuilt the dailies and still the 
>> same...
>>
>>
>> On Wednesday, November 18, 2020 at 4:01:13 PM UTC-5 vince wrote:
>>
>>> The lack of the archive_day_wind table tells me perhaps your 
>>> --rebuild-daily didn't complete 
>>>
>>>

-- 
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/55fd7f56-4db8-4934-af38-3767382f8c66n%40googlegroups.com.

[weewx-user] Re: ws6in1 sensor mapping

[Steven Garré]

Gary,

Thanks! Just tried this and works like a charm. Data from outTemp isn't 
needed because of the inaccurate readings, so i used the first option.
Really grateful for the help. 

Kind regards
Steven

Op woensdag 18 november 2020 om 22:18:22 UTC+1 schreef gjr80:

> Hi,
>
> If a driver does not support sensor mapping you can in some cases use the 
> StdCalibrate service to achieve a similar outcome. For example, to have 
> your second sensor fill outTemp/outHumidity you could place something like 
> the following under [StdCalibrate] in weewx.conf (untested):
>
> [StdCalibrate]
> [[Corrections]]
> outTemp = extraTemp1
> outHumidity = extraHumid1
>
> Of course this relies on the driver placing the data you seek in 
> extraTemp1 and extraHumid1. This will result in your extraTemp1 value 
> appearing in both outTemp and extraTemp1. You could use a further 
> correction to set extraTemp1 to None, but that would interfere with archive 
> records as corrections are applied to both loop packets and archive 
> records. Likewise for extraHumid1.
>
> If you did want to keep your original outTemp data you could first place 
> it in another field, say extraTemp2 by including something like:
>
> [StdCalibrate]
> [[Corrections]]
> extraTemp2 = outTemp
> outTemp = extraTemp1
>
> If saving the original outTemp to database is not important you could 
> instead save it to a new field, say outTemp_orig. This would make the 
> current (original outTemp) data available in reports via the 
> $current.outTemp_orig tag but it would not be saved to database. 
> Againlikewise for outHumidity.
>
> There are a couple of caveats though; first you need to be using WeeWX 
> v4.2.0 or later. Second is that order matters with the lines under 
> [[Corrections]], corrections are applied in the order they appear.
>
> Gary
>
> On Thursday, 19 November 2020 at 01:36:08 UTC+10 steven...@gmail.com 
> wrote:
>
>> Hello
>>
>> My main unit from the Garni935pc gets too hot when the sun is all out. So 
>> i tried to make my second sensor in the Stevenson screen make the default 
>> sensor for reporting to website/WU/WOW but can't make it to work.
>>
>> I tried the following:
>>
>> [WS6in1]
>> driver = user.ws6in1
>> [[sensor_map]]
>> outTemp =  extraTemp1
>> outHumidity =  extraHumid1
>>
>> But makes no difference. How do i make this work?
>>
>> Kind regards
>> Steven
>>
>>
>>

-- 
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/87b5fa97-99dc-4835-9d3b-900e5de76340n%40googlegroups.com.

[weewx-user] Re: errors from power outage

[vince]

Try "*.schema | sudo sqlite3 /var/lib/weewx/weewx.sdb*" and see if you get 
all the various tables that are expected there, if I recall the path to the 
database correctly there

On Wednesday, November 18, 2020 at 1:09:50 PM UTC-8 gccobse...@gmail.com 
wrote:

> I thought so too, but I redropped and rebuilt the dailies and still the 
> same...
>
>
> On Wednesday, November 18, 2020 at 4:01:13 PM UTC-5 vince wrote:
>
>> The lack of the archive_day_wind table tells me perhaps your 
>> --rebuild-daily didn't complete 
>>
>>

-- 
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/648429a1-5967-4fd7-99bf-cc17a075073an%40googlegroups.com.

[weewx-user] Re: ws6in1 sensor mapping

[gjr80]

Hi,

If a driver does not support sensor mapping you can in some cases use the 
StdCalibrate service to achieve a similar outcome. For example, to have 
your second sensor fill outTemp/outHumidity you could place something like 
the following under [StdCalibrate] in weewx.conf (untested):

[StdCalibrate]
[[Corrections]]
outTemp = extraTemp1
outHumidity = extraHumid1

Of course this relies on the driver placing the data you seek in extraTemp1 
and extraHumid1. This will result in your extraTemp1 value appearing in 
both outTemp and extraTemp1. You could use a further correction to set 
extraTemp1 to None, but that would interfere with archive records as 
corrections are applied to both loop packets and archive records. Likewise 
for extraHumid1.

If you did want to keep your original outTemp data you could first place it 
in another field, say extraTemp2 by including something like:

[StdCalibrate]
[[Corrections]]
extraTemp2 = outTemp
outTemp = extraTemp1

If saving the original outTemp to database is not important you could 
instead save it to a new field, say outTemp_orig. This would make the 
current (original outTemp) data available in reports via the 
$current.outTemp_orig tag but it would not be saved to database. 
Againlikewise for outHumidity.

There are a couple of caveats though; first you need to be using WeeWX 
v4.2.0 or later. Second is that order matters with the lines under 
[[Corrections]], corrections are applied in the order they appear.

Gary

On Thursday, 19 November 2020 at 01:36:08 UTC+10 steven...@gmail.com wrote:

> Hello
>
> My main unit from the Garni935pc gets too hot when the sun is all out. So 
> i tried to make my second sensor in the Stevenson screen make the default 
> sensor for reporting to website/WU/WOW but can't make it to work.
>
> I tried the following:
>
> [WS6in1]
> driver = user.ws6in1
> [[sensor_map]]
> outTemp =  extraTemp1
> outHumidity =  extraHumid1
>
> But makes no difference. How do i make this work?
>
> Kind regards
> Steven
>
>
>

-- 
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/23fa9c2e-9111-4e91-a5ea-1b12d5134697n%40googlegroups.com.

[weewx-user] Re: errors from power outage

[GCC Observatory]

I thought so too, but I redropped and rebuilt the dailies and still the 
same...


On Wednesday, November 18, 2020 at 4:01:13 PM UTC-5 vince wrote:

> The lack of the archive_day_wind table tells me perhaps your 
> --rebuild-daily didn't complete 
>
>

-- 
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/3771b0cb-976b-4c01-acae-73c53316a999n%40googlegroups.com.

[weewx-user] Re: errors from power outage

[vince]

The lack of the archive_day_wind table tells me perhaps your 
--rebuild-daily didn't complete 

-- 
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/b7e57e9e-772e-46ae-abdf-19c06b260834n%40googlegroups.com.

[weewx-user] errors from power outage

[GCC Observatory]

Had a power outage the other night and did some weird things to my Davis 
station once power was restored... 

did a "wee_device --dump" and "wee_device --clear-memory" and removed a 
couple of odd entries in the database by hand.  Things look back to mostly 
normal, except for below.  

I did "wee_database --drop-daily/--rebuild-daily" but still having the 
problem.  

Also upgraded from 4.1 to 4.2 after the power outage, and don't know if the 
upgrade is the cause of the problem below or not...

Thanks in advance...






Nov 18 15:45:24 localhost weewx[16767] ERROR weewx.reportengine:
   NoTableError: no such table: archive_day_wind
Nov 18 15:45:24 localhost weewx[16767] ERROR weewx.reportengine:
   Generator terminated
Nov 18 15:45:24 localhost weewx[16767] INFO weewx.reportengine: Copied 0 
files to /var/www/weewx/skins/standard
Nov 18 15:45:25 localhost weewx[16767] INFO weewx.cheetahgenerator: 
Generated 17 files for report Belchertown in 1.08 seconds
Nov 18 15:45:25 localhost weewx[16767] INFO weewx.reportengine: Copied 2 
files to /var/www/weewx
Nov 18 15:45:28 localhost weewx[16767] ERROR weewx.restx: AWEKAS: Failed to 
publish record 2020-11-18 15:45:00 EST (1605732300): Server returned 
'Luftfeuchte administrativ gesperrt - Transfer OK'
Nov 18 15:45:30 localhost weewx[16767] INFO weewx.restx: WeatherCloud: 
Published record 2020-11-18 15:45:00 EST (1605732300)
Nov 18 15:48:51 localhost vncserver-x11[992]: Connections: connected: 
10.16.106.76::57086
Nov 18 15:48:51 localhost vncserver-x11[992]: Connections: authenticated: 
10.16.106.76::57086, as (anonymous) (d permissions)
Nov 18 15:50:01 localhost CRON[11511]: (root) CMD (nice -2 
/home/talon/bwcs2/bin/bwcs2_cron_5min.csh >> 
/home/talon/bwcs2/bin/bwcs2_cron_5min.log 2>&1)
Nov 18 15:50:01 localhost CRON[11513]: (root) CMD (nice -2 
/home/talon/local/bin/domyallsky.sh >> /home/talon/allsky/domyallsky.log 
2>&1)
Nov 18 15:50:21 localhost weewxd: onewire: sensor0 found value of 44.6
Nov 18 15:50:21 localhost weewxd: onewire: /var/www/weewx/onewire.txt 
removed
Nov 18 15:50:22 localhost weewxd: onewire: sensor1 found value of 45.1625
Nov 18 15:50:23 localhost weewxd: onewire: sensor2 found value of 45.8375
Nov 18 15:50:23 localhost weewx[16767] INFO weewx.manager: Added record 
2020-11-18 15:50:00 EST (1605732600) to database 'weewx.sdb'
Nov 18 15:50:23 localhost weewx[16767] INFO weewx.manager: Added record 
2020-11-18 15:50:00 EST (1605732600) to daily summary in 'weewx.sdb'
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator: 
Generate failed with exception ''
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'raw' while searching for 'day.wind.count.raw'
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
  File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 430, in 
respond
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
NotFound: cannot find 'raw' while searching for 'day.wind.count.raw'
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.restx: AWEKAS: Failed to 
publish record 2020-11-18 15:50:00 EST (1605732600): Server returned 
'Luftfeuchte administrativ gesperrt - Transfer OK'
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator: 
Generate failed with exception ''
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y.txt.tmpl
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'raw' while searching for 'month.wind.count.raw'
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in generate
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
  File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y_txt_tmpl.py", line 861, in 
respond
Nov 18 15:50:23 localhost weewx[16767] ERROR weewx.cheetahgenerator:   
NotFound: cannot find 'raw' while searching for 'month.wind.count.raw'
Nov 18 15:50:23 localhost weewx[16767] INFO weewx.cheetahgenerator: 
Generated 6 files for report 

[weewx-user] Re: ws6in1 sensor mapping

[Jarda Uher]

Hello Steven and Bob
I also use a garni 935 pc with one external sensor in the weewx 4.2.0 
configuration, I use the ws6in1 driver version 0.8 and the Belchertown 1.2 
skin. I didn't have to use sensor_map in weewx.conf, but just write the 
sequence to graps.conf.example in the skin. the temperature display will 
then appear on the graph page. Bob's driver works without problems and is 
able to load more sensors in the database.
[[chart1]]
title = Teplota
[[[outTemp]]]
zIndex = 1
name = Temperature
[[[extraTemp1]]]
name = Přízemní teplota
[[[appTemp]]]
name = pocitová teplota
color = "#f7a35c"
[[[dewpoint]]]
color = purple

Best regards
Jarda
Dne středa 18. listopadu 2020 v 19:02:06 UTC+1 uživatel steven...@gmail.com 
napsal:

> Hello Bob
>
> Well, that would be really amazing if you can implement the driver.
>  
> i'm a bit disappointed in the Garni935 mean unit. Offcourse when it's 
> cloudy or at night the unit is mostly spot on. But otherwise in full sun 
> i'm getting readings with more than 1°C-1.5C difference with the closest 
> Davis or more official stations. (and it's not even summer yet) As back up 
> i'm using a TFA weatherhub sensor (and the second Garni sensor), wich never 
> reads those temp differences, so it must be the unit sadly enough. 
>
> Only other options left is tweaking the screen off the sensor mean unit, 
> or placing the whole unit in the shade wich than renders the anemometer and 
> UV-meter useless.
>
> Regards
> Steven
>
> Op woensdag 18 november 2020 om 18:30:26 UTC+1 schreef Bob Atchley:
>
>> Hi Steven,
>>
>> I'm afraid, put very simply, this is a driver option that I have not 
>> implemented in the WS6in1 driver.
>> As I now have an additional sensor this is something I could add ... I'll 
>> have a play this weekend.
>>
>> Personally I have the identical Youshiko YC9388 and I find the 
>> temperature accuracy to be very good (compared to an old WS2300 - mounted 
>> in a stevenson screen ... sort of.  Also compared to other local weather 
>> stations)
>>
>> I'd be interested to see the temperature differences you are getting 
>> between the main unit and your extra sensor (on a day with the sun out!)
>>
>> Regards
>>
>> Bob
>>
>> On Wednesday, 18 November 2020 at 15:36:08 UTC steven...@gmail.com wrote:
>>
>>> Hello
>>>
>>> My main unit from the Garni935pc gets too hot when the sun is all out. 
>>> So i tried to make my second sensor in the Stevenson screen make the 
>>> default sensor for reporting to website/WU/WOW but can't make it to work.
>>>
>>> I tried the following:
>>>
>>> [WS6in1]
>>> driver = user.ws6in1
>>> [[sensor_map]]
>>> outTemp =  extraTemp1
>>> outHumidity =  extraHumid1
>>>
>>> But makes no difference. How do i make this work?
>>>
>>> Kind regards
>>> Steven
>>>
>>>
>>>

-- 
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/d46c9e49-7e5f-46b5-b3a2-6093227072d9n%40googlegroups.com.

Re: [weewx-user] Re: Weatherlink IP replacement

[Nicolas Peninguy]

Hello,

Le 11/18/20 à 2:07 PM, galfert a écrit :
Davis pretty much discontinued the Weatherlink IP around the time they 
released the WeatherLink Live. My recommendation is to go with the 
WeatherLink Live.


It took me some time to find relevant information on the Internet, so 
may be this will be of some interest for someone.


This thing embeds an HTTP server with a local API described here:

https://weatherlink.github.io/weatherlink-live-local-api/

There are some good things, like broadcast of live data or discovery 
through mDNS.



BUT:

Currently there is no local access to archive data, nor device health 
data: https://github.com/weatherlink/weatherlink-live-local-api/issues


This thing will be useless if for whatever reason using Davis 
weatherlink.com service is not wanted or possible.



Regards,

Nicolas

--
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/826d7c86-124e-beda-798e-154c0d75333a%40lostgeeks.org.

[weewx-user] Re: ws6in1 sensor mapping

[Steven Garré]

Hello Bob

Well, that would be really amazing if you can implement the driver.
 
i'm a bit disappointed in the Garni935 mean unit. Offcourse when it's 
cloudy or at night the unit is mostly spot on. But otherwise in full sun 
i'm getting readings with more than 1°C-1.5C difference with the closest 
Davis or more official stations. (and it's not even summer yet) As back up 
i'm using a TFA weatherhub sensor (and the second Garni sensor), wich never 
reads those temp differences, so it must be the unit sadly enough. 

Only other options left is tweaking the screen off the sensor mean unit, or 
placing the whole unit in the shade wich than renders the anemometer and 
UV-meter useless.

Regards
Steven

Op woensdag 18 november 2020 om 18:30:26 UTC+1 schreef Bob Atchley:

> Hi Steven,
>
> I'm afraid, put very simply, this is a driver option that I have not 
> implemented in the WS6in1 driver.
> As I now have an additional sensor this is something I could add ... I'll 
> have a play this weekend.
>
> Personally I have the identical Youshiko YC9388 and I find the temperature 
> accuracy to be very good (compared to an old WS2300 - mounted in a 
> stevenson screen ... sort of.  Also compared to other local weather 
> stations)
>
> I'd be interested to see the temperature differences you are getting 
> between the main unit and your extra sensor (on a day with the sun out!)
>
> Regards
>
> Bob
>
> On Wednesday, 18 November 2020 at 15:36:08 UTC steven...@gmail.com wrote:
>
>> Hello
>>
>> My main unit from the Garni935pc gets too hot when the sun is all out. So 
>> i tried to make my second sensor in the Stevenson screen make the default 
>> sensor for reporting to website/WU/WOW but can't make it to work.
>>
>> I tried the following:
>>
>> [WS6in1]
>> driver = user.ws6in1
>> [[sensor_map]]
>> outTemp =  extraTemp1
>> outHumidity =  extraHumid1
>>
>> But makes no difference. How do i make this work?
>>
>> Kind regards
>> Steven
>>
>>
>>

-- 
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/e0b22d9d-6f71-4341-a681-54f88cb0b128n%40googlegroups.com.

[weewx-user] Re: ws6in1 sensor mapping

[Bob Atchley]

Hi Steven,

I'm afraid, put very simply, this is a driver option that I have not 
implemented in the WS6in1 driver.
As I now have an additional sensor this is something I could add ... I'll 
have a play this weekend.

Personally I have the identical Youshiko YC9388 and I find the temperature 
accuracy to be very good (compared to an old WS2300 - mounted in a 
stevenson screen ... sort of.  Also compared to other local weather 
stations)

I'd be interested to see the temperature differences you are getting 
between the main unit and your extra sensor (on a day with the sun out!)

Regards

Bob

On Wednesday, 18 November 2020 at 15:36:08 UTC steven...@gmail.com wrote:

> Hello
>
> My main unit from the Garni935pc gets too hot when the sun is all out. So 
> i tried to make my second sensor in the Stevenson screen make the default 
> sensor for reporting to website/WU/WOW but can't make it to work.
>
> I tried the following:
>
> [WS6in1]
> driver = user.ws6in1
> [[sensor_map]]
> outTemp =  extraTemp1
> outHumidity =  extraHumid1
>
> But makes no difference. How do i make this work?
>
> Kind regards
> Steven
>
>
>

-- 
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/0f6f2fc5-ebe9-4dc1-bd87-ddb354c1ec9fn%40googlegroups.com.

[weewx-user] ws6in1 sensor mapping

[Steven Garré]

Hello

My main unit from the Garni935pc gets too hot when the sun is all out. So i 
tried to make my second sensor in the Stevenson screen make the default 
sensor for reporting to website/WU/WOW but can't make it to work.

I tried the following:

[WS6in1]
driver = user.ws6in1
[[sensor_map]]
outTemp =  extraTemp1
outHumidity =  extraHumid1

But makes no difference. How do i make this work?

Kind regards
Steven


-- 
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/8c0e9460-f888-42f8-a05e-63b9cf2858ecn%40googlegroups.com.

Re: [weewx-user] Weatherlink IP replacement

[weather list]

I have two of the Meteobridge NANO SD units, not cheap at all but very capable 
units, and they free you from needing to use a USB cable. But galfert’s summary 
of the WLLive is compelling, especially as you can run multiple idfferent 
systems against it at once.

> On 18 Nov, 2020, at 00:13, Robin Hunt  wrote:
> 
> Hi
> 
> I used to use the Davis WeatherLink IP ethernet data logger which has broken.
> 
> I tried to buy a new one but I see it has been discontinued.
> 
> How do I connect my Davis Vantage Pro 2 to my weewx installation now? What 
> hardware should I buy?
> 
> Kind regards
> Robin
> 
> -- 
> 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/c1e9244c-5522-4ad2-8855-e74b6c1dea88n%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/E0F437DD-4F42-47C7-BFBF-AFCDA24D62EF%40gmail.com.

Re: [weewx-user] Replacement for 6540 data logger.

[bgra...@umw.edu]

Thanks, John, that’s just what I needed to know.  Scaled Instruments has a 
very good price on these.
Bob

On Tuesday, November 17, 2020 at 7:36:55 PM UTC-5 jo...@johnkline.com wrote:

> The WeatherLinkIP (
> https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/) 
> Ethernet data logger is discontinued.
>
> The USB and serial data loggers are still being sold:
> https://www.davisinstruments.com/product/weatherlink-windows-usb/
> https://www.davisinstruments.com/product/weatherlink-windows-serial-port/
>
> The USB data logger will run fine with your Raspberry Pi.
>
>
> On Nov 17, 2020, at 3:17 PM, bgra...@umw.edu  wrote:
>
> Hello,
>
> My 6540 VP2 console logger is bad and I understand that they are no longer 
> making them. I’d rather try something better.
>
> My present weewx runs on an rpi with a RS232 to USB dongle from the 6540 
> on the console. I don’t need APRS connectivity, just something to get the 
> VP2 data to weewx.
>
> Could anyone suggest something to solve my problem? There must be plenty 
> of things out there but I’m not familiar with them.
>
> Thanks in advance.
>
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/68d1e882-b953-42e8-a255-4214ffb1c0e8n%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/c64a8003-7253-48e7-9f0e-86763226f4dan%40googlegroups.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[lecoqacr...@gmail.com]

What is a good way to test the symlink rule to verify that it was created 
correctly? There is the new file in /dev/weather but is there a more 
complete way to test? thank you

On Tuesday, November 17, 2020 at 7:29:08 PM UTC-6 Greg from Oz wrote:

> I set my fineoffset rule to:
>
> SUBSYSTEM=="usb", ATTRS{idVendor}=="1941", ATTRS{idProduct}=="8021", 
> MODE="0666", GROUP="plugdev", SYMLINK+="weather"
>
> That way it is always /dev/weather regardless of the ttyUsb it is attached 
> to.
>
> ll /dev/weather 
> lrwxrwxrwx 1 root root 15 Nov 17 09:26 /dev/weather -> bus/usb/002/002
>
> On Wednesday, 18 November 2020 at 12:14:53 UTC+11 tke...@gmail.com wrote:
>
>> Are you sure? Depending on what permissions the usb port has, you may 
>> need to use sudo to run lsof:
>>
>> *sudo lsof /dev/ttyUSB0*
>>
>> Come to think of it, you may have to do that with minicom, too.
>>
>> Personally, I change the udev rule that governs permissions for usb 
>> devices to give everyone access to the port. The rule that governs this is 
>> most likely in the directory /lib/udev/rules.d, but which file it is in 
>> depends on the operating system. I believe on Raspbian, it's in file 
>> 91-permissions.rules, but it may be in 50-udev-default.rules.  Wherever 
>> you find it, you want to change this
>>
>> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0664"
>>
>> to this
>>
>> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
>>
>>
>> -tk
>>
>> On Tue, Nov 17, 2020 at 3:07 PM bgra...@umw.edu  wrote:
>>
>>>
>>> Thanks everyone, I think I have a bad logger (6540).
>>> On Tuesday, November 17, 2020 at 9:41:56 AM UTC-5 bgra...@umw.edu wrote:
>>>
 root@raspberrypi:/home/pi# ll /dev/ttyUSB0
 crw-rw 1 root dialout 188, 0 Nov 16 17:48 /dev/ttyUSB0


 root@raspberrypi:/home/pi# lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.

 On Monday, November 16, 2020 at 8:43:34 PM UTC-5 tke...@gmail.com 
 wrote:

> If it were a permissions problem, it would have said so. Same if 
> modemmanager controlled the port. Still, it doesn't hurt to try lsof and 
> see if anything else is using the port.
>
> *lsof /dev/ttyUSB0*
>
>
>
>
> On Mon, Nov 16, 2020 at 5:36 PM Greg from Oz  
> wrote:
>
>> Is the user running this in the dialout group? 
>>
>> On Tuesday, 17 November 2020 at 12:30:14 UTC+11 tke...@gmail.com 
>> wrote:
>>
>>> The only thing I can think of to try is to reseat the logger. 
>>>
>>> Unless, you actually have the serial version of the VantagePro and 
>>> are using a serial-to-usb converter. They are notoriously flakey. If 
>>> you 
>>> have a spare one, try that.
>>>
>>> If none of that works, call Davis.
>>>
>>> On Mon, Nov 16, 2020 at 5:04 PM bgra...@umw.edu  
>>> wrote:
>>>
 Yes, I did hit enter many times. Since dmesg said that the usb had 
 attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had 
 connected. I’m at a loss because everything was working...  Thanks.

 On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com 
 wrote:

> OK, but did you hit  a few times before typing "TEST"? If 
> so, you have a connectivity problem, not a WeeWX problem.
>
> But, you probably already knew that!
>
> -tk
>
> On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  
> wrote:
>
>>
>> I don’t remember the minicom string but it was the one posted to 
>> test TEST. When I opened minicom it just sat there no echo on TEST 
>> or VER. 
>> No reply. Several reboots no results. /dev/ttyUSB0 is there but does 
>> not 
>> respond. Dmesg Seems to have found it.
>> I checked all plugs and connections. Removed batteries from 
>> console to reboot. Even tried new RS232/USB dongle. I have a main 
>> ubuntu 
>> linux pc running from the ISS so I know that’s working and sending 
>> data. 
>> The rpi is setup as a second console which was running weather34. 
>> Thanks 
>> Tom and Graham (you helped me in the days of wview).
>> Bob
>> Main setup: grattans.org/wx
>> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com 
>> wrote:
>>
>>> When you say  you "tried listening to the console with minicom 
>>> but got no data" what do you mean?
>>>
>>> In particular, did you set the baudrate? And, did you type 
>>>  a few types before trying to type TEST?
>>>
>>> -tk
>>>
>>> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  
>>> wrote:
>>>
 I have a VP2 console that I am connecting to an RPI OS 

[weewx-user] Re: Weatherlink IP replacement

[galfert]

Davis pretty much discontinued the Weatherlink IP around the time they 
released the WeatherLink Live. My recommendation is to go with the 
WeatherLink Live. Doing so will allow you to even run additional software. 
You could even run two instances of WeeWX on different computers if you'd 
like simultaneously. That way you can play around testing plugins and 
customizations and the production system keeps running. You could also 
simultaneously then run Cumulux MX or Meteobridge or Weather-Display. 
You'll also gain live data on the Weatherlink mobile app when on your WiFi. 
The WeatherLink Live is the essential building block for a very expandable 
weather station. The WeatherLink Live is also capable of receiving data 
from multiple ISS and expansion transmitters.

On Wednesday, November 18, 2020 at 12:13:19 AM UTC-5 robinh...@gmail.com 
wrote:

> Hi
>
> I used to use the Davis WeatherLink IP ethernet data logger which has 
> broken.
>
> I tried to buy a new one but I see it has been discontinued.
>
> How do I connect my Davis Vantage Pro 2 to my weewx installation now? What 
> hardware should I buy?
>
> Kind regards
> Robin
>

-- 
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/7932-e36e-4dde-8d2b-9d4864734b61n%40googlegroups.com.

Re: [weewx-user] Weatherlink IP replacement

[Dave Webb KB1PVH]

Yes, the USB version will work with a Raspberry Pi.

Dave-KB1PVH


Sent from my Galaxy S9

On Wed, Nov 18, 2020, 1:55 AM Robin Hunt  wrote:

> Thanks very much - does anyone know if the USB version will work on a
> Raspberry Pi model 3?
>
> On Wednesday, November 18, 2020 at 8:10:10 AM UTC+2 garrya...@gmail.com
> wrote:
>
>> I use:
>>
>> WeatherLink® USB Data Logger (#6510USB)
>> Regards,
>>
>> Garry Lockyer
>> C: +1.250.689.0686 <(250)%20689-0686>
>> E: ga...@lockyer.ca
>>
>>
>> On Nov 17, 2020, at 21:13, Robin Hunt  wrote:
>>
>> Hi
>>
>>
>> I used to use the Davis WeatherLink IP ethernet data logger which has
>> broken.
>>
>> I tried to buy a new one but I see it has been discontinued.
>>
>> How do I connect my Davis Vantage Pro 2 to my weewx installation now?
>> What hardware should I buy?
>>
>> Kind regards
>> Robin
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/c1e9244c-5522-4ad2-8855-e74b6c1dea88n%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/c9bb9d60-bbc7-49ca-b49f-a074b2135f2en%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/CAEMY9FcTTd8N2Drq-p%3Dx4yPEySudO6EuaH59O8oF%3DHM0Ncr8iA%40mail.gmail.com.

Re: [weewx-user] Weatherlink IP replacement

[Richard G]

You should also consider the weather link logger.

https://www.weatherstations.co.uk/wifi-logger.htm

On Wednesday, 18 November 2020 at 06:55:42 UTC robinh...@gmail.com wrote:

> Thanks very much - does anyone know if the USB version will work on a 
> Raspberry Pi model 3?
>
> On Wednesday, November 18, 2020 at 8:10:10 AM UTC+2 garrya...@gmail.com 
> wrote:
>
>> I use:
>>
>> WeatherLink® USB Data Logger (#6510USB)
>> Regards,
>>
>> Garry Lockyer
>> C: +1.250.689.0686 <(250)%20689-0686>
>> E: ga...@lockyer.ca
>>
>>
>> On Nov 17, 2020, at 21:13, Robin Hunt  wrote:
>>
>> Hi
>>
>>
>> I used to use the Davis WeatherLink IP ethernet data logger which has 
>> broken.
>>
>> I tried to buy a new one but I see it has been discontinued.
>>
>> How do I connect my Davis Vantage Pro 2 to my weewx installation now? 
>> What hardware should I buy?
>>
>> Kind regards
>> Robin
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c1e9244c-5522-4ad2-8855-e74b6c1dea88n%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/76810d64-77da-47d9-afbc-db6861e4d2bdn%40googlegroups.com.

Re: [weewx-user] Re: TFA Klimalogg PRO on RaspberryPi

[Luc Heijst]

Herman,
For tfrec working in Buster, see my 
post https://groups.google.com/g/weewx-user/c/b-GiJ1qkdF8
Luc

Op dinsdag 17 november 2020 om 09:51:02 UTC-3 schreef cool...@gmail.com:

> Working again...:)) A lot of changes to the config file...  Good lesson to 
> backup a working weewx.conf..
> But still interested in tfrec working in Buster..
> regards
> Herman
>
> Op dinsdag 17 november 2020 om 12:50:59 UTC+1 schreef cool...@gmail.com:
>
>> a dump from the tail of syslog:
>>
>> Nov 17 12:45:14 central weewx[20281] INFO __main__: Starting up weewx 
>> version 4.2.0
>>
>> Nov 17 12:45:14 central weewx[20281] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>>
>> Nov 17 12:46:14 central weewx[20281] ERROR user.kl: unable to terminate 
>> RF thread after 60 seconds
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: Caught 
>> unrecoverable exception:
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Unknown 
>> data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> Traceback (most recent call last):
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewxd", line 154, in main
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> engine.run()
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 173, in run
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> self.dispatchEvent(weewx.Event(weewx.STARTUP))
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> callback(event)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/engine.py", line 562, in startup
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> dbmanager = self.engine.db_binder.get_manager(self.data_binding, 
>> initialize=True)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 529, in get_manager
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> default_binding_dict=defaults)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 634, in 
>> get_manager_dict_from_config
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> raise weewx.UnknownBinding("Unknown data binding '%s'" % e)
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   
>> UnknownBinding: Unknown data binding 'u'kl_binding''
>>
>> Nov 17 12:46:14 central weewx[20281] CRITICAL __main__:   Exiting.
>>
>>
>> Op dinsdag 17 november 2020 om 12:40:26 UTC+1 schreef cool...@gmail.com:
>>
>>> Hello Luc,
>>>
>>> Since the last update of weewx (I stupidly accepted the change in the 
>>> config file) my klimmalogg setup is broken. I tried to copy back some info 
>>> I had from previous whew.conf backups but it seems that some things are 
>>> changed within weewx itself. I can't get it to work anymore. e.g. kl.py is 
>>> not in the drivers directory. 
>>> other example is the change from  weewx.manager.WXDaySummaryManager into 
>>> weewx.manager.DaySummaryManager in the conf file. 
>>> I tried reinstalling the plugin from scratch but that didn't help 
>>> either. Any idea about this update and the impact on KL?
>>>
>>> And for sure I would like to do the same as Walter Speth and just push 
>>> the data on an MQTT topic to flow into an influxdb. So yes, a bit curious 
>>> how you got tired working. I didn't manage to go that way.
>>>
>>> Regards
>>> Herman
>>>
>>> Op maandag 24 augustus 2020 om 13:23:57 UTC+2 schreef Luc Heijst:
>>>
 Hi Walter,

 I don't know if your approach is working. The software in the KlimaLogg 
 PRO station is very time critical.
 Perhaps you try the driver first within weewx and when it is working 
 you can go from there.

 The KlimaLogg PRO base station needs to be synchronized once with the 
 driver.
 To do this:
 Press and hold the USB button for three seconds until a beep is heard, 
 then start weewx with the kl-driver (within 5 seconds). A second beep is 
 heard when the synchronization was succesfull.

 From now on a short press on the USB button is needed whenever the 
 driver lost communication with the base station. The driver is telling you 
 to do so.

 There is another (much easier) way to read the values of the KlimaLogg 
 sensors with a SDR-dongle (the base station is not needed anymore), see: 
 https://github.com/baycom/tfrec 
 The instructions on this site to compile the tfrc program don't work 
 anymore for Raspbian Buster. 

[weewx-user] Installattion of tfrec on Raspberry PI with Raspbian Buster

[Luc Heijst]

Program tfrec can read the data of the KlimaLogg Pro sensors directly with 
use of a rtl-sdr dongle.
The KlimaLogg Pro console is not needed anymore. The advantages are:
1. No need for pressing a USB button on the Klimalogg Pro console after 
each restart of the weewx driver.
2. No need for 'learning' the sensor data (e.g. after replacing worn out 
batteries of the console).
3. The number of Klimalogg Pro sensors are not limited to eight anymore.
4. For new configurations one doesn't have to buy the console anymore; only 
the sensors will do.

For the weewx driver see readme file of 
https://github.com/matthewwall/weewx-tfrc

For Raspbian these are the steps:

sudo apt-get install clang cmake git pkg-config librtlsdr-dev -y

b) install rtl-sdr:
cd /home/weewx
git clone https://github.com/steve-m/librtlsdr.git
cd librtlsdr
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make
sudo make install
sudo ldconfig

c) install tfrc:
cd /home/weewx
sudo git clone https://github.com/baycom/tfrec.git
cd tfrec

For Rapbbian Stretch:
Compile tfrec source:
For RasPI3 use:
sudo make -f Makefile.arm
for RasPI 2 or Zero:
make -f Makefile.raspi2

For Raspbian Buster:
Note: In Raspbian Buster the make command gets undefined reference errors 
like:
/usr/bin/ld: sdr.o: in function `sdr::read_thread()':
sdr.cpp:(.text+0xd8): undefined reference to `rtlsdr_read_async'
 
The followings steps will fix this error:  

1. modify file /home/weewx/librtlsdr/build/librtlsdr.pc

Change the first four lines:
prefix=
exec_prefix=
libdir=
includedir=
into:
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include

2. modify file /home/weewx/tfrec/Makefile.arm 
(or file /home/weewx/tfrec/Makefile.raspi2 for RasPI 2 or Zero)
 
Change the first line:
PACKAGES= librtlsdr
into:
PACKAGES= /home/weewx/librtlsdr/build/librtlsdr.pc

3. repeat the make command
sudo make -f Makefile.arm
Now the make command will finish without errors:

Test tfrec:
/home/weewx/tfrec/tfrec -D -T 1

Luc

-- 
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/77c7b6df-0cf2-467f-9120-e7e9eeb7749bn%40googlegroups.com.