Re: [weewx-user] ;:; SQLite schema report

[gjr80]

Perhaps I need to change my glasses, but the last time I looked 
*weewx-belchertown-release-1.2.tar.gz* is different to 
*weewx-belchertown-1.2.tar.gz*.

Perhaps you should try:

$ sudo /home/weewx/bin/wee_extension --install 
/home/david/Downloads/weewx-belchertown-release-1.2.tar.gz

Gary
On Friday, 5 March 2021 at 15:34:46 UTC+10 david.a@gmail.com wrote:

> Gary:
> ls -l /home/david/Downloads:
> -r 1 david david 1518145 Mar  3 18:02 
> weewx-belchertown-release-1.2.tar.gz
> and i used the fully qualified sudo string for execution:
> sudo /home/weewx/bin/wee_extension --install 
> /home/david/Downloads/weewx-belchertown-1.2.tar.gz
>
> On Thursday, March 4, 2021 at 6:40:46 PM UTC-8 gjr80 wrote:
>
>> Did you ls the directory containing the extension package to confirm the 
>> file name? According to the Belchertown repo the 1.2 extension package is 
>> named weewx-belchertown-release-1.2.tar.gz, slightly different to that used 
>> in your commands.
>>
>> Gary
>>
>> On Friday, 5 March 2021 at 12:28:08 UTC+10 david.a@gmail.com wrote:
>>
>>> Vince - thanks! I'll take that approach on the imports!
>>>
>>> Glenn:
>>> I had hand-transcribed the command entry - i'd entered the correct 
>>> command string:
>>> sudo /home/weewx/bin/wee_extension --install 
>>> /home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
>>> /tmp/wee-extension-out.txt
>>>
>>> This is the results:
>>> ==
>>> Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
>>> Traceback (most recent call last):
>>>   File "/home/weewx/bin/wee_extension", line 88, in 
>>> main()
>>>   File "/home/weewx/bin/wee_extension", line 80, in main
>>> ext.install_extension(options.install)
>>>
>>>   File "/home/weewx/bin/weecfg/extension.py", line 134, in 
>>> install_extension
>>> raise InstallError("Extension '%s' not found." % extension_path)
>>> weecfg.extension.InstallError: Extension 
>>> '/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
>>> 
>>>
>>> No info about where to put the tar.gz file. Again, i'd used the 
>>> "setup.py" script to install weewx, so all the relevant folders are off 
>>> "/home". 
>>> /David
>>> On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
>>>
 /home/david/Downloads/weewx-belchertown.1.2.tar.gz 

 Check the filename 

 Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet) 
 or is it ... weewx-belchertown-1.2.tar.gz as per the release page at 

 https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
  

 note: there are 2 dashes in the correct name. 

 On 04/03/2021, David Prellwitz  wrote: 
 > error trying to install belchertown. my weewx install was using 
 setup.py. I 
 > 
 > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
 folder. 
 > I ran the sudo wee-extension command and get "File 
 > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension 
 > weecfg.extension.InstallError: Extension 
 > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found. 
 > can't find what i did wrong. Should i extract the tar.gz file first? 
 move 
 > it to another folder to start install? 
 > /David 
 > 
 > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote: 
 > 
 >> Lightning is difficult because there's no units for 'energy' in the 
 UDP 
 >> API. I might also add perhaps don't bother, as lightning is bogus 
 anyway. 
 >> 
 >> It's what your sensor reported, but it is not remotely close to the 
 >> crowd-sourced info their web or mobile interfaces provide, of which 
 your 
 >> sensor measurements are just a small part of what they aggregate and 
 >> display. 
 >> 
 >> I think the simplest thing to do is map stuff and see what the 
 driver puts 
 >> 
 >> in the db. It's possible the driver forces metric (or not metric) 
 and 
 >> does the conversions under the hood before weewx ever sees the 
 assembled 
 >> LOOP. Sometimes it's easier to just look at the code or do a little 
 >> experimentation. 
 >> 
 >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 
 david.a@gmail.com 
 >> wrote: 
 >> 
 >>> Vince, if i'm reading your post correctly (and carefully reading 
 the 
 >>> links you've provided), weewx.sdb stores all elements in a 
 unit-base type 
 >>> 
 >>> as specified in the usUnits group (*"Each observation type, such 
 >>> as outTemp or pressure, is associated with a unit group, such 
 >>> as group_temperature or group_pressure. Each unit group is 
 associated 
 >>> with 
 >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an 
 >>> entry in [StdConvert] section "target_unit = us " i can assume that 
 all 
 >>> weewx.sdb entries conform 

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Gary:
ls -l /home/david/Downloads:
-r 1 david david 1518145 Mar  3 18:02 
weewx-belchertown-release-1.2.tar.gz
and i used the fully qualified sudo string for execution:
sudo /home/weewx/bin/wee_extension --install 
/home/david/Downloads/weewx-belchertown-1.2.tar.gz

On Thursday, March 4, 2021 at 6:40:46 PM UTC-8 gjr80 wrote:

> Did you ls the directory containing the extension package to confirm the 
> file name? According to the Belchertown repo the 1.2 extension package is 
> named weewx-belchertown-release-1.2.tar.gz, slightly different to that used 
> in your commands.
>
> Gary
>
> On Friday, 5 March 2021 at 12:28:08 UTC+10 david.a@gmail.com wrote:
>
>> Vince - thanks! I'll take that approach on the imports!
>>
>> Glenn:
>> I had hand-transcribed the command entry - i'd entered the correct 
>> command string:
>> sudo /home/weewx/bin/wee_extension --install 
>> /home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
>> /tmp/wee-extension-out.txt
>>
>> This is the results:
>> ==
>> Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/wee_extension", line 88, in 
>> main()
>>   File "/home/weewx/bin/wee_extension", line 80, in main
>> ext.install_extension(options.install)
>>
>>   File "/home/weewx/bin/weecfg/extension.py", line 134, in 
>> install_extension
>> raise InstallError("Extension '%s' not found." % extension_path)
>> weecfg.extension.InstallError: Extension 
>> '/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
>> 
>>
>> No info about where to put the tar.gz file. Again, i'd used the 
>> "setup.py" script to install weewx, so all the relevant folders are off 
>> "/home". 
>> /David
>> On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
>>
>>> /home/david/Downloads/weewx-belchertown.1.2.tar.gz 
>>>
>>> Check the filename 
>>>
>>> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet) 
>>> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at 
>>>
>>> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>>>  
>>>
>>> note: there are 2 dashes in the correct name. 
>>>
>>> On 04/03/2021, David Prellwitz  wrote: 
>>> > error trying to install belchertown. my weewx install was using 
>>> setup.py. I 
>>> > 
>>> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
>>> folder. 
>>> > I ran the sudo wee-extension command and get "File 
>>> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension 
>>> > weecfg.extension.InstallError: Extension 
>>> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found. 
>>> > can't find what i did wrong. Should i extract the tar.gz file first? 
>>> move 
>>> > it to another folder to start install? 
>>> > /David 
>>> > 
>>> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote: 
>>> > 
>>> >> Lightning is difficult because there's no units for 'energy' in the 
>>> UDP 
>>> >> API. I might also add perhaps don't bother, as lightning is bogus 
>>> anyway. 
>>> >> 
>>> >> It's what your sensor reported, but it is not remotely close to the 
>>> >> crowd-sourced info their web or mobile interfaces provide, of which 
>>> your 
>>> >> sensor measurements are just a small part of what they aggregate and 
>>> >> display. 
>>> >> 
>>> >> I think the simplest thing to do is map stuff and see what the driver 
>>> puts 
>>> >> 
>>> >> in the db. It's possible the driver forces metric (or not metric) and 
>>> >> does the conversions under the hood before weewx ever sees the 
>>> assembled 
>>> >> LOOP. Sometimes it's easier to just look at the code or do a little 
>>> >> experimentation. 
>>> >> 
>>> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com 
>>> >> wrote: 
>>> >> 
>>> >>> Vince, if i'm reading your post correctly (and carefully reading the 
>>> >>> links you've provided), weewx.sdb stores all elements in a unit-base 
>>> type 
>>> >>> 
>>> >>> as specified in the usUnits group (*"Each observation type, such 
>>> >>> as outTemp or pressure, is associated with a unit group, such 
>>> >>> as group_temperature or group_pressure. Each unit group is 
>>> associated 
>>> >>> with 
>>> >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an 
>>> >>> entry in [StdConvert] section "target_unit = us " i can assume that 
>>> all 
>>> >>> weewx.sdb entries conform to the US Group column. further assumption 
>>> is 
>>> >>> that if WeatherFlow Tempest device provides data in m/b and i spec 
>>> it as 
>>> >>> 
>>> >>> m/b for the LOOP process, it will be converted to inHg as part of 
>>> the UDP 
>>> >>> 
>>> >>> LOOP process. If i import data from WF using the API's i just need 
>>> to 
>>> >>> spec 
>>> >>> the API page's listing of unit WF will be providing for those fields 
>>> and 
>>> >>> 
>>> >>> wee_import will correct those to the weewx.sdb needed 

Re: [weewx-user] Re: ERROR weewx.reportengine: **** TypeError: list indices must be integers or slices, not str

[Andre]

Thanks guys, I could solve my problem.

tke...@gmail.com schrieb am Donnerstag, 4. März 2021 um 16:45:07 UTC+1:

> As Karen says, you have two errors. I cannot speak to the error in the 
> Belchertown skin. 
>
> However, the upload to wetter.com may have failed because you  have an 
> older version of the wetter extension. This error was fixed in V0.7. Try 
> upgrading your copy of the extension.
>
> On Thu, Mar 4, 2021 at 2:57 AM Karen K  wrote:
>
>> I see 2 errors that seem independent to me:
>>
>>- Upload to wetter.com fails
>>- AerisWeather data could not be downloaded
>>
>> I would start checking the account at both those services.
>>
>> Andre schrieb am Donnerstag, 4. März 2021 um 10:08:28 UTC+1:
>>
>>> First: I use WeeWX 4.4.0.0 at Raspberry Pi 4. Skin Belchertown.
>>>
>>> Yesterday WeeWX has stopped working. Last data are from 2021-03-03 at 
>>> 19:40 MEZ.
>>> MQTT is working as aspected.
>>>
>>> I've tried:
>>>
>>> sudo wee_database weewx.conf --drop-daily
>>> sudo wee_database weewx.conf --rebuild-daily
>>> sudo wee_database --fix-strings
>>>
>>> ---Here my log---
>>> Mar  4 10:00:07 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:08 CET (1614848408)
>>> Mar  4 10:00:09 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:10 CET (1614848410)
>>> Mar  4 10:00:11 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:12 CET (1614848412)
>>> Mar  4 10:00:14 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:14 CET (1614848414)
>>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Getting 
>>> archive packets since 2021-03-04 09:55:00 CET (1614848100)
>>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle 
>>> wake up of console successful
>>> Mar  4 10:00:15 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:16 CET (1614848416)
>>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: 
>>> Retrieving 1 page(s); starting index= 1
>>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
>>> 2021-03-04 10:00:00 CET (1614848400) to database 'weewx.sdb'
>>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
>>> 2021-03-04 10:00:00 CET (1614848400) to daily summary in 'weewx.sdb'
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: DMPAFT 
>>> complete: page timestamp 2021-02-23 12:45:00 CET (1614080700) less than 
>>> final timestamp 2021-03-04 10:00:00 CET (1614848400)
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Catch up 
>>> complete.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running 
>>> reports for latest time in the database.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: 
>>> Requesting 200 LOOP packets.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
>>> 'SeasonsReport' not enabled. Skipping.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
>>> 'SmartphoneReport' not enabled. Skipping.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
>>> 'MobileReport' not enabled. Skipping.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
>>> 'StandardReport' not enabled. Skipping.
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running 
>>> report 'Belchertown'
>>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: MQTT: Published 
>>> record 2021-03-04 10:00:00 CET (1614848400)
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle 
>>> wake up of console successful
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
>>> 'Belchertown'
>>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: Windy: Published 
>>> record 2021-03-04 10:00:00 CET (1614848400)
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: Wetter: Unexpected 
>>> exception of type 
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** Traceback (most 
>>> recent call last):
>>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.restx: CWOP: Connected to 
>>> server cwop.aprs.net:14580
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/weewx/restx.py", line 381, in run_loop
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>>>  self.process_record(_record, dbmanager)
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/weewx/restx.py", line 446, in process_record
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>>>  self.post_with_retries(_request, data)
>>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
>>> "/usr/share/weewx/weewx/restx.py", line 485, in post_with_retries
>>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: AWEKAS: Published 
>>> record 2021-03-04 10:00:00 CET 

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

[monmul]

pi@WeatherPi:~ $ lsusb
Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
drive
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@WeatherPi:~ $ 

Having pulled out the line from the Envoy, rebooted, and hit lsusb, by 
elimination the "Future Technology" must be the one!

On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote:

> or just note which /dev/ttyUSB* comes and goes
>
> once identified i like to put in a udev rule to create a known device file 
> such as /dev/vp2
>
> > On 5 Mar 2021, at 12:33 pm, vince  wrote:
> > 
> > One good way to identify a USB device is to unplug it, plug it back in, 
> and see what the 'dmesg' command reported. You'll tend to be able to figure 
> out which USB port it connected to that way.
>

-- 
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/f7d99875-d320-48d0-96bf-678f06efb18dn%40googlegroups.com.

Re: [weewx-user] ;:; SQLite schema report

[gjr80]

Did you ls the directory containing the extension package to confirm the 
file name? According to the Belchertown repo the 1.2 extension package is 
named weewx-belchertown-release-1.2.tar.gz, slightly different to that used 
in your commands.

Gary

On Friday, 5 March 2021 at 12:28:08 UTC+10 david.a@gmail.com wrote:

> Vince - thanks! I'll take that approach on the imports!
>
> Glenn:
> I had hand-transcribed the command entry - i'd entered the correct command 
> string:
> sudo /home/weewx/bin/wee_extension --install 
> /home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
> /tmp/wee-extension-out.txt
>
> This is the results:
> ==
> Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 88, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 80, in main
> ext.install_extension(options.install)
>
>   File "/home/weewx/bin/weecfg/extension.py", line 134, in 
> install_extension
> raise InstallError("Extension '%s' not found." % extension_path)
> weecfg.extension.InstallError: Extension 
> '/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.
> 
>
> No info about where to put the tar.gz file. Again, i'd used the "setup.py" 
> script to install weewx, so all the relevant folders are off "/home". 
> /David
> On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:
>
>> /home/david/Downloads/weewx-belchertown.1.2.tar.gz 
>>
>> Check the filename 
>>
>> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet) 
>> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at 
>>
>> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>>  
>>
>> note: there are 2 dashes in the correct name. 
>>
>> On 04/03/2021, David Prellwitz  wrote: 
>> > error trying to install belchertown. my weewx install was using 
>> setup.py. I 
>> > 
>> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
>> folder. 
>> > I ran the sudo wee-extension command and get "File 
>> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension 
>> > weecfg.extension.InstallError: Extension 
>> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found. 
>> > can't find what i did wrong. Should i extract the tar.gz file first? 
>> move 
>> > it to another folder to start install? 
>> > /David 
>> > 
>> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote: 
>> > 
>> >> Lightning is difficult because there's no units for 'energy' in the 
>> UDP 
>> >> API. I might also add perhaps don't bother, as lightning is bogus 
>> anyway. 
>> >> 
>> >> It's what your sensor reported, but it is not remotely close to the 
>> >> crowd-sourced info their web or mobile interfaces provide, of which 
>> your 
>> >> sensor measurements are just a small part of what they aggregate and 
>> >> display. 
>> >> 
>> >> I think the simplest thing to do is map stuff and see what the driver 
>> puts 
>> >> 
>> >> in the db. It's possible the driver forces metric (or not metric) and 
>> >> does the conversions under the hood before weewx ever sees the 
>> assembled 
>> >> LOOP. Sometimes it's easier to just look at the code or do a little 
>> >> experimentation. 
>> >> 
>> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com 
>> >> wrote: 
>> >> 
>> >>> Vince, if i'm reading your post correctly (and carefully reading the 
>> >>> links you've provided), weewx.sdb stores all elements in a unit-base 
>> type 
>> >>> 
>> >>> as specified in the usUnits group (*"Each observation type, such 
>> >>> as outTemp or pressure, is associated with a unit group, such 
>> >>> as group_temperature or group_pressure. Each unit group is associated 
>> >>> with 
>> >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an 
>> >>> entry in [StdConvert] section "target_unit = us " i can assume that 
>> all 
>> >>> weewx.sdb entries conform to the US Group column. further assumption 
>> is 
>> >>> that if WeatherFlow Tempest device provides data in m/b and i spec it 
>> as 
>> >>> 
>> >>> m/b for the LOOP process, it will be converted to inHg as part of the 
>> UDP 
>> >>> 
>> >>> LOOP process. If i import data from WF using the API's i just need to 
>> >>> spec 
>> >>> the API page's listing of unit WF will be providing for those fields 
>> and 
>> >>> 
>> >>> wee_import will correct those to the weewx.sdb needed units? If i 
>> wish 
>> >>> to 
>> >>> have lightning information, i'll need to map to those "signal7/8" 
>> and/or 
>> >>> 
>> >>> "xxx/yyy" fields, and i'll have to figure out what units they use? 
>> >>> thanks! 
>> >>> 
>> >>> 
>> >>> On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz 
>> wrote: 
>> >>> 
>>  Vince - yea, my way of apologizing for running down some rabbit hole 
>> i 
>>  didn't need to. Thanks for the guidance, I'll map it out and 

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

[Graham Eddy]

or just note which /dev/ttyUSB* comes and goes

once identified i like to put in a udev rule to create a known device file such 
as /dev/vp2

> On 5 Mar 2021, at 12:33 pm, vince  wrote:
> 
> One good way to identify a USB device is to unplug it, plug it back in, and 
> see what the 'dmesg' command reported.You'll tend to be able to figure 
> out which USB port it connected to that way.

-- 
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/00A833D2-4689-4DF1-916D-5B7A88CA5EF8%40gmail.com.

Re: [weewx-user] ;:; SQLite schema report

[David Prellwitz]

Vince - thanks! I'll take that approach on the imports!

Glenn:
I had hand-transcribed the command entry - i'd entered the correct command 
string:
sudo /home/weewx/bin/wee_extension --install 
/home/david/Downloads/weewx-belchertown-1.2.tar.gz |& tee 
/tmp/wee-extension-out.txt

This is the results:
==
Request to install '/home/david/Downloads/weewx-belchertown-1.2.tar.gz'
Traceback (most recent call last):
  File "/home/weewx/bin/wee_extension", line 88, in 
main()
  File "/home/weewx/bin/wee_extension", line 80, in main
ext.install_extension(options.install)
  File "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 
'/home/david/Downloads/weewx-belchertown-1.2.tar.gz' not found.


No info about where to put the tar.gz file. Again, i'd used the "setup.py" 
script to install weewx, so all the relevant folders are off "/home". 
/David
On Wednesday, March 3, 2021 at 9:41:10 PM UTC-8 Glenn McKechnie wrote:

> /home/david/Downloads/weewx-belchertown.1.2.tar.gz
>
> Check the filename
>
> Is it really ... weewx-belchertown.1.2.tar.gz ( as per your snippet)
> or is it ... weewx-belchertown-1.2.tar.gz as per the release page at
>
> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-1.2
>
> note: there are 2 dashes in the correct name.
>
> On 04/03/2021, David Prellwitz  wrote:
> > error trying to install belchertown. my weewx install was using 
> setup.py. I
> >
> > downloaded the belchertown 1.2 tar.gz into my home/david/Downloads 
> folder.
> > I ran the sudo wee-extension command and get "File
> > "/home/weewx/bin/weecfg/extension.py", line 134, in install_extension
> > weecfg.extension.InstallError: Extension
> > '/home/david/Downloads/weewx-belchertown.1.2.tar.gz' not found.
> > can't find what i did wrong. Should i extract the tar.gz file first? move
> > it to another folder to start install?
> > /David
> >
> > On Wednesday, March 3, 2021 at 2:51:02 PM UTC-8 vince wrote:
> >
> >> Lightning is difficult because there's no units for 'energy' in the UDP
> >> API. I might also add perhaps don't bother, as lightning is bogus 
> anyway.
> >>
> >> It's what your sensor reported, but it is not remotely close to the
> >> crowd-sourced info their web or mobile interfaces provide, of which your
> >> sensor measurements are just a small part of what they aggregate and
> >> display.
> >>
> >> I think the simplest thing to do is map stuff and see what the driver 
> puts
> >>
> >> in the db. It's possible the driver forces metric (or not metric) and
> >> does the conversions under the hood before weewx ever sees the assembled
> >> LOOP. Sometimes it's easier to just look at the code or do a little
> >> experimentation.
> >>
> >> On Wednesday, March 3, 2021 at 1:42:13 PM UTC-8 david.a@gmail.com
> >> wrote:
> >>
> >>> Vince, if i'm reading your post correctly (and carefully reading the
> >>> links you've provided), weewx.sdb stores all elements in a unit-base 
> type
> >>>
> >>> as specified in the usUnits group (*"Each observation type, such
> >>> as outTemp or pressure, is associated with a unit group, such
> >>> as group_temperature or group_pressure. Each unit group is associated
> >>> with
> >>> a unit type such as degree_F or mbar.*" So, as my weewx.conf has an
> >>> entry in [StdConvert] section "target_unit = us " i can assume that all
> >>> weewx.sdb entries conform to the US Group column. further assumption is
> >>> that if WeatherFlow Tempest device provides data in m/b and i spec it 
> as
> >>>
> >>> m/b for the LOOP process, it will be converted to inHg as part of the 
> UDP
> >>>
> >>> LOOP process. If i import data from WF using the API's i just need to
> >>> spec
> >>> the API page's listing of unit WF will be providing for those fields 
> and
> >>>
> >>> wee_import will correct those to the weewx.sdb needed units? If i wish
> >>> to
> >>> have lightning information, i'll need to map to those "signal7/8" 
> and/or
> >>>
> >>> "xxx/yyy" fields, and i'll have to figure out what units they use?
> >>> thanks!
> >>>
> >>>
> >>> On Wednesday, March 3, 2021 at 11:34:05 AM UTC-8 David Prellwitz wrote:
> >>>
>  Vince - yea, my way of apologizing for running down some rabbit hole i
>  didn't need to. Thanks for the guidance, I'll map it out and see if it
>  works. I'll try to get a decent mapping setup and forward to you for
>  comment.
>  My next attempt is to install and use Belchertown skins.
> 
>  On Wednesday, March 3, 2021 at 8:31:12 AM UTC-8 vince wrote:
> 
> > That's a lot of words, but I still think you're possibly 
> overthinking.
> >
> > Anyway, I'm pretty lost re: what you're actually trying to do.
> >
> > - There is a sample mapping of Tempest UDP elements to Weewx
> > database elements both in the driver code and in the docs on the
> > 

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

[vince]

One good way to identify a USB device is to unplug it, plug it back in, and 
see what the 'dmesg' command reported.You'll tend to be able to figure 
out which USB port it connected to that way.

-- 
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/8ab62c82-a65c-49f4-9881-12604802cfban%40googlegroups.com.

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

[Tom Keffer]

The device "Future Technologies" is probably your Envoy.

On Thu, Mar 4, 2021 at 1:35 PM monmul  wrote:

> Not using serial...using USB.
>
> On Friday, 5 March 2021 at 10:34:32 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ lsusb
>> Bus 001 Device 006: ID 0403:6001 Future Technology Devices International,
>> Ltd FT232 Serial (UART) IC
>> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash
>> drive
>> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> pi@WeatherPi:~ $
>>
>>
>> On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:
>>
>>> Well, if you're sure you have the right port (/dev/ttyUSB0), and you
>>> have correctly completed the test (a couple of enters, followed by ENTER,
>>> all caps) and you got nothing back, then that is as definitive a test that
>>> I know of that you have a connectivity problem.
>>>
>>> Do you have a USB version of the logger? Or, if you have a serial
>>> version, are you using a serial-to-usb converter? Either way, make sure
>>> your computer is recognizing the USB connection to the logger:
>>>
>>> *lsusb*
>>>
>>> If you have a serial version of the logger (very rare these days), then
>>> what serial port are you plugging it into?
>>>
>>>
>>>
>>> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>>>
 Yes, apologieswas in a rush typing and did not review."new
 envoy"..it should be...and "initiation" is the other typo!

 On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:

> ‘new’ envoy?
>
> Gary
>
> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>
>> What do you mean by "net Envoy"? If you are using a serial port like
>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
>> network connector. Or, are you using an IP logger?
>>
>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>
>>> I have not had time to do the reseating yethopefully later
>>> today. One thing strikes me (probably becuase it has been so long since 
>>> I
>>> set it up) I just switched envoys, how does the net envoy know what to
>>> do...I have not gone to any itiation or set up page etcI just 
>>> plugged
>>> and supposed it would go. Am I missing something?
>>>
>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>>
 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
>>> 

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

[monmul]

Not using serial...using USB.

On Friday, 5 March 2021 at 10:34:32 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ lsusb
> Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, 
> Ltd FT232 Serial (UART) IC
> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
> drive
> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> pi@WeatherPi:~ $ 
>
>
> On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:
>
>> Well, if you're sure you have the right port (/dev/ttyUSB0), and you have 
>> correctly completed the test (a couple of enters, followed by ENTER, all 
>> caps) and you got nothing back, then that is as definitive a test that I 
>> know of that you have a connectivity problem.
>>
>> Do you have a USB version of the logger? Or, if you have a serial 
>> version, are you using a serial-to-usb converter? Either way, make sure 
>> your computer is recognizing the USB connection to the logger:
>>
>> *lsusb*
>>
>> If you have a serial version of the logger (very rare these days), then 
>> what serial port are you plugging it into?
>>
>>
>>
>> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>>
>>> Yes, apologieswas in a rush typing and did not review."new 
>>> envoy"..it should be...and "initiation" is the other typo!
>>>
>>> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>>>
 ‘new’ envoy?

 Gary

 On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. 
>> One thing strikes me (probably becuase it has been so long since I set 
>> it 
>> up) I just switched envoys, how does the net envoy know what to do...I 
>> have 
>> not gone to any itiation or set up page etcI just plugged and 
>> supposed 
>> it would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> 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
>>

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

[monmul]

pi@WeatherPi:~ $ lsusb
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, 
Ltd FT232 Serial (UART) IC
Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
drive
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@WeatherPi:~ $ 


On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:

> Well, if you're sure you have the right port (/dev/ttyUSB0), and you have 
> correctly completed the test (a couple of enters, followed by ENTER, all 
> caps) and you got nothing back, then that is as definitive a test that I 
> know of that you have a connectivity problem.
>
> Do you have a USB version of the logger? Or, if you have a serial version, 
> are you using a serial-to-usb converter? Either way, make sure your 
> computer is recognizing the USB connection to the logger:
>
> *lsusb*
>
> If you have a serial version of the logger (very rare these days), then 
> what serial port are you plugging it into?
>
>
>
> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>
>> Yes, apologieswas in a rush typing and did not review."new 
>> envoy"..it should be...and "initiation" is the other typo!
>>
>> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>>
>>> ‘new’ envoy?
>>>
>>> Gary
>>>
>>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>>>
 What do you mean by "net Envoy"? If you are using a serial port like 
 /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
 network connector. Or, are you using an IP logger?

 On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:

> I have not had time to do the reseating yethopefully later today. 
> One thing strikes me (probably becuase it has been so long since I set it 
> up) I just switched envoys, how does the net envoy know what to do...I 
> have 
> not gone to any itiation or set up page etcI just plugged and 
> supposed 
> it would go. Am I missing something?
>
> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>
>> 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

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

[Tom Keffer]

Well, if you're sure you have the right port (/dev/ttyUSB0), and you have
correctly completed the test (a couple of enters, followed by ENTER, all
caps) and you got nothing back, then that is as definitive a test that I
know of that you have a connectivity problem.

Do you have a USB version of the logger? Or, if you have a serial version,
are you using a serial-to-usb converter? Either way, make sure your
computer is recognizing the USB connection to the logger:

*lsusb*

If you have a serial version of the logger (very rare these days), then
what serial port are you plugging it into?



On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:

> Yes, apologieswas in a rush typing and did not review."new
> envoy"..it should be...and "initiation" is the other typo!
>
> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>
>> ‘new’ envoy?
>>
>> Gary
>>
>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>>
>>> What do you mean by "net Envoy"? If you are using a serial port like
>>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
>>> network connector. Or, are you using an IP logger?
>>>
>>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>>
 I have not had time to do the reseating yethopefully later today.
 One thing strikes me (probably becuase it has been so long since I set it
 up) I just switched envoys, how does the net envoy know what to do...I have
 not gone to any itiation or set up page etcI just plugged and supposed
 it would go. Am I missing something?

 On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:

> 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 

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

[monmul]

Yes, apologieswas in a rush typing and did not review."new 
envoy"..it should be...and "initiation" is the other typo!

On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:

> ‘new’ envoy?
>
> Gary
>
> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>
>> What do you mean by "net Envoy"? If you are using a serial port like 
>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
>> network connector. Or, are you using an IP logger?
>>
>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>
>>> I have not had time to do the reseating yethopefully later today. 
>>> One thing strikes me (probably becuase it has been so long since I set it 
>>> up) I just switched envoys, how does the net envoy know what to do...I have 
>>> not gone to any itiation or set up page etcI just plugged and supposed 
>>> it would go. Am I missing something?
>>>
>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>>
 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 

[weewx-user] Re: Wrong pressure value at AWEKAS

[gjr80]

Hi,

As I understand it both WU and AWEKAS expect WeeWX field ‘barometer’ for 
pressure. Have you set debug = 2, restarted WeeWX and checked the log to 
see what data is actually being posted by WeeWX? Also, would help to know 
something about your setup, what station do you use and which WeeWX version 
did you upgrade from/to.

Gary 
On Friday, 5 March 2021 at 04:40:01 UTC+10 felix.m...@gmail.com wrote:

>
> Hello,
>
> after updating weewx I have some trouble with AWEKAS:
>
> Pressure (station): 
> 1,014.77 hPa --> ok
>
> Pressure posted to AWEKAS:
> 1030.4 hPa --> not ok
>
> Pressure posted to WU:
> 1,014.77 hPa --> ok 
>
> any ideas?
>

-- 
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/229d0733-e5ea-4d60-b3a6-74368d4efb4an%40googlegroups.com.

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

[gjr80]

‘new’ envoy?

Gary

On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. One 
>> thing strikes me (probably becuase it has been so long since I set it up) I 
>> just switched envoys, how does the net envoy know what to do...I have not 
>> gone to any itiation or set up page etcI just plugged and supposed it 
>> would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> 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] 

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

[gjr80]

‘new’ logger?

Gary

On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. One 
>> thing strikes me (probably becuase it has been so long since I set it up) I 
>> just switched envoys, how does the net envoy know what to do...I have not 
>> gone to any itiation or set up page etcI just plugged and supposed it 
>> would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> 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] 

