Re: [weewx-user] V4 with python2 OWFS errors

[Gazza]

OK, I have done some more tests, first I have removed python-ow and now the 
owfs service in weewx is not working.

When I run systemctl status owserver it shows that it is enabled and 
running.

pi@GazPi4:~ $ systemctl status owserver
* owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Tue 2020-05-26 15:08:43 AEST; 34min ago
 Docs: man:owserver(1)
 Main PID: 365 (owserver)
Tasks: 3 (limit: 4915)
   Memory: 2.8M
   CGroup: /system.slice/owserver.service
   `-365 /usr/bin/owserver -c /etc/owfs.conf

May 26 15:08:43 GazPi4 systemd[1]: Starting Backend server for 1-wire 
control...
May 26 15:08:43 GazPi4 owserver[365]: DEFAULT: ow_opt.c:(670) systemd mode 
-- ignore 'p' option
May 26 15:08:43 GazPi4 systemd[1]: Started Backend server for 1-wire 
control.

When I run owdir, the sensor is detected but I get no readings.

pi@GazPi4:~ $ owdir
/28.E1044104
/bus.0
/uncached
/settings
/system
/statistics
/structure
/simultaneous
/alarm

When I try to to run weewx owfs direct command it fails.


pi@GazPi4:~ $ sudo PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/
owfs.py --sensors --iface=localhost:4304
Traceback (most recent call last):
  File "/home/weewx/bin/user/owfs.py", line 713, in 
main()
  File "/home/weewx/bin/user/owfs.py", line 674, in main
traverse(ow.Sensor('/'), identify_sensor)
  File "/home/weewx/bin/user/owfs.py", line 264, in Sensor
return self.proxy.Sensor(path)
AttributeError: '_Proxy' object has no attribute 'Sensor'

It seems that even though I had changed the weewx.conf from =/dec/i2c-1 to 
=localhost:4304 it was still using pyownet.


Gaz

-- 
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/20399341-5557-4466-bbe2-e300d40215dd%40googlegroups.com.

[weewx-user] WeeWX time out of sync in reports

[gjr80]

Hi,

Would be good to understand exactly what is in your config. Could you post a 
wee_debug (http://weewx.com/docs/utilities.htm#wee_debug_utility) report 
please. Before posting the wee_debug report do check it for sensitive info such 
as passwords, api keys etc, wee_debug is good at obfuscating such info but it 
is not perfect.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6e961132-1833-4317-a3cb-75d470d5f4bc%40googlegroups.com.

[weewx-user] Additional Sensors

[ttech]

Hello,
I am trying to combine the sensor data from a Vantage Vue and a Tempest so 
I can add UV and battery monitoring. Is there any easy way to store the 
data as part of the station feed? Or can I use a custom sensor collector - 
since I want to collect particulates, uv, and battery which is not 
available as part of the Davis Vantage Vue system. 



-- 
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/724859f2-6202-4f40-8fa0-d617857ac9dc%40googlegroups.com.

[weewx-user] Re: wee_extension inigo-data.txt is not generated

[Greg from Oz]

I assume you have done this verbatum?
https://github.com/evilbunny2008/weeWXWeatherApp/wiki

On Tuesday, 26 May 2020 14:20:57 UTC+10, Ronald Berghammer wrote:
>
> Thanks for the fast answer.
>
> No, it never worked!
>

-- 
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/965e0351-f1b5-4894-8970-f76841903063%40googlegroups.com.

[weewx-user] Re: wee_extension inigo-data.txt is not generated

[Greg from Oz]

I use it every day and it is great on the phone app.
What version weewx are you on?
I am running 4.1 and it works.


On Tuesday, 26 May 2020 14:20:57 UTC+10, Ronald Berghammer wrote:
>
> Thanks for the fast answer.
>
> No, it never worked!
>

-- 
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/19b91924-5519-4f88-b45a-fa8d998dfb58%40googlegroups.com.

[weewx-user] Re: wee_extension inigo-data.txt is not generated

[Ronald Berghammer]

Thanks for the fast answer.

No, it never worked!

-- 
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/ad8256a2-6a25-4198-812a-53d22a2942d0%40googlegroups.com.

Re: [weewx-user] V4 with python2 OWFS errors

[Gazza]

The system must be using owserver as the weewx.conf has been changed to 
point to localhost:4304.

I haven't removed python-ow should I do that ??


Gaz

-- 
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/5489e320-a6b7-4b43-9354-81f8970267e2%40googlegroups.com.

[weewx-user] Re: wee_extension inigo-data.txt is not generated

[Greg from Oz]

Has it EVER worked or have you changed something else?

On Tuesday, 26 May 2020 04:20:25 UTC+10, Ronald Berghammer wrote:
>
> Hello!
>
> I have a problem with the inigo wee_extension, the inigo-data.txt is not 
> generated.
>
> Here are my logfile:
>
> May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.reportengine: Running 
> report 'Inigo'
> May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Inigo/skin.conf for report 'Inigo'
> May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.cheetahgenerator: 
> Using search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras', u'user.alltime.ExtendedStatistics', 
> u'user.inigo-since.Since']
> May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.manager: Daily 
> summary version is 2.0
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
> Generate failed with exception ''
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
>  Ignoring template /etc/weewx/skins/Inigo/inigo-data.txt.tmpl
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
>  Reason: a float is required
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
>   Traceback (most recent call last):
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in 
> generate
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
>   unicode_string = compiled_template.respond()
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_Inigo_inigo_data_txt_tmpl.py", line 791, in 
> respond
> May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
>   TypeError: a float is required
> May 25 20:16:24 raspberrypi weewx[12508] INFO weewx.cheetahgenerator: 
> Generated 0 files for report Inigo in 0.23 seconds
>
> Can anybody help me?
>
> Thanks a lot :o)
>

-- 
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/3f597f01-efea-4324-afbf-a7628d151215%40googlegroups.com.

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

[pete_panic]

Hey Luc,

this is fantastic! Thank you so much. Copied it to the weewx installation, 
fine tuned a bit et voilá. Working smoothly!

The original problem was that I installed ubuntu 20.4 on a raspi 2 and that 
package only includes python 3. Installing pyhton 2 and switching between 
versions I ran into some more trouble regarding dependencies.

Thank you really very much, Luc, you made my day. Very much so!

Greatest help!

Cheers Peter


Am Montag, 25. Mai 2020 17:21:24 UTC+2 schrieb Luc Heijst:
>
> Hi Pete,
>
> Attached the Klimalogg Pro driver compatible with python2, python3 and the 
> weewx v.4.0 logging.
>
> Luc
>
> On Monday, 25 May 2020 03:23:25 UTC-3, pete_panic wrote:
>>
>> Hi everyone!
>>
>> This thread has been extremely helpful. Thank you so much for all the 
>> input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
>> rf communication between the raspi and the Klimalogg Pro started. 
>>
>> I was able to connect to the transceiver and everything went well until 
>> the log showed the error message "exception in doRF: %s" after "starting rf 
>> communication". Since I am not firm (yet) with python (I'm more one of the 
>> old php guys), I wonder if there was the possibility to have a python3 
>> compatible version of the Klimalogg Pro driver? I did get the message to 
>> press the USB button on the console but that did not help, it kept on 
>> showing up...
>>
>> Did anyone else have this problem?
>>
>> Thank you again and cheers
>>
>> Pete
>>
>>

-- 
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/98da1c4b-0f4a-4616-bee0-668f139f6695%40googlegroups.com.

Re: [weewx-user] V4 with python2 OWFS errors

[Glenn McKechnie]

Gazza wrote:
> 
> Hi Glen,
> 
> I don't fully understand the pyownet bit but owserver would not run without 
> it being installed.

Okay, that is confusing as pyownet is the client, it needs owserver.
Owserver doesn't care whether pyownet is there or not.
We do, it doesn't.

If you were still running weewx with python-ow then /dev/i2c-1 would still
have been claimed by it; then owserver would complain, and I think it
might even segfault?


owserver does seem to be finicky when initially starting (under debian
Buster) and that could be a systemd thing, but no-one who has had the
problem has clearly defined what the fix is, it just "comes good".
I run Devuan which doesn't use systemd so I'm very low on the list of
possible fixers.

It may be that owserver fails to start (for its own reasons) and
systemd takes that personally and supplies a cryptic message. (too
often, too fast, something...protocols)?

Owserver does need a working config file for it to start, and it needs
the 1-wire bus interface to be correctly defined. That may be why it
comes with an oddly configured owfs.conf file (the fake server).

Getting back to ow, pyownet and owserver...

When python-ow is available, that's all that is needed to talk to the
busmaster (1-wire interface). No owserver is required as ow has wrapped
up owservers library and uses that instead...
weewx -- owfs.py -- ow -- /dev/i2c-1

pyownet is a package that only interfaces with owserver and also does it
using the python language.
Where we once needed to tell ow what the interface was we now need to
give that information to owserver and it does all the protocol,
handshaking business. Think of it as replacing the interface (as ow used it).

Once owserver is working correctly we point pyownet to the owserver and
with that change we should be in business with no further changes (other
than setting up the [OWFS] section as we always did.) We now have...
weewx -- owfs.py -- pyownet -- owserver -- /dev/i2c-1

https://github.com/miccoli/pyownet

Okay. My cup runneth over again. HTHelped :-)

-- 

Cheers
  Glenn

 rorpi - read only raspberry pi & various weewx addons
 https://github.com/glennmckechnie

-- 
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/20200526012725.ur5njorbo4r6mnjr%40gmail.com.

Re: [weewx-user] V4 with python2 OWFS errors

[Gazza]

Hi Glen,

I don't fully understand the pyownet bit but owserver would not run without 
it being installed.



Gaz

-- 
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/95b3140b-3cde-4686-86ab-5daed7f85f09%40googlegroups.com.

RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

Thanks Tom.  Working fine now.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Monday, May 25, 2020 6:13 PM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

 

My apologies. The layout of the configuration dictionary changed, and I have 
not had a chance to update the Wiki. The change makes it more consistent with 
the Python docs. You want:

 

[Logging]
# Root logger
[[root]]
   handlers = rotate,   
[[loggers]]
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG  
formatter = verbose   
class = logging.handlers.RotatingFileHandler  
filename = /var/log/weewx.log

 

The difference is that the root logger, [[root]], is now a peer, instead of a 
child, of [[loggers]].

 

V4.1.0 can now handle the integer options maxBytes and backupCount, if you want 
to put them back in.

 

-tk

 

 

 

On Mon, May 25, 2020 at 3:55 PM mailto:nineb...@gmail.com> 
> wrote:

Following these instructions I had logging to weewx.log working.  I upgraded to 
4.1.0 and am now logging to syslog and not weewx.log.  I tied Logging with and 
without the integers in my config file as below.

 

#[Logging]

#[[loggers]]

## Root logger

#[[[root]]]

#handlers = rotate,

#[[handlers]]

## Log to a set of rotating files

#[[[rotate]]]

#level = DEBUG   

#formatter = verbose

#class = logging.handlers.RotatingFileHandler   

#filename = /var/log/weewx.log

#maxBytes = 1000

#backupCount = 4   

 

[Logging]

[[loggers]]

# Root logger

[[[root]]]

handlers = rotate,

[[handlers]]

# Log to a set of rotating files

[[[rotate]]]

level = DEBUG   

formatter = verbose

class = logging.handlers.RotatingFileHandler   

filename = /var/log/weewx.log

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Tom Keffer
Sent: Friday, May 15, 2020 7:09 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Sorry, Tom. This is due to a bug in how weewx configures the logger. The 
problem is that weewx does not convert strings to int when configuring.  It was 
fixed a couple weeks ago (commit  

 6348741), but I totally forgot about it.

 

You have two choices: 

1.   Replace your copy of weeutil/logger.py with the one in the repository 
 , 
or 

2.   remove the integers from the configuration stanza. It becomes

[Logging]
[[loggers]]
# Root logger
[[[root]]]
  handlers = rotate,# 1
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG   # 2
formatter = standard# 3
class = logging.handlers.RotatingFileHandler  # 4
filename = /var/log/weewx.log   # 5

-tk

 

On Fri, May 15, 2020 at 3:58 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

Thinking out loud here...  Running as the Pi user?  Have write access to 
/var/log?

-- 
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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 

Re: [weewx-user] V4 with python2 OWFS errors

[Glenn McKechnie]

Hi Gaz,

Excellent.
Good to hear it's working for you, and may it keep doing so!

You've certainly given it a good test, with the Service setup, python
versions, and especially the owserver - pyownet combination!

Great to have your working config setup too. It's always good to have
that sort of info, wraps it up nicely.


On 25/05/2020, Gazza  wrote:
>
> OK, I have had a read of the posts about pyton-ow being no longer supported
>
> and have now installed owserver and owshell and pyownet.
>
> As I am using a DS2482-100 I2C Bus master my owfs.conf contains:
>
> # DS2482-100 I2C Bus master
> server: device = /dev/i2c-1
> server: port = localhost:4304
>
> I changed the weewx service section to:
>
> [OWFS]  # Options for extension owfs.py using owserver
>
> interface = localhost:4304
> [[sensor_map]]
> # 1wire - solar
> extraTemp5 =  /uncached/28.E1044104/temperature   # test
> DS18S20
>
> So far it is all working as expected.
>
>
> Gaz
>
> --


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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/CAAraAzhRiY91SGcqRK5r3QUcQ03CCfnNmiuej%2Bas-tqKG1YdMg%40mail.gmail.com.

Re: [weewx-user] Noisy logging, log_success = False not followed

[Tom Keffer]

My apologies. The layout of the configuration dictionary changed, and I
have not had a chance to update the Wiki. The change makes it more
consistent with the Python docs. You want:

[Logging]
# Root logger
[[root]]
   handlers = rotate,
[[loggers]]
[[handlers]]
# Log to a set of rotating files
[[[rotate]]]
level = DEBUG
formatter = verbose
class = logging.handlers.RotatingFileHandler
filename = /var/log/weewx.log

The difference is that the root logger, [[root]], is now a peer, instead of
a child, of [[loggers]].

V4.1.0 can now handle the integer options maxBytes and backupCount, if you
want to put them back in.

-tk



On Mon, May 25, 2020 at 3:55 PM  wrote:

> Following these instructions I had logging to weewx.log working.  I
> upgraded to 4.1.0 and am now logging to syslog and not weewx.log.  I tied
> Logging with and without the integers in my config file as below.
>
>
>
> #[Logging]
>
> #[[loggers]]
>
> ## Root logger
>
> #[[[root]]]
>
> #handlers = rotate,
>
> #[[handlers]]
>
> ## Log to a set of rotating files
>
> #[[[rotate]]]
>
> #level = DEBUG
>
> #formatter = verbose
>
> #class = logging.handlers.RotatingFileHandler
>
> #filename = /var/log/weewx.log
>
> #maxBytes = 1000
>
> #backupCount = 4
>
>
>
> [Logging]
>
> [[loggers]]
>
> # Root logger
>
> [[[root]]]
>
> handlers = rotate,
>
> [[handlers]]
>
> # Log to a set of rotating files
>
> [[[rotate]]]
>
> level = DEBUG
>
> formatter = verbose
>
> class = logging.handlers.RotatingFileHandler
>
> filename = /var/log/weewx.log
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Tom Keffer
> *Sent:* Friday, May 15, 2020 7:09 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Noisy logging, log_success = False not
> followed
>
>
>
> Sorry, Tom. This is due to a bug in how weewx configures the logger. The
> problem is that weewx does not convert strings to int when configuring.  It
> was fixed a couple weeks ago (commit 6348741
> ),
> but I totally forgot about it.
>
>
>
> You have two choices:
>
> 1.   Replace your copy of weeutil/logger.py with the one in the repository
> ,
> or
>
> 2.   remove the integers from the configuration stanza. It becomes
>
> [Logging]
> [[loggers]]
> # Root logger
> [[[root]]]
>   handlers = rotate,# 1
> [[handlers]]
> # Log to a set of rotating files
> [[[rotate]]]
> level = DEBUG   # 2
> formatter = standard# 3
> class = logging.handlers.RotatingFileHandler  # 4
> filename = /var/log/weewx.log   # 5
>
> -tk
>
>
>
> On Fri, May 15, 2020 at 3:58 PM Chris Nelson  wrote:
>
> Thinking out loud here...  Running as the Pi user?  Have write access to
> /var/log?
>
> --
> 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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
> 
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/08c501d632e7%24a27a3340%24e76e99c0%24%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

RE: [weewx-user] Noisy logging, log_success = False not followed

[nineback]

Following these instructions I had logging to weewx.log working.  I upgraded to 
4.1.0 and am now logging to syslog and not weewx.log.  I tied Logging with and 
without the integers in my config file as below.

 

#[Logging]

#[[loggers]]

## Root logger

#[[[root]]]

#handlers = rotate,

#[[handlers]]

## Log to a set of rotating files

#[[[rotate]]]

#level = DEBUG   

#formatter = verbose

#class = logging.handlers.RotatingFileHandler   

#filename = /var/log/weewx.log

#maxBytes = 1000

#backupCount = 4   

 

[Logging]

[[loggers]]

# Root logger

[[[root]]]

handlers = rotate,

[[handlers]]

# Log to a set of rotating files

[[[rotate]]]

level = DEBUG   

formatter = verbose

class = logging.handlers.RotatingFileHandler   

filename = /var/log/weewx.log

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: Friday, May 15, 2020 7:09 PM
To: weewx-user 
Subject: Re: [weewx-user] Noisy logging, log_success = False not followed

 

Sorry, Tom. This is due to a bug in how weewx configures the logger. The 
problem is that weewx does not convert strings to int when configuring.  It was 
fixed a couple weeks ago (commit  

 6348741), but I totally forgot about it.

 

You have two choices: 

1.   Replace your copy of weeutil/logger.py with the one in the repository 
 , 
or 

2.   remove the integers from the configuration stanza. It becomes

[Logging]
[[loggers]]
# Root logger
[[[root]]]
  handlers = rotate,# 1
[[handlers]]
# Log to a set of rotating files   
[[[rotate]]]
level = DEBUG   # 2
formatter = standard# 3
class = logging.handlers.RotatingFileHandler  # 4
filename = /var/log/weewx.log   # 5

-tk

 

On Fri, May 15, 2020 at 3:58 PM Chris Nelson mailto:cjncj...@gmail.com> > wrote:

Thinking out loud here...  Running as the Pi user?  Have write access to 
/var/log?

-- 
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/8fb4e590-c1f8-4220-beef-ab6e6baba964%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/CAPq0zEAkF8DDP%3D5ahXooNr2KiSFzQbcLWKo2tU4Y4RQMb7f8yw%40mail.gmail.com
 

 .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/08c501d632e7%24a27a3340%24e76e99c0%24%40gmail.com.

Re: [weewx-user] upgrade 4.0 to 4.1 - ImportError: No module named configobj at setup.py install

[Tarmo]

of course it is default python thing. thanks! :)

On Tuesday, May 26, 2020 at 12:16:38 AM UTC+3, Tom Keffer wrote:
>
> Follow the setup.py instructions  
> carefully. You want
>
> *sudo python3 ./setup.py install*
>
> Otherwise it will use whatever is the default version of Python on your 
> system, which is probably python 2.
>
> -tk
>
> On Mon, May 25, 2020 at 1:49 PM Tarmo > 
> wrote:
>
>> hi!
>>
>> please help on this:
>>
>> sudo ./setup.py install
>> .
>> .
>> .
>> Removing /home/weewx/bin/weewx-4.1.0.egg-info
>> Writing /home/weewx/bin/weewx-4.1.0.egg-info
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/wee_config", line 12, in 
>> from weecfg.config import ConfigEngine, Logger
>>   File "/home/weewx/bin/weecfg/__init__.py", line 22, in 
>> import configobj
>> ImportError: No module named configobj
>>
>> pi@pi3:~/weewx-4.1.0 $ sudo apt install python3-configobj
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> python3-configobj is already the newest version (5.0.6-2).
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>>
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/66f0a262-1021-4080-b784-720de1e81807%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/2ba1199e-ef94-4516-b1a6-76f5069a0c46%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

Gary, yes, I did try to install pysftp via pip, it failed, and I went onto 
other things. Will read more about this (including Matt's *readme*) and try 
this tomorrow.
Meanwhile I'm having problems related to plain ftp that defy logical 
consistency but that's for another subject.

On Monday, May 25, 2020 at 11:15:29 PM UTC+2, gjr80 wrote:
>
> I think the weewx-sftp issue was the inability to install pysftp via pip. 
> It installed fine for me on raspbian Stretch last night though I needed to 
> use pip2 not pip. A bit of googling the OPs pip error message suggested pip 
> may need to be upgraded, wouldn’t be the first time that has come up. 
>
> Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/310a5639-2c3e-425d-b973-26b391ee744f%40googlegroups.com.

Re: [weewx-user] upgrade 4.0 to 4.1 - ImportError: No module named configobj at setup.py install

[Tom Keffer]

In fairness, I just noticed that the upgrade instructions on the Upgrade
Guide say use "sudo python ./setup.py install". We should probably update
the update.

-tk

On Mon, May 25, 2020 at 2:16 PM Tom Keffer  wrote:

> Follow the setup.py instructions 
> carefully. You want
>
> *sudo python3 ./setup.py install*
>
> Otherwise it will use whatever is the default version of Python on your
> system, which is probably python 2.
>
> -tk
>
> On Mon, May 25, 2020 at 1:49 PM Tarmo  wrote:
>
>> hi!
>>
>> please help on this:
>>
>> sudo ./setup.py install
>> .
>> .
>> .
>> Removing /home/weewx/bin/weewx-4.1.0.egg-info
>> Writing /home/weewx/bin/weewx-4.1.0.egg-info
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/wee_config", line 12, in 
>> from weecfg.config import ConfigEngine, Logger
>>   File "/home/weewx/bin/weecfg/__init__.py", line 22, in 
>> import configobj
>> ImportError: No module named configobj
>>
>> pi@pi3:~/weewx-4.1.0 $ sudo apt install python3-configobj
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> python3-configobj is already the newest version (5.0.6-2).
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>>
>>
>> --
>> 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/66f0a262-1021-4080-b784-720de1e81807%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/CAPq0zED9JFW5LQqiF7n6DYhAS%2B5D%3DfWgwWymT-PewqNYYz--Mw%40mail.gmail.com.

[weewx-user] upgrade 4.0 to 4.1 - ImportError: No module named configobj at setup.py install

[gjr80]

Are you sure you are running setup.py under python 3 or is it perhaps 
defaulting to python 2 (and thus you need python-configobj)?

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0170150f-622b-4f3a-a308-1485356b5374%40googlegroups.com.

Re: [weewx-user] upgrade 4.0 to 4.1 - ImportError: No module named configobj at setup.py install

[Tom Keffer]

Follow the setup.py instructions 
carefully. You want

*sudo python3 ./setup.py install*

Otherwise it will use whatever is the default version of Python on your
system, which is probably python 2.

-tk

On Mon, May 25, 2020 at 1:49 PM Tarmo  wrote:

> hi!
>
> please help on this:
>
> sudo ./setup.py install
> .
> .
> .
> Removing /home/weewx/bin/weewx-4.1.0.egg-info
> Writing /home/weewx/bin/weewx-4.1.0.egg-info
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_config", line 12, in 
> from weecfg.config import ConfigEngine, Logger
>   File "/home/weewx/bin/weecfg/__init__.py", line 22, in 
> import configobj
> ImportError: No module named configobj
>
> pi@pi3:~/weewx-4.1.0 $ sudo apt install python3-configobj
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> python3-configobj is already the newest version (5.0.6-2).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
>
>
> --
> 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/66f0a262-1021-4080-b784-720de1e81807%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/CAPq0zED9JqiAAjfUU7FWdTM2uRXTj%3DU1NxmjbpqcuvzB3RFzfw%40mail.gmail.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[gjr80]

I think the weewx-sftp issue was the inability to install pysftp via pip. It 
installed fine for me on raspbian Stretch last night though I needed to use 
pip2 not pip. A bit of googling the OPs pip error message suggested pip may 
need to be upgraded, wouldn’t be the first time that has come up.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d4beb70c-467b-43e1-9e73-001dcad72c19%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

Aha. "ReadMe". So that's what that's for.   jk
  I probably missed it. Thanks.


On Mon, May 25, 2020 at 10:49 PM mwall  wrote:

>
>
> On Monday, May 25, 2020 at 3:56:16 PM UTC-4, Messy Potamia wrote:
>>
>> one.com's robotic tech support said they only do ftp, sftp, and ssh, and
>> don't support ftps. I don't think that offshore robot even knew what ftps
>> was.
>> So can somebody tell me about the thing that MWALL has on github?
>>
>
> as it says in the readme, it is a client that uses sftp (not ftps, not ftp)
>
> if you can connect to your sftp server using some other sftp client, then
> the weewx-sftp extension should work using the same credentials/parameters
>
> you can verify by invoking the weewx-sftp extension directly, for example:
>
> PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/sftp.py
> /home/weewx/weewx.conf
>
> change the paths if you are using a deb or rpm installation
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GdlSK3vTvYE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c3075a6c-1c68-4098-99e7-378d96b384ee%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/CAB7-S75CP45JgXNk9-HWyEO9b6TaknwSmOA5hRu0COF-ivz4-A%40mail.gmail.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[mwall]

On Monday, May 25, 2020 at 3:56:16 PM UTC-4, Messy Potamia wrote:
>
> one.com's robotic tech support said they only do ftp, sftp, and ssh, and 
> don't support ftps. I don't think that offshore robot even knew what ftps 
> was.
> So can somebody tell me about the thing that MWALL has on github?
>

as it says in the readme, it is a client that uses sftp (not ftps, not ftp)

if you can connect to your sftp server using some other sftp client, then 
the weewx-sftp extension should work using the same credentials/parameters

you can verify by invoking the weewx-sftp extension directly, for example:

PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/sftp.py 
/home/weewx/weewx.conf

change the paths if you are using a deb or rpm installation

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c3075a6c-1c68-4098-99e7-378d96b384ee%40googlegroups.com.

[weewx-user] upgrade 4.0 to 4.1 - ImportError: No module named configobj at setup.py install

[Tarmo]

hi!

please help on this:

sudo ./setup.py install
.
.
.
Removing /home/weewx/bin/weewx-4.1.0.egg-info
Writing /home/weewx/bin/weewx-4.1.0.egg-info
Traceback (most recent call last):
  File "/home/weewx/bin/wee_config", line 12, in 
from weecfg.config import ConfigEngine, Logger
  File "/home/weewx/bin/weecfg/__init__.py", line 22, in 
import configobj
ImportError: No module named configobj

pi@pi3:~/weewx-4.1.0 $ sudo apt install python3-configobj
Reading package lists... Done
Building dependency tree   
Reading state information... Done
python3-configobj is already the newest version (5.0.6-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



-- 
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/66f0a262-1021-4080-b784-720de1e81807%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

one.com's robotic tech support said they only do ftp, sftp, and ssh, and 
don't support ftps. I don't think that offshore robot even knew what ftps 
was.
So can somebody tell me about the thing that MWALL has on github? 
My pi's all have ssh enabled and can ssh & scp amongst each other. Not sure 
that helps. 
Thanks.

On Monday, May 25, 2020 at 9:35:46 PM UTC+2, Tom Keffer wrote:
>
> (Aren't we already in weewx-user?)
>>
>
> So, we are! For some reason, gmail didn't tag it 'weewx' like it usually 
> does.
>
> From your response, I take it you are using SFTP? If so, weewx does not 
> support that. Only FTPS.
>
> -tk
>

-- 
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/d4d2b32a-0ffd-4299-aef4-48624a0b2cc6%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Tom Keffer]

>
> (Aren't we already in weewx-user?)
>

So, we are! For some reason, gmail didn't tag it 'weewx' like it usually
does.

>From your response, I take it you are using SFTP? If so, weewx does not
support that. Only FTPS.

-tk

-- 
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/CAPq0zEB2Bah-GhBie5LrNx7%3DekkRJ5ibRJTnFOvRPfojqXJTnQ%40mail.gmail.com.

[weewx-user] Version 4.1.0 is ready

[Tom Keffer]

A couple new features, but mostly lots of little bug fixes.

*New features:*

Archive records emitted by the Vantage driver now include the number of wind
samples per archive interval in field wind_samples.

wee_import can now import WeatherCat monthly .cat files.

Added a logging handler for rotating files. See https://bit.ly/2StYSHb for how
to use it. It is the default for MacOS.

*Bug fixes:*

Changed the logging configuration dictionary to match the Python documents.
Thanks to user Graham for figuring this out!

Fixed problem that prevented ws1 driver from working under Python 3. PR #556.

Eliminate use of logging in wee_config, allowing it to be used for installs
without syslog.

Allow expressions to be used as a datatype when plotting.

Added option 'reuse_ssl' to FTP. This activates a workaround for a bug in the
Python ftp library that causes long-lived connections to get closed prematurely.
Works only with Python 3.6 and greater.

The cc3000 driver will automatically reboot the hardware if it stops sending
observations. PR #549.

Install using setup.py forgot to set WEEWX_ROOT when installing in non-standard
places. Fixes issue #546.

Fixed bug in ws28xx driver that prevented it from running under Python 3.
Fixes issue #543.

Changed query strategy for calculating min and max wind vectors, which
should result in much faster plot generation.

Fixed bug in wmr9x8 driver that prevented it from running under Python 3.

Fixed several bugs in the te923 driver that prevented it from running under
Python 3.

More information if an exception is raised while querying for vantage hardware
type.

wunderfixer: fixed problem under Python 3 where response was not converted to
str before attempting to parse the JSON. Option --simulate now requires api_key
and password, so it can hit the WU.

Fixed problem in te923 driver under Python 3 that caused it to crash.

-- 
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/CAPq0zECm5fhnifO8NshFb%2BdwDhQ4cdW3B6db-hXscp8jUGw22g%40mail.gmail.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

Here's what I get when I connect via cmd line from my pi:
Password:
230 OK. Current restricted directory is /
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>
Remote system type is UNIX. Duh. 


(Aren't we already in weewx-user?)

On Monday, May 25, 2020 at 9:19:12 PM UTC+2, Tom Keffer wrote:
>
> If you connect via the command line command "ftp", it will usually tell 
> you the server make.
>
> BTW, let's switch to weewx-user for these questions. That way, others can 
> contribute and learn. 
>
> -tk
>
> On Mon, May 25, 2020 at 12:09 PM Messy Potamia  > wrote:
>
>> They haven't replied what kind of server they use. They're a pretty
>> big hosting entity (one.com). I've been using their service for about
>> 7 years, it includes my host name and about 20Gig of server space (I
>> only host two weewx wx systems on it, so use less than 2%) and a bunch
>> of other services which I'll never use. I enabled ssh/sftp per their
>> instructions, and my Filezilla now connects using sftp protocol. They
>> issue you a slightly different login (i.e. "ssh.webhostname.dom" or
>> "sftp.webhostname.dom" and you pick a different password from your FTP
>> password, other than that it's the same. I doubt this answers your
>> question.
>> I wish the mwall github resources was documented so I could see if it
>> even applied to me.
>> Thanks --
>>
>> On Mon, May 25, 2020 at 2:19 PM Tom Keffer > > wrote:
>> >
>> > WeeWX supports FTPS, not SFTP. Two questions:
>> >
>> > Which one does your server support?
>> >
>> > If it supports FTPS, do you know what kind of FTP server it is? The 
>> PureFTP server tickles a bug in the Python FTP library, but we have a work 
>> around.
>> >
>> > -tk
>> >
>> > On Mon, May 25, 2020 at 3:12 AM Messy Potamia > > wrote:
>> >>
>> >> Note, per another post the relevance of which I'm not certain, i added 
>> the following to the [[FTP]] section
>> >>secure_ftp = True
>> >>secure_data = False
>> >>
>> >> Makes no difference, still won't connect. Filezilla using sftp 
>> connects fine, and the native weewx ftp connects fine. I'm trying to use 
>> secure ftp.
>> >> May 25 12:05:21 RPI3 weewx[26625]: copygenerator: copied 14 files to 
>> /home/weewx/public_html
>> >> May 25 12:05:41 RPI3 weewx[26625]: ftpupload: Unable to connect or log 
>> into server : timed out
>> >> May 25 12:06:01 RPI3 weewx[26625]: ftpupload: Unable to connect or log 
>> into server : timed out
>> >> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Unable to connect or log 
>> into server : timed out
>> >> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Attempted 3 times to 
>> connect to server sftp.. Giving up.
>> >> May 25 12:06:21 RPI3 weewx[26625]: ftpgenerator: ftp'd 0 files in 
>> 60.69 seconds
>> >>
>> >>
>> >>
>> >>
>> >> On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
>> >>>
>> >>> --
>> >>>
>> >>> In summary, the Secure FTP capability is indicated in weewx.conf (& 
>> the caveat comment seems satisfied with testing of Filezilla's success), 
>> however in weewx's native install it does not work.
>> >>>
>> >>> --
>> >>> First I tried the method suggested in weewx.conf and the weewx guide: 
>> I enabled ssh/sftp with my provider (one.com), followed their 
>> instructions, tested it with filezilla, and I connect and upload/dnload 
>> just fine. Here's one.com's instructions on the matter:
>> >>>
>> >>> SSH & SFTP Administration
>> >>>
>> >>> SSH increases the security on your web space by encrypting your web 
>> space connections. With SSH enabled, you can transfer files securely via 
>> SFTP or connect to your web space directly from a terminal.
>> >>>
>> >>> Allow SSH & SFTP access Off On
>> >>>
>> >>> To log in with SSH & SFTP, use this info:
>> >>>
>> >>> Host: ssh..net
>> >>>
>> >>> Username: .net
>> >>>
>> >>> Port: 22
>> >>>
>> >>> Then their faq on the subject has this:
>> >>>
>> >>>
>> >>> Open your SFTP client, and enter the following details, replacing 
>> yourdomain.com with your own domain:
>> >>>
>> >>> Host: sftp.yourdomain.com
>> >>> Username: yourdomain.com
>> >>> Password: the password you have chosen for SFTP
>> >>> Port: 22
>> >>>
>> >>> Click the connect button in your client to log in. If it is the first 
>> time you login using SFTP on this computer, you need to approve the 
>> connection.
>> >>>
>> >>> Note: I have verified that with filezilla, both sftp.mydomain.net 
>> and ssh.mydomain.net, using my ssh/sftp password, connect fine.
>> >>>
>> >>>
>> >>> When I make the appropriate changes to weewx.conf, it is unable to 
>> connect. I tried a couple variations just to cross-validate disparities in 
>> their guide. No connect.
>> >>>
>> >>>
>> >>> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other 
>> things, MWall's 
>> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
>> >>>
>> >>> to wit:
>> >>>
>> >>> sudo pip install pysftp
>> >>>
>> >>> which results in:
>> >>>
>> >>> pi@RPI3:/home/weewx $ sudo pip install pysftp
>> >>> 

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Tom Keffer]

If you connect via the command line command "ftp", it will usually tell you
the server make.

BTW, let's switch to weewx-user for these questions. That way, others can
contribute and learn.

-tk

On Mon, May 25, 2020 at 12:09 PM Messy Potamia 
wrote:

> They haven't replied what kind of server they use. They're a pretty
> big hosting entity (one.com). I've been using their service for about
> 7 years, it includes my host name and about 20Gig of server space (I
> only host two weewx wx systems on it, so use less than 2%) and a bunch
> of other services which I'll never use. I enabled ssh/sftp per their
> instructions, and my Filezilla now connects using sftp protocol. They
> issue you a slightly different login (i.e. "ssh.webhostname.dom" or
> "sftp.webhostname.dom" and you pick a different password from your FTP
> password, other than that it's the same. I doubt this answers your
> question.
> I wish the mwall github resources was documented so I could see if it
> even applied to me.
> Thanks --
>
> On Mon, May 25, 2020 at 2:19 PM Tom Keffer  wrote:
> >
> > WeeWX supports FTPS, not SFTP. Two questions:
> >
> > Which one does your server support?
> >
> > If it supports FTPS, do you know what kind of FTP server it is? The
> PureFTP server tickles a bug in the Python FTP library, but we have a work
> around.
> >
> > -tk
> >
> > On Mon, May 25, 2020 at 3:12 AM Messy Potamia 
> wrote:
> >>
> >> Note, per another post the relevance of which I'm not certain, i added
> the following to the [[FTP]] section
> >>secure_ftp = True
> >>secure_data = False
> >>
> >> Makes no difference, still won't connect. Filezilla using sftp connects
> fine, and the native weewx ftp connects fine. I'm trying to use secure ftp.
> >> May 25 12:05:21 RPI3 weewx[26625]: copygenerator: copied 14 files to
> /home/weewx/public_html
> >> May 25 12:05:41 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> >> May 25 12:06:01 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> >> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> >> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Attempted 3 times to
> connect to server sftp.. Giving up.
> >> May 25 12:06:21 RPI3 weewx[26625]: ftpgenerator: ftp'd 0 files in 60.69
> seconds
> >>
> >>
> >>
> >>
> >> On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
> >>>
> >>> --
> >>>
> >>> In summary, the Secure FTP capability is indicated in weewx.conf (&
> the caveat comment seems satisfied with testing of Filezilla's success),
> however in weewx's native install it does not work.
> >>>
> >>> --
> >>> First I tried the method suggested in weewx.conf and the weewx guide:
> I enabled ssh/sftp with my provider (one.com), followed their
> instructions, tested it with filezilla, and I connect and upload/dnload
> just fine. Here's one.com's instructions on the matter:
> >>>
> >>> SSH & SFTP Administration
> >>>
> >>> SSH increases the security on your web space by encrypting your web
> space connections. With SSH enabled, you can transfer files securely via
> SFTP or connect to your web space directly from a terminal.
> >>>
> >>> Allow SSH & SFTP access Off On
> >>>
> >>> To log in with SSH & SFTP, use this info:
> >>>
> >>> Host: ssh..net
> >>>
> >>> Username: .net
> >>>
> >>> Port: 22
> >>>
> >>> Then their faq on the subject has this:
> >>>
> >>>
> >>> Open your SFTP client, and enter the following details, replacing
> yourdomain.com with your own domain:
> >>>
> >>> Host: sftp.yourdomain.com
> >>> Username: yourdomain.com
> >>> Password: the password you have chosen for SFTP
> >>> Port: 22
> >>>
> >>> Click the connect button in your client to log in. If it is the first
> time you login using SFTP on this computer, you need to approve the
> connection.
> >>>
> >>> Note: I have verified that with filezilla, both sftp.mydomain.net and
> ssh.mydomain.net, using my ssh/sftp password, connect fine.
> >>>
> >>>
> >>> When I make the appropriate changes to weewx.conf, it is unable to
> connect. I tried a couple variations just to cross-validate disparities in
> their guide. No connect.
> >>>
> >>>
> >>> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other
> things, MWall's
> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
> >>>
> >>> to wit:
> >>>
> >>> sudo pip install pysftp
> >>>
> >>> which results in:
> >>>
> >>> pi@RPI3:/home/weewx $ sudo pip install pysftp
> >>> Downloading/unpacking pysftp
> >>>   Downloading pysftp-0.2.9.tar.gz
> >>>   Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py)
> egg_info for package pysftp
> >>>
> >>> no previously-included directories found matching 'docs/_build'
> >>> Downloading/unpacking paramiko>=1.17 (from pysftp)
> >>>   Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB
> downloaded
> >>> Cleaning up...
> >>> Exception:
> >>> Traceback (most recent call last):
> >>>   File 

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

They haven't replied what kind of server they use. They're a pretty
big hosting entity (one.com). I've been using their service for about
7 years, it includes my host name and about 20Gig of server space (I
only host two weewx wx systems on it, so use less than 2%) and a bunch
of other services which I'll never use. I enabled ssh/sftp per their
instructions, and my Filezilla now connects using sftp protocol. They
issue you a slightly different login (i.e. "ssh.webhostname.dom" or
"sftp.webhostname.dom" and you pick a different password from your FTP
password, other than that it's the same. I doubt this answers your
question.
I wish the mwall github resources was documented so I could see if it
even applied to me.
Thanks --

On Mon, May 25, 2020 at 2:19 PM Tom Keffer  wrote:
>
> WeeWX supports FTPS, not SFTP. Two questions:
>
> Which one does your server support?
>
> If it supports FTPS, do you know what kind of FTP server it is? The PureFTP 
> server tickles a bug in the Python FTP library, but we have a work around.
>
> -tk
>
> On Mon, May 25, 2020 at 3:12 AM Messy Potamia  wrote:
>>
>> Note, per another post the relevance of which I'm not certain, i added the 
>> following to the [[FTP]] section
>>secure_ftp = True
>>secure_data = False
>>
>> Makes no difference, still won't connect. Filezilla using sftp connects 
>> fine, and the native weewx ftp connects fine. I'm trying to use secure ftp.
>> May 25 12:05:21 RPI3 weewx[26625]: copygenerator: copied 14 files to 
>> /home/weewx/public_html
>> May 25 12:05:41 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
>> server : timed out
>> May 25 12:06:01 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
>> server : timed out
>> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
>> server : timed out
>> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Attempted 3 times to connect 
>> to server sftp.. Giving up.
>> May 25 12:06:21 RPI3 weewx[26625]: ftpgenerator: ftp'd 0 files in 60.69 
>> seconds
>>
>>
>>
>>
>> On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
>>>
>>> --
>>>
>>> In summary, the Secure FTP capability is indicated in weewx.conf (& the 
>>> caveat comment seems satisfied with testing of Filezilla's success), 
>>> however in weewx's native install it does not work.
>>>
>>> --
>>> First I tried the method suggested in weewx.conf and the weewx guide: I 
>>> enabled ssh/sftp with my provider (one.com), followed their instructions, 
>>> tested it with filezilla, and I connect and upload/dnload just fine. Here's 
>>> one.com's instructions on the matter:
>>>
>>> SSH & SFTP Administration
>>>
>>> SSH increases the security on your web space by encrypting your web space 
>>> connections. With SSH enabled, you can transfer files securely via SFTP or 
>>> connect to your web space directly from a terminal.
>>>
>>> Allow SSH & SFTP access Off On
>>>
>>> To log in with SSH & SFTP, use this info:
>>>
>>> Host: ssh..net
>>>
>>> Username: .net
>>>
>>> Port: 22
>>>
>>> Then their faq on the subject has this:
>>>
>>>
>>> Open your SFTP client, and enter the following details, replacing 
>>> yourdomain.com with your own domain:
>>>
>>> Host: sftp.yourdomain.com
>>> Username: yourdomain.com
>>> Password: the password you have chosen for SFTP
>>> Port: 22
>>>
>>> Click the connect button in your client to log in. If it is the first time 
>>> you login using SFTP on this computer, you need to approve the connection.
>>>
>>> Note: I have verified that with filezilla, both sftp.mydomain.net and 
>>> ssh.mydomain.net, using my ssh/sftp password, connect fine.
>>>
>>>
>>> When I make the appropriate changes to weewx.conf, it is unable to connect. 
>>> I tried a couple variations just to cross-validate disparities in their 
>>> guide. No connect.
>>>
>>>
>>> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other things, 
>>> MWall's 
>>> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
>>>
>>> to wit:
>>>
>>> sudo pip install pysftp
>>>
>>> which results in:
>>>
>>> pi@RPI3:/home/weewx $ sudo pip install pysftp
>>> Downloading/unpacking pysftp
>>>   Downloading pysftp-0.2.9.tar.gz
>>>   Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py) egg_info 
>>> for package pysftp
>>>
>>> no previously-included directories found matching 'docs/_build'
>>> Downloading/unpacking paramiko>=1.17 (from pysftp)
>>>   Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB downloaded
>>> Cleaning up...
>>> Exception:
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in 
>>> main
>>> status = self.run(options, args)
>>>   File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 
>>> 290, in run
>>> requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, 
>>> bundle=self.bundle)
>>>   File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1266, in 
>>> prepare_files
>>> 

[weewx-user] Re: sdr.py not parsing Oregon WGR800X output correctly.

['Rob Series' via weewx-user]

Hi Gazza,
The 'if' statement is on the right hand side of the '=' sign is actually a 
ternary operator. Read the expression as :

  if obj.get('battery_ok') == 'OK':
   pkt['battery'] = 1 
else:
  pkt['battery']=0

(In python Numeric zero, None or False all evaluate to False, anything else 
is true). 

C++ has a similar operator ? : operator.

See https://www.python.org/dev/peps/pep-0308/ for the rational. Personally 
I find it very confusing to use 'if' for both forms.

Hope this helps. Good luck.

Rob


On Monday, 25 May 2020 11:09:09 UTC+1, Gazza wrote:
>
>
> Hi Rob,
>
> I don't know much about python so can you explain how the new version of 
> the battery status works as I still have to sort that for my mates station. 
>
> if 'battery_ok' in obj:
> pkt['battery'] = 1 if obj.get('battery_ok') == 'OK' else 0
>
> If the received data is "battery_ok" : 1 ( or "battery_ok" : 0 for flat 
> battery), what is the == 'OK' doing as it will never return a result of 
> 'OK" ??
>
>
> Gaz
>

-- 
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/662e5e8a-7cbb-4cac-af52-405abae5f1a4%40googlegroups.com.

[weewx-user] wee_extension inigo-data.txt is not generated

[Ronald Berghammer]

Hello!

I have a problem with the inigo wee_extension, the inigo-data.txt is not 
generated.

Here are my logfile:

May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.reportengine: Running 
report 'Inigo'
May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Inigo/skin.conf for report 'Inigo'
May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.cheetahgenerator: 
Using search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.alltime.ExtendedStatistics', 
u'user.inigo-since.Since']
May 25 20:16:24 raspberrypi weewx[12508] DEBUG weewx.manager: Daily summary 
version is 2.0
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
Generate failed with exception ''
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Inigo/inigo-data.txt.tmpl
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator:  
Reason: a float is required
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
  Traceback (most recent call last):
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in 
generate
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
File "_etc_weewx_skins_Inigo_inigo_data_txt_tmpl.py", line 791, in 
respond
May 25 20:16:24 raspberrypi weewx[12508] ERROR weewx.cheetahgenerator: 
  TypeError: a float is required
May 25 20:16:24 raspberrypi weewx[12508] INFO weewx.cheetahgenerator: 
Generated 0 files for report Inigo in 0.23 seconds

Can anybody help me?

Thanks a lot :o)

-- 
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/a79021a3-cdf1-4457-81a5-294e276b1fde%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Stephen Backway]

The issue appears to be with passing of the interface, as changing the 
default interface at line 310 of interceptor.py to the correct interface 
and not specifying the interface in the weewx.cfg results in it working.

For me this is what I changed it to:
310  DEFAULT_IFACE = 'wlan0'

Calling it a night, so hopefully that assists with tracking down the bug.

On Monday, 25 May 2020 22:03:50 UTC+10, Stephen Backway wrote:
>
> Running the script directly works, so it is something todo with the Weewx 
> - Interceptor link that isn't quite right.
>
>
>

-- 
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/f72dbd1c-71a3-4ecb-8c2a-b589e293d4fd%40googlegroups.com.

[weewx-user] Re: Highcharts on Weewx v4

[Phil Owers]

Thanks Gary
To keep every thing in its own sub-directory  I did add HTML_ROOT = 
public_html/highchartaverages in weewx.conf
Cant remember if it was like that before or if I added it.
And thanks again for all your great work, and all others of course
Phil


On Saturday, April 18, 2020 at 7:48:17 PM UTC+1, Phil Owers wrote:
>
> Hi Guys
>
> Loaded highcharts onto my weewx v4 machine and it failed
> averagesSearchX.py line 105 which is 
>  except Exception, e:
>
> Just wondered if this was a known problem
>
> Cheers Phil
>

-- 
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/bf65d5ce-043b-45e5-b54c-c28d96ddbe44%40googlegroups.com.

Re: [weewx-user] V4 with python2 OWFS errors

[Gazza]

OK, I have had a read of the posts about pyton-ow being no longer supported 
and have now installed owserver and owshell and pyownet.

As I am using a DS2482-100 I2C Bus master my owfs.conf contains:

# DS2482-100 I2C Bus master
server: device = /dev/i2c-1
server: port = localhost:4304

I changed the weewx service section to:

[OWFS]  # Options for extension owfs.py using owserver

interface = localhost:4304
[[sensor_map]]
# 1wire - solar
extraTemp5 =  /uncached/28.E1044104/temperature   # test DS18S20

So far it is all working as expected.


Gaz

-- 
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/0dbcbb96-e95b-47f3-a3e4-ccd6888565b5%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Tom Keffer]

WeeWX supports FTPS, not SFTP. Two questions:

Which one does your server support?

If it supports FTPS, do you know what kind of FTP server it is? The PureFTP
server tickles a bug in the Python FTP library, but we have a work around.

-tk

On Mon, May 25, 2020 at 3:12 AM Messy Potamia 
wrote:

> Note, per another post the relevance of which I'm not certain, i added the
> following to the [[FTP]] section
>secure_ftp = True
>secure_data = False
>
> Makes no difference, still won't connect. Filezilla using sftp connects
> fine, and the native weewx ftp connects fine. I'm trying to use secure ftp.
> May 25 12:05:21 RPI3 weewx[26625]: copygenerator: copied 14 files to /home
> /weewx/public_html
> May 25 12:05:41 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> May 25 12:06:01 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Unable to connect or log
> into server : timed out
> May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Attempted 3 times to
> connect to server sftp.. Giving up.
> May 25 12:06:21 RPI3 weewx[26625]: ftpgenerator: ftp'd 0 files in 60.69
> seconds
>
>
>
>
> On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
>>
>> --
>>
>> In summary, the Secure FTP capability is indicated in weewx.conf (& the
>> caveat comment seems satisfied with testing of Filezilla's success),
>> however in weewx's native install it does not work.
>> --
>> First I tried the method suggested in weewx.conf and the weewx guide: I
>> enabled ssh/sftp with my provider (one.com), followed their
>> instructions, tested it with filezilla, and I connect and upload/dnload
>> just fine. Here's one.com's instructions on the matter:
>> SSH & SFTP Administration
>>
>> *SSH* increases the security on your web space by encrypting your web
>> space connections. With SSH enabled, you can transfer files securely via
>> *SFTP* or connect to your web space directly from a terminal.
>>
>> Allow SSH & SFTP access Off On
>>
>> To log in with SSH & SFTP, use this info:
>>
>> Host: ssh..net
>>
>> Username: .net
>>
>> Port: 22
>>
>> Then their faq on the subject has this:
>>
>>
>> Open your SFTP client, and enter the following details, replacing 
>> *yourdomain.com
>> * with your own domain:
>>
>>- *Host:* sftp.yourdomain.com
>>- *Username:* yourdomain.com
>>- *Password:* the password you have chosen for SFTP
>>- *Port:* 22
>>
>> Click the connect button in your client to log in. If it is the first
>> time you login using SFTP on this computer, you need to approve the
>> connection.
>>
>> Note: I have verified that with filezilla, both sftp.mydomain.net and
>> ssh.mydomain.net, using my ssh/sftp password, connect fine.
>>
>>
>> When I make the appropriate changes to weewx.conf, it is unable to
>> connect. I tried a couple variations just to cross-validate disparities in
>> their guide. No connect.
>>
>>
>> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other things,
>> MWall's
>> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
>>
>> to wit:
>>
>> sudo pip install pysftp
>>
>> which results in:
>>
>> pi@RPI3:/home/weewx $ sudo pip install pysftp
>> Downloading/unpacking pysftp
>>   Downloading pysftp-0.2.9.tar.gz
>>   Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py) egg_info
>> for package pysftp
>>
>> no previously-included directories found matching 'docs/_build'
>> Downloading/unpacking paramiko>=1.17 (from pysftp)
>>   Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB
>> downloaded
>> Cleaning up...
>> Exception:
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122,
>> in main
>> status = self.run(options, args)
>>   File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line
>> 290, in run
>> requirement_set.prepare_files(finder, force_root_egg_info=self.bundle
>> , bundle=self.bundle)
>>   File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1266, in
>> prepare_files
>> req_to_install.extras):
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2401, in
>> requires
>> dm = self._dep_map
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2597, in
>> _dep_map
>> self.__dep_map = self._compute_dependencies()
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2630, in
>> _compute_dependencies
>> common = frozenset(reqs_for_extra(None))
>>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2627, in
>> reqs_for_extra
>> if req.marker_fn(override={'extra':extra}):
>>   File "/usr/lib/python2.7/dist-packages/_markerlib/markers.py", line 113
>> , in marker_fn
>> return eval(compiled_marker, environment)
>>   File "", line 1, in 
>> NameError: name 'platform_system' is not defined
>>
>> Storing debug log for failure in /root/.pip/pip.log
>> I tried a 

[weewx-user] Re: Import of driver failed [Interceptor]

[Stephen Backway]

Running the script directly works, so it is something todo with the Weewx - 
Interceptor link that isn't quite right.

Example output:

sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=sniff 
--iface=wlan0 --filter="src 192.168.4.50 and dst port 80"
mapped packet: {'barometer': 30.58, 'windchill': 46.4, 'dewpoint': 44.6, 
'outHumidity': 94.0, 'UV': 0.0, 'radiation': 0.0, 'rain': None, 'dateTime': 
1590407824, 'windDir': 86.0, 'outTemp': 46.4, 'windSpeed': 0.7, 
'inHumidity': 57.0, 'inTemp': 70.0, 'windGust': 1.1, 'usUnits': 1}
mapped packet: {'barometer': 30.58, 'windchill': 46.4, 'dewpoint': 44.6, 
'outHumidity': 94.0, 'UV': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 
1590407824, 'windDir': 80.0, 'outTemp': 46.4, 'windSpeed': 0.9, 
'inHumidity': 57.0, 'inTemp': 70.0, 'windGust': 1.1, 'usUnits': 1}
mapped packet: {'barometer': 30.58, 'windchill': 46.4, 'dewpoint': 44.6, 
'outHumidity': 94.0, 'UV': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 
1590407884, 'windDir': 80.0, 'outTemp': 46.4, 'windSpeed': 0.9, 
'inHumidity': 57.0, 'inTemp': 69.8, 'windGust': 1.1, 'usUnits': 1}
mapped packet: {'barometer': 30.58, 'windchill': 46.4, 'dewpoint': 44.6, 
'outHumidity': 94.0, 'UV': 0.0, 'radiation': 0.0, 'rain': 0.0, 'dateTime': 
1590407884, 'windDir': 128.0, 'outTemp': 46.4, 'windSpeed': 1.1, 
'inHumidity': 57.0, 'inTemp': 69.8, 'windGust': 1.1, 'usUnits': 1}



-- 
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/8a7a45f2-c475-4226-845d-917560ba2251%40googlegroups.com.

[weewx-user] Re: Highcharts on Weewx v4

[gjr80]

I actually made the changes but never published the release. You will find 
v1.0.0 which is WeeWX 3/4 python2/3 compatible on the weewx-averages 
releases tab  on GitHub.

Gary

On Sunday, 24 May 2020 23:41:10 UTC+10, Phil Owers wrote:
>
> Hi Gary
> Just wondered if you have updated highcharts to work with ver4 /p3 yet
> Cheers Phil
>
> On Saturday, April 18, 2020 at 7:48:17 PM UTC+1, Phil Owers wrote:
>>
>> Hi Guys
>>
>> Loaded highcharts onto my weewx v4 machine and it failed
>> averagesSearchX.py line 105 which is 
>>  except Exception, e:
>>
>> Just wondered if this was a known problem
>>
>> Cheers Phil
>>
>

-- 
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/075374b8-0b3e-45ae-b68c-12a945ab400e%40googlegroups.com.

[weewx-user] Re: Ecowitt GW1000 and Passkey error

[galfert]

On Thursday, May 21, 2020 at 4:28:19 AM UTC-4, Gert Andersen wrote:
> Hi Gary
> 
> 
> Thanks for looking.
> 
> 
> It works with multiple instances listening to different ports, so the 
> solution, buy more GW1000 devices.
> 
> 
> I'm also using mqtt and the solution here was to have 1 instance publishing 
> and the other instances just subscribing  to the topic. Using Belchertown.
> 
> 
> Maybe in the future, Interceptor can do the same.
> 
> 
> Gert
> 
> On Thursday, May 21, 2020 at 8:39:09 AM UTC+2, gjr80 wrote:
> Well that answers that question :) Was reading through the interceptor driver 
> and was starting to come to that conclusion. 
> 
> 
> 
> Gary
> 
> On Thursday, 21 May 2020 16:19:27 UTC+10, Gert Andersen  wrote:
> Hi
> 
> 
> Unfortunately, it seems not possible to have 2 weewx instances using the same 
> port:
> 
> 
> 
> May 21 08:13:52 GAND weewx-billeder[17360] INFO user.interceptor: driver 
> version is 0.53
> May 21 08:13:52 GAND weewx-billeder[17360] INFO user.interceptor: device 
> type: ecowitt-client
> May 21 08:13:52 GAND weewx-billeder[17360] INFO user.interceptor: mode is 
> listen
> May 21 08:13:52 GAND weewx-billeder[17360] INFO user.interceptor: listen on 
> :8000
> May 21 08:13:52 GAND weewx-billeder[17360] ERROR weewx.engine: Import of 
> driver failed: [Errno 98] Address already in use ()
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:       
> Traceback (most recent call last):
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/weewx/engine.py", line 103, in setupStation
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   self.console = loader_function(config_dict, self)
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/user/interceptor.py", line 315, in loader
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   return InterceptorDriver(**config_dict[DRIVER_NAME])
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/user/interceptor.py", line 2523, in __init__
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   self._device = self.DEVICE_TYPES.get(self._device_type)(**stn_dict)
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/user/interceptor.py", line 2298, in __init__
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   super(EcowittClient, self).__init__(
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/user/interceptor.py", line 429, in __init__
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   self._server = Consumer.TCPServer(address, port, handler)
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/home/weewx/bin/user/interceptor.py", line 584, in __init__
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   TCPServer.__init__(self, (address, int(port)), handler)
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/usr/lib/python3.8/socketserver.py", line 452, in __init__
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   self.server_bind()
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
> File "/usr/lib/python3.8/socketserver.py", line 466, in server_bind
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:         
>   self.socket.bind(self.server_address)
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL weewx.engine:       
> OSError: [Errno 98] Address already in use
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL __main__: Unable to load 
> driver: [Errno 98] Address already in use
> May 21 08:13:52 GAND weewx-billeder[17360] CRITICAL __main__:       
> Exiting...
> 
> Gert
> 
> 
> 
> On Thursday, May 21, 2020 at 7:52:53 AM UTC+2, Gert Andersen wrote:
> Hi 
> 
> 
> Yes multiple weewx instances listening to the same port. I have 2 weewx 
> instances serving two different domain(different languages). It could be 
> fine, if they can use the same port. Otherwise I need 2 GW1000 devices using 
> different ports or..?
> 
> 
> Gert
> 
> On Thursday, May 21, 2020 at 6:31:52 AM UTC+2, gjr80 wrote:
> 
> Hi Gert,
> 
> 
> Do you mean multiple WeeWX instances on the same machine listening to the 
> same port? To be truthful I don't know but I would have expected there would 
> be some contention there somewhere. It's an easy enough experiment to do 
> though, you just need another WeeWX config file with the appropriate settings 
> changed and then run directly.
> 
> 
> Gary
> 
> On Thursday, 21 May 2020 14:09:56 UTC+10, Gert Andersen  wrote:
> Hi Gary
> 
> 
> Thanks, working now.
> 
> 
> Do you know if I can more 

[weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

Note, per another post the relevance of which I'm not certain, i added the 
following to the [[FTP]] section
   secure_ftp = True
   secure_data = False

Makes no difference, still won't connect. Filezilla using sftp connects 
fine, and the native weewx ftp connects fine. I'm trying to use secure ftp.
May 25 12:05:21 RPI3 weewx[26625]: copygenerator: copied 14 files to /home/
weewx/public_html
May 25 12:05:41 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
server : timed out
May 25 12:06:01 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
server : timed out
May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Unable to connect or log into 
server : timed out
May 25 12:06:21 RPI3 weewx[26625]: ftpupload: Attempted 3 times to connect 
to server sftp.. Giving up.
May 25 12:06:21 RPI3 weewx[26625]: ftpgenerator: ftp'd 0 files in 60.69 
seconds




On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
>
> -- 
>
> In summary, the Secure FTP capability is indicated in weewx.conf (& the 
> caveat comment seems satisfied with testing of Filezilla's success), 
> however in weewx's native install it does not work.
> --
> First I tried the method suggested in weewx.conf and the weewx guide: I 
> enabled ssh/sftp with my provider (one.com), followed their instructions, 
> tested it with filezilla, and I connect and upload/dnload just fine. Here's 
> one.com's instructions on the matter:
> SSH & SFTP Administration 
>
> *SSH* increases the security on your web space by encrypting your web 
> space connections. With SSH enabled, you can transfer files securely via 
> *SFTP* or connect to your web space directly from a terminal. 
>
> Allow SSH & SFTP access Off On 
>
> To log in with SSH & SFTP, use this info:
>
> Host: ssh..net 
>
> Username: .net 
>
> Port: 22
>
> Then their faq on the subject has this:
>
>
> Open your SFTP client, and enter the following details, replacing 
> *yourdomain.com 
> * with your own domain:
>
>- *Host:* sftp.yourdomain.com
>- *Username:* yourdomain.com
>- *Password:* the password you have chosen for SFTP
>- *Port:* 22
>
> Click the connect button in your client to log in. If it is the first time 
> you login using SFTP on this computer, you need to approve the connection.
>
> Note: I have verified that with filezilla, both sftp.mydomain.net and 
> ssh.mydomain.net, using my ssh/sftp password, connect fine.
>
>
> When I make the appropriate changes to weewx.conf, it is unable to 
> connect. I tried a couple variations just to cross-validate disparities in 
> their guide. No connect.
>
>
> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other things, 
> MWall's 
> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
>
> to wit:
>
> sudo pip install pysftp
>
> which results in:
>
> pi@RPI3:/home/weewx $ sudo pip install pysftp
> Downloading/unpacking pysftp
>   Downloading pysftp-0.2.9.tar.gz
>   Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py) egg_info 
> for package pysftp
>
> no previously-included directories found matching 'docs/_build'
> Downloading/unpacking paramiko>=1.17 (from pysftp)
>   Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB 
> downloaded
> Cleaning up...
> Exception:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in 
> main
> status = self.run(options, args)
>   File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 
> 290, in run
> requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, 
> bundle=self.bundle)
>   File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1266, in 
> prepare_files
> req_to_install.extras):
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2401, in 
> requires
> dm = self._dep_map
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2597, in 
> _dep_map
> self.__dep_map = self._compute_dependencies()
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2630, in 
> _compute_dependencies
> common = frozenset(reqs_for_extra(None))
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2627, in 
> reqs_for_extra
> if req.marker_fn(override={'extra':extra}):
>   File "/usr/lib/python2.7/dist-packages/_markerlib/markers.py", line 113, 
> in marker_fn
> return eval(compiled_marker, environment)
>   File "", line 1, in 
> NameError: name 'platform_system' is not defined
>
> Storing debug log for failure in /root/.pip/pip.log
> I tried a sudo apt-get install but that failed also.
> pi@RPI3:/home/weewx $ sudo apt-get install pysftp
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package pysftp
> So couldn't get to 1st base this inning.
>
>
> In summary, the Secure FTP capability as indicated in weewx.conf (& the 
> caveat comment seems satisfied with testing of Filezilla's 

[weewx-user] Re: sdr.py not parsing Oregon WGR800X output correctly.

[Gazza]

Hi Rob,

I don't know much about python so can you explain how the new version of 
the battery status works as I still have to sort that for my mates station. 

if 'battery_ok' in obj:
pkt['battery'] = 1 if obj.get('battery_ok') == 'OK' else 0

If the received data is "battery_ok" : 1 ( or "battery_ok" : 0 for flat 
battery), what is the == 'OK' doing as it will never return a result of 
'OK" ??


Gaz

-- 
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/e8aabc20-d62b-44ab-934f-7187f5383c27%40googlegroups.com.

[weewx-user] Re: sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

I should amend the subj line from "sftp" to "secure_ftp" because I 
understand that sftp doesn't work, and I was intending to use the native 
secure_ftp feature.

On Monday, May 25, 2020 at 11:33:06 AM UTC+2, Messy Potamia wrote:
>
> -- 
>
> In summary, the Secure FTP capability is indicated in weewx.conf (& the 
> caveat comment seems satisfied with testing of Filezilla's success), 
> however in weewx's native install it does not work.
> --
> First I tried the method suggested in weewx.conf and the weewx guide: I 
> enabled ssh/sftp with my provider (one.com), followed their instructions, 
> tested it with filezilla, and I connect and upload/dnload just fine. Here's 
> one.com's instructions on the matter:
> SSH & SFTP Administration 
>
> *SSH* increases the security on your web space by encrypting your web 
> space connections. With SSH enabled, you can transfer files securely via 
> *SFTP* or connect to your web space directly from a terminal. 
>
> Allow SSH & SFTP access Off On 
>
> To log in with SSH & SFTP, use this info:
>
> Host: ssh..net 
>
> Username: .net 
>
> Port: 22
>
> Then their faq on the subject has this:
>
>
> Open your SFTP client, and enter the following details, replacing 
> *yourdomain.com 
> * with your own domain:
>
>- *Host:* sftp.yourdomain.com
>- *Username:* yourdomain.com
>- *Password:* the password you have chosen for SFTP
>- *Port:* 22
>
> Click the connect button in your client to log in. If it is the first time 
> you login using SFTP on this computer, you need to approve the connection.
>
> Note: I have verified that with filezilla, both sftp.mydomain.net and 
> ssh.mydomain.net, using my ssh/sftp password, connect fine.
>
>
> When I make the appropriate changes to weewx.conf, it is unable to 
> connect. I tried a couple variations just to cross-validate disparities in 
> their guide. No connect.
>
>
> SO THEN I google "weewx 3.9.2 sftp" and come up with, among other things, 
> MWall's 
> https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py
>
> to wit:
>
> sudo pip install pysftp
>
> which results in:
>
> pi@RPI3:/home/weewx $ sudo pip install pysftp
> Downloading/unpacking pysftp
>   Downloading pysftp-0.2.9.tar.gz
>   Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py) egg_info 
> for package pysftp
>
> no previously-included directories found matching 'docs/_build'
> Downloading/unpacking paramiko>=1.17 (from pysftp)
>   Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB 
> downloaded
> Cleaning up...
> Exception:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in 
> main
> status = self.run(options, args)
>   File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 
> 290, in run
> requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, 
> bundle=self.bundle)
>   File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1266, in 
> prepare_files
> req_to_install.extras):
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2401, in 
> requires
> dm = self._dep_map
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2597, in 
> _dep_map
> self.__dep_map = self._compute_dependencies()
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2630, in 
> _compute_dependencies
> common = frozenset(reqs_for_extra(None))
>   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2627, in 
> reqs_for_extra
> if req.marker_fn(override={'extra':extra}):
>   File "/usr/lib/python2.7/dist-packages/_markerlib/markers.py", line 113, 
> in marker_fn
> return eval(compiled_marker, environment)
>   File "", line 1, in 
> NameError: name 'platform_system' is not defined
>
> Storing debug log for failure in /root/.pip/pip.log
> I tried a sudo apt-get install but that failed also.
> pi@RPI3:/home/weewx $ sudo apt-get install pysftp
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package pysftp
> So couldn't get to 1st base this inning.
>
>
> In summary, the Secure FTP capability as indicated in weewx.conf (& the 
> caveat comment seems satisfied with testing of Filezilla's success), in 
> weewx's native install does not work. Not for me. And I believe I've double 
> checked everything.
>
>
> If it requires a hack to package(s) (.py) in weewx I'm comfortable doing 
> that if the instructions are clear, concise, well written. Note, I'm not 
> comfortable writing my own driver.
>
>
> Thank you for helping.
>
>
> Phil
>
>
>

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

[weewx-user] sftp on 3.9.2, RPI3B -- not working with several methods

[Messy Potamia]

-- 

In summary, the Secure FTP capability is indicated in weewx.conf (& the 
caveat comment seems satisfied with testing of Filezilla's success), 
however in weewx's native install it does not work.
--
First I tried the method suggested in weewx.conf and the weewx guide: I 
enabled ssh/sftp with my provider (one.com), followed their instructions, 
tested it with filezilla, and I connect and upload/dnload just fine. Here's 
one.com's instructions on the matter:
SSH & SFTP Administration 

*SSH* increases the security on your web space by encrypting your web space 
connections. With SSH enabled, you can transfer files securely via *SFTP* 
or connect to your web space directly from a terminal. 

Allow SSH & SFTP access Off On 

To log in with SSH & SFTP, use this info:

Host: ssh..net 

Username: .net 

Port: 22

Then their faq on the subject has this:


Open your SFTP client, and enter the following details, replacing 
*yourdomain.com* with your own domain:

   - *Host:* sftp.yourdomain.com
   - *Username:* yourdomain.com
   - *Password:* the password you have chosen for SFTP
   - *Port:* 22

Click the connect button in your client to log in. If it is the first time 
you login using SFTP on this computer, you need to approve the connection.

Note: I have verified that with filezilla, both sftp.mydomain.net and 
ssh.mydomain.net, using my ssh/sftp password, connect fine.


When I make the appropriate changes to weewx.conf, it is unable to connect. 
I tried a couple variations just to cross-validate disparities in their 
guide. No connect.


SO THEN I google "weewx 3.9.2 sftp" and come up with, among other things, 
MWall's 
https://github.com/matthewwall/weewx-sftp/blob/master/bin/user/sftp.py

to wit:

sudo pip install pysftp

which results in:

pi@RPI3:/home/weewx $ sudo pip install pysftp
Downloading/unpacking pysftp
  Downloading pysftp-0.2.9.tar.gz
  Running setup.py (path:/tmp/pip-build-6MvFgx/pysftp/setup.py) egg_info for 
package pysftp

no previously-included directories found matching 'docs/_build'
Downloading/unpacking paramiko>=1.17 (from pysftp)
  Downloading paramiko-2.7.1-py2.py3-none-any.whl (206kB): 206kB downloaded
Cleaning up...
Exception:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in 
main
status = self.run(options, args)
  File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 290, 
in run
requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, 
bundle=self.bundle)
  File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1266, in 
prepare_files
req_to_install.extras):
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2401, in 
requires
dm = self._dep_map
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2597, in 
_dep_map
self.__dep_map = self._compute_dependencies()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2630, in 
_compute_dependencies
common = frozenset(reqs_for_extra(None))
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2627, in 
reqs_for_extra
if req.marker_fn(override={'extra':extra}):
  File "/usr/lib/python2.7/dist-packages/_markerlib/markers.py", line 113, 
in marker_fn
return eval(compiled_marker, environment)
  File "", line 1, in 
NameError: name 'platform_system' is not defined

Storing debug log for failure in /root/.pip/pip.log
I tried a sudo apt-get install but that failed also.
pi@RPI3:/home/weewx $ sudo apt-get install pysftp
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package pysftp
So couldn't get to 1st base this inning.


In summary, the Secure FTP capability as indicated in weewx.conf (& the 
caveat comment seems satisfied with testing of Filezilla's success), in 
weewx's native install does not work. Not for me. And I believe I've double 
checked everything.


If it requires a hack to package(s) (.py) in weewx I'm comfortable doing 
that if the instructions are clear, concise, well written. Note, I'm not 
comfortable writing my own driver.


Thank you for helping.


Phil


-- 
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/315d7689-7b54-454b-a71c-594d9702483c%40googlegroups.com.

[weewx-user] Problem getting rasp pi zero w to talk to wh2310

[neil hancock]

Hi all
I'm unable to get a connection going between wh2310 and pi, most likely 
from what I've read, because the usb voltage is not high enough and I'm 
waiting on powered hub 
but in the meantime if I could get you guys to check the config would be 
great.
Sorry not able to run with debug on in config because the station is not at 
this site but I think it's probably a more basic problem

Syslog-:

May 16 13:33:57 raspberrypi dbus-daemon[563]: [session uid=1000 pid=563] 
Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
May 16 13:33:57 raspberrypi systemd[470]: Started Virtual filesystem 
service - GNOME Online Accounts monitor.
May 16 13:34:04 raspberrypi systemd[1]: systemd-hostnamed.service: 
Succeeded.
May 16 13:34:07 raspberrypi vncserver-x11[365,root]: Connections: 
connected: fe80::1d0:9447:9f59:373b%wlan0::56399 (TCP)
May 16 13:34:07 raspberrypi vncserver-x11[365,root]: Connections: 
authenticated: fe80::1d0:9447:9f59:373b%wlan0::56399 (TCP), as pi (f 
permissions)
May 16 13:34:08 raspberrypi vncserver-x11[365,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
May 16 13:38:01 raspberrypi vncserver-x11[365,root]: Connections: 
disconnected: fe80::1d0:9447:9f59:373b%wlan0::56399 (TCP) ([ViewerClosed] 
VNC Viewer closed)
May 16 13:39:17 raspberrypi vncserver-x11[365,root]: Connections: 
connected: fe80::1d0:9447:9f59:373b%wlan0::56411 (TCP)
May 16 13:39:18 raspberrypi vncserver-x11[365,root]: Connections: 
authenticated: fe80::1d0:9447:9f59:373b%wlan0::56411 (TCP), as pi (f 
permissions)
May 16 13:39:18 raspberrypi vncserver-x11[365,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
May 16 13:42:27 raspberrypi kernel: [  574.389546] usb 1-1: new full-speed 
USB device number 2 using dwc2
May 16 13:42:28 raspberrypi kernel: [  574.640825] usb 1-1: New USB device 
found, idVendor=10c4, idProduct=8468, bcdDevice= 0.00
May 16 13:42:28 raspberrypi kernel: [  574.640846] usb 1-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
May 16 13:42:28 raspberrypi kernel: [  574.640854] usb 1-1: Product: 
HIDtoSPI Slave
May 16 13:42:28 raspberrypi kernel: [  574.640861] usb 1-1: Manufacturer: 
SLAB
May 16 13:42:28 raspberrypi kernel: [  574.655863] hid-generic 
0003:10C4:8468.0001: hiddev96,hidraw0: USB HID v1.01 Device [SLAB HIDtoSPI 
Slave] on usb-2098.usb-1/input0
May 16 13:42:28 raspberrypi mtp-probe: checking bus 1, device 2: 
"/sys/devices/platform/soc/2098.usb/usb1/1-1"
May 16 13:42:28 raspberrypi mtp-probe: bus: 1, device: 2 was not an MTP 
device
May 16 13:42:29 raspberrypi mtp-probe: checking bus 1, device 2: 
"/sys/devices/platform/soc/2098.usb/usb1/1-1"
May 16 13:42:29 raspberrypi mtp-probe: bus: 1, device: 2 was not an MTP 
device
May 16 13:48:10 raspberrypi systemd[1]: Starting Cleanup of Temporary 
Directories...
May 16 13:48:11 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: 
Succeeded.
May 16 13:48:11 raspberrypi systemd[1]: Started Cleanup of Temporary 
Directories.
May 16 13:48:12 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...
May 16 13:48:13 raspberrypi weewx[1336]: Stopping weewx weather system: 
weewx not running
May 16 13:48:13 raspberrypi systemd[1]: weewx.service: Succeeded.
May 16 13:48:13 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
May 16 13:48:25 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
May 16 13:48:28 raspberrypi weewx[1396] INFO __main__: Initializing weewx 
version 4.0.0
May 16 13:48:28 raspberrypi weewx[1396] INFO __main__: Using Python 3.7.3 
(default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
May 16 13:48:28 raspberrypi weewx[1396] INFO __main__: Platform 
Linux-4.19.97+-armv6l-with-debian-10.3
May 16 13:48:28 raspberrypi weewx[1396] INFO __main__: Locale is 
'en_US.UTF-8'
May 16 13:48:28 raspberrypi weewx[1396] INFO __main__: PID file is 
/var/run/weewx.pid
May 16 13:48:29 raspberrypi weewx[1384]: Starting weewx weather system: 
weewx.
May 16 13:48:29 raspberrypi systemd[1]: Started LSB: weewx weather system.
May 16 13:48:29 raspberrypi weewx[1400] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
May 16 13:48:30 raspberrypi weewx[1400] INFO weewx.engine: Loading station 
type WS1 (weewx.drivers.ws1)
May 16 13:48:30 raspberrypi weewx[1400] INFO weewx.drivers.ws1: driver 
version is 0.40
May 16 13:48:30 raspberrypi weewx[1400] INFO weewx.drivers.ws1: using 
serial port /dev/ttyUSB0
May 16 13:48:30 raspberrypi weewx[1400] ERROR weewx.engine: Import of 
driver failed: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No 
such file or directory: '/dev/ttyUSB0' ()
May 16 13:48:30 raspberrypi weewx[1400] CRITICAL weewx.engine:   
Traceback (most recent call last):
May 16 13:48:30 raspberrypi weewx[1400] CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in 
open
May 16 13:48:30 raspberrypi weewx[1400] CRITICAL weewx.engine: 
  self.fd = 

[weewx-user] Re: Import of driver failed [Interceptor]

[Stephen Backway]

> scott,
>
> i still have no idea what changes you are making between runs, and which 
> log output is associated with each change.  it sounds like you are 
> modifying the libpcap layer and the python pcap layer - i've seen at least 
> two different pypcap versions in the log output (1.1 and 1.2.2). 
>
> m
>

Matt, did you ever get to the bottom of this issue?
I have just done an apt-get upgrade, which upgrade the pcap & weewx and ran 
into this same issue.  
I have made sure I'm using the latest version of interceptor. 

I'm regretting upgrading the entire system, rather than just the security 
updates...

Here is my log extract:
May 25 17:56:02 GreatWall weewx[10284] INFO __main__: Initializing weewx 
version 4.0.0
May 25 17:56:02 GreatWall weewx[10284] INFO __main__: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
May 25 17:56:02 GreatWall weewx[10284] INFO __main__: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.11
May 25 17:56:02 GreatWall weewx[10284] INFO __main__: Locale is 
'en_AU.UTF-8'
May 25 17:56:02 GreatWall weewx[10284] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
May 25 17:56:02 GreatWall weewx[10284] INFO weewx.engine: Loading station 
type Interceptor (user.interceptor)
May 25 17:56:02 GreatWall weewx[10284] INFO user.interceptor: driver 
version is 0.53
May 25 17:56:02 GreatWall weewx[10284] INFO user.interceptor: device type: 
wu-client
May 25 17:56:02 GreatWall weewx[10284] INFO user.interceptor: mode is sniff
May 25 17:56:02 GreatWall weewx[10284] INFO user.interceptor: sniff 
iface=wlan0 promiscuous=0
May 25 17:56:02 GreatWall weewx[10284] INFO user.interceptor: sniff filter 
'src 192.168.4.50 and dst port 80'
May 25 17:56:02 GreatWall weewx[10284] ERROR weewx.engine: Import of driver 
failed: in method 'pcapObject_open_live', argument 2 of type 'char *' 
()
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
Traceback (most recent call last):
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/user/interceptor.py", line 315, in loader
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
return InterceptorDriver(**config_dict[DRIVER_NAME])
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/user/interceptor.py", line 2522, in __init__
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
self._device = self.DEVICE_TYPES.get(self._device_type)(**stn_dict)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/user/interceptor.py", line 728, in __init__
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
WUClient.Parser(), handler=WUClient.Handler, **stn_dict)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
iface, pcap_filter, promiscuous)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine: 
File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
def open_live(self, *args): return _pcap.pcapObject_open_live(self, *args)
May 25 17:56:02 GreatWall weewx[10284] CRITICAL weewx.engine:   
TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
May 25 17:56:02 GreatWall weewx[10284] CRITICAL __main__: Unable to load 
driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
May 25 17:56:02 GreatWall weewx[10284] CRITICAL __main__:   
Exiting...

I'm using Raspbian, with the following versions: 

   - python-libpcap v0.6.4-1
   - weewx v4.0.0-1
   - Python v2.7.13-2+deb9u3
   - interceptor v0.54


Here is the weewx config file:
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

[weewx-user] Account of setting up an Ambient WS-2902A with SDR and an additional sensor

[David Robinson]

Of possible interest:

I wrote a detailed end-to-end guide 
based on my 
experiences setting up a weather station  
with the following specs:

   - Ambient Weather WS-2902A
   - NooElec NESDR Smart v4 SDR
   - BMP180 sensor board
   - Raspberry Pi 3B+ running Raspbian Buster
   - WeeWX
   - RTL-SDR
   - RTL_433
   - WeeWX SDR Adapter (modified)
   - Adafruit_Python_BMP Library
   - WeeWX Extra Sensors Adapter (modified)

I hope someone finds it useful.

Regards,

David Robinson

-- 
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/b36c241b-0fd6-4677-82f1-95e965b36e83%40googlegroups.com.

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

[pete_panic]

Hi everyone!

This thread has been extremely helpful. Thank you so much for all the 
input. Nevertheless unfortunatly I wasn't able yet to successfully get the 
rf communication between the raspi and the Klimalogg Pro started. 

I was able to connect to the transceiver and everything went well until the 
log showed the error message "exception in doRF: %s" after "starting rf 
communication". Since I am not firm (yet) with python (I'm more one of the 
old php guys), I wonder if there was the possibility to have a python3 
compatible version of the Klimalogg Pro driver? I did get the message to 
press the USB button on the console but that did not help, it kept on 
showing up...

Did anyone else have this problem?

Thank you again and cheers

Pete

-- 
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/41a0b461-d3ca-4861-aac5-36a9b5e41fec%40googlegroups.com.

[weewx-user] Re: upgrade from 3.9.1 to 4 failed

[Neville Davis]

Actually I will run my getrain.py as a service so all I will need to do is 
access the ramdisk.

Nev

On Monday, May 25, 2020 at 3:58:17 PM UTC+10, Neville Davis wrote:
>
> I have managed to hack owget.py to output directly to a csv file I create 
> in a ramdisk...and I get this by not entering any arguments..so a simple 
> call to to owget.py.
>
> Using this csv I will pull the data into my main sensor reading file.. 
>
> The csv holds the correct data but I get some extra characters I will have 
> to mask...so getting there :)
>
> Neville
>
> On Monday, May 25, 2020 at 11:37:59 AM UTC+10, Neville Davis wrote:
>>
>> I have almost everything working in version 4, all my i2C modules are 
>> detected wind sensors air-conditioning data etc all except my 1wire rain 
>> system.
>> Everything is setup for python 3 so I understand from other posts of the 
>> issue with python-ow.
>> I installed ow-server and pyownet and I get this from the command prompt
>>
>> *pi@raspberrypi*:*/home/sensorreadings $* python getrain.py 
>> //localhost:4304/1D.E3AB0D00/counter.B
>>
>>16570
>>
>> *pi@raspberrypi*:*/home/sensorreadings $* 
>>
>> which is great and does show correct bucket tip info.
>>
>> What I am now attempting to do (with very little success , i am blaming 
>> my age(75) :) is how to get the command line arguments required with the 
>> owget.py script and call that script from my main sensordata.py script 
>> (this collects all data from i2C network and wind.
>>
>> What I want to end up with e.g 16570 returned to my main script and I 
>> process it further from there.
>>
>> I have been looking at subprocess but I am way over my head and any 
>> guidance would be appreciated.
>>
>>
>> Neville
>>
>> On Thursday, May 21, 2020 at 6:32:25 PM UTC+10, Neville Davis wrote:
>>>
>>> Thanks very much Gary
>>>
>>> Nev
>>>
>>> On Thursday, May 21, 2020 at 5:45:16 PM UTC+10, gjr80 wrote:

 You did a setup.py install so just install 3.9.1 over the top. The user 
 directory won't be touched and of course backup your data. Might be 
 worthwhile looking at the log rather than the abbreviated systemctl 
 view, the last part of the systemctl output tells me nothing, there 
 almost certainly will be more in the log.

 A tip for posting logs too, rather than using systemctl status weewx 
 run another terminal and tail the WeeWX log file (nominally 
 /var/log/syslog) in that terminal with something like tail -f -n50 
 /var/log/syslog and take copies as required or edit and copy from the 
 log file. that way you can get a longer log extract not the 'looking 
 through a straw' view that systemctl gives you.

 Gary

 On Thursday, 21 May 2020 17:35:55 UTC+10, Neville Davis wrote:
>
> Well done those edits that problem with my driver cleared others have 
> happened. I then tried to run on simulator and I get
>
> *●* weewx.service - LSB: weewx weather system
>
>Loaded: loaded (/etc/init.d/weewx)
>
>Active: *active (exited)* since Thu 2020-05-21 16:20:37 AEST; 1h 
> 9min ago
>
>   Process: 426 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>
>
> May 21 16:20:37 raspberrypi weewxd[558]: *weewx[558] CRITICAL 
> __main__:   if console and hasattr(console, 'hardware_name'):*
>
> May 21 16:20:37 raspberrypi weewxd[558]: *weewx[558] CRITICAL 
> __main__: File "/home/weewx/bin/weewx/drivers/__init__.py", 
> line 17, in hardware_name*
>
> May 21 16:20:37 raspberrypi weewxd[558]: *weewx[558] CRITICAL 
> __main__:   raise NotImplementedError("Property 
> 'hardware_name' 
> not implemented")*
>
> May 21 16:20:37 raspberrypi weewxd[558]: *weewx[558] CRITICAL 
> __main__:   NotImplementedError: Property 'hardware_name' not 
> implemented*
>
> May 21 16:20:37 raspberrypi weewxd[558]: *weewx[558] CRITICAL 
> __main__:   Exiting.*
>
> May 21 16:39:53 raspberrypi systemd[1]: Started LSB: weewx weather 
> system.
>
> May 21 16:48:24 raspberrypi systemd[1]: Started LSB: weewx weather 
> system.
>
> May 21 16:58:44 raspberrypi systemd[1]: Started LSB: weewx weather 
> system.
>
> May 21 17:25:32 raspberrypi systemd[1]: Started LSB: weewx weather 
> system.
>
> May 21 17:30:24 raspberrypi systemd[1]: Started LSB: weewx weather 
> system.
>
> *pi@raspberrypi*:*/home/weewx/bin/weewx/drivers $* 
>  So now I have a bit of work to do.
> I have another system I have started to build up so will proceed with 
> that get the basic system working then find out why I am having issues 
> with 
> my driver.
>
> Don' suppose there is a quick revert to version 3.9.1 ?? in the interim
>
> Nev
>
> On Thursday, May 21, 2020 at 2:51:39 PM UTC+10, Neville Davis wrote:
>>