Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-06-06 Thread Jever Hägen
Hello,

Please apologize my asking if you are on the way updating wh23xx, your last 
note 
about that was a month ago?
If you need information or testing on wh23xx don't hesitate to ask.


Greetings and best wishes
Jürgen

Am Sonntag, 3. Mai 2020, 05:21:54 CEST schrieb mwall:


On Saturday, May 2, 2020 at 2:27:49 PM UTC-4, mwall wrote:
On Saturday, May 2, 2020 at 10:01:39 AM UTC-4, Tom Keffer wrote:
The weewx usage map[1] shows 26 installations (out of 1471 registered 
stations), or 
less than 2%. That's not enough usage to justify the work. Get your friends to 
use it!


Still, I'll see what I can do...




tom,


i'll take care of it - its one of my drivers.  but its over 50F for the first 
time in weeks, 
so it will have to wait until after sunset US eastern time :)


sorry to reply to myself, but a little update: the certs expired on the vpn on 
which 
my wh23xx is running, so i won't be able to test with the hardware until i get 
on 
site.  luckily that *should* be tuesday, not months from now.


-- 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[2].To view this 
discussion on the web visit https://groups.google.com/d/msgid/weewx-user/
87200d54-73e6-450a-9e61-7099e36a5856%40googlegroups.com[3].




[1] http://weewx.com/stations.html
[2] mailto:weewx-user+unsubscr...@googlegroups.com
[3] https://groups.google.com/d/msgid/weewx-user/
87200d54-73e6-450a-9e61-7099e36a5856%40googlegroups.com?
utm_medium=email_source=footer

-- 
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/22736624.dAJXXpjYeQ%40laptop-jl.


Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-03 Thread Jever Hägen
Hello Mathew,

that are very good news. Thanks in advance.

Am Samstag, 2. Mai 2020 20:27:49 UTC+2 schrieb mwall:
>
> On Saturday, May 2, 2020 at 10:01:39 AM UTC-4, Tom Keffer wrote:
>>
>> The weewx usage map  shows 26 
>> installations (out of 1471 registered stations), or less than 2%. That's 
>> not enough usage to justify the work. Get your friends to use it!
>>
>> Still, I'll see what I can do...
>>
>>>
>>>
> tom,
>
> i'll take care of it - its one of my drivers.  but its over 50F for the 
> first time in weeks, so it will have to wait until after sunset US eastern 
> time :)
>
> 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/52551b6f-dea1-46e5-85cc-10fff75a9cef%40googlegroups.com.


Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Jever Hägen
Thanks for thinking about of doing that work.

