[weewx-user] Re: Belchertown About.inc (consBatteryVoltage)

[Jacques Terrettaz]

Hi,

use $current.consBatteryVoltage

Le mardi 26 mai 2020 23:45:13 UTC+2, Jeff Rabin a écrit :
>
> Ok, so I'm feeling really stupid, and someone is going to state the 
> obvious.   But how do I put the Console Voltage in the about.inc for 
> Belchertown skin?
>
> $station.consBatteryVoltage does not work.   Hm
>

-- 
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/31c3065e-0549-4dbd-87cd-c75b647b1d36%40googlegroups.com.

Re: [weewx-user] Re: Is there a way of making a Windows version of WeeWX?

[Harry P]

will try

On Tue, May 26, 2020 at 5:51 PM vince  wrote:

> On Tuesday, May 26, 2020 at 3:47:30 PM UTC-7, Harry P wrote:
>>
>>
>> Is there a way of porting Weewx over to windows?  I cannot seem to  get
>> it installed on my dedicated Ubuntu laptop and or Ubuntu in Windows 10.  I
>> would love to get weewx working thru my sdr as my Lacrosse does not report
>> back to Weatherunderground.
>>
>>
>>
> Run it in a VM or in Docker ?
>
>
>
> --
> 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/8721f3e8-9878-47c8-9273-871e23510365%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/CA%2Bd253rPNWO8pYcUdULM41ycr7_5hbJ5DHLrif_GvDApDgngNw%40mail.gmail.com.

[weewx-user] Re: Is there a way of making a Windows version of WeeWX?

[vince]

On Tuesday, May 26, 2020 at 3:47:30 PM UTC-7, Harry P wrote:
>
>
> Is there a way of porting Weewx over to windows?  I cannot seem to  get it 
> installed on my dedicated Ubuntu laptop and or Ubuntu in Windows 10.  I 
> would love to get weewx working thru my sdr as my Lacrosse does not report 
> back to Weatherunderground. 
>
>
>
Run it in a VM or in Docker ?

 

-- 
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/8721f3e8-9878-47c8-9273-871e23510365%40googlegroups.com.

Re: [weewx-user] New Database weewx 4.0

[Greg from Oz]

Edited the backup from
Make a backup just in case
mysqldump -uroot -p weewx_new > weewx.sql
to
Make a backup just in case
mysqldump -uroot -p weewx > weewx.sql