Re: [weewx-user] Re: weewx stopped working after restart

[miso k]

Thanks Tom,
the aqi guy does not respond for longer time, but i restarted the weewx 
today and it is working. AQI is taking only values from last 12 hours, this 
is maybe the reason.

Michal

Dátum: streda 3. marca 2021, čas: 22:57:53 UTC+1, odosielateľ: 
tke...@gmail.com

> It looks like the extension aqi is unprepared to accept null (Python None) 
> outside temperature values (outTemp). 
>
> Observation values are set to None to signal bad or missing data. All 
> well-behaved extensions should be prepared for that.
>
> On Wed, Mar 3, 2021 at 1:29 PM miso k  wrote:
>
>> I tried:
>>
>> sudo wee_database weewx.conf --drop-daily
>> sudo wee_database weewx.conf --rebuild-daily
>> sudo wee_database --fix-strings
>>
>> nothing helped.
>>
>> Dátum: streda 3. marca 2021, čas: 21:03:30 UTC+1, odosielateľ: miso k
>>
>>> Hello, 
>>> after restart, my weewx 4.4 on RPi3 stopped working. this is the log 
>>> with debug = 1
>>>
>>> Mar  3 20:58:05 WeeWX systemd[1]: Starting LSB: weewx weather system...
>>> Mar  3 20:58:06 WeeWX weewx[1306] INFO __main__: Initializing weewx 
>>> version 4.4.0
>>> Mar  3 20:58:06 WeeWX weewx[1306] INFO __main__: Using Python 3.7.3 
>>> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
>>> Mar  3 20:58:06 WeeWX weewx[1306] INFO __main__: Platform 
>>> Linux-5.10.11-v7+-armv7l-with-debian-10.8
>>> Mar  3 20:58:06 WeeWX weewx[1306] INFO __main__: Locale is 'sk_SK.UTF-8'
>>> Mar  3 20:58:06 WeeWX weewx[1306] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO __main__: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO __main__: Debug is 1
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG __main__: Initializing engine
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO weewx.engine: Loading station 
>>> type Interceptor (user.interceptor)
>>> Mar  3 20:58:06 WeeWX weewx[1294]: Starting weewx weather system: weewx.
>>> Mar  3 20:58:06 WeeWX systemd[1]: Started LSB: weewx weather system.
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.interceptor: driver version 
>>> is 0.53
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.interceptor: device type: 
>>> observer
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.interceptor: mode is listen
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.interceptor: listen on :8085
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.interceptor: sensor map: 
>>> {'pressure': 'pressure', 'barometer': 'barometer', 'outHumidity': 
>>> 'humidity_out', 'inHumidity': 'humidity_in', 'outTemp': 'temperature_out', 
>>> 'inTemp': 'temperature_in', 'windSpeed': 'wind_speed', 'windGust': 
>>> 'wind_gust', 'windDir': 'wind_dir', 'windGustDir': 'wind_gust_dir', 
>>> 'radiation': 'solar_radiation', 'dewpoint': 'dewpoint', 'windchill': 
>>> 'windchill', 'rain': 'rain', 'rainRate': 'rain_rate', 'UV': 'uv', 
>>> 'txBatteryStatus': 'battery', 'extraTemp1': 'temperature_1', 'extraTemp2': 
>>> 'temperature_2', 'extraTemp3': 'temperature_3', 'extraHumid1': 
>>> 'humidity_1', 'extraHumid2': 'humidity_2', 'soilTemp1': 
>>> 'soil_temperature_1', 'soilTemp2': 'soil_temperature_2', 'soilMoist1': 
>>> 'soil_moisture_1', 'soilMoist2': 'soil_moisture_2', 'soilMoist3': 
>>> 'soil_moisture_3', 'soilMoist4': 'soil_moisture_4', 'leafWet1': 
>>> 'leafwetness_1', 'leafWet2': 'leafwetness_2', 'pm2_5': 'pm2_5', 
>>> 'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5', 'extraTemp6': 
>>> 'temperature_6', 'extraTemp7': 'temperature_7', 'extraTemp8': 
>>> 'temperature_8', 'extraHumid3': 'humidity_3', 'extraHumid4': 'humidity_4', 
>>> 'extraHumid5': 'humidity_5', 'extraHumid6': 'humidity_6', 'extraHumid7': 
>>> 'humidity_7', 'extraHumid8': 'humidity_8', 'soilTemp3': 
>>> 'soil_temperature_3', 'soilTemp4': 'soil_temperature_4'}
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG user.interceptor: start tcp 
>>> server
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG weewx.engine: Loading service 
>>> weewx.engine.StdTimeSynch
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG weewx.engine: Finished loading 
>>> service weewx.engine.StdTimeSynch
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG weewx.engine: Loading service 
>>> user.filepile.FilePile
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.filepile: Using 
>>> /var/www/html/weewx/sds011pmdata.txt with the 'METRICWX' unit system
>>> Mar  3 20:58:06 WeeWX weewx[1310] INFO user.filepile: Label map is 
>>> {'SDS_P1': 'pm10_0', 'SDS_P2': 'pm2_5', 'BME280_temperature': 'extraTemp1', 
>>> 'BME280_humidity': 'extraHumid1', 'signal': 'signal1'}
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG weewx.engine: Finished loading 
>>> service user.filepile.FilePile
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG weewx.engine: Loading service 
>>> user.MQTTSubscribe.MQTTSubscribeService
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG user.MQTTSubscribe: (Service) 
>>> Using weewx version 4.4.0
>>> Mar  3 20:58:06 WeeWX weewx[1310] DEBUG user.MQTTSubscribe: (Service) 
>>> Using Python 3.7.3 (default, Jul 25 2020, 13:03:44) 