yes, there are not very much wh23xx stations registered beside mine.
But overall they are on rank 9 ;-)
1 Vantage 537 
2 FineOffsetUSB 274 
3 AcuRite 147 
4 Interceptor 87 
5 TE923 67 
6 WMR100 40 
7 SDR 33 
8 WMR200 29 
*9* *WH23xx* *26* 
10 WS23xx 24 
11 WS28xx 24 
12 netatmo 17 
13 Ultimeter 15 
14 WeatherFlowUDP 14 
15 WMR300 14 
16 FileParse 11 
17 Simulator 11 

Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:
>
> The weewx usage map <http://weewx.com/stations.html> shows 26 
> installations (out of 1471 registered stations), or less than 2%. That's 
> not enough usage to justify the work. Get your friends to use it!
>
> Still, I'll see what I can do...
>
> -tk
>
> On Sat, May 2, 2020 at 5:30 AM Jever Hägen  > wrote:
>
>> Hi Tom,
>>
>> yes I know, but wouldn't it be possible for you or some of the guys out 
>> there to integrate the driver into weewx v4?
>>
>> Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>>>
>>> It looks like the wh23xx driver has not been ported to Python 3 and 
>>> weewx V4 (it's not actually part of weewx).
>>>
>>> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин  wrote:
>>>
>>>> I had the same problem today, when weewx updated to 4. The station is 
>>>> WH2310. I made a little analyze of problem and found that import of 
>>>> log_traceback in the ws23xx driver no more valid, because of changings in 
>>>> weewx.
>>>> Try to replace
>>>> the string in the file wh23xx.py: 
>>>> from weeutil.weeutil import timestamp_to_string, log_traceback
>>>>
>>>> to:
>>>> from weeutil.weeutil import timestamp_to_string
>>>> from weeutil.log log_traceback
>>>>
>>>> This is solved my problem. 
>>>> I made pull request to the sources of this driver, hope that it will be 
>>>> accepted.
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to weewx...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%40googlegroups.com.


Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Jever Hägen
Hi Tom,

yes I know, but wouldn't it be possible for you or some of the guys out 
there to integrate the driver into weewx v4?

Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>
> It looks like the wh23xx driver has not been ported to Python 3 and weewx 
> V4 (it's not actually part of weewx).
>
> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин  > wrote:
>
>> I had the same problem today, when weewx updated to 4. The station is 
>> WH2310. I made a little analyze of problem and found that import of 
>> log_traceback in the ws23xx driver no more valid, because of changings in 
>> weewx.
>> Try to replace
>> the string in the file wh23xx.py: 
>> from weeutil.weeutil import timestamp_to_string, log_traceback
>>
>> to:
>> from weeutil.weeutil import timestamp_to_string
>> from weeutil.log log_traceback
>>
>> This is solved my problem. 
>> I made pull request to the sources of this driver, hope that it will be 
>> accepted.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%40googlegroups.com.


[weewx-user] weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-01 Thread Jever Hägen
Hi out there.

The machine is a wandboard-quad running pure Debian9 connected over USB 
with a froggit WH4000 station. 
It saves all weather data into a mariadb on a central server, transfers all 
the webdata to a website via sFTP and gives data to several services, also 
saves the logdata with rsyslog to the central server..

After upgrading weewx didn't start up again.
I figured out, that the import of 'log_traceback' in the driver written by 
Mathew Wall is the reason.
"https://github.com/matthewwall/weewx-wh23xx;
I was very pleased to have that code available, thx to Mathew.

As I'm not handy with python, I ask her for getting help with getting the 
looging content being reduced again.

May  1 12:42:07 wandboard-quad systemd[1]: Reloading.
May  1 12:42:07 wandboard-quad systemd[1]: Starting LSB: weewx weather 
system...
May  1 12:42:08 wandboard-quad weewx[12910] INFO __main__: Initializing 
weewx version 4.0.0
May  1 12:42:08 wandboard-quad weewx[12910] INFO __main__: Using Python 
2.7.13 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
May  1 12:42:08 wandboard-quad weewx[12910] INFO __main__: Platform 
Linux-4.9.0-12-armmp-armv7l-with-debian-9.12
May  1 12:42:08 wandboard-quad weewx[12910] INFO __main__: Locale is 
'de_DE.UTF-8'
May  1 12:42:08 wandboard-quad weewx[12910] INFO __main__: PID file is 
/var/run/weewx.pid
May  1 12:42:08 wandboard-quad weewx[12899]: Starting weewx weather system: 
weewx.
May  1 12:42:08 wandboard-quad systemd[1]: Started LSB: weewx weather 
system.
May  1 12:42:08 wandboard-quad weewx[12914] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf
May  1 12:42:08 wandboard-quad weewx[12914] INFO weewx.engine: Loading 
station type WH23xx (user.wh23xx)
May  1 12:42:08 wandboard-quad weewx[12914] CRITICAL __main__: Caught 
unrecoverable exception:
May  1 12:42:08 wandboard-quad weewx[12914] CRITICAL __main__:   
cannot import name log_traceback
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__:   
Traceback (most recent call last):
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
File "/usr/share/weewx/weewxd", line 148, in main
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
  engine = weewx.engine.StdEngine(config_dict)
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 69, in __init__
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
  self.setupStation(config_dict)
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 92, in setupStation
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
  __import__(driver)
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
File "/usr/share/weewx/user/wh23xx.py", line 255, in 
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__: 
  from weeutil.weeutil import timestamp_to_string, log_traceback
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__:   
ImportError: cannot import name log_traceback
May  1 12:42:09 wandboard-quad weewx[12914] CRITICAL __main__:   
Exiting.
May  1 12:42:09 wandboard-quad systemd[1]: Reloading.


So I changed the code as you can see below and it works again.
But now the syslog is flooded with useless content


--- wh23xx.py   2017-01-29 18:22:30.0 +0100
+++ /usr/share/weewx/user/wh23xx.py 2020-05-01 14:50:38.367750070 +0200
@@ -252,7 +252,8 @@
 import usb

 import weewx.drivers
-from weeutil.weeutil import timestamp_to_string, log_traceback
+from weeutil.weeutil import timestamp_to_string
+from weeutil.logger import log_traceback
 from weewx.wxformulas import calculate_rain

 DRIVER_NAME = 'WH23xx'
@@ -425,7 +426,7 @@
 yield packet
 except IndexError, e:
 logerr("decode failed: %s (%s)" % (e, _fmt(raw)))
-log_traceback(loglevel=syslog.LOG_DEBUG)
+log_traceback(loglevel=syslog.LOG_INFO)
 time.sleep(self._poll_interval)

 def _get_current(self):



Content of the logfile: 

May  1 17:38:43 wandboard-quad weewxd: wh23xx: read_record: write: 02 02 04 
04 (len=4)
May  1 17:38:43 wandboard-quad weewxd: wh23xx: read_record: buf: 01 3b 04 
4a 01 02 7c 02 02 28 03 01 b2 04 02 28 05 02 28 06 2c 07 2d 08 26 74 09 26 
91 0a 00 2d 0b 00 0e 0c 00 18 0e 00 00 00 00 10 00 00 00 03 11 00 00 00 8a 
12 00 00 00 03 13 00 00 (len=61)
May  1 17:38:43 wandboard-quad weewxd: wh23xx: read_record: record_size: 74
May  1 17:38:43 wandboard-quad weewxd: wh23xx: read_record: buf: 01 12 09 
33 14 00 00 43 95 15 00 01 78 4a 16 02 1c 17 02 79 2c 07 2d 08 26 74 09 26 
91 0a 00 2d 0b 00 0e 0c 00 18 0e 00 00 00 00 10 00 00 00 03 11 00 00 00 8a 
12 00 00 00 03 13 00 00 (len=61)
May  1 17:38:43 wandboard-quad weewxd: wh23xx: read_record: rbuf: 01 02 7c 
02 02 28