On Tuesday, 26 May 2020 20:10:50 UTC+10, Greg from Oz wrote:
>
> Hi I thought I would upgrade the schema and I know that I don't have 
> but.
> I couldn't find any documentation on how to do this for *mysql*.
> I did it this way and it seems to work. I am using weewx 4.1
>
> stop weewx
> Make a backup just in case
> mysqldump -uroot -p weewx > weewx.sql
> Because --reconfigure database makes a database called weewx_new I had to 
> allow new permissions for the weewx uer
>  mysql -uroot -p 
>  GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP ON `weewx_new`.* TO 
> 'weewx'@'localhost'
>  exit mysql
>  add the line below to weewx.conf [[wx_binding]]
>  schema = schemas.wview_extended.schema
>  wee_database --reconfigure
>  mysqldump -uroot -p weewx_new > weewx_new.sql
>  the line below is the only way to rename the database
>  mysql -uroot -p weewx < weewx_new.sql
>  delete the weewx_new database
> start weewx and cross your fingers.
>
> I don't know if this is the correct way to do this or if there is 
> documentation somewhere else but it works.
>
> On Friday, 22 May 2020 21:20:31 UTC+10, Tom Keffer wrote:
>>
>> WeeWX Version 4 introduces a new, more flexible, way of specifying 
>> schemas. The old way is still supported. If I understand you correctly, 
>> you're trying to use the new way on an old copy of WeeWX.
>>
>> Try upgrading WeeWX, then try again.
>>
>> -tk
>>
>> On Thu, May 21, 2020 at 9:26 PM Echo 7 Foxtrot <
>> michael...@echo7foxtrot.com> wrote:
>>
>>> I'm very new...been running my weewx 3.9.2 (rpi4) install for about a 
>>> month, using the standard wview.schema.  I've been working on adding some 
>>> sensors and wanting to extend the schema, then I saw the wview_extended 
>>> schema rolling out with 4.0.  It's got everything I wanted to add in the 
>>> near future, and if I'm going to add I thought it'd be best to stick to the 
>>> naming conventions chosen for 4.0.  I placed a copy of wview_extended.py 
>>> from 4.0 in /weewx/schemas and changed the schema in weewx.conf to 
>>> schemas.wview_extended.schema as mentioned in this thread.  This is what I 
>>> get:
>>>
>>> pi@raspberrypi:~ $ sudo wee_database /etc/weewx/weewx.conf --reconfigure
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'archive_sqlite'
>>> New database 'weewx.sdb_new' already exists. Delete it first (y/n)? y
>>> Copying database 'weewx.sdb' to 'weewx.sdb_new'
>>> The new database will use the same unit system as the old ('US').
>>> Are you sure you wish to proceed (y/n)? y
>>> Traceback (most recent call last):
>>>   File "/usr/bin/wee_database", line 794, in 
>>> main()
>>>   File "/usr/bin/wee_database", line 156, in main
>>> reconfigMainDatabase(config_dict, db_binding)
>>>   File "/usr/bin/wee_database", line 336, in reconfigMainDatabase
>>> new_schema=manager_dict['schema'])
>>>   File "/usr/share/weewx/weewx/manager.py", line 817, in reconfig
>>> with Manager.open_with_create(new_db_dict, schema=new_schema) as 
>>> new_archive:
>>>   File "/usr/share/weewx/weewx/manager.py", line 141, in open_with_create
>>> dbmanager = cls(connection, table_name=table_name, schema=schema)
>>>   File "/usr/share/weewx/weewx/manager.py", line 82, in __init__
>>> self._initialize_database(schema)
>>>   File "/usr/share/weewx/weewx/manager.py", line 175, in 
>>> _initialize_database
>>> _sqltypestr = ', '.join(["`%s` %s" % _type for _type in schema])
>>> TypeError: not enough arguments for format string
>>>
>>> The _new .sdb file is created but it is empty (I did it again to capture 
>>> for this post, that's why it was already there).  I went to the syslog to 
>>> capture anything there for this post as well, but there were no entries 
>>> from attempting this.  This first time I tried it I stopped weewx first but 
>>> left it running when I ran wee_database the 2nd time...result was the same.
>>>
>>> Not sure what to do from here...I know just enough about python to have 
>>> a general idea of what the problem is but no idea how to digest this and 
>>> apply corrective action.  Thanks in advance for any help.
>>>
>>> -Michael F.
>>>
>>>
>>> On Saturday, May 9, 2020 at 6:57:09 AM UTC-5, Tom Keffer wrote:

 Updating to WeeWX V4 and changing your schema are two different things. 
 They have nothing to do with each other. Version 4 offers a new schema, 
 but 
 it is used only for new databases.

 If for some reason you wish to change schemas and use the new schema, 
 you can do so using either WeeWX V3 or V4. Follow the directions in the 
 section *Adding a new type to the database 
 * in the 
 Customizing Guide, except skip step #1, and in step #2 change this

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

[Glenn McKechnie]

Thanks Neville,

That's interesting and certainly of note. It may be just what we are
looking for.

Stefano Miccoli is the author of pyownet so we are doubly on topic!

The original post is at...
https://sourceforge.net/p/owfs/mailman/message/36765345/
and part of a much longer thread...
https://sourceforge.net/p/owfs/mailman/owfs-developers/?viewmonth=201909

To me, the take away is to create the override file as follows...

"/etc/systemd/system/owserver.service.d/override.conf is an override
file, that you create with"
sudo systemctl edit owserver.service

and include the following content...

# /etc/systemd/system/owserver.service.d/override.conf
[Service]
User=Debian-ow
Group=Debian-ow
ExecStart=
ExecStart=/usr/bin/owserver -c /etc/owfs.conf --foreground

[Install]
Also=

For context, read the full post at the above link.

I'll add...
We will continue to run owserver as root (skipping his point #1) and
will perform points #2 and #3 by creating the file as he has outlined
above.

I'll add the above to the install notes, and wiki when I get a moment.



On 27/05/2020, Neville Davis  wrote:
> Guys I too have been following, I am now running pythonv3 weewxv4 with
> 1wire rain, my solution is different and messy but seems to work for me,
> But while trying to sort out my problem found a report about problems with
> owserver on Pi using bustergithub miccoli in the config file edit
> owserver.service ExecStart=/user/bin/owserver -c /etc/OWFS,conf
> —foreground, Apparently on the OWFS developer mailing list this is
> discussed. My system is working without the foreground option apparently
> the problem is intermittent.
> Don’t know if this is related to your problem though
>
> On Tuesday, May 26, 2020 at 9:16:24 PM UTC+10, Glenn McKechnie wrote:
>>
>> On 26/05/2020, Messy Potamia > wrote:
>> >
>> > *I'm following this because one of my weewx stations rely heavily on OW
>> >
>> > sensors to augment the data from my Davis Vantage pro2. *
>> > *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
>> > Thx/mp
>>
>> By weewx4 I assume you mean python3 and weewx4?
>>
>> What are the sensors? Just temperature or...?
>>
>>
>> You shouldn't lose anything. The driver does work with weewx4 and python3
>>
>> I have it running with 4.0.b18 which was the last version? before the
>> final release of weewx4.
>> If you know your sensor_map and sensor_type then you are halfway
>> there. Nothings changed in that respect.
>>
>> The biggest hurdle seems to be getting owserver to behave. You could
>> try installing that now and when it runs okay then you'll be set.
>> There may be an interruption if your existing owfs.py (with python-ow
>> I assume) and owserver both point to the busmaster device and attempt
>> a query at the same time (Gaz's was /dev/i2c-1, mine is the USB
>> dongle). It may just simply block on access, or segfault but a restart
>> of either service will fix that, nothing should break.
>> When it comes to restarting services (keeping in mind that I use SysV
>> eg: /etc/init.d/weewx) I no longer use restart. I actually stop them
>> first (regardless of their state) then start them. I have more success
>> that way, probably gives them a chance to regain state.
>>
>> If you do much the same as Gaz but stick with python2.7 then you can
>> test it all before making the big shift to weewx4 running under
>> python3
>>
>> --
>>
>>
>> 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/414b4af4-9539-4110-8000-207fe8ff5814%40googlegroups.com.
>


-- 


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/CAAraAziMBU1Uxq128tN7HQhn7ZcU1Tre4K1JdkcynYbviG70QA%40mail.gmail.com.

[weewx-user] Is there a way of making a Windows version of WeeWX?

[Harry P]

Is there a way of porting Weewx over to windows?  I cannot seem to  get it 
installed on my dedicated Ubuntu laptop and or Ubuntu in Windows 10.  I 
would love to get weewx working thru my sdr as my Lacrosse does not report 
back to Weatherunderground. 


-- 
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/1ae9435b-622d-40b9-b315-b5eb96cf68c3%40googlegroups.com.

[weewx-user] Belchertown About.inc (consBatteryVoltage)

[Jeff Rabin]

Ok, so I'm feeling really stupid, and someone is going to state the 
obvious.   But how do I put the Console Voltage in the about.inc for 
Belchertown skin?

$station.consBatteryVoltage does not work.   Hm

-- 
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/58cf5c25-601b-40bb-9511-2b148ee26131%40googlegroups.com.

[weewx-user] event.record['ET'] throws me a KeyError. Why?

[Maarten van der Hoeven]

Hi group,

Having programming experience, but new to python. Want to write some piece 
of code, that calculates the amount of precipitation shortage (rain minus 
evaotranspiration). It's a measure of drought.

Using some example coding, and extended those.


See the piece of code below. event.record['barometer'] and 
event.record['outTemp'] is working (used as an example, no drought-relation 
ship); they give real values.

However, event.record['ET'] gives me a KeyError. I dont understand it. It 
is in my wview_extended schema (which I extended), its also populated in my 
database.

Why the KeyError?


import schemas.wview_extended
schema = {
'table': schemas.wview_extended.table + [('neerslagtekort', 'REAL')],
'day_summaries' : schemas.wview_extended.day_summaries + 
[('neerslagtekort', 'SCALAR')]
}

import weewx.units
weewx.units.obs_group_dict['neerslagtekort'] = 'group_rain'


neerslag = 0
verdamping = 0
neerslagtekort = 0

class AddElectricity(StdService):

def __init__(self, engine, config_dict):

  # Initialize my superclass first:
  super(AddElectricity, self).__init__(engine, config_dict)

  # Bind to any new archive record events:
  self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)

  self.last_total = None

def new_archive_record(self, event):


   barometer = event.record['barometer']
   outTemp = event.record['outTemp']
   ET = event.record['ET']
   shortage = precipitation - evaporation

   if self.last_total:
  event.record['neerslagtekort'] = shortage

   self.last_total = shortage
   print(" NEERSLAGTEKORT  ")
   print(shortage)



Traceback (most recent call last):
  File "/usr/share/weewx/weewxd", line 261, in 
main()
  File "/usr/share/weewx/weewxd", line 154, in main
engine.run()
  File "/usr/share/weewx/weewx/engine.py", line 202, in run
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
callback(event)
  File "/usr/share/weewx/weewx/engine.py", line 596, in post_loop
self._software_catchup()
  File "/usr/share/weewx/weewx/engine.py", line 656, in _software_catchup
self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
callback(event)
  File "/usr/share/weewx/user/electricity.py", line 64, in 
new_archive_record
ET = event.record['ET']
KeyError: 'ET'


mysql> select from_unixtime(datetime), neerslagtekort,ET,rain from archive 
order by datetime desc limit 5;
+-+-+--+--+
| from_unixtime(datetime) | neerslagtekort  | ET  
 | rain |
+-+-+--+--+
| 2020-05-26 23:26:00 | -1.5559202862588535 |  0.0515329020092 
|0 |
| 2020-05-26 23:25:00 |NULL |  0.05156477243511403 
|0 |
| 2020-05-26 23:24:00 |  20 |  0.05159745765396156 
|0 |
| 2020-05-26 23:23:00 |  20 | 0.051629007161015734 
|0 |
| 2020-05-26 23:22:00 |NULL |  0.05165840624070325 
|0 |
+-+-+--+--+
5 rows in set (0.00 sec)


-- 
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/901f6de4-762e-4dae-8604-427b4168b25c%40googlegroups.com.

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

[Neville Davis]

Guys I too have been following, I am now running pythonv3 weewxv4 with 
1wire rain, my solution is different and messy but seems to work for me, 
But while trying to sort out my problem found a report about problems with 
owserver on Pi using bustergithub miccoli in the config file edit 
owserver.service ExecStart=/user/bin/owserver -c /etc/OWFS,conf 
—foreground, Apparently on the OWFS developer mailing list this is 
discussed. My system is working without the foreground option apparently 
the problem is intermittent.
Don’t know if this is related to your problem though

On Tuesday, May 26, 2020 at 9:16:24 PM UTC+10, Glenn McKechnie wrote:
>
> On 26/05/2020, Messy Potamia > wrote: 
> > 
> > *I'm following this because one of my weewx stations rely heavily on OW 
> > sensors to augment the data from my Davis Vantage pro2. * 
> > *I'd upgrade to weewx 4.x but really can't lose owfs operability*. 
> > Thx/mp 
>
> By weewx4 I assume you mean python3 and weewx4? 
>
> What are the sensors? Just temperature or...? 
>
>
> You shouldn't lose anything. The driver does work with weewx4 and python3 
> I have it running with 4.0.b18 which was the last version? before the 
> final release of weewx4. 
> If you know your sensor_map and sensor_type then you are halfway 
> there. Nothings changed in that respect. 
>
> The biggest hurdle seems to be getting owserver to behave. You could 
> try installing that now and when it runs okay then you'll be set. 
> There may be an interruption if your existing owfs.py (with python-ow 
> I assume) and owserver both point to the busmaster device and attempt 
> a query at the same time (Gaz's was /dev/i2c-1, mine is the USB 
> dongle). It may just simply block on access, or segfault but a restart 
> of either service will fix that, nothing should break. 
> When it comes to restarting services (keeping in mind that I use SysV 
> eg: /etc/init.d/weewx) I no longer use restart. I actually stop them 
> first (regardless of their state) then start them. I have more success 
> that way, probably gives them a chance to regain state. 
>
> If you do much the same as Gaz but stick with python2.7 then you can 
> test it all before making the big shift to weewx4 running under 
> python3 
>
> -- 
>
>
> 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/414b4af4-9539-4110-8000-207fe8ff5814%40googlegroups.com.

Re: [weewx-user] On upgrade, the new weewx.conf keeps losing quotes around the passwords

[Tom Keffer]

Unless there's some secret setting in ConfigObj that I'm not aware of, it
looks like this is what ConfigObj does on write.

In practice, the only time the quotes are necessary is if your password
contains a comma (',') or the sharp ('#') sign. Otherwise, there should be
no problem.

But, clearly, we need to change the comments.

-tk


On Tue, May 26, 2020 at 8:34 AM Joel Bion  wrote:

> I have modified my weewx.conf file to put quotes around the passwords
> (example: my mysql password), as the comments in that file request me to
> do. Every upgrade, all those quotes are lost. I have to put them all back
> in. Can these quotes be kept across upgrades?
>
> --
> 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/030a6fb7-befc-4e50-a331-2a091442193f%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/CAPq0zEBV-_xkQQwMS0c2HEACG%2BBqvHXkvwS6-%2BCT9EB1vAWVHg%40mail.gmail.com.

[weewx-user] Re: draw user-defined lines in graphics

[Jeff A. D.]

I just realized I didn't answer about the average value in the first plot.  
That's just the outTemp under [[[yeartempdew]]] that was included 
in the original skin.conf that I commented out the dewpoint on for the 
yearly plot.

So normally it would have just looked like this:

> [[[yeartempdew]]]
> outTemp
> dewpoint
>




On Tuesday, May 26, 2020 at 3:35:01 AM UTC-6, Remy Lavabre wrote:
>
> Hi Jeff,
>
> Hello,
> Your curves are superb!
> Could you tell me the parameters to retrieve the maximum, minimum and 
> average values and be able to plot them in curve tables?
> Thank you very much ! ;-)
>
>
>>