[weewx-user] Wrong pressure value at AWEKAS

[felix.m...@gmail.com]

Hello,

after updating weewx I have some trouble with AWEKAS:

Pressure (station): 
1,014.77 hPa --> ok

Pressure posted to AWEKAS:
1030.4 hPa --> not ok

Pressure posted to WU:
1,014.77 hPa --> ok 

any ideas?

-- 
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/9c91789c-c058-4dab-8a71-107c645ecc50n%40googlegroups.com.

[weewx-user] Re: Raspberry pi with sensor (temperature/humidity) working?

[storm...@gmail.com]

Did you read the following:

https://groups.google.com/g/weewx-user/c/udZCCCJlNE8/m/LeR2Mp3iBQAJ

On Thursday, March 4, 2021 at 5:34:07 AM UTC-5 giulianodir...@gmail.com 
wrote:

> Hey
>
> I'm quite new to the field with the Raspberry Pi. Now to my question.. We 
> got a job at school to implement a scientific project with the help of a 
> Raspberry Pie. Since I am very interested in the weather and climatology, I 
> thought that I would build a climate logger/weather staion with the help of 
> a Raspberry Pie. Now before I buy the components, I wanted to let someone 
> look over them again. My idea is using sensors (air 
> pressure/temperature/humidity /CO2 content). 
> display. After a few hours of research I came across the program "Weewx". 
> Now my question is whether it would be possible to implement this project 
> using sensors that I connect to a Raspberry Pi. Since I also met suitable 
> hardware in the documentation on very expensive "finished" weather station 
> modules, I got a bit stupid.
>
> I would be pleased to receive an answer ^^
>
> Hardware:
> -Raspberry Pi Zero
>
> -Air pressure/humidity and temperature sensor  
>
> Would this work with the Weewx program? 
>

