from:"Ralph Underwood"

[weewx-development] MQTTSubscribe with WeeWX 4.0.0.b8

2020-01-14 Thread Ralph Underwood

I have been working on getting *MQTTSubscribe* working on my development 
station (RPi3 with Buster) running WeeWx 4.0.0.b8. I think I have managed 
to get Python3 versions of all of the prerequisites for WeeWx and 
MQTTSubscribe. I am using the Simulator as the driver, MQTTSubscribe as a 
service.


Thanks for any help!
Ralph


*I'm getting a lot of messages - these standout to me:*
Jan 14 15:29:19 TestPi weewx[5118] DEBUG user.MQTTSubscribe: 
MessageCallbackProvider For weather has QOS of 0 and retain of 0 received: 
b'TIME:0,soilTemp3:14.68,INHU:40.00'
Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe: 
MessageCallbackProvider on_message_keyword failed with: must be str or 
None, not list
Jan 14 15:29:19 TestPi weewx[5118] ERROR user.MQTTSubscribe:  
MessageCallbackProvider Ignoring topic=weather and 
payload=b'TIME:0,soilTemp3:14.68,INHU:40.00'


*This is log after a WeeWx restart:*
Jan 14 15:39:39 TestPi systemd[1]: Starting LSB: weewx weather system...
Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Initializing weewx 
version 4.0.0b8
Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Using Python 3.7.3 
(default, Apr  3 2019, 05:39:12) #012[GCC 8.2.0]
Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Platform 
Linux-4.19.75-v7+-armv7l-with-debian-10.1
Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: Locale is 
'en_US.UTF-8'
Jan 14 15:39:39 TestPi weewx[5252] INFO weewx.engine: PID file is 
/var/run/weewx.pid
Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Using configuration 
file /home/weewx/weewx.conf
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Debug is 1
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Initializing engine
Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: Loading station type 
Simulator (weewx.drivers.simulator)
Jan 14 15:39:40 TestPi weewx[5241]: Starting weewx weather system: weewx.
Jan 14 15:39:40 TestPi systemd[1]: Started LSB: weewx weather system.
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
user.MQTTSubscribe.MQTTSubscribeService
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Service binding 
is loop
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Overlap is 0.0
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: TopicManager 
config is {'unit_system': 'US', 'overlap': 0.0, 'weather': {}}
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message 
callback config is {'type': 'keyword', 'keyword_delimiter': [], 
'keyword_separator': ':', 'label_map': {'soilTemp3': 'soilTemp3', 
'soilTemp2': 'soilTemp2', 'tempSoil1': 'soilTemp1'}}
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message 
callback provider is user.MQTTSubscribe.MessageCallbackProvider
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Client id is 
MQTTSubscribe-7942
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Clean session 
is True
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: MQTTSubscribe 
version is 1.4.0
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Host is 
192.168.7.37
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Port is 1883
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Keep alive is 60
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Username is None
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Password is not 
set
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Archive topic 
is None
Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Starting loop
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading 
service user.MQTTSubscribe.MQTTSubscribeService
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Jan 14 15:39:40 TestPi weewx[5256] INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Jan 14 15:39:40 TestPi weewx[5256] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Connected with 
result code 0
Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Connected 
flags {'session present': 0}
Jan 14 15:39:40 TestPi weewx[5256] DEBUG user.MQTTSubscribe: Subscribe to 
weather has a mid 1 and rc 0
Jan 14

Re: [weewx-development] MQTTSubscribe.py installing as service

2020-01-14 Thread Ralph Underwood

I am using WeeWx 4.0.0.b8 (latest development version) and I copied 
MQTTSubscribe from your GitHub.  I did not install via wee_extension. 

My plan was to replace my standalone python program which subscribes to 
MQTT and writes a file for the filepile.py extension. I converted it to 
Python3 so with WeeWx 4 I will be all Python3. That has worked fine on one 
of my stations, however my program does not have a queue and only handles 
one MQTT message and I want to add more MQTT sensors to the stations. I 
have a separate development station that I am working with to get 
MQTTSubscribe working. I am going to start over with a clean installation 
and use wee-extension to install MQTTSubscribe. 