-- 
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/c76820f0-580c-4d2c-b284-3f9de7432e9b%40googlegroups.com.

[weewx-user] Re: Belchertown MQTT update time is chaotic

[Jacques Terrettaz]

In the original skin.conf of Belchertown v 1.1 , i see :

mqtt_websockets_connected   = Connected to weather station live. Data 
received

On my side, I have a running Belchertown 1.1 template, translated 
in French,  ( see http://meteo-sciez.fr/weewx/belchertown/ ) with :

mqtt_websockets_connected   = Connecté à la station. Mesures du

On your side, if you have for instance :

mqtt_websockets_connected   = Verbonden met weerstation. Data received on 

with "Data received on"  translated in your language,  does it works ?

If not, I really don't know where is the cause of your problem.


 

-- 
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/69c91f0d-d596-4446-a31e-5feb6f4684fe%40googlegroups.com.

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

[Ronald Berghammer]

Thanks a lot, no Stress it is not urgent

-- 
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/128f218f-4e1e-4bcd-b1da-d311ccc1cb61%40googlegroups.com.

[weewx-user] Re: draw user-defined lines in graphics

[Jeff A. D.]

Thanks Remy,

I added this under "[[year_images]]" in the "skins.conf" file for the 
Seasons skin I''m using.

# Plot of high/low temperatures
> [[[yearhilow]]]
> freezeLine
> data_type = 32
> label = ' '
> color = 0x42b442
> hi
> data_type = outTemp
> aggregate_type = max
> label = High Outside Temperature
> color = 0x4242b4
> low
> data_type = outTemp
> aggregate_type = min
> label = Low Outside Temperature
> color = 0xb48242
>

Assuming you don't want the freeze line you can just leave it and the 
"color" parameters out I think:

[[[yearhilow]]]
> hi
> data_type = outTemp
> aggregate_type = max
> label = High Outside Temperature
> low
> data_type = outTemp
> aggregate_type = min
> label = Low Outside Temperature
>

I think that's all I did?  (I always forget and have to play with things to 
get them to do what I want.)

I also assume you could have all three variables (Out Temp, Hi Out Temp, 
and Lo Out Temp) on one plot if you wanted, but I didn't try it.

I think I got the example from some of the documentation, probably the 
Customization Guide.

On Tuesday, May 26, 2020 at 3:35:01 AM UTC-6, Remy Lavabre wrote:

> Hi Jeff,
>
> Hello,
> Your curves are superb!
> Could you tell me the parameters to retrieve the maximum, minimum and 
> average values and be able to plot them in curve tables?
> Thank you very much ! ;-)
>
>
>>

-- 
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/91af0d30-e4d7-45ab-bc52-085b5d67a601%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT update time is chaotic

[Jacques Terrettaz]

Hi,

Text segments ? What do you mean ?



> Le 26 mai 2020 à 18:49, Keimpe Bleeker  a écrit :
> 
> What remains is the correct connection of text segments, but trhat is realy 
> minor a minor issue!

-- 
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/B4708BC0-C00F-4D7A-A70B-2ADF583DDC78%40gmail.com.

[weewx-user] Re: Belchertown MQTT update time is chaotic

[Keimpe Bleeker]

Hi Manfred, Tried everything with commas, dots, quotation marks, ... But 
stil I see only 'connected to weatherstation - ', while 'Date 
received' is missing for the real-time update. Strange enough the sentence 
is correctly presented with the text 'Connected, waiting for...'.


Op zondag 24 mei 2020 21:22:38 UTC+2 schreef Manfred Maier:
>
> I guess the system can't properly work with your commas and dots in your 
> translation. Try to either delete the commas or put the translation in 
> quotes "Verbonden met weerstation,"
>
> Manfred 
>
> Am Sonntag, 24. Mai 2020 20:54:46 UTC+2 schrieb Keimpe Bleeker:
>>
>> Thanks for your much appreciated assistance!
>>
>> I would not dare to change someting deep in de system like in 
>> /weewx/skins/Belchetown/js/belchertown.js.tmpl. Nevertheless and on your 
>> advice, I checked line 839 and it is exactly as you mentioned.
>>
>> In /weewx/skins/Belchertown/skin.conf I have these Dutch terms:
>>
>> header_last_updated = Laatste update
>> mqtt_websockets_connecting  = Verbinden met weerstation,
>> mqtt_websockets_waiting = Verbonden, wacht op data.
>> mqtt_websockets_connected   = Verbonden met weerstation,
>> mqtt_websockets_stopped = Updates zijn gestopt
>> mqtt_websockets_continue= Updates hervatten
>> mqtt_websockets_failed  = Verbinding verbroken
>> mqtt_websockets_lost= Verbinding verbroken
>>
>> In weewx.conf the term '...websockets...' was not found.  
>>
>>
>>
>>
>>
>> Op zondag 24 mei 2020 20:03:47 UTC+2 schreef Jacques Terrettaz:
>>>
>>> The text is defined by the variable *mqtt_websockets_connected * in 
>>> skin.conf.
>>>
>>> If it does not correspond, check your skin.conf as well as your 
>>> weewx.conf to be sure that you have not the variable   
>>> *mqtt_websockets_connected 
>>>  *defined also elsewhere*.*
>>> If you have changed something in the template 
>>> weewx/skins/Belchetown/js/belchertown.js.tmpl, verify that the line 839 is :
>>>
>>> updated_text = "$obs.label.mqtt_websockets_connected " + updated;
>>>  
>>>
>>> Le dimanche 24 mai 2020 19:38:27 UTC+2, Keimpe Bleeker a écrit :

 Thank you so much Jacques Terrettaz, you have solved my time-issue; it 
 seems that I have spoiled a variable!

 Last issue is to get the text 'Connected to weather station live. Data 
 received ' up and running. 


 [image: Brackets_24052020.jpg]
 As you can see on the screencap, I only get (in Dutch) 'Connected to 
 weatherstation' between brackets and single quotes...




 Op zondag 24 mei 2020 10:13:36 UTC+2 schreef Jacques Terrettaz:
>
> I think I have found the problem :
>
> In your first post I see :
>
> # moment.js default labels formats
> time_earthquake= "LLL"
> time_lastUpdated   = "LL, 
> LTS"
> time_snapshot_records_today_header  = ", LL"
> time_snapshot_records_month_header = " "
> ...
>
> You should replace 
>  time_lastUpdated by time_last_updated :
>
>  # moment.js default labels formats
> time_earthquake= "LLL"
> *time_last_updated  * = 
> "LL, LTS"
> time_snapshot_records_today_header  = ", LL"
> time_snapshot_records_month_header = " "
>   
>
>
>

-- 
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/e9df221c-9e3a-45ad-9657-db2347d35c94%40googlegroups.com.

[weewx-user] Re: Belchertown MQTT update time is chaotic

[Keimpe Bleeker]

Thanks Jacques, you solved a major problem!

What remains is the correct connection of text segments, but trhat is realy 
minor a minor issue!

Again thanks!

 

Op zondag 24 mei 2020 10:13:36 UTC+2 schreef Jacques Terrettaz:
>
> I think I have found the problem :
>
> In your first post I see :
>
> # moment.js default labels formats
> time_earthquake= "LLL"
> time_lastUpdated   = "LL, LTS"
> time_snapshot_records_today_header  = ", LL"
> time_snapshot_records_month_header = " "
> ...
>
> You should replace 
>  time_lastUpdated by time_last_updated :
>
>  # moment.js default labels formats
> time_earthquake= "LLL"
> *time_last_updated  * = "LL, 
> LTS"
> time_snapshot_records_today_header  = ", LL"
> time_snapshot_records_month_header = " "
>   
>
>
>

-- 
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/c0d75822-4c7c-4821-be5f-7734ed783e1a%40googlegroups.com.

Re: [weewx-user] Re: Lacrosse CA80550 Weather Station and Weewx

[Harry P]

Thank you for the information.the sdr info u sent talks about recieving in
the 415mhz range. Mine are in 915mhz.  I will try the sdr setup. Looks cool

On Tue, May 26, 2020, 4:10 AM mwall  wrote:

> On Tuesday, May 26, 2020 at 2:51:46 AM UTC-4, Harry P wrote:
>>
>> Do I have any chance of having Weewx work with my Lacrosse CA80550
>> Weatherstation?
>>
>
> it looks like the wifi in that weather station is receive-only - it pulls
> forecasts from the us nws.  if the station *sends* data, for example to
> weather underground, then you can use the weewx-interceptor extension to
> capture the data.  if the station has a usb or other communication port,
> then it might be possible to pull data using that interface.
>
> otherwise, your only option would be to purchase a usb sdr dongle and use
> the weewx-sdr extension to capture data from the wind and temperature
> sensors directly.
>
> here is a guide for how to do it with acurite sensors:
>
> https://github.com/weewx/weewx/wiki/sdr-rpi-recipe
>
> the process is the same for lacross sensors
>
> 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/8a260190-5a07-4a38-9289-2d2376e54eeb%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/CA%2Bd253otK%2Btd0rHtNLV84J_-O-aqypT%3DTeB-pr6poKbT146i2Q%40mail.gmail.com.

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

[G Hammer]

Excellent write up! Thank you.

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

[weewx-user] On upgrade, the new weewx.conf keeps losing quotes around the passwords

[Joel Bion]

I have modified my weewx.conf file to put quotes around the passwords 
(example: my mysql password), as the comments in that file request me to 
do. Every upgrade, all those quotes are lost. I have to put them all back 
in. Can these quotes be kept across upgrades?

-- 
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/030a6fb7-befc-4e50-a331-2a091442193f%40googlegroups.com.

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

[John Smith]

On Tuesday, 26 May 2020 17:59:58 UTC+10, Ronald Berghammer wrote:
>
> I have a Outdoor and Indoor Sensor (temp/humidity) and a rain sensor.
> Windsensor i don't have!


I've been making changes to the skin to work round this, but I don't have 
time today to finish fixing it.

-- 
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/0ee9fb53-8e84-4ba9-bc43-35545528b075%40googlegroups.com.

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

[Tom Keffer]

One pip quirk that consistently bites me over and over again, is trying to
use pip from the WeeWX home directory, /home/weewx. It appears that is what
you're trying to do.

The problem is the presence of the file setup.cfg. Pip sees it, and tries
to install in the directories it specifies, in this case /home/weewx. Take
a look in /home/weewx/bin and see if your missing pysftp is in there.

The solution is to clean up /home/weewx/bin, then cd to some other
directory, then use pip.

-tk



On Tue, May 26, 2020 at 4:26 AM mwall  wrote:

>
>
> On Tuesday, May 26, 2020 at 4:35:50 AM UTC-4, Messy Potamia wrote:
>>
>> Well I knew that was too good to be true.
>>
>
> the first error you posted, regarding 'platform_system' NameError, is
> probably due to an old version of setuptools.  to fix that, update the
> setuptools for the python installation associated with the 'pip' version
> that you are invoking.
>
>
>
>> May 26 10:30:21 RPI3 weewx[21915]: sftpgenerator: upload not possible: No
>> module named pysftp
>>
>>>
>>>
> that indicates the python with which you are invoking weewx does not have
> pysftp installed.  perhaps you installed pysftp for python3 but you are
> using python2 to invoke weewx?
>
> dog's breakfast indeed.  welcome to the world of python dependencies!
> (this is why we try really hard to keep weewx dependencies to a minimum)
>
> one way to avoid this is to install your own python, completely
> independent of the system's python.  then use the 'pip' from that python
> installation to install all of the python packages you need.  you may still
> have to install the build environment and the occasional dev package for
> your operating system.
>
> the you can use that python by setting it in /etc/default/weewx (if you
> have a deb/apt or rpm/yum/dnf install) or by invoking it when you do
> 'setup.py install' (if you have a setup.py install of weewx).
>
> 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/82433072-10b1-400c-bf00-3cd94191cc5e%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/CAPq0zEC4YGNiOgWzgqh_pEiOzMWTUwE1s9%2BPJbvz0yVaeBYBFA%40mail.gmail.com.

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

[mwall]

On Tuesday, May 26, 2020 at 4:35:50 AM UTC-4, Messy Potamia wrote:
>
> Well I knew that was too good to be true.
>

the first error you posted, regarding 'platform_system' NameError, is 
probably due to an old version of setuptools.  to fix that, update the 
setuptools for the python installation associated with the 'pip' version 
that you are invoking.

 

> May 26 10:30:21 RPI3 weewx[21915]: sftpgenerator: upload not possible: No 
> module named pysftp
>
>>
>>
that indicates the python with which you are invoking weewx does not have 
pysftp installed.  perhaps you installed pysftp for python3 but you are 
using python2 to invoke weewx?

dog's breakfast indeed.  welcome to the world of python dependencies!  
(this is why we try really hard to keep weewx dependencies to a minimum)

one way to avoid this is to install your own python, completely independent 
of the system's python.  then use the 'pip' from that python installation 
to install all of the python packages you need.  you may still have to 
install the build environment and the occasional dev package for your 
operating system.

the you can use that python by setting it in /etc/default/weewx (if you 
have a deb/apt or rpm/yum/dnf install) or by invoking it when you do 
'setup.py install' (if you have a setup.py install of weewx).

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/82433072-10b1-400c-bf00-3cd94191cc5e%40googlegroups.com.

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

[Glenn McKechnie]

On 26/05/2020, Messy Potamia  wrote:
>
> *I'm following this because one of my weewx stations rely heavily on OW
> sensors to augment the data from my Davis Vantage pro2. *
> *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
> Thx/mp