-- 
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/dec17274-ea72-40f7-9129-2598d7a9n%40googlegroups.com.

Re: [weewx-user] Rest Service for OpenSenseMap

[Karen K]

I tried it, and it is working.

sbar...@gmail.com schrieb am Sonntag, 28. Februar 2021 um 22:10:29 UTC+1:

> Hi, 
>
> Thanks for the info. I updated the installer.
>
> On Sunday, February 28, 2021 at 9:14:57 PM UTC+1 pmcg...@gmail.com wrote:
>
>> Your installer adds UsUnit instead of the required UsUnits in your code.  
>> Otherwise seems to work good.
>>
>> Thanks!
>>
>> On Sunday, February 28, 2021 at 9:34:30 AM UTC-7 sbar...@gmail.com wrote:
>>
>>> You are right, this override is not needed and has been removed from 
>>> v0.2 :)
>>>
>>> On Sunday, February 28, 2021 at 4:48:47 PM UTC+1 tke...@gmail.com wrote:
>>>
 Sorry. I meant post_request().

 On Sun, Feb 28, 2021 at 12:04 AM sbar...@gmail.com  
 wrote:

> Well Thank you.
>
> I added the extension to the wiki.
>
> The get_request override allows for setting the authkey in the header.
>
> On Sunday, February 28, 2021 at 3:17:18 AM UTC+1 tke...@gmail.com 
> wrote:
>
>> 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+...@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+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/ae59e6e7-b866-4157-afda-8a610f4d0acfn%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/71e81014-c3d5-4d5d-a852-e81ad007250an%40googlegroups.com.