It's snowing here in Seattle, so I should have some time to experiment.

I will start a new thread to report success or ask for help - I didn't 
notice that there were 5 pages on this thread before I asked about running 
as a service.

On Tuesday, January 14, 2020 at 12:02:43 PM UTC-8, Rich Bell wrote:
>
> Ralph,
> What version of WeeWX and MQTTSubscribe? Did you install via 
> wee_extension? If you post a copy of your config (making sure to remove any 
> sensitive information), I’d be happy to take a look.
> We should probably move this out of the wxMesh thread...
> Rich
>
>
>

-- 
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/70eea334-56d2-4a26-a102-5170bb26988f%40googlegroups.com.

Re: [weewx-development] MQTTSubscribe.py installing as service

2020-01-14 Thread Ralph Underwood

I was replying to a post on an earlier page. I just found Rich's 
MQTTSubscribe.py and have started to experiment with it as a service.

I managed to get to this:

Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Caught 
unrecoverable exception:
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:   Empty 
module name
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 897, in main
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:  
 engine = StdEngine(config_dict)
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 83, in __init__
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:  
 self.loadServices(config_dict)
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 144, in loadServices
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:   obj 
= weeutil.weeutil.get_object(svc)(self,config_dict)
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: File 
"/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:   mod 
= __import__(module)
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:  
 ValueError: Empty module name
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine:   Exiting.

Sleuthing begins.

-- 
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/0f790eb9-5cea-4056-8614-bb3340238b14%40googlegroups.com.

Re: [weewx-development] Re: continuation of discussion on wxMesh MQTT

2020-01-14 Thread Ralph Underwood

I am setting up a test station with WeeWx version 4 on a Rpi. I have three 
sensors publishing MQTT and I want to test the wxMesh driver. Can this be 
run as a service with the Simulator driver running?

Thanks, Ralph



-- 
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/37afe49a-5f05-4fd9-a542-d92bc1e488d1%40googlegroups.com.

Re: [weewx-development] Crash with 4.0.0b6

2020-01-08 Thread Ralph Underwood

Everything ran fine all night. My guess is that this was a timing issue, 
where I started the sensor at the same time my python subscription program 
was running and somehow managed to write an incomplete file for filepile. I 
overwrite the file each time so I can't go back and see what actually 
happened. 

In other news, WeeWx 4.0.0b6 appears to be very stable. I have the mem skin 
working and it is drawing nice flat lines. With the 3.? version and 'old' 
Ultimeter driver I was seeing a slow but steady increase in memory use 
until it would crash. I was also using cmom on the 3.? version, so that may 
have been a factor in the memory problem.

I have a station running in my basement lab in Seattle that I plan on 
converting to the mqtt service instead of my standalone python subscription 
program and filepile.   

Thanks.