By weewx4 I assume you mean python3 and weewx4?

What are the sensors? Just temperature or...?


You shouldn't lose anything. The driver does work with weewx4 and python3
I have it running with 4.0.b18 which was the last version? before the
final release of weewx4.
If you know your sensor_map and sensor_type then you are halfway
there. Nothings changed in that respect.

The biggest hurdle seems to be getting owserver to behave. You could
try installing that now and when it runs okay then you'll be set.
There may be an interruption if your existing owfs.py (with python-ow
I assume) and owserver both point to the busmaster device and attempt
a query at the same time (Gaz's was /dev/i2c-1, mine is the USB
dongle). It may just simply block on access, or segfault but a restart
of either service will fix that, nothing should break.
When it comes to restarting services (keeping in mind that I use SysV
eg: /etc/init.d/weewx) I no longer use restart. I actually stop them
first (regardless of their state) then start them. I have more success
that way, probably gives them a chance to regain state.

If you do much the same as Gaz but stick with python2.7 then you can
test it all before making the big shift to weewx4 running under
python3

-- 


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/CAAraAzjEqh-W-z2VUo6hCsKEyzTxcJEqX_pvEDkx8pcQKShOuw%40mail.gmail.com.

Re: [weewx-user] Additional Sensors

[Greg Troxel]

ttech  writes:

> 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 almost certainly want to configure a "service" in addition to the
vantage "driver" to get the extra data and merge it in.

First, read

  http://www.weewx.com/docs/customizing.htm

all the way through.

I would suggest also looking at:

  https://github.com/bellrichm/WeeWX-MQTTSubscribe

as a hint, even if you don't want to just post your other data to a
local MQTT broker.

-- 
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/rmi7dwzvtke.fsf%40s1.lexort.com.

[weewx-user] Re: Lacrosse CA80550 Weather Station and Weewx

[mwall]

On Tuesday, May 26, 2020 at 2:51:46 AM UTC-4, Harry P wrote:
>
> Do I have any chance of having Weewx work with my Lacrosse CA80550 
> Weatherstation?
>

it looks like the wifi in that weather station is receive-only - it pulls 
forecasts from the us nws.  if the station *sends* data, for example to 
weather underground, then you can use the weewx-interceptor extension to 
capture the data.  if the station has a usb or other communication port, 
then it might be possible to pull data using that interface.

otherwise, your only option would be to purchase a usb sdr dongle and use 
the weewx-sdr extension to capture data from the wind and temperature 
sensors directly.

here is a guide for how to do it with acurite sensors:

https://github.com/weewx/weewx/wiki/sdr-rpi-recipe

the process is the same for lacross sensors

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/8a260190-5a07-4a38-9289-2d2376e54eeb%40googlegroups.com.

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

[Glenn McKechnie]

On 26/05/2020, Gazza  wrote:
> Hi Glen,
>
> My interface board is based on one I milled on my CNC a couple of years
> ago, for the new one I had the board made as it makes it much easier to
> assemble that the bare copper ones.

CNC!
As an ex fitter, toolmaker come "jack of all" that's my language.

> This one is in the shape of a Pi HAT and has a RTC and the DS2482-100 I2C
> Bus plus provision to attach a BME280 barometer module. So far testing has
> shown that the RTC and the 1wire works but I have noticed that the self
> heating of the test DS18B20 probably means that it is not feasible to add
> the barometer to the board and it will need to mounted externally.
>
> If you want one to do some testing I have a few boards spare thanks to
> minimum orders and Maxims (previous) generosity with samples.

That sounds good Gaz. I'll take you up on it.

Bcc'ing you with this mail.


-- 


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/CAAraAzhAeoBSgkC7w%3D-6VvZ%2BTX7R%2Bv3AcMF5%3DUZbvJ3gyt%2BZ1g%40mail.gmail.com.

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

[Messy Potamia]

*Thanks good to know. I extended my schema ~5 yrs ago, to add some lake 
height and wave height measured by a MaxBotix rangefinder, and lightning, 
parameters. A couple other params I stuffed into unused columns in the 
weewx.sdb and renamed the reports. *

*I'm going to have to rebuild my whole server next time I'm home because I 
think the system took a power hit, my cameras show a bright flash last 
month and stuff started malfunctioning. *