Re: [weewx-user] Re: ERROR weewx.reportengine: **** TypeError: list indices must be integers or slices, not str

[Tom Keffer]

As Karen says, you have two errors. I cannot speak to the error in the
Belchertown skin.

However, the upload to wetter.com may have failed because you  have an
older version of the wetter extension. This error was fixed in V0.7. Try
upgrading your copy of the extension.

On Thu, Mar 4, 2021 at 2:57 AM Karen K  wrote:

> I see 2 errors that seem independent to me:
>
>- Upload to wetter.com fails
>- AerisWeather data could not be downloaded
>
> I would start checking the account at both those services.
>
> Andre schrieb am Donnerstag, 4. März 2021 um 10:08:28 UTC+1:
>
>> First: I use WeeWX 4.4.0.0 at Raspberry Pi 4. Skin Belchertown.
>>
>> Yesterday WeeWX has stopped working. Last data are from 2021-03-03 at
>> 19:40 MEZ.
>> MQTT is working as aspected.
>>
>> I've tried:
>>
>> sudo wee_database weewx.conf --drop-daily
>> sudo wee_database weewx.conf --rebuild-daily
>> sudo wee_database --fix-strings
>>
>> ---Here my log---
>> Mar  4 10:00:07 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:08 CET (1614848408)
>> Mar  4 10:00:09 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:10 CET (1614848410)
>> Mar  4 10:00:11 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:12 CET (1614848412)
>> Mar  4 10:00:14 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:14 CET (1614848414)
>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Getting
>> archive packets since 2021-03-04 09:55:00 CET (1614848100)
>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle
>> wake up of console successful
>> Mar  4 10:00:15 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:16 CET (1614848416)
>> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Retrieving
>> 1 page(s); starting index= 1
>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record
>> 2021-03-04 10:00:00 CET (1614848400) to database 'weewx.sdb'
>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record
>> 2021-03-04 10:00:00 CET (1614848400) to daily summary in 'weewx.sdb'
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: DMPAFT
>> complete: page timestamp 2021-02-23 12:45:00 CET (1614080700) less than
>> final timestamp 2021-03-04 10:00:00 CET (1614848400)
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Catch up
>> complete.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running
>> reports for latest time in the database.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Requesting
>> 200 LOOP packets.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report
>> 'SeasonsReport' not enabled. Skipping.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report
>> 'SmartphoneReport' not enabled. Skipping.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report
>> 'MobileReport' not enabled. Skipping.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report
>> 'StandardReport' not enabled. Skipping.
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running
>> report 'Belchertown'
>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: MQTT: Published
>> record 2021-03-04 10:00:00 CET (1614848400)
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle
>> wake up of console successful
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Found
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
>> 'Belchertown'
>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: Windy: Published
>> record 2021-03-04 10:00:00 CET (1614848400)
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: Wetter: Unexpected
>> exception of type 
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** Traceback (most
>> recent call last):
>> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.restx: CWOP: Connected to
>> server cwop.aprs.net:14580
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 381, in run_loop
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>>  self.process_record(_record, dbmanager)
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 446, in process_record
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>>  self.post_with_retries(_request, data)
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/weewx/restx.py", line 485, in post_with_retries
>> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: AWEKAS: Published
>> record 2021-03-04 10:00:00 CET (1614848400)
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>>  self.check_response(_response)
>> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File
>> "/usr/share/weewx/user/wetter.py", line 143, in check_response
>> Mar  4 10:00:16 weewx 

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