On Wednesday, January 8, 2020 at 4:49:15 AM UTC-8, Tom Keffer wrote:
>
> One of the strings in the file that filepile is reading cannot be 
> converted to a number. It probably looks something like
>
> outTemp =
>
> or possibly
>
> outTemp = ""
>
> This is probably a bug in filepile. It should accept either of these, 
> returning None for the value. Fixed in commit 3863f21 
> <https://github.com/tkeffer/filepile/commit/3863f2141e3b2f9d239d5f459a634d2bd12adf7b>
> .
>
> Thanks for your detailed report!
>
> -tk
>
>
> On Tue, Jan 7, 2020 at 9:15 PM Ralph Underwood  > wrote:
>
>> My system crashed this afternoon.  This is the log starting with the last 
>> successful Ftp.  I had been working on my MQTT sensor code, adding some 
>> delay to cut down on the file writes to the SD card. 
>>
>> My setup is an RPi 4 with an Ultimeter Station and an additional BME280 
>> sensor connected to a Huzzah ESP8266 that publishes an MQTT payload. I have 
>> a little Python3 program that subscribes to the MQTT and writes a file for 
>> the file pile service. This basic set up has been working for several days, 
>> until I restarted the MQTT based sensor, the MQTT messages are being 
>> published OK and all looked good. I thought I heard rain and looked to my 
>> web site and the time was 15:45 on the site, real time was about 19:00.
>>
>> So my question is - did I uncover a bug or did I screw something up.  
>>
>> Jan  7 15:45:26 JV-Wx weewx[24318] INFO weewx.reportengine: ftpgenerator: 
>> Ftp'd 24 files in 9.25 seconds
>> Jan  7 15:45:26 JV-Wx weewx[24318] DEBUG weewx.reportengine: 
>> reportengine: Report 'RSYNC' not enabled. Skipping.
>> Jan  7 15:50:15 JV-Wx weewx[24318] INFO weewx.engine: Main loop exiting. 
>> Shutting engine down.
>> Jan  7 15:50:15 JV-Wx weewx[24318] INFO weewx.engine: Shutting down 
>> StdReport thread
>> Jan  7 15:50:15 JV-Wx weewx[24318] DEBUG weewx.engine: StdReport thread 
>> has been terminated
>> Jan  7 15:50:15 JV-Wx weewx[24318] DEBUG weewx.drivers.ultimeter: Close 
>> serial port /dev/ttyUSB0
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: Caught 
>> unrecoverable exception:
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   could 
>> not convert string to float: 
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  Traceback (most recent call last):
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/weewx/engine.py", line 201, in run
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/weewx/engine.py", line 230, in dispatchEvent
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  callback(event)
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/weewx/engine.py", line 582, in check_loop
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  raise BreakLoop
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  weewx.engine.BreakLoop
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  During handling of the above exception, another exception occurred:
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
>>  Traceback (most recent call last):
>> Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/weewx/eng

[weewx-development] Re: Crash with 4.0.0b6

2020-01-07 Thread Ralph Underwood

WeeWx has been running fine since I restarted it at 19:40.


-- 
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/74e626c2-8081-4ee2-8866-9062318f3c21%40googlegroups.com.

[weewx-development] Crash with 4.0.0b6

2020-01-07 Thread Ralph Underwood

My system crashed this afternoon.  This is the log starting with the last 
successful Ftp.  I had been working on my MQTT sensor code, adding some 
delay to cut down on the file writes to the SD card. 

My setup is an RPi 4 with an Ultimeter Station and an additional BME280 
sensor connected to a Huzzah ESP8266 that publishes an MQTT payload. I have 
a little Python3 program that subscribes to the MQTT and writes a file for 
the file pile service. This basic set up has been working for several days, 
until I restarted the MQTT based sensor, the MQTT messages are being 
published OK and all looked good. I thought I heard rain and looked to my 
web site and the time was 15:45 on the site, real time was about 19:00.

So my question is - did I uncover a bug or did I screw something up.  

Jan  7 15:45:26 JV-Wx weewx[24318] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 24 files in 9.25 seconds
Jan  7 15:45:26 JV-Wx weewx[24318] DEBUG weewx.reportengine: reportengine: 
Report 'RSYNC' not enabled. Skipping.
Jan  7 15:50:15 JV-Wx weewx[24318] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jan  7 15:50:15 JV-Wx weewx[24318] INFO weewx.engine: Shutting down 
StdReport thread
Jan  7 15:50:15 JV-Wx weewx[24318] DEBUG weewx.engine: StdReport thread has 
been terminated
Jan  7 15:50:15 JV-Wx weewx[24318] DEBUG weewx.drivers.ultimeter: Close 
serial port /dev/ttyUSB0
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: Caught 
unrecoverable exception:
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   could 
not convert string to float: 
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 201, in run
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 230, in dispatchEvent
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 callback(event)
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 582, in check_loop
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 raise BreakLoop
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 weewx.engine.BreakLoop
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   During 
handling of the above exception, another exception occurred:
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 598, in post_loop
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 self._catchup(self.engine.console.genArchiveRecords)
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 639, in _catchup
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   for 
record in generator(lastgood_ts):
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/drivers/__init__.py", line 30, in genArchiveRecords
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 raise NotImplementedError("Method 'genArchiveRecords' not implemented")
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 NotImplementedError: Method 'genArchiveRecords' not implemented
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   During 
handling of the above exception, another exception occurred:
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:   
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 903, in main
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 engine.run()
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 208, in run
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line 230, in dispatchEvent
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine:  
 callback(event)