*I'm not energetic enough to build my own I2C owfs interace; as for mine I 
use Sheepwalk Electronics' RPI hat. *
*My whole system is on an isolated (or so I thought), 12V --> 5V / 3.3V 
power supply based on a standard fire/burg system standby power supply. My 
system was up for over 400 days until I started having weird problems, and 
I had to reboot it. Still having problems which are logically inconsistent 
-- weewx ftp (to my web hosting service) often fails and is very slow, 
however -- the logically inconsistent part -- speedtest-cli shows good 
up/down speeds, and ftp from another server at the local network to the 
hosting service is very fast, so it seems something in the weewx ftp 
utility is affected and I'm suspecting it's damaged. I had to rebuild this 
pi a few years ago due to a zap which, i believe, came through the router 
in the boathouse (it's in a boathouse).*
*So that's my main system. I'm temporarily stationed in Germany for another 
couple years but like to know the conditions & status of stuff back home 
(on the Tennessee river, Alabama)*

*"mp"*

On Tuesday, May 26, 2020 at 12:25:54 PM UTC+2, Gazza wrote:
>
>
>
> On Tuesday, May 26, 2020 at 6:18:17 PM UTC+10, Messy Potamia wrote:
>>
>>
>> *I'm following this because one of my weewx stations rely heavily on OW 
>> sensors to augment the data from my Davis Vantage pro2. *
>> *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
>> Thx/mp
>>
>
> This testing has been with a fresh install of Buster on a Pi4 and OWFS 
> seems to be working fine with Weewx V4 and python2 using the wview-extended 
> schema. I specifically wanted to use the extended schema so I could use the 
> additional extraTemp and extraHumid fields (currently using extraTemp1-5 
> and extraHumid1-4). 
>
> I have tested the V3 database to V4 conversion and it worked but I don't 
> think that is much use as some of my sensors will now use different 
> database fields.
>
>
> 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/557c97cf-fdc3-4bf9-9b34-7ed6d7f478a8%40googlegroups.com.

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

[Gazza]

On Tuesday, May 26, 2020 at 6:18:17 PM UTC+10, Messy Potamia wrote:
>
>
> *I'm following this because one of my weewx stations rely heavily on OW 
> sensors to augment the data from my Davis Vantage pro2. *
> *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
> Thx/mp
>

This testing has been with a fresh install of Buster on a Pi4 and OWFS 
seems to be working fine with Weewx V4 and python2 using the wview-extended 
schema. I specifically wanted to use the extended schema so I could use the 
additional extraTemp and extraHumid fields (currently using extraTemp1-5 
and extraHumid1-4). 

I have tested the V3 database to V4 conversion and it worked but I don't 
think that is much use as some of my sensors will now use different 
database fields.


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/7d3287eb-29a4-4072-a2bf-4d24113a1e6d%40googlegroups.com.

Re: [weewx-user] New Database weewx 4.0

[Greg from Oz]

Hi I thought I would upgrade the schema and I know that I don't have 
but.
I couldn't find any documentation on how to do this for *mysql*.
I did it this way and it seems to work. I am using weewx 4.1

stop weewx
Make a backup just in case
mysqldump -uroot -p weewx_new > weewx.sql
Because --reconfigure database makes a database called weewx_new I had to 
allow new permissions for the weewx uer
 mysql -uroot -p 
 GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP ON `weewx_new`.* TO 
'weewx'@'localhost'
 exit mysql
 add the line below to weewx.conf [[wx_binding]]
 schema = schemas.wview_extended.schema
 wee_database --reconfigure
 mysqldump -uroot -p weewx_new > weewx_new.sql
 the line below is the only way to rename the database
 mysql -uroot -p weewx < weewx_new.sql
 delete the weewx_new database
start weewx and cross your fingers.

I don't know if this is the correct way to do this or if there is 
documentation somewhere else but it works.

On Friday, 22 May 2020 21:20:31 UTC+10, Tom Keffer wrote:
>
> WeeWX Version 4 introduces a new, more flexible, way of specifying 
> schemas. The old way is still supported. If I understand you correctly, 
> you're trying to use the new way on an old copy of WeeWX.
>
> Try upgrading WeeWX, then try again.
>
> -tk
>
> On Thu, May 21, 2020 at 9:26 PM Echo 7 Foxtrot <
> michael...@echo7foxtrot.com > wrote:
>
>> I'm very new...been running my weewx 3.9.2 (rpi4) install for about a 
>> month, using the standard wview.schema.  I've been working on adding some 
>> sensors and wanting to extend the schema, then I saw the wview_extended 
>> schema rolling out with 4.0.  It's got everything I wanted to add in the 
>> near future, and if I'm going to add I thought it'd be best to stick to the 
>> naming conventions chosen for 4.0.  I placed a copy of wview_extended.py 
>> from 4.0 in /weewx/schemas and changed the schema in weewx.conf to 
>> schemas.wview_extended.schema as mentioned in this thread.  This is what I 
>> get:
>>
>> pi@raspberrypi:~ $ sudo wee_database /etc/weewx/weewx.conf --reconfigure
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> New database 'weewx.sdb_new' already exists. Delete it first (y/n)? y
>> Copying database 'weewx.sdb' to 'weewx.sdb_new'
>> The new database will use the same unit system as the old ('US').
>> Are you sure you wish to proceed (y/n)? y
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_database", line 794, in 
>> main()
>>   File "/usr/bin/wee_database", line 156, in main
>> reconfigMainDatabase(config_dict, db_binding)
>>   File "/usr/bin/wee_database", line 336, in reconfigMainDatabase
>> new_schema=manager_dict['schema'])
>>   File "/usr/share/weewx/weewx/manager.py", line 817, in reconfig
>> with Manager.open_with_create(new_db_dict, schema=new_schema) as 
>> new_archive:
>>   File "/usr/share/weewx/weewx/manager.py", line 141, in open_with_create
>> dbmanager = cls(connection, table_name=table_name, schema=schema)
>>   File "/usr/share/weewx/weewx/manager.py", line 82, in __init__
>> self._initialize_database(schema)
>>   File "/usr/share/weewx/weewx/manager.py", line 175, in 
>> _initialize_database
>> _sqltypestr = ', '.join(["`%s` %s" % _type for _type in schema])
>> TypeError: not enough arguments for format string
>>
>> The _new .sdb file is created but it is empty (I did it again to capture 
>> for this post, that's why it was already there).  I went to the syslog to 
>> capture anything there for this post as well, but there were no entries 
>> from attempting this.  This first time I tried it I stopped weewx first but 
>> left it running when I ran wee_database the 2nd time...result was the same.
>>
>> Not sure what to do from here...I know just enough about python to have a 
>> general idea of what the problem is but no idea how to digest this and 
>> apply corrective action.  Thanks in advance for any help.
>>
>> -Michael F.
>>
>>
>> On Saturday, May 9, 2020 at 6:57:09 AM UTC-5, Tom Keffer wrote:
>>>
>>> Updating to WeeWX V4 and changing your schema are two different things. 
>>> They have nothing to do with each other. Version 4 offers a new schema, but 
>>> it is used only for new databases.
>>>
>>> If for some reason you wish to change schemas and use the new schema, 
>>> you can do so using either WeeWX V3 or V4. Follow the directions in the 
>>> section *Adding a new type to the database 
>>> * in the 
>>> Customizing Guide, except skip step #1, and in step #2 change this
>>>
>>> [DataBindings]
>>> [[wx_binding]]
>>> database = archive_sqlite
>>> table_name = archive
>>> manager = weewx.wxmanager.DaySummaryManager
>>> schema = user.electricity.electricity_schema
>>>
>>> to this
>>>
>>> [DataBindings]
>>> [[wx_binding]]
>>> database = archive_sqlite
>>> table_name = 

[weewx-user] Re: [weewx-development] Version 4.1.0 is ready

[Greg from Oz]

Apt update went OK...up and running.

Thanks


On Tuesday, 26 May 2020 19:39:37 UTC+10, Graham Eddy wrote:
>
> update 4.0.0 to 4.1.0 on macOS using setup.py was smooth.
> g-eddy
>
> On 26 May 2020, at 5:35 am, Tom Keffer > 
> wrote:
>
> 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-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-de...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-development/CAPq0zECm5fhnifO8NshFb%2BdwDhQ4cdW3B6db-hXscp8jUGw22g%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/94bf356b-913e-4f84-aa5c-3c1d8452d6ea%40googlegroups.com.

[weewx-user] Re: [weewx-development] Version 4.1.0 is ready

[Graham Eddy]

update 4.0.0 to 4.1.0 on macOS using setup.py was smooth.
g-eddy

> On 26 May 2020, at 5:35 am, Tom Keffer  wrote:
> 
> 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-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-development+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-development/CAPq0zECm5fhnifO8NshFb%2BdwDhQ4cdW3B6db-hXscp8jUGw22g%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/E31312CA-2DFA-4113-891B-55C9205D327A%40gmail.com.

[weewx-user] Re: draw user-defined lines in graphics

[Remy Lavabre]

Hi Jeff,

Hello,
Your curves are superb!
Could you tell me the parameters to retrieve the maximum, minimum and 
average values and be able to plot them in curve tables?
Thank you very much ! ;-)


>

-- 
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/0bd81d61-da8c-4c8d-bc19-1034226dd512%40googlegroups.com.

Re: [weewx-user] Re: draw user-defined lines in graphics

[Jeff A. D.]

Thanks!

Working again with 4.1.0 "Allow expressions to be used as a datatype when 
plotting."

[image: TempCharts.png]
Makes it easier to see how long my growing season is in case I decide to 
invest in tropical fruit crops. :)

Thanks again, and thanks to others here for the idea!


On Friday, May 1, 2020 at 3:48:37 PM UTC-6, Tom Keffer wrote:
>
> I added it to the TODO list 
> .
>
>
>

-- 
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/49a6317b-234e-4874-bfd4-a28304db16fe%40googlegroups.com.

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

[Messy Potamia]

Well I knew that was too good to be true.

May 26 10:30:21 RPI3 weewx[21915]: sftpgenerator: upload not possible: No 
module named pysftp

although the problematic pip install of pysftp "suggested" that module was 
installed, to wit:

> Successfully built pysftp pynacl bcrypt
> Failed to build cryptography
> ERROR: Could not build wheels for cryptography which use PEP 517 and 
> cannot be installed directly
>
so I thought since it built the pysftp it would be available for this. 
Definitely a #DOG'sBREAKFAST.
Thanks for your help so far. 
Anyone else gone / going through this?
Thx/MP
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 

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

[Glenn McKechnie]

>> If you are running the owfs.py from my fork, the syslog message will
>> tell you what module it has opted to run under. That message occurs in
>> the first few log entries after weewx initializes. It's an INFO
>> message
>>
>
> So with python-ow installed I get this in the INFO:
>
> May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: service version is 0.23
> ( ow)
[...]

> With python-ow removed I get this:
>
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: service version is 0.23
> (pyownet)
[...]

> I have waited for a REC  to be generated and the 1wire sensor allocated to
> extraTemp5 is being reported OK, so it does look like it is working fine
> with either method.

That's good news. For you and me ;-)

> I think I was thrown off track when running direct failed, does that mean
> the broken _main_ section is not called when it is running from weewx ?

Correct.

It's a separate section quite distinct from the Driver/Service side.
It does need to be, and will be fixed as it's required to sort out the
system_map. Thankfully you knew yours already.
When it starts raining again, or we get locked up again :)  I'll get
back to it and see if inspiration strikes.

It borrows a few functions from the main script, but the rest of it is
fairly unique. Made more difficult at the moment as ow and pyownet
approach things in different ways.
Almost had it working on mine but I have a 1-wire hub which
complicates a simple directory walk with pyownet.