[Tom Keffer]

What do you mean by "net Envoy"? If you are using a serial port like
/dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
network connector. Or, are you using an IP logger?

On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:

> I have not had time to do the reseating yethopefully later today. One
> thing strikes me (probably becuase it has been so long since I set it up) I
> just switched envoys, how does the net envoy know what to do...I have not
> gone to any itiation or set up page etcI just plugged and supposed it
> would go. Am I missing something?
>
> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>
>> 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
 

[weewx-user] Re: ERROR weewx.reportengine: **** TypeError: list indices must be integers or slices, not str

[Karen K]

I see 2 errors that seem independent to me:

   - Upload to wetter.com fails
   - AerisWeather data could not be downloaded
   
I would start checking the account at both those services.

Andre schrieb am Donnerstag, 4. März 2021 um 10:08:28 UTC+1:

> First: I use WeeWX 4.4.0.0 at Raspberry Pi 4. Skin Belchertown.
>
> Yesterday WeeWX has stopped working. Last data are from 2021-03-03 at 
> 19:40 MEZ.
> MQTT is working as aspected.
>
> I've tried:
>
> sudo wee_database weewx.conf --drop-daily
> sudo wee_database weewx.conf --rebuild-daily
> sudo wee_database --fix-strings
>
> ---Here my log---
> Mar  4 10:00:07 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:08 CET (1614848408)
> Mar  4 10:00:09 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:10 CET (1614848410)
> Mar  4 10:00:11 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:12 CET (1614848412)
> Mar  4 10:00:14 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:14 CET (1614848414)
> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Getting 
> archive packets since 2021-03-04 09:55:00 CET (1614848100)
> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle wake 
> up of console successful
> Mar  4 10:00:15 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:16 CET (1614848416)
> Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Retrieving 
> 1 page(s); starting index= 1
> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
> 2021-03-04 10:00:00 CET (1614848400) to database 'weewx.sdb'
> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
> 2021-03-04 10:00:00 CET (1614848400) to daily summary in 'weewx.sdb'
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: DMPAFT 
> complete: page timestamp 2021-02-23 12:45:00 CET (1614080700) less than 
> final timestamp 2021-03-04 10:00:00 CET (1614848400)
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Catch up 
> complete.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Requesting 
> 200 LOOP packets.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
> 'SeasonsReport' not enabled. Skipping.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
> 'StandardReport' not enabled. Skipping.
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running report 
> 'Belchertown'
> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
> 2021-03-04 10:00:00 CET (1614848400)
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle wake 
> up of console successful
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
> 'Belchertown'
> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: Windy: Published 
> record 2021-03-04 10:00:00 CET (1614848400)
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: Wetter: Unexpected 
> exception of type 
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** Traceback (most 
> recent call last):
> Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.restx: CWOP: Connected to 
> server cwop.aprs.net:14580
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 381, in run_loop
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>  self.process_record(_record, dbmanager)
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 446, in process_record
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>  self.post_with_retries(_request, data)
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 485, in post_with_retries
> Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: AWEKAS: Published 
> record 2021-03-04 10:00:00 CET (1614848400)
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
>  self.check_response(_response)
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
> "/usr/share/weewx/user/wetter.py", line 143, in check_response
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** if 
> txt.find('"errorcode":"100"') != -1 or \
> Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** TypeError: 
> argument should be integer or bytes-like object, not 'str'
> Mar  4 10:00:16 weewx weewx[7220] CRITICAL weewx.restx: Wetter: Thread 
> terminating. Reason: argument should be integer or bytes-like object, not 
> 'str'
> 