Jan  7 15:50:16 JV-Wx weewx[24318] CRITICAL weewx.engine: File 
"/home/weewx/bin/weewx/engine.py", line

Re: [weewx-development] Re: WeeWX Version 4, beta 6

2019-12-31 Thread Ralph Underwood

It was relatively painless to convert/upgrade my python code to 3.7.  A few 
stumbles as the great internet  has many wrong examples and "solutions". 
For instance trying to install pyehem - what worked is *sudo pip3 install 
ephem* 

Same kind of issues with install the mosquitto and paho client - being sure 
that the solutions are valid for python 3

(google sure does like to "fix" spelling)

I think that there will be a lot of work to update the docs and wiki for 
version 4 - probably can't get it done this year :)

happy New Year.



On Tuesday, December 31, 2019 at 3:13:59 PM UTC-8, Tom Keffer wrote:
>
> Come on, Python 2.6 is over 11 years old, and hasn't been supported for 
> well over 6 years! Time to upgrade! 
>
> If you're running Python 3, WeeWX requires Python v3.5 or greater. 
> Versions before that do not support % formatting of bytes and bytearrays.
>
> Not sure what the problem is. Are you two using an old version of 
> configobj? That could do it. Try
>
> *python -c "import configobj; print(configobj.__version__)"*
>
>
> -tk
>
> On Tue, Dec 31, 2019 at 11:42 AM Vince Skahan  > wrote:
>
>> On Monday, December 30, 2019 at 1:28:50 PM UTC-8, Tom Keffer wrote:
>>>
>>> ... is up. In the usual spot. 
>>> http://weewx.com/downloads/development_versions/
>>>
>>>
>> Does b6 have a minimum python version ?
>>
>> Rolled the dice and tried an upgrade of my ancient Seagate Dockstar 3.9.0 
>> to beta-6.  Fail on startup.
>>
>> Python is 2.7.3,  debian version is 7.6
>> I'd have to compile my own python pieces from source to get a current 
>> version if you wanted me to try that.
>> Same goes for trying to get to python3.  Nothing newer than 3.2.3 
>> available precompiled for this box.
>>
>> root@debian:/home/src/weewx-4.0.0b6# service weewx start
>> [] Starting weewx weather system: weewxTraceback (most recent call 
>> last):
>>   File "/home/weewx/bin/weewxd", line 16, in 
>> import weewx.engine
>>   File "/home/weewx/bin/weewx/engine.py", line 30, in 
>> import weewx.accum
>>   File "/home/weewx/bin/weewx/accum.py", line 95, in 
>> defaults_dict = configobj.ConfigObj(StringIO(DEFAULTS_INI), 
>> encoding='utf-8')
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1230, in 
>> __init__
>> self._load(infile, configspec)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1290, in 
>> _load
>> infile = self._handle_bom(infile)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1430, in 
>> _handle_bom
>> if not line.startswith(BOM):
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: 
>> ordinal not in range(128)
>>  failed!
>>
>>  
>>
>> -- 
>> 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/c71931fd-e57d-4f7d-94ec-60648a934f98%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/a7445948-6163-47d6-ad1b-5ec25e46e27b%40googlegroups.com.

[weewx-development] Re: WeeWX Version 4, beta 6

2019-12-31 Thread Ralph Underwood

Slam and dunk! One station now on 4.0.0b6.  

The script I was referring to is the "weewx flexible installer script for 
Debian(ish) systems". 

Using the six steps was easy once I remembered to add the -xf to tar.

BTW - under the 3.? versions I was having seemingly random crashes (7 to 14 
days between) that I suspect were caused by running out of memory. I was 
wondering if the Ultimeter driver was causing a memory leak. I also am not 
using cmon with version 4, so this may be why things are more "stable". 
 Again, knowing just enough unix & python to be dangerous, it's beyond me 
to figure that one out.

Thanks, Ralph

-- 
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/f3ec6610-0bda-43dd-a01c-55ffe9949d1d%40googlegroups.com.

[weewx-development] Re: WeeWX Version 4, beta 6

2019-12-31 Thread Ralph Underwood