-- 


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/CAAraAzjCqdYpu5nC%3D%3DYo5qwWrcs11g8djVnvgHjsDyXDiQ-OuQ%40mail.gmail.com.

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

[Messy Potamia]

*I'm following this because one of my weewx stations rely heavily on OW 
sensors to augment the data from my Davis Vantage pro2. *
*I'd upgrade to weewx 4.x but really can't lose owfs operability*.
Thx/mp

On Tuesday, May 26, 2020 at 10:06:04 AM UTC+2, Gazza wrote:
>
>
> If you are running the owfs.py from my fork, the syslog message will 
>> tell you what module it has opted to run under. That message occurs in 
>> the first few log entries after weewx initializes. It's an INFO 
>> message 
>>
>
> So with python-ow installed I get this in the INFO:
>
> May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: service version is 0.23 
> (ow)
> May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: interface is localhost:
> 4304
>
> With python-ow removed I get this:
>
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: service version is 0.23 
> (pyownet)
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: interface is localhost:
> 4304
> May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: sensor map is {u
> 'extraTemp5': u'/uncached/28.E1044104/temperature'}
>
>
> I have waited for a REC  to be generated and the 1wire sensor allocated to 
> extraTemp5 is being reported OK, so it does look like it is working fine 
> with either method.
>
> I think I was thrown off track when running direct failed, does that mean 
> the broken _main_ section is not called when it is running from weewx ?
>
>
> 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/e7e9f9b7-4388-48d0-ac7d-776b91c59dd7%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B --//pysftp module won't load//

[Messy Potamia]

Messy Potamia  
9:53 AM (2 minutes ago)


to weewx-user 
And let me tell you there are still problems regarding python version,
setuptools version,; this is turning into a dog's breakfast. 
My pip isthe latest version I have ascertained. But cryptography won't 
install.
 
sudo pip -V
  pip 20.1.1 from /usr/local/lib/python2.7/dist-packages/pip (python 2.7
)ode here...

 --- but ---
Successfully built pysftp pynacl bcrypt
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot 
be installed directly
This is a PI3B (a02082) on Jessie lite.