Re: [weewx-user] Re: Error at Translation Belchertown Skin

[Didier Decoodt]

Thank's

Le jeu. 4 mars 2021 à 10:08, Christian Radermacher <
radermacherchrist...@gmail.com> a écrit :

> I copied only the necessary sections to whew, conf.
> But consider, that the Section have other [ ] levels. Each Section is 2
> brackets deeper than in skin.conf.
>
> Regards
> Christian
>
> didier@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:59:14
> UTC+1:
>
>> Hi
>>
>> Is skin.conf could be « copied « completly in weewx.conf or just a part ?
>>
>> Didier
>>
>> Le jeu. 4 mars 2021 à 09:38, Manfred Maier  a
>> écrit :
>>
>>> Hi Christian,
>>> you might want to move all your customizations to the weewx.conf file
>>> (and not store them in skin.conf).
>>> The reason is: When you update the belchertown skin, all your changes to
>>> the skin.conf will be lost.
>>>
>>> Manfred
>>>
>>> radermache...@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:32:44
>>> UTC+1:
>>>
 Sorry, I saved the Problem.
 Started with a new skin.conf I transfer all Customizing step by step to
 the whew conf.
 No it worked correct, and is the better solution.

 Regards
 Christian

 Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36
 UTC+1:

> Hi,
> i have an error if I translate the Skin:
>
> All customizing I made in the skin.conf.
>
> If I haver the following in the skin.conf
> # General Forecast translations
> forecast_header = 7 Day Forecast
> daily_forecast  = Daily Forecast
> alert_in_effect = in effect until
> forecast_last_updated   = Last Updated on
> I get a parsing error.
> If remove this (forecast with aeris is on) I have a Problem at display
> the Timestamps.
> Maybe this is not the same error.
>
>
> --
>>> 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/c9d7df23-1b28-4604-832c-2ca8771c5f25n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> Quel temps fait-il à Auffargis  ?
>>
> --
> 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/cc4d99a8-7dd0-41df-82bb-8fa9530aca5an%40googlegroups.com
> 
> .
>


-- 
Quel temps fait-il à Auffargis  ?

-- 
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/CAAvt3%3DTMB%2B3TJ2zDVf2nkb99QqETXbbwxhCXeL9h5Lh4TjcoLQ%40mail.gmail.com.

[weewx-user] Raspberry pi with sensor (temperature/humidity) working?

[Giuliano Di Rosa]

Hey

I'm quite new to the field with the Raspberry Pi. Now to my question.. We 
got a job at school to implement a scientific project with the help of a 
Raspberry Pie. Since I am very interested in the weather and climatology, I 
thought that I would build a climate logger/weather staion with the help of 
a Raspberry Pie. Now before I buy the components, I wanted to let someone 
look over them again. My idea is using sensors (air 
pressure/temperature/humidity /CO2 content). 
display. After a few hours of research I came across the program "Weewx". 
Now my question is whether it would be possible to implement this project 
using sensors that I connect to a Raspberry Pi. Since I also met suitable 
hardware in the documentation on very expensive "finished" weather station 
modules, I got a bit stupid.

I would be pleased to receive an answer ^^

Hardware:
-Raspberry Pi Zero

-Air pressure/humidity and temperature sensor  

Would this work with the Weewx program? 

-- 
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/167a3748-fc6e-4d80-952e-002650ed7aa8n%40googlegroups.com.

Re: [weewx-user] Bootstrap skin update preview

[michael.k...@gmx.at]

There is no out-of-the-box template for displaying these values. The way 
you did this, is one of several possible ways to go. Adapting the templates 
to your own, customized needs, is always possible.

For the missing template in the installer: thank you, I fixed it.
Michael schrieb am Donnerstag, 4. März 2021 um 09:20:25 UTC+1:

> Is there a (hopefully simple) way to display the values of the gauge in 
> tabular form (e.g. as they are displayed in the Seasons skin)?
> For this display I have added the lines to the file livegauges.html.tmpl
>
>   
> $Labels.Generic.outTemp
> 23 °C / 57%
>   
>
> Example:
> [image: Screenshot.png]
>
>

-- 
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/9f677df5-66c6-4e94-94ff-6d26b67581b6n%40googlegroups.com.

Re: [weewx-user] Re: Error at Translation Belchertown Skin

[Christian Radermacher]

I copied only the necessary sections to whew, conf.
But consider, that the Section have other [ ] levels. Each Section is 2 
brackets deeper than in skin.conf.

Regards
Christian

didier@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:59:14 UTC+1:

> Hi
>
> Is skin.conf could be « copied « completly in weewx.conf or just a part ?
>
> Didier 
>
> Le jeu. 4 mars 2021 à 09:38, Manfred Maier  a 
> écrit :
>
>> Hi Christian,
>> you might want to move all your customizations to the weewx.conf file 
>> (and not store them in skin.conf).
>> The reason is: When you update the belchertown skin, all your changes to 
>> the skin.conf will be lost.
>>
>> Manfred 
>>
>> radermache...@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:32:44 
>> UTC+1:
>>
>>> Sorry, I saved the Problem.
>>> Started with a new skin.conf I transfer all Customizing step by step to 
>>> the whew conf.
>>> No it worked correct, and is the better solution.
>>>
>>> Regards
>>> Christian
>>>
>>> Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36 
>>> UTC+1:
>>>
 Hi, 
 i have an error if I translate the Skin:

 All customizing I made in the skin.conf.

 If I haver the following in the skin.conf
 # General Forecast translations
 forecast_header = 7 Day Forecast
 daily_forecast  = Daily Forecast
 alert_in_effect = in effect until
 forecast_last_updated   = Last Updated on
 I get a parsing error.
 If remove this (forecast with aeris is on) I have a Problem at display 
 the Timestamps.
 Maybe this is not the same error.


 -- 
>> 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/c9d7df23-1b28-4604-832c-2ca8771c5f25n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> Quel temps fait-il à Auffargis  ?
>

-- 
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/cc4d99a8-7dd0-41df-82bb-8fa9530aca5an%40googlegroups.com.

[weewx-user] ERROR weewx.reportengine: **** TypeError: list indices must be integers or slices, not str

[Andre]

First: I use WeeWX 4.4.0.0 at Raspberry Pi 4. Skin Belchertown.

Yesterday WeeWX has stopped working. Last data are from 2021-03-03 at 19:40 
MEZ.
MQTT is working as aspected.

I've tried:

sudo wee_database weewx.conf --drop-daily
sudo wee_database weewx.conf --rebuild-daily
sudo wee_database --fix-strings

---Here my log---
Mar  4 10:00:07 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:08 CET (1614848408)
Mar  4 10:00:09 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:10 CET (1614848410)
Mar  4 10:00:11 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:12 CET (1614848412)
Mar  4 10:00:14 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:14 CET (1614848414)
Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2021-03-04 09:55:00 CET (1614848100)
Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Mar  4 10:00:15 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:16 CET (1614848416)
Mar  4 10:00:15 weewx weewx[7220] DEBUG weewx.drivers.vantage: Retrieving 1 
page(s); starting index= 1
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
2021-03-04 10:00:00 CET (1614848400) to database 'weewx.sdb'
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.manager: Added record 
2021-03-04 10:00:00 CET (1614848400) to daily summary in 'weewx.sdb'
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: DMPAFT 
complete: page timestamp 2021-02-23 12:45:00 CET (1614080700) less than 
final timestamp 2021-03-04 10:00:00 CET (1614848400)
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Catch up 
complete.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
'SeasonsReport' not enabled. Skipping.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Running report 
'Belchertown'
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: MQTT: Published record 
2021-03-04 10:00:00 CET (1614848400)
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
'Belchertown'
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: Windy: Published record 
2021-03-04 10:00:00 CET (1614848400)
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: Wetter: Unexpected 
exception of type 
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** Traceback (most 
recent call last):
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.restx: CWOP: Connected to 
server cwop.aprs.net:14580
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 381, in run_loop
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
 self.process_record(_record, dbmanager)
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 446, in process_record
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
 self.post_with_retries(_request, data)
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 485, in post_with_retries
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: AWEKAS: Published 
record 2021-03-04 10:00:00 CET (1614848400)
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***
 self.check_response(_response)
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: ***   File 
"/usr/share/weewx/user/wetter.py", line 143, in check_response
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** if 
txt.find('"errorcode":"100"') != -1 or \
Mar  4 10:00:16 weewx weewx[7220] ERROR weewx.restx: *** TypeError: 
argument should be integer or bytes-like object, not 'str'
Mar  4 10:00:16 weewx weewx[7220] CRITICAL weewx.restx: Wetter: Thread 
terminating. Reason: argument should be integer or bytes-like object, not 
'str'
Mar  4 10:00:16 weewx weewx[7220] INFO weewx.restx: CWOP: Published record 
2021-03-04 10:00:00 CET (1614848400)
Mar  4 10:00:16 weewx weewx[7220] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 

Re: [weewx-user] Re: Error at Translation Belchertown Skin

[Didier Decoodt]

Hi

Is skin.conf could be « copied « completly in weewx.conf or just a part ?

Didier

Le jeu. 4 mars 2021 à 09:38, Manfred Maier  a
écrit :

> Hi Christian,
> you might want to move all your customizations to the weewx.conf file (and
> not store them in skin.conf).
> The reason is: When you update the belchertown skin, all your changes to
> the skin.conf will be lost.
>
> Manfred
>
> radermache...@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:32:44
> UTC+1:
>
>> Sorry, I saved the Problem.
>> Started with a new skin.conf I transfer all Customizing step by step to
>> the whew conf.
>> No it worked correct, and is the better solution.
>>
>> Regards
>> Christian
>>
>> Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36 UTC+1:
>>
>>> Hi,
>>> i have an error if I translate the Skin:
>>>
>>> All customizing I made in the skin.conf.
>>>
>>> If I haver the following in the skin.conf
>>> # General Forecast translations
>>> forecast_header = 7 Day Forecast
>>> daily_forecast  = Daily Forecast
>>> alert_in_effect = in effect until
>>> forecast_last_updated   = Last Updated on
>>> I get a parsing error.
>>> If remove this (forecast with aeris is on) I have a Problem at display
>>> the Timestamps.
>>> Maybe this is not the same error.
>>>
>>>
>>> --
> 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/c9d7df23-1b28-4604-832c-2ca8771c5f25n%40googlegroups.com
> 
> .
>
-- 
Quel temps fait-il à Auffargis  ?

-- 
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/CAAvt3%3DRYZ6CQx%2ByjGe0CtkmaTC%3DCxP9M2bqMUjThuV-Hzymb7Q%40mail.gmail.com.

[weewx-user] Re: Error at Translation Belchertown Skin

[Christian Radermacher]

Thanks Manfred,
i am on the way. I do this for alle Custom things in the skin, also the new 
Page "Über die Station". Your Station is a great template, for this. I have 
disabled the "Reports Page too.

Now I am searching for translation for aeris forecast.

Regards
Christian 

Manfred Maier schrieb am Donnerstag, 4. März 2021 um 09:38:44 UTC+1:

> Hi Christian,
> you might want to move all your customizations to the weewx.conf file (and 
> not store them in skin.conf).
> The reason is: When you update the belchertown skin, all your changes to 
> the skin.conf will be lost.
>
> Manfred 
>
> radermache...@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:32:44 
> UTC+1:
>
>> Sorry, I saved the Problem.
>> Started with a new skin.conf I transfer all Customizing step by step to 
>> the whew conf.
>> No it worked correct, and is the better solution.
>>
>> Regards
>> Christian
>>
>> Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36 UTC+1:
>>
>>> Hi, 
>>> i have an error if I translate the Skin:
>>>
>>> All customizing I made in the skin.conf.
>>>
>>> If I haver the following in the skin.conf
>>> # General Forecast translations
>>> forecast_header = 7 Day Forecast
>>> daily_forecast  = Daily Forecast
>>> alert_in_effect = in effect until
>>> forecast_last_updated   = Last Updated on
>>> I get a parsing error.
>>> If remove this (forecast with aeris is on) I have a Problem at display 
>>> the Timestamps.
>>> Maybe this is not the same error.
>>>
>>>
>>>

-- 
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/7a0b2ea8-8949-47d7-98e1-d5707a967149n%40googlegroups.com.

[weewx-user] Re: Error at Translation Belchertown Skin

[Manfred Maier]

Hi Christian,
you might want to move all your customizations to the weewx.conf file (and 
not store them in skin.conf).
The reason is: When you update the belchertown skin, all your changes to 
the skin.conf will be lost.

Manfred 

radermache...@gmail.com schrieb am Donnerstag, 4. März 2021 um 09:32:44 
UTC+1:

> Sorry, I saved the Problem.
> Started with a new skin.conf I transfer all Customizing step by step to 
> the whew conf.
> No it worked correct, and is the better solution.
>
> Regards
> Christian
>
> Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36 UTC+1:
>
>> Hi, 
>> i have an error if I translate the Skin:
>>
>> All customizing I made in the skin.conf.
>>
>> If I haver the following in the skin.conf
>> # General Forecast translations
>> forecast_header = 7 Day Forecast
>> daily_forecast  = Daily Forecast
>> alert_in_effect = in effect until
>> forecast_last_updated   = Last Updated on
>> I get a parsing error.
>> If remove this (forecast with aeris is on) I have a Problem at display 
>> the Timestamps.
>> Maybe this is not the same error.
>>
>>
>>

-- 
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/c9d7df23-1b28-4604-832c-2ca8771c5f25n%40googlegroups.com.

[weewx-user] Re: Error at Translation Belchertown Skin

[Christian Radermacher]

Sorry, I saved the Problem.
Started with a new skin.conf I transfer all Customizing step by step to the 
whew conf.
No it worked correct, and is the better solution.

Regards
Christian

Christian Radermacher schrieb am Mittwoch, 3. März 2021 um 21:42:36 UTC+1:

> Hi, 
> i have an error if I translate the Skin:
>
> All customizing I made in the skin.conf.
>
> If I haver the following in the skin.conf
> # General Forecast translations
> forecast_header = 7 Day Forecast
> daily_forecast  = Daily Forecast
> alert_in_effect = in effect until
> forecast_last_updated   = Last Updated on
> I get a parsing error.
> If remove this (forecast with aeris is on) I have a Problem at display the 
> Timestamps.
> Maybe this is not the same error.
>
>
>

-- 
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/d2bafbbe-2fcd-484b-a334-8c37261343c5n%40googlegroups.com.

Re: [weewx-user] Bootstrap skin update preview

[Michael]

Is there a (hopefully simple) way to display the values of the gauge in 
tabular form (e.g. as they are displayed in the Seasons skin)?
For this display I have added the lines to the file livegauges.html.tmpl

  
$Labels.Generic.outTemp
23 °C / 57%
  

Example:
[image: Screenshot.png]

-- 
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/f4e636fe-2898-4f12-98af-5be827e5beefn%40googlegroups.com.