I'm running fine with 4.0.0b5 and the newest version of 
the Ultimeter driver on two different RPi4 stations. Knowing just enough 
unix & python to be dangerous, I thought maybe I should clarify a few 
things before using Vince's script to update to beta 6. 

I have extra sensors that use mqtt. I have a Python 3.7 program 
that subscribes to mqtt and writes a file for the filepile service. On one 
station this is working great, on the other I am not getting my mqtt 
publications (same code except for broker IP address) so I have 
some sleuthing to do on that station. The rest of the station is working 
fine - so it's not a WeeWx problem.

My python mqtt program and filepile.py are in /home/weewx/bin/user. And all 
of my other changes to WeeWx are in the Seasons directory. 

So is my understanding that these will be "safe" during the upgrade 
correct? Will I have to re-install the filepile changes to the weewx.conf?

Thanks
Ralph




-- 
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/af435800-3cc3-4e2a-916f-13168a3c62f4%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-16 Thread Ralph Underwood

I found most of those items, but I was still getting a bunch of errors. My 
system running 3.?? died a few days ago and my backups were not good so I 
was installing the version 4 as a replacement - consequently I had less 
that 24 hours data on the system I mistakenly installed cmon on.

I am interested in cmon because I want to track down why my "old" system 
was periodically crashing - I was suspecting a memory leak. The memory in 
use would just creep up, seemed to crash 

I just made a clean installation using a newly imaged card and Vince's 
script. Copied over the latest ultimeter driver and I am up and running.

I still have to get my MQTT stuff working again - I stumbled upon how to 
get the python 3 version of paho.mqtt installed yesterday, but didn't make 
good notes.

Thanks again to Tom, Vince and Gary!




-- 
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/c5f6e1cb-4934-4ae3-b62c-aab93668bd07%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-16 Thread Ralph Underwood

I commented out various cmon stuff in weewx.conf and have whew running 
again.

Thanks,
Ralph


On Monday, December 16, 2019 at 1:29:23 PM UTC-8, Ralph Underwood wrote:
>
> OK. I tried doing a wee-extension uninstall with no success.  Any hints on 
> how/where  to remove it?  May be simpler to just start with another install 
> of WeeWx. 
>
>
> I did manage to update my program that reads the mqtt data and write to 
> file pile.txt without those 'b's.
>
>
>
>
> On Monday, December 16, 2019 at 1:19:10 PM UTC-8, Tom Keffer wrote:
>>
>> cmon has not been ported to Python 3.
>>
>> On Mon, Dec 16, 2019 at 2:17 PM Ralph Underwood  wrote:
>>
>>> I tried to install the cmon extension with the version 4 and got this 
>>> error.  
>>>
>>> I had just restarted my tail of the log so I hope this is enough.
>>>
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>>  obj = weeutil.weeutil.get_object(svc)(self,config_dict)
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>>  File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>>  mod = __import__(module)
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>>  File "/home/weewx/bin/user/cmon.py", line 331
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>>  except (ValueError, IOError, KeyError), e:
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>>  ^
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>>  SyntaxError: invalid syntax
>>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>>  Exiting.
>>> Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Main process exited, 
>>> code=exited, status=1/FAILURE
>>> Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>>
>>> -- 
>>> 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/67b362a4-7cc3-417f-8c98-6894e5149706%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-development/67b362a4-7cc3-417f-8c98-6894e5149706%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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/b19a56a0-cb62-476e-9e68-2c7657b5d7f6%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-16 Thread Ralph Underwood

OK. I tried doing a wee-extension uninstall with no success.  Any hints on 
how/where  to remove it?  May be simpler to just start with another install 
of WeeWx. 


I did manage to update my program that reads the mqtt data and write to 
file pile.txt without those 'b's.




On Monday, December 16, 2019 at 1:19:10 PM UTC-8, Tom Keffer wrote:
>
> cmon has not been ported to Python 3.
>
> On Mon, Dec 16, 2019 at 2:17 PM Ralph Underwood  > wrote:
>
>> I tried to install the cmon extension with the version 4 and got this 
>> error.  
>>
>> I had just restarted my tail of the log so I hope this is enough.
>>
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>  obj = weeutil.weeutil.get_object(svc)(self,config_dict)
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>  mod = __import__(module)
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>  File "/home/weewx/bin/user/cmon.py", line 331
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>  except (ValueError, IOError, KeyError), e:
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:    
>>  ^
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>  SyntaxError: invalid syntax
>> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
>>  Exiting.
>> Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Main process exited, 
>> code=exited, status=1/FAILURE
>> Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>>
>> -- 
>> 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/67b362a4-7cc3-417f-8c98-6894e5149706%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-development/67b362a4-7cc3-417f-8c98-6894e5149706%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/556b5e20-e66f-4edb-b432-acc49d91108d%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-16 Thread Ralph Underwood

I tried to install the cmon extension with the version 4 and got this 
error.  

I had just restarted my tail of the log so I hope this is enough.

Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:   obj 
= weeutil.weeutil.get_object(svc)(self,config_dict)
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine: File 
"/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:   mod 
= __import__(module)
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine: File 
"/home/weewx/bin/user/cmon.py", line 331
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
 except (ValueError, IOError, KeyError), e:
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
   ^
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:  
 SyntaxError: invalid syntax
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine:   Exiting.
Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Dec 16 13:02:16 JV-Wx systemd[1]: weewx.service: Failed with result 
'exit-code'.

-- 
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/67b362a4-7cc3-417f-8c98-6894e5149706%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-14 Thread Ralph Underwood

Thanks Tom.  WeeWx appears to be running - I'm getting output  to 
home/weewx/public_html/index.html 
.

Now to tackle the damn 'b's, should keep me busy for a few hours.

I plan on waiting a bit before adding cmom, I have been having trouble with 
the old system stopping, I suspect because of  a memory leak with either 
cmom or the Ultimeter driver. Never got a good log to determine what was 
happening before the crash so I am speculating. 

New system is a RPi4 with a new memory card and a RTC.  Going Python3 all 
the way with this station.


Ralph

-- 
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/ae5a3c40-8d6d-4eff-83ef-c7343f775660%40googlegroups.com.

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-14 Thread Ralph Underwood

This is the result with latest ultimeter.py and debug_serial = 1


Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: retrying...
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Using configuration 
file /home/weewx/weewx.conf
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Debug is 1
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Initializing engine
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Loading station type 
Ultimeter (weewx.drivers.ultimeter)
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.drivers.ultimeter: Driver 
version is 0.40
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.drivers.ultimeter: Using 
serial port /dev/ttyUSB0
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.drivers.ultimeter: Open 
serial port /dev/ttyUSB0
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: StdConvert target 
unit is 0x1
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.manager: Daily summary 
version is 2.0
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.wxservices: The following 
values will be calculated: altimeter=prefer_hardware, 
appTemp=prefer_hardware, barometer=prefer_hardware, 
beaufort=prefer_hardware, cloudbase=prefer_hardware, 
dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, 
humidex=prefer_hardware, inDewpoint=prefer_hardware, 
maxSolarRad=prefer_hardware, pressure=prefer_hardware, 
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.wxservices: The following 
algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Archive will use data 
binding wx_binding
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: StationRegistry: 
Registration not requested.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: Wunderground: Posting 
not enabled.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: PWSweather: Posting 
not enabled.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdCWOP
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: CWOP: Posting not 
enabled.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdCWOP
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdWOW
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: WOW: Posting not 
enabled.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWOW
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Loading service 
weewx.restx.StdAWEKAS
Dec 14 10:06:36 JV-Wx weewx[12591] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Dec 14 10:06:36 JV-Wx weewx[12591] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdAWEKAS
Dec 14 10:06:36 JV-Wx weewx[12591]

Re: [weewx-development] Re: V4.0.0b4 is up

2019-12-13 Thread Ralph Underwood

/low calculations: 1
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdStationRegistry
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: StationRegistry: 
Registration not requested.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdStationRegistry
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdWunderground
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: Wunderground: Posting 
not enabled.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWunderground
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdPWSweather
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: PWSweather: Posting not 
enabled.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdPWSweather
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdCWOP
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: CWOP: Posting not 
enabled.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdCWOP
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdWOW
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: WOW: Posting not 
enabled.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdWOW
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.restx.StdAWEKAS
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdAWEKAS
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.engine.StdPrint
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdPrint
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Loading service 
weewx.engine.StdReport
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdReport
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.engine: Starting up weewx 
version 4.0.0b5
Dec 13 18:24:33 JV-Wx weewx[3658] DEBUG weewx.engine: Station does not 
support reading the time
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.manager: Starting backfill of 
daily summaries
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.engine: Starting main packet 
loop.
Dec 13 18:24:33 JV-Wx weewx[3658] INFO weewx.drivers.ultimeter: Failed 
attempt 1 of 5 to get readings: Unexpected buffer length 22
Dec 13 18:24:36 JV-Wx weewx[3658] INFO weewx.drivers.ultimeter: Failed 
attempt 2 of 5 to get readings: Unexpected header bytes 'b'!!''
Dec 13 18:24:39 JV-Wx weewx[3658] INFO weewx.drivers.ultimeter: Failed 
attempt 3 of 5 to get readings: Unexpected header bytes 'b'!!''
Dec 13 18:24:42 JV-Wx weewx[3658] INFO weewx.drivers.ultimeter: Failed 
attempt 4 of 5 to get readings: Unexpected header bytes 'b'!!''
Dec 13 18:24:45 JV-Wx weewx[3658] INFO weewx.drivers.ultimeter: Failed 
attempt 5 of 5 to get readings: Unexpected header bytes 'b'!!''
Dec 13 18:24:48 JV-Wx weewx[3658] ERROR weewx.drivers.ultimeter: Max 
retries (5) exceeded for readings
Dec 13 18:24:48 JV-Wx weewx[3658] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Dec 13 18:24:48 JV-Wx weewx[3658] DEBUG weewx.drivers.ultimeter: close 
serial port /dev/ttyUSB0
Dec 13 18:24:49 JV-Wx weewx[3658] CRITICAL weewx.engine: Caught 
WeeWxIOError: Max retries (5) exceeded for readings
Dec 13 18:24:49 JV-Wx weewx[3658] CRITICAL weewx.engine:   Waiting 
60 seconds then retrying...

On Friday, December 13, 2019 at 3:58:11 PM UTC-8, Tom Keffer wrote:
>
> Thank you, Ralph, for giving the Ultimeter driver a try!
>
> Looking through the code, it appears that, under Python 3, the driver is 
> attempting to use unicode strings, when bytes are called for. In the 
> attached version, I've fixed the most obvious cases where this is 
> happening, but I've probably missed a few.
>
> Can you give it a try?
>
> Thanks
>
> -tk
>
>
> On Fri, Dec 13, 2019 at 4:07 PM Ralph Underwood  > wrote:
>
>> Hi,
>>
>>
>> I used Vince's script to install ( that was easy).  After all worked with 
>> Simulator, I changed the driver to the Ultimeter, shut down the Rpi4 and 
>> connected the hardware and restarted.
>> This is my log output. I'm thinking I may need to look into USB rules or 
>> the serialutl.py python3 issue??
>>
>>
>> Dec 13 14:51:17 JV-Wx systemd[1]: Started weewx weather system.
>> Dec 13 14:51:17 JV-Wx weewx[1441] INFO weewx.engine: Initializing weewx 
>> vers

[weewx-development] MQTTSubscribe with WeeWX 4.0.0.b8

Re: [weewx-development] MQTTSubscribe.py installing as service

Re: [weewx-development] MQTTSubscribe.py installing as service

Re: [weewx-development] Re: continuation of discussion on wxMesh MQTT

Re: [weewx-development] Crash with 4.0.0b6

[weewx-development] Re: Crash with 4.0.0b6

[weewx-development] Crash with 4.0.0b6

Re: [weewx-development] Re: WeeWX Version 4, beta 6

[weewx-development] Re: WeeWX Version 4, beta 6

[weewx-development] Re: WeeWX Version 4, beta 6

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

Re: [weewx-development] Re: V4.0.0b4 is up

17 matches

Site Navigation

Mail list logo

Footer information