On Tuesday, May 26, 2020 at 9:38:48 AM UTC+2, Messy Potamia wrote:
>
> Here's what I did to allow pysftp module to install via pip. I found this 
> on a RaspberryPi forum. You search on this problem and hits come from all 
> over the place with no solutions, until I found this:
>
> sudo apt-get install python-pip
> pip install --user -U setuptools
> sudo pip install --upgrade pip
> sudo apt-get install libffi-dev
> sudo pip install pysftp   #errors during pysftp install, "  Building wheel 
> for pynacl (PEP 517) ... \" still working...
>
> This is on my Pi3 running Jessie.
>
>
> On Tuesday, May 26, 2020 at 8:59:12 AM UTC+2, Messy Potamia wrote:
>>
>> Matt, I get the same result whether I invoke pip, pip2, pip3:
>> pi@RPI3:~ $ sudo pip2 install pysftp
>> Downloading/unpacking pysftp
>>   Downloading pysftp-0.2.9.tar.gz
>>   Running setup.py (path:/tmp/pip-build-QfuB69/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 also tried apt-get install and it can't find the pkg. 
>> The /root/.pip/pip.log is large 
>> -rw-r--r-- 1 root root 84870 May 26 08:48 pip.log
>> and I more'd it but couldn't see anything that made sense to me.
>> Any ideas? btw I did download the rest of the pkg from github including 
>> wget the generator, but probably shouldn't proceed until I can get pysftp 
>> on my Pi.
>> Thanks!
>> ---
>>
>>
>>
>>
>> On Monday, May 25, 2020 at 10:49:00 PM UTC+2, 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 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/0d5ed4d5-f9ec-47d5-b8d9-b74cba16caae%40googlegroups.com.

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

[Gazza]

> If you are running the owfs.py from my fork, the syslog message will 
> tell you what module it has opted to run under. That message occurs in 
> the first few log entries after weewx initializes. It's an INFO 
> message 
>

So with python-ow installed I get this in the INFO:

May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: service version is 0.23 (
ow)
May 26 17:43:02 GazPi4 weewx[1159] INFO user.owfs: interface is localhost:
4304

With python-ow removed I get this:

May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: service version is 0.23 (
pyownet)
May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: interface is localhost:
4304
May 26 17:50:52 GazPi4 weewx[1259] INFO user.owfs: sensor map is {u
'extraTemp5': u'/uncached/28.E1044104/temperature'}


I have waited for a REC  to be generated and the 1wire sensor allocated to 
extraTemp5 is being reported OK, so it does look like it is working fine 
with either method.

I think I was thrown off track when running direct failed, does that mean 
the broken _main_ section is not called when it is running from weewx ?


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/4a631711-fbe0-4a73-b815-298cafb9b980%40googlegroups.com.

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

[Ronald Berghammer]

I have a Outdoor and Indoor Sensor (temp/humidity) and a rain sensor.
Windsensor i don't have!

-- 
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/f1a43543-5635-41c1-8e8f-0769e09f6ff0%40googlegroups.com.

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

[Ronald Berghammer]

I use weewx v4.0 and yes i have make the Tutorial.
My Weatherstation: Netatmo

-- 
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/74367db1-568c-4a36-a057-829c827f1f5a%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B --//pysftp module won't load//

[Messy Potamia]

And let me tell you there are still problems regarding python version,
setuptools version,; this is turning into a dog's breakfast. My pip is
the latest version I have ascertained. But cryptography won't install.
 sudo pip -V
  pip 20.1.1 from /usr/local/lib/python2.7/dist-packages/pip (python 2.7)
 --- but ---
Successfully built pysftp pynacl bcrypt
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and
cannot be installed directly

--MP



On Tue, May 26, 2020 at 9:38 AM Messy Potamia  wrote:
>
> Here's what I did to allow pysftp module to install via pip. I found this on 
> a RaspberryPi forum. You search on this problem and hits come from all over 
> the place with no solutions, until I found this:
>
> sudo apt-get install python-pip
> pip install --user -U setuptools
> sudo pip install --upgrade pip
> sudo apt-get install libffi-dev
> sudo pip install pysftp   #errors during pysftp install, "  Building wheel 
> for pynacl (PEP 517) ... \" still working...
>
> This is on my Pi3 running Jessie.
>
>
> On Tuesday, May 26, 2020 at 8:59:12 AM UTC+2, Messy Potamia wrote:
>>
>> Matt, I get the same result whether I invoke pip, pip2, pip3:
>> pi@RPI3:~ $ sudo pip2 install pysftp
>> Downloading/unpacking pysftp
>>   Downloading pysftp-0.2.9.tar.gz
>>   Running setup.py (path:/tmp/pip-build-QfuB69/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 also tried apt-get install and it can't find the pkg.
>> The /root/.pip/pip.log is large
>> -rw-r--r-- 1 root root 84870 May 26 08:48 pip.log
>> and I more'd it but couldn't see anything that made sense to me.
>> Any ideas? btw I did download the rest of the pkg from github including wget 
>> the generator, but probably shouldn't proceed until I can get pysftp on my 
>> Pi.
>> Thanks!
>> ---
>>
>>
>>
>>
>> On Monday, May 25, 2020 at 10:49:00 PM UTC+2, 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/94d1c767-7972-4c5f-92ab-e69a349eab1e%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 

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B --//pysftp module won't load//

[Messy Potamia]

Here's what I did to allow pysftp module to install via pip. I found this 
on a RaspberryPi forum. You search on this problem and hits come from all 
over the place with no solutions, until I found this:

sudo apt-get install python-pip
pip install --user -U setuptools
sudo pip install --upgrade pip
sudo apt-get install libffi-dev
sudo pip install pysftp   #errors during pysftp install, "  Building wheel for 
pynacl (PEP 517) ... \" still working...

This is on my Pi3 running Jessie.


On Tuesday, May 26, 2020 at 8:59:12 AM UTC+2, Messy Potamia wrote:
>
> Matt, I get the same result whether I invoke pip, pip2, pip3:
> pi@RPI3:~ $ sudo pip2 install pysftp
> Downloading/unpacking pysftp
>   Downloading pysftp-0.2.9.tar.gz
>   Running setup.py (path:/tmp/pip-build-QfuB69/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 also tried apt-get install and it can't find the pkg. 
> The /root/.pip/pip.log is large 
> -rw-r--r-- 1 root root 84870 May 26 08:48 pip.log
> and I more'd it but couldn't see anything that made sense to me.
> Any ideas? btw I did download the rest of the pkg from github including 
> wget the generator, but probably shouldn't proceed until I can get pysftp 
> on my Pi.
> Thanks!
> ---
>
>
>
>
> On Monday, May 25, 2020 at 10:49:00 PM UTC+2, 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 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/94d1c767-7972-4c5f-92ab-e69a349eab1e%40googlegroups.com.

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

[Glenn McKechnie]

On 26/05/2020, Gazza  wrote:
> OK, I have done some more tests, first I have removed python-ow and now the
> owfs service in weewx is not working.

If you are running the owfs.py from my fork, the syslog message will
tell you what module it has opted to run under. That message occurs in
the first few log entries after weewx initializes. It's an INFO
message

This is from my current session, I'm running with (pyownet)
 INFO user.owfs-dallas: driver version is 0.23.6 (pyownet)

Have a look in the last log, before you removed python-ow and see
which one it picked up, it will be either (ow) or (pyownet).
Might as well have a look at what it's using after you deleted
python-ow (ie: now)  and see what it's running with..


to get pyownet installed, how was that done? Through pip?

A quick check to see if python can find them...

$ python2.7
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ow
>>> import pyownet
>>> import arflegarflegloop
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named arflegarflegloop
>>>

If the module isn't present it will throw the ImportError message above.



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

So far so good.

> 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

try running...
 owdir /28.E1044104
and you should get the tree for that sensor, of which temperature
should be included in it.

I'm assuming that  /28.E1044104 is your DS1820, in which case the
following is the command to reveal it's temperature reading...
 owget /28.E1044104/temperature


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

That doesn't surprise me.
I have a note on my fork that the _main_ section is broken if you are
using pyownet.
Mathews revision is a work in progress, as is mine. If memory serves
they can only pickup python-ow, not pyownet and the Sensor tree isn't
functioning , so yes. broken but a work in progress.
 (In my fork, owfs-dallas.py is further advanced - it works under
python3,, but I'm not suggesting to swap to that either.)


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

When you run weewx, take note of that INFO version message. Then we'll
know which module one to focus on.





-- 


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/CAAraAzgjTtuirS734zZvyefCjk20oCk-coTCvCHhbrOx%2B7dg-g%40mail.gmail.com.

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

[David Robinson]

Fixed. It was totally that typo. Thanks very much! I don't know how many 
times I looked at that and missed it.

All is well once more: https://oneeyedman.net/weather/

Cheers,

David

On Monday, 25 May 2020 23:10:02 UTC-7, David Robinson wrote:
>
> Hello Gary --
>
> Thanks for your response!
>
> I have attached the wee_debug output as requested.
>
> Cheers,
>
> David
>
>
>
>
> On Monday, 25 May 2020 22:09:54 UTC-7, gjr80 wrote:
>>
>> 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/8961693a-539f-4240-bbf1-0f6b10b8bc4f%40googlegroups.com.

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

[John Smith]

Can you tell me what weather station you are using?

My guess is your station isn't spitting out as many variables as other 
stations.


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/bdc00776-11e9-4887-a109-3e6c77910f14%40googlegroups.com.

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

[gjr80]

Thanks David, and there is your problem, your longitude is invalid:

longitude = -222.355811

Longitude should be between -180 and 180. Perhaps you meant -122.3811 ?

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/51e7c1dd-4856-4d8d-838d-4038e7ed064b%40googlegroups.com.

Re: [weewx-user] Re: sftp on 3.9.2, RPI3B --//pysftp module won't load//

[Messy Potamia]

Matt, I get the same result whether I invoke pip, pip2, pip3:
pi@RPI3:~ $ sudo pip2 install pysftp
Downloading/unpacking pysftp
  Downloading pysftp-0.2.9.tar.gz
  Running setup.py (path:/tmp/pip-build-QfuB69/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 also tried apt-get install and it can't find the pkg. 
The /root/.pip/pip.log is large 
-rw-r--r-- 1 root root 84870 May 26 08:48 pip.log
and I more'd it but couldn't see anything that made sense to me.
Any ideas? btw I did download the rest of the pkg from github including 
wget the generator, but probably shouldn't proceed until I can get pysftp 
on my Pi.
Thanks!
---




On Monday, May 25, 2020 at 10:49:00 PM UTC+2, 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 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/035de97e-8904-4987-a1a7-0ce9259e57d5%40googlegroups.com.

[weewx-user] Lacrosse CA80550 Weather Station and Weewx

[Harry P]

Do I have any chance of having Weewx work with my Lacrosse CA80550 
Weatherstation?
Really new to this so  I hope I don't annoy anyone.  Thank You

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6c265fe5-37c6-4f06-8d54-034452ca1342%40googlegroups.com.

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

[David Robinson]

Hello Gary --

Thanks for your response!

I have attached the wee_debug output as requested.

Cheers,

David




On Monday, 25 May 2020 22:09:54 UTC-7, gjr80 wrote:
>
> 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/883433f7-faf5-4572-a0f0-ebc0a5335c5b%40googlegroups.com.
pi@poley:/etc/weewx $ sudo wee_debug --info weewx.conf --verbosity=2 
Using verbosity=2, displaying all info

wee_debug output will be sent to stdout(console)

Using configuration file weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'

System info
  Platform:   Linux-4.19.97-v7+-armv7l-with-debian-10.4
  Python Version: 2.7.16

Environment
  LANG=en_US.UTF-8
  NO_AT_BRIDGE=1
  TERM=xterm-256color
  SHELL=/bin/bash
  LANGUAGE=en_US.UTF-8
  MAIL=/var/mail/root
  SUDO_UID=1000
  SUDO_GID=1000
  SUDO_COMMAND=/usr/bin/wee_debug --info weewx.conf --verbosity=2
  LOGNAME=root
  USER=root
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  LC_ALL=en_US.UTF-8
  SUDO_USER=pi
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  HOME=/root

Load Information
  1 minute load average:  0.22
  5 minute load average:  0.13
  15 minute load average: 0.06

General Weewx info
  Weewx version 3.9.2 detected.

Station info
  Station type: SDR
  Driver:   user.sdr

Driver info
[SDR]

# This section is for the software-defined radio driver.

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# Direct testing command:
# PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
--cmd="rtl_433 -M utc -F json -f 91498 -s 25"
# Command probably needs a -p frequency offset parameter.

# The driver to use
driver = user.sdr
path = /usr/share/weewx/user/
# ld_library_path = /usr/local/include
cmd = rtl_433 -M utc -F json -R 78 -f 91498 -s 25
[[sensor_map]]
outTemp = temperature.16.FOWH65BAltPacket
outHumidity = humidity.16.FOWH65BAltPacket
windDir = wind_dir.16.FOWH65BAltPacket
windSpeed = wind_speed.16.FOWH65BAltPacket
windGust = wind_gust.16.FOWH65BAltPacket
rain_total = rain_total.16.FOWH65BAltPacket
UV = uv_index.16.FOWH65BAltPacket
# uv = uv.16.FOWH65BAltPacket # Not displaying in web page
# light = light.16.FOWH65BAltPacket # Not displaying in web page
outTempBatteryStatus = battery.16.FOWH65BAltPacket
[[deltas]]
rain = rain_total

Currently installed extensions
Extension NameVersion   Description
sdr   0.77  Capture data from rtl_433

Archive info
  Database name:weewx.sdb
  Table name:   archive
  Version   2.0
  Unit system:  1 (US)
  First good timestamp: 2020-04-26 18:10:00 PDT (1587949800)
  Last good timestamp:  2020-05-25 22:45:00 PDT (1590471900)
  Number of records:8176
  weewx (weewx.conf) is set