[weewx-user] Weewx-Weather34 Skin Questions

[Dun Mac]

Can anyone shed light on these matters from the Weewx-Weather34 skin;
1. Position 4, in the easyW34skinsetup.php only gives the options of of 
advisory_rw, _eu,_uk. Is this the only options for position 4? Some 
previous versions on the internet are showing Position 4 with more options  
((W34-HC-IMJD-2.0.0)  WeeWX-(4.2.0)  Ecowitt GW1000). My version is 
(W34-HC-IMJD-4.1.3)  WeeWX-(4.5.1)  Davis Vantage Pro2)
2. easyW34skinsetup.php - ICAO code for METAR Station1 did not change the 
station. Is this because the field is held in weewx.conf and as such weewx 
needs to be stopped and then restarted to change the setting?
3. Position 9, Barometer. The default range for the dial is 950 - 1050 hPa, 
(28 - 31 inHg). I changed the barometer.php file to min 980 min 1050 max, 
(29 inHg - 31inHg) but the barometric reading which is currently 1005.5 is 
still sitting at 1 o'clock on the dial and with the range adjustment it 
should be sitting at 11 o'clock. The descriptor on the dial reads min 980 
hPa and max 1050 hPa. Is there anyway of changing the scaling of the 
barometer display so that 12 o'clock on the scale is 1015 hPa and not the 
default 1000 hPa? 
Thank you, Duncan


-- 
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/f8e4ade6-e958-4084-b3f9-3ae1c206b087n%40googlegroups.com.

Re: [weewx-user] ultimeter driver

[p q]

Sorry for the wrong answer!

On Fri, Apr 9, 2021 at 3:05 PM Tom Keffer  wrote:

> You had the right idea, but we have to be careful about values that are
> encoded in only two bytes.
>
> Try this version.
>
> -tk
>
> On Fri, Apr 9, 2021 at 8:50 AM Chris Thompstone <
> chris.thompst...@gmail.com> wrote:
>
>> Don't worry, I think I may have patched it.  I'm not really much of a
>> coder (although can do some stuff)...
>> Modded your file.  see line 345 onwards.
>> See attached
>>
>> On Friday, 9 April 2021 at 16:36:35 UTC+1 tke...@gmail.com wrote:
>>
>>> Sorry. I’ll try to get an update out later today.
>>>
>>> On Fri, Apr 9, 2021 at 8:18 AM Chris Thompstone 
>>> wrote:
>>>

 just tried that and get:
 Apr  9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close
 serial port /dev/ttyUSB0
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught
 unrecoverable exception:
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 startswith first arg must be bytes or a tuple of bytes, not str
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 Traceback (most recent call last):
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewx/drivers/ultimeter.py", line 346, in _decode
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   v =
 int(s, 16)
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 ValueError: invalid literal for int() with base 16: b''
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   During
 handling of the above exception, another exception occurred:
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 Traceback (most recent call last):
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewxd", line 157, in main
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 engine.run()
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewx/engine.py", line 208, in run
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   for
 packet in self.console.genLoopPackets():
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewx/drivers/ultimeter.py", line 132, in genLoopPackets
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   data
 = Station.parse_readings(readings)
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewx/drivers/ultimeter.py", line 317, in parse_readings
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 data['inHumidity'] = Station._decode(buf[28:32], 0.1)  # percent
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
 "/home/weewx/bin/weewx/drivers/ultimeter.py", line 354, in _decode
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   if
 not s. startswith('--'):
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
 TypeError: startswith first arg must be bytes or a tuple of bytes, not str
 Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Exiting.

 On Friday, 9 April 2021 at 16:03:24 UTC+1 tke...@gmail.com wrote:

> The driver should work fine with Python 3.
>
> However, the driver has a small, non-functional bug that causes it to
> emit that error message when it encounters a "dash" value. It's
> non-functional because it emits the right value ("None"). It just 
> shouldn't
> log an error.
>
> Try this version. I've taken the occasion of having a real, live
> Ultimeter user to also fix some ambiguities around byte array types. Let 
> me
> know if it works.
>
> -tk
>
> On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone 
> wrote:
>
>> Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
>> Is that what your saying?
>> Oh, had not planned on that.
>> I found some sort of error in my template, which I've kind of
>> resolved.
>> But the Ultimeter driver... not sure on this one.
>> Thanks
>> Chris
>>
>> On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:
>>
>>> Looks like you switched to Python 3 from Python 2.7 and the driver
>>> isn't compatible, based on the error message.
>>>
>>> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone <
>>> chris.th...@gmail.com> wrote:
>>>
 Hi Guys,
 I have been trying to upgrade to version 4 since my Pi decided to
 throw a strop.
 Anyway, it's been fairly hardwork.

 I have this message continuous in the logs:
 DEBUG weewx.drivers.ultimeter: 

Re: [weewx-user] Re: Combining data from wview archive with recent data from weewx

[richard maliszewski]

Converting the wview DB to the extended schema made everything happy.  Took 
a while.

--Richard

On Friday, April 9, 2021 at 3:08:33 PM UTC-7 tke...@gmail.com wrote:

> Alternatively, V4.5.1 allows you to add new data types one-by-one. See the 
> section *Adding a new type to an existing database* in the Customizing 
> Guide.
>
> On Fri, Apr 9, 2021 at 2:12 PM vince  wrote:
>
>> Not a great problem description for us to work on, but my guess is that 
>> your old db is the old wview-compatible schema and the new software expects 
>> the newer wview-extended schema.  
>>
>> Easiest way to check your db is see how many tables are in your db:
>>   echo ".schema" | sqlite3 /home/weewx/archive/weewx.sdb | wc -l
>>
>> If you see 114 lines there, you have the extended schema.  I think the 
>> number is 40 or so with the old wview-compatible schema.
>>
>> Converting from old to new/bigger schema is documented in the wiki at 
>> https://github.com/weewx/weewx/wiki/Switching-to-the-new-wview_extended-schema
>>
>>
>> On Friday, April 9, 2021 at 2:02:27 PM UTC-7 rlmali...@gmail.com wrote:
>>
>>> Probably not worth sweating, as Weewx seems to have stitched everything 
>>> back together except earlier today...and that's fine.  However, after 
>>> switching to the wview SDB file, I am seeing an error every cycle from 
>>> WeeWX in the log:
>>>
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: Caught 
>>> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  pm2_5
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  Traceback (most recent call last):
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  obj.start()
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  self.run()
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in run
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  self.genImages(self.gen_ts)
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>File "/usr/share/weewx/weewx/imagegenerator.py", line 180, in genImages
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  aggregate_interval=aggregate_interval)
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>File "/usr/share/weewx/weewx/xtypes.py", line 91, in get_series
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  raise weewx.UnknownType(obs_type)
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  UnknownType: pm2_5
>>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>>>  Generator terminated
>>>
>>> This is new behavior as of the switch to the wview archive.  Nothing 
>>> else has been changed.  It looks like things are mostly trundling along.  
>>> Any idea why this new error?  I am suspicious that the GW1000 extension 
>>> install did something to the DB that my switch to the wview DB has now 
>>> undone.  Digging.
>>>
>>> --Richard
>>>
>>> On Friday, April 9, 2021 at 1:25:07 PM UTC-7 richard maliszewski wrote:
>>>
 WeeWX and I are getting along well.  We had a wview installation that 
 had accumulated 7+ years of readings from a TE923W.  The recent WeeWX data 
 is only a week or two.  I have done the DB shuflle and WeeWX is creating 
 summary data and such for the pile of wview data.

 It's not a huge loss if it's not doable, but once that settles, is 
 there any reasonable way to import the recent WeeWX data into the 
 resulting 
 weewx.sdb?  Per the guide, I kept that as weewx.sdb.bak, so it's still 
 available.

 --Richard

 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/723afe71-8b4c-43a4-913e-dcb5f6a0c91cn%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] Wind direction resolution after update of WeeWX

[Tom Keffer]

What type of hardware?

Did you change the kind of record generation?

On Fri, Apr 9, 2021 at 10:46 AM 'Tom' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi,
>
> I have updated WeeWX from version 3.8 to the current version. Now I have
> the problem that the wind direction is only written into the SQLite
> database with a resolution of 22.5 degrees. I took over the old
> configuration file weewx.conf during the update.
>
> Previously, the wind direction was saved in 1 degree steps. What should I
> change so that the resolution of the wind direction is correct again?
>
> Tom[image: Unbenannt.JPG]
>
> --
> 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/76c19ea6-9afc-4ca0-86bd-30b99f2469f1n%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/CAPq0zEBCzdtdWjs35Nq1MiRHYLnUev-ATsReiGnWDQG-NQ3YHg%40mail.gmail.com.

Re: [weewx-user] Re: Combining data from wview archive with recent data from weewx

[Tom Keffer]

Alternatively, V4.5.1 allows you to add new data types one-by-one. See the
section *Adding a new type to an existing database
* in
the Customizing Guide.

On Fri, Apr 9, 2021 at 2:12 PM vince  wrote:

> Not a great problem description for us to work on, but my guess is that
> your old db is the old wview-compatible schema and the new software expects
> the newer wview-extended schema.
>
> Easiest way to check your db is see how many tables are in your db:
>   echo ".schema" | sqlite3 /home/weewx/archive/weewx.sdb | wc -l
>
> If you see 114 lines there, you have the extended schema.  I think the
> number is 40 or so with the old wview-compatible schema.
>
> Converting from old to new/bigger schema is documented in the wiki at
> https://github.com/weewx/weewx/wiki/Switching-to-the-new-wview_extended-schema
>
>
> On Friday, April 9, 2021 at 2:02:27 PM UTC-7 rlmali...@gmail.com wrote:
>
>> Probably not worth sweating, as Weewx seems to have stitched everything
>> back together except earlier today...and that's fine.  However, after
>> switching to the wview SDB file, I am seeing an error every cycle from
>> WeeWX in the log:
>>
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: Caught
>> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  pm2_5
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  Traceback (most recent call last):
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  obj.start()
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  self.run()
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in run
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  self.genImages(self.gen_ts)
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>File "/usr/share/weewx/weewx/imagegenerator.py", line 180, in genImages
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  aggregate_interval=aggregate_interval)
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>File "/usr/share/weewx/weewx/xtypes.py", line 91, in get_series
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  raise weewx.UnknownType(obs_type)
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  UnknownType: pm2_5
>> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: 
>>  Generator terminated
>>
>> This is new behavior as of the switch to the wview archive.  Nothing else
>> has been changed.  It looks like things are mostly trundling along.  Any
>> idea why this new error?  I am suspicious that the GW1000 extension install
>> did something to the DB that my switch to the wview DB has now undone.
>> Digging.
>>
>> --Richard
>>
>> On Friday, April 9, 2021 at 1:25:07 PM UTC-7 richard maliszewski wrote:
>>
>>> WeeWX and I are getting along well.  We had a wview installation that
>>> had accumulated 7+ years of readings from a TE923W.  The recent WeeWX data
>>> is only a week or two.  I have done the DB shuflle and WeeWX is creating
>>> summary data and such for the pile of wview data.
>>>
>>> It's not a huge loss if it's not doable, but once that settles, is there
>>> any reasonable way to import the recent WeeWX data into the resulting
>>> weewx.sdb?  Per the guide, I kept that as weewx.sdb.bak, so it's still
>>> available.
>>>
>>> --Richard
>>>
>>> --
> 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/723afe71-8b4c-43a4-913e-dcb5f6a0c91cn%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/CAPq0zEBixRfvmvxrjYi4c2eqokR2hh9iE8u7e24-xRnHFAnu6Q%40mail.gmail.com.

Re: [weewx-user] ultimeter driver

[Tom Keffer]

You had the right idea, but we have to be careful about values that are
encoded in only two bytes.

Try this version.

-tk

On Fri, Apr 9, 2021 at 8:50 AM Chris Thompstone 
wrote:

> Don't worry, I think I may have patched it.  I'm not really much of a
> coder (although can do some stuff)...
> Modded your file.  see line 345 onwards.
> See attached
>
> On Friday, 9 April 2021 at 16:36:35 UTC+1 tke...@gmail.com wrote:
>
>> Sorry. I’ll try to get an update out later today.
>>
>> On Fri, Apr 9, 2021 at 8:18 AM Chris Thompstone 
>> wrote:
>>
>>>
>>> just tried that and get:
>>> Apr  9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close
>>> serial port /dev/ttyUSB0
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught
>>> unrecoverable exception:
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> startswith first arg must be bytes or a tuple of bytes, not str
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback
>>> (most recent call last):
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 346, in _decode
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   v =
>>> int(s, 16)
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> ValueError: invalid literal for int() with base 16: b''
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   During
>>> handling of the above exception, another exception occurred:
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback
>>> (most recent call last):
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewxd", line 157, in main
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> engine.run()
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewx/engine.py", line 208, in run
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   for
>>> packet in self.console.genLoopPackets():
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 132, in genLoopPackets
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   data
>>> = Station.parse_readings(readings)
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 317, in parse_readings
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> data['inHumidity'] = Station._decode(buf[28:32], 0.1)  # percent
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
>>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 354, in _decode
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   if
>>> not s. startswith('--'):
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
>>> TypeError: startswith first arg must be bytes or a tuple of bytes, not str
>>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Exiting.
>>>
>>> On Friday, 9 April 2021 at 16:03:24 UTC+1 tke...@gmail.com wrote:
>>>
 The driver should work fine with Python 3.

 However, the driver has a small, non-functional bug that causes it to
 emit that error message when it encounters a "dash" value. It's
 non-functional because it emits the right value ("None"). It just shouldn't
 log an error.

 Try this version. I've taken the occasion of having a real, live
 Ultimeter user to also fix some ambiguities around byte array types. Let me
 know if it works.

 -tk

 On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone 
 wrote:

> Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
> Is that what your saying?
> Oh, had not planned on that.
> I found some sort of error in my template, which I've kind of resolved.
> But the Ultimeter driver... not sure on this one.
> Thanks
> Chris
>
> On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:
>
>> Looks like you switched to Python 3 from Python 2.7 and the driver
>> isn't compatible, based on the error message.
>>
>> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone <
>> chris.th...@gmail.com> wrote:
>>
>>> Hi Guys,
>>> I have been trying to upgrade to version 4 since my Pi decided to
>>> throw a strop.
>>> Anyway, it's been fairly hardwork.
>>>
>>> I have this message continuous in the logs:
>>> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid
>>> literal for int() with base 16: ''
>>> just coming every 1s or so.
>>>
>>> I also have some other issue which I can't seem to find:
>>> ERROR weewx.cheetahgenerator: Generate failed 

[weewx-user] Re: Combining data from wview archive with recent data from weewx

[vince]

Not a great problem description for us to work on, but my guess is that 
your old db is the old wview-compatible schema and the new software expects 
the newer wview-extended schema.  

Easiest way to check your db is see how many tables are in your db:
  echo ".schema" | sqlite3 /home/weewx/archive/weewx.sdb | wc -l

If you see 114 lines there, you have the extended schema.  I think the 
number is 40 or so with the old wview-compatible schema.

Converting from old to new/bigger schema is documented in the wiki 
at 
https://github.com/weewx/weewx/wiki/Switching-to-the-new-wview_extended-schema


On Friday, April 9, 2021 at 2:02:27 PM UTC-7 rlmali...@gmail.com wrote:

> Probably not worth sweating, as Weewx seems to have stitched everything 
> back together except earlier today...and that's fine.  However, after 
> switching to the wview SDB file, I am seeing an error every cycle from 
> WeeWX in the log:
>
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>  pm2_5
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>obj.start()
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>self.run()
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in run
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>self.genImages(self.gen_ts)
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/imagegenerator.py", line 180, in genImages
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>aggregate_interval=aggregate_interval)
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/xtypes.py", line 91, in get_series
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
>raise weewx.UnknownType(obs_type)
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>  UnknownType: pm2_5
> Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
>  Generator terminated
>
> This is new behavior as of the switch to the wview archive.  Nothing else 
> has been changed.  It looks like things are mostly trundling along.  Any 
> idea why this new error?  I am suspicious that the GW1000 extension install 
> did something to the DB that my switch to the wview DB has now undone. 
>  Digging.
>
> --Richard
>
> On Friday, April 9, 2021 at 1:25:07 PM UTC-7 richard maliszewski wrote:
>
>> WeeWX and I are getting along well.  We had a wview installation that had 
>> accumulated 7+ years of readings from a TE923W.  The recent WeeWX data is 
>> only a week or two.  I have done the DB shuflle and WeeWX is creating 
>> summary data and such for the pile of wview data.
>>
>> It's not a huge loss if it's not doable, but once that settles, is there 
>> any reasonable way to import the recent WeeWX data into the resulting 
>> weewx.sdb?  Per the guide, I kept that as weewx.sdb.bak, so it's still 
>> available.
>>
>> --Richard
>>
>>

-- 
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/723afe71-8b4c-43a4-913e-dcb5f6a0c91cn%40googlegroups.com.

[weewx-user] Re: Combining data from wview archive with recent data from weewx

[richard maliszewski]

Probably not worth sweating, as Weewx seems to have stitched everything 
back together except earlier today...and that's fine.  However, after 
switching to the wview SDB file, I am seeing an error every cycle from 
WeeWX in the log:

Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
 pm2_5
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
 Traceback (most recent call last):
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
   obj.start()
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
   self.run()
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in run
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
   self.genImages(self.gen_ts)
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/imagegenerator.py", line 180, in genImages
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
   aggregate_interval=aggregate_interval)
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
 File "/usr/share/weewx/weewx/xtypes.py", line 91, in get_series
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:    
   raise weewx.UnknownType(obs_type)
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
 UnknownType: pm2_5
Apr  9 13:50:24 minix weewx[6296] ERROR weewx.reportengine:  
 Generator terminated

This is new behavior as of the switch to the wview archive.  Nothing else 
has been changed.  It looks like things are mostly trundling along.  Any 
idea why this new error?  I am suspicious that the GW1000 extension install 
did something to the DB that my switch to the wview DB has now undone. 
 Digging.

--Richard

On Friday, April 9, 2021 at 1:25:07 PM UTC-7 richard maliszewski wrote:

> WeeWX and I are getting along well.  We had a wview installation that had 
> accumulated 7+ years of readings from a TE923W.  The recent WeeWX data is 
> only a week or two.  I have done the DB shuflle and WeeWX is creating 
> summary data and such for the pile of wview data.
>
> It's not a huge loss if it's not doable, but once that settles, is there 
> any reasonable way to import the recent WeeWX data into the resulting 
> weewx.sdb?  Per the guide, I kept that as weewx.sdb.bak, so it's still 
> available.
>
> --Richard
>
>

-- 
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/18ecf4d7-fac4-450b-a24b-3762142bdb3dn%40googlegroups.com.

[weewx-user] Combining data from wview archive with recent data from weewx

[richard maliszewski]

WeeWX and I are getting along well.  We had a wview installation that had 
accumulated 7+ years of readings from a TE923W.  The recent WeeWX data is 
only a week or two.  I have done the DB shuflle and WeeWX is creating 
summary data and such for the pile of wview data.

It's not a huge loss if it's not doable, but once that settles, is there 
any reasonable way to import the recent WeeWX data into the resulting 
weewx.sdb?  Per the guide, I kept that as weewx.sdb.bak, so it's still 
available.

--Richard

-- 
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/47211286-5da4-4f43-9580-3c8ff43e1d91n%40googlegroups.com.

[weewx-user] Wind direction resolution after update of WeeWX

['Tom' via weewx-user]

Hi,

I have updated WeeWX from version 3.8 to the current version. Now I have 
the problem that the wind direction is only written into the SQLite 
database with a resolution of 22.5 degrees. I took over the old 
configuration file weewx.conf during the update. 

Previously, the wind direction was saved in 1 degree steps. What should I 
change so that the resolution of the wind direction is correct again? 

Tom[image: Unbenannt.JPG]

-- 
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/76c19ea6-9afc-4ca0-86bd-30b99f2469f1n%40googlegroups.com.

Re: [weewx-user] ultimeter driver

[Chris Thompstone]

Don't worry, I think I may have patched it.  I'm not really much of a coder 
(although can do some stuff)...
Modded your file.  see line 345 onwards.
See attached

On Friday, 9 April 2021 at 16:36:35 UTC+1 tke...@gmail.com wrote:

> Sorry. I’ll try to get an update out later today.
>
> On Fri, Apr 9, 2021 at 8:18 AM Chris Thompstone  
> wrote:
>
>>
>> just tried that and get:
>> Apr  9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close 
>> serial port /dev/ttyUSB0
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught unrecoverable 
>> exception:
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   startswith 
>> first arg must be bytes or a tuple of bytes, not str
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback 
>> (most recent call last):
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 346, in _decode
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   v = 
>> int(s, 16)
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
>> ValueError: invalid literal for int() with base 16: b''
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   During 
>> handling of the above exception, another exception occurred:
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback 
>> (most recent call last):
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewxd", line 157, in main
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
>> engine.run()
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewx/engine.py", line 208, in run
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   for 
>> packet in self.console.genLoopPackets():
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 132, in genLoopPackets
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   data = 
>> Station.parse_readings(readings)
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 317, in parse_readings
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
>> data['inHumidity'] = Station._decode(buf[28:32], 0.1)  # percent
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
>> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 354, in _decode
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   if not 
>> s. startswith('--'):
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   TypeError: 
>> startswith first arg must be bytes or a tuple of bytes, not str
>> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Exiting.
>>
>> On Friday, 9 April 2021 at 16:03:24 UTC+1 tke...@gmail.com wrote:
>>
>>> The driver should work fine with Python 3.
>>>
>>> However, the driver has a small, non-functional bug that causes it to 
>>> emit that error message when it encounters a "dash" value. It's 
>>> non-functional because it emits the right value ("None"). It just shouldn't 
>>> log an error. 
>>>
>>> Try this version. I've taken the occasion of having a real, live 
>>> Ultimeter user to also fix some ambiguities around byte array types. Let me 
>>> know if it works.
>>>
>>> -tk
>>>
>>> On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone  
>>> wrote:
>>>
 Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
 Is that what your saying?
 Oh, had not planned on that.
 I found some sort of error in my template, which I've kind of resolved.
 But the Ultimeter driver... not sure on this one.
 Thanks
 Chris

 On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:

> Looks like you switched to Python 3 from Python 2.7 and the driver 
> isn't compatible, based on the error message.
>
> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone  
> wrote:
>
>> Hi Guys,
>> I have been trying to upgrade to version 4 since my Pi decided to 
>> throw a strop.
>> Anyway, it's been fairly hardwork.
>>
>> I have this message continuous in the logs:
>> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid 
>> literal for int() with base 16: ''
>> just coming every 1s or so.
>>
>> I also have some other issue which I can't seem to find:
>> ERROR weewx.cheetahgenerator: Generate failed with exception '> 'TypeError'>'
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
>> Ignoring template /home/weewx/skins/Standard/index.html.tmpl
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
>> 

Re: [weewx-user] ultimeter driver

[Tom Keffer]

Sorry. I’ll try to get an update out later today.

On Fri, Apr 9, 2021 at 8:18 AM Chris Thompstone 
wrote:

>
> just tried that and get:
> Apr  9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close
> serial port /dev/ttyUSB0
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught unrecoverable
> exception:
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   startswith
> first arg must be bytes or a tuple of bytes, not str
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback
> (most recent call last):
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 346, in _decode
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   v =
> int(s, 16)
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   ValueError:
> invalid literal for int() with base 16: b''
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   During
> handling of the above exception, another exception occurred:
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback
> (most recent call last):
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewxd", line 157, in main
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
> engine.run()
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewx/engine.py", line 208, in run
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   for
> packet in self.console.genLoopPackets():
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 132, in genLoopPackets
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   data =
> Station.parse_readings(readings)
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 317, in parse_readings
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: 
> data['inHumidity'] = Station._decode(buf[28:32], 0.1)  # percent
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File
> "/home/weewx/bin/weewx/drivers/ultimeter.py", line 354, in _decode
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   if not
> s. startswith('--'):
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   TypeError:
> startswith first arg must be bytes or a tuple of bytes, not str
> Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Exiting.
>
> On Friday, 9 April 2021 at 16:03:24 UTC+1 tke...@gmail.com wrote:
>
>> The driver should work fine with Python 3.
>>
>> However, the driver has a small, non-functional bug that causes it to
>> emit that error message when it encounters a "dash" value. It's
>> non-functional because it emits the right value ("None"). It just shouldn't
>> log an error.
>>
>> Try this version. I've taken the occasion of having a real, live
>> Ultimeter user to also fix some ambiguities around byte array types. Let me
>> know if it works.
>>
>> -tk
>>
>> On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone 
>> wrote:
>>
>>> Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
>>> Is that what your saying?
>>> Oh, had not planned on that.
>>> I found some sort of error in my template, which I've kind of resolved.
>>> But the Ultimeter driver... not sure on this one.
>>> Thanks
>>> Chris
>>>
>>> On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:
>>>
 Looks like you switched to Python 3 from Python 2.7 and the driver
 isn't compatible, based on the error message.

 On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone 
 wrote:

> Hi Guys,
> I have been trying to upgrade to version 4 since my Pi decided to
> throw a strop.
> Anyway, it's been fairly hardwork.
>
> I have this message continuous in the logs:
> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid
> literal for int() with base 16: ''
> just coming every 1s or so.
>
> I also have some other issue which I can't seem to find:
> ERROR weewx.cheetahgenerator: Generate failed with exception ' 'TypeError'>'
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Ignoring template /home/weewx/skins/Standard/index.html.tmpl
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Reason: '>' not supported between instances of 'NoneType' and 'float'
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
> Apr  9 14:45:16 weewx weewx[868] ERROR 

Re: [weewx-user] ultimeter driver

[Chris Thompstone]

just tried that and get:
Apr  9 16:17:18 weewx weewx[1719] DEBUG weewx.drivers.ultimeter: Close 
serial port /dev/ttyUSB0
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: Caught unrecoverable 
exception:
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   startswith 
first arg must be bytes or a tuple of bytes, not str
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback 
(most recent call last):
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewx/drivers/ultimeter.py", line 346, in _decode
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   v = 
int(s, 16)
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   ValueError: 
invalid literal for int() with base 16: b''
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   During 
handling of the above exception, another exception occurred:
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Traceback 
(most recent call last):
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewxd", line 157, in main
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
engine.run()
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 208, in run
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   for 
packet in self.console.genLoopPackets():
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewx/drivers/ultimeter.py", line 132, in genLoopPackets
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   data = 
Station.parse_readings(readings)
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewx/drivers/ultimeter.py", line 317, in parse_readings
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   
data['inHumidity'] = Station._decode(buf[28:32], 0.1)  # percent
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__: File 
"/home/weewx/bin/weewx/drivers/ultimeter.py", line 354, in _decode
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   if not 
s. startswith('--'):
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   TypeError: 
startswith first arg must be bytes or a tuple of bytes, not str
Apr  9 16:17:19 weewx weewx[1719] CRITICAL __main__:   Exiting.

On Friday, 9 April 2021 at 16:03:24 UTC+1 tke...@gmail.com wrote:

> The driver should work fine with Python 3.
>
> However, the driver has a small, non-functional bug that causes it to emit 
> that error message when it encounters a "dash" value. It's non-functional 
> because it emits the right value ("None"). It just shouldn't log an error. 
>
> Try this version. I've taken the occasion of having a real, live Ultimeter 
> user to also fix some ambiguities around byte array types. Let me know if 
> it works.
>
> -tk
>
> On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone  
> wrote:
>
>> Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
>> Is that what your saying?
>> Oh, had not planned on that.
>> I found some sort of error in my template, which I've kind of resolved.
>> But the Ultimeter driver... not sure on this one.
>> Thanks
>> Chris
>>
>> On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:
>>
>>> Looks like you switched to Python 3 from Python 2.7 and the driver isn't 
>>> compatible, based on the error message.
>>>
>>> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone  
>>> wrote:
>>>
 Hi Guys,
 I have been trying to upgrade to version 4 since my Pi decided to throw 
 a strop.
 Anyway, it's been fairly hardwork.

 I have this message continuous in the logs:
 DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid 
 literal for int() with base 16: ''
 just coming every 1s or so.

 I also have some other issue which I can't seem to find:
 ERROR weewx.cheetahgenerator: Generate failed with exception '>>> 'TypeError'>'
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
 Ignoring template /home/weewx/skins/Standard/index.html.tmpl
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
 Reason: '>' not supported between instances of 'NoneType' and 'float'
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
 Traceback (most recent call last):
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
 File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
   unicode_string = compiled_template.respond()
 Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
 File 

Re: [weewx-user] ultimeter driver

[Tom Keffer]

The driver should work fine with Python 3.

However, the driver has a small, non-functional bug that causes it to emit
that error message when it encounters a "dash" value. It's non-functional
because it emits the right value ("None"). It just shouldn't log an error.

Try this version. I've taken the occasion of having a real, live Ultimeter
user to also fix some ambiguities around byte array types. Let me know if
it works.

-tk

On Fri, Apr 9, 2021 at 7:26 AM Chris Thompstone 
wrote:

> Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
> Is that what your saying?
> Oh, had not planned on that.
> I found some sort of error in my template, which I've kind of resolved.
> But the Ultimeter driver... not sure on this one.
> Thanks
> Chris
>
> On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:
>
>> Looks like you switched to Python 3 from Python 2.7 and the driver isn't
>> compatible, based on the error message.
>>
>> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone 
>> wrote:
>>
>>> Hi Guys,
>>> I have been trying to upgrade to version 4 since my Pi decided to throw
>>> a strop.
>>> Anyway, it's been fairly hardwork.
>>>
>>> I have this message continuous in the logs:
>>> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid literal
>>> for int() with base 16: ''
>>> just coming every 1s or so.
>>>
>>> I also have some other issue which I can't seem to find:
>>> ERROR weewx.cheetahgenerator: Generate failed with exception '>> 'TypeError'>'
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> Ignoring template /home/weewx/skins/Standard/index.html.tmpl
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> Reason: '>' not supported between instances of 'NoneType' and 'float'
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> Traceback (most recent call last):
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> unicode_string = compiled_template.respond()
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> File "_home_weewx_skins_Standard_index_html_tmpl.py", line 1378, in respond
>>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>>> TypeError: '>' not supported between instances of 'NoneType' and 'float'
>>>
>>> My wind vein has blown off the roof, so wind direction and speed are
>>> probably both None.
>>> Whether this is something to do with it I don't know, but I can't get
>>> the index template generated.
>>> Thanks
>>> Chris
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/dd2cd2fd-515b-47b3-a8c5-cb1692508eb8n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Peter Quinn
>> (415)794-2264 <(415)%20794-2264>
>>
> --
> 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/c4ef6c55-ddee-4c9e-a7d6-23cc1f5beb2an%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/CAPq0zECiR6W0-ksDSmKSLoUL9LQFPRSqUPwsrXH4fPyaqFQt6w%40mail.gmail.com.
#!/usr/bin/env python
#
# Copyright 2014-2020 Matthew Wall
# Copyright 2014 Nate Bargmann 
# See the file LICENSE.txt for your rights.
#
# Credit to and contributions from:
#   Jay Nugent (WB8TKL) and KRK6 for weather-2.kr6k-V2.1
# http://server1.nuge.com/~weather/
#   Steve (sesykes71) for testing the first implementations of this driver
#   Garret Power for improved decoding and proper handling of negative values
#   Chris Thompstone for testing the fast-read implementation
#
# Thanks to PeetBros for publishing the communication protocols and details
# about each model they manufacture.

"""Driver for Peet Bros Ultimeter weather stations except the Ultimeter II

This driver assumes the Ultimeter is emitting data in Peet Bros Data Logger
mode format.  This driver will set the 

Re: [weewx-user] ultimeter driver

[Chris Thompstone]

Oh, the ultimeter isn't supported on Python 3 and ver 4 weewx ?
Is that what your saying?
Oh, had not planned on that.
I found some sort of error in my template, which I've kind of resolved.
But the Ultimeter driver... not sure on this one.
Thanks
Chris

On Friday, 9 April 2021 at 15:20:41 UTC+1 peterq...@gmail.com wrote:

> Looks like you switched to Python 3 from Python 2.7 and the driver isn't 
> compatible, based on the error message.
>
> On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone  
> wrote:
>
>> Hi Guys,
>> I have been trying to upgrade to version 4 since my Pi decided to throw a 
>> strop.
>> Anyway, it's been fairly hardwork.
>>
>> I have this message continuous in the logs:
>> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid literal 
>> for int() with base 16: ''
>> just coming every 1s or so.
>>
>> I also have some other issue which I can't seem to find:
>> ERROR weewx.cheetahgenerator: Generate failed with exception '> 'TypeError'>'
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
>> Ignoring template /home/weewx/skins/Standard/index.html.tmpl
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
>> Reason: '>' not supported between instances of 'NoneType' and 'float'
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
>> Traceback (most recent call last):
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
>> unicode_string = compiled_template.respond()
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_Standard_index_html_tmpl.py", line 1378, in respond
>> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
>> TypeError: '>' not supported between instances of 'NoneType' and 'float'
>>
>> My wind vein has blown off the roof, so wind direction and speed are 
>> probably both None.
>> Whether this is something to do with it I don't know, but I can't get the 
>> index template generated.
>> Thanks
>> Chris
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/dd2cd2fd-515b-47b3-a8c5-cb1692508eb8n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Peter Quinn
> (415)794-2264 <(415)%20794-2264>
>

-- 
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/c4ef6c55-ddee-4c9e-a7d6-23cc1f5beb2an%40googlegroups.com.

Re: [weewx-user] ultimeter driver

[p q]

Looks like you switched to Python 3 from Python 2.7 and the driver isn't
compatible, based on the error message.

On Fri, Apr 9, 2021 at 6:56 AM Chris Thompstone 
wrote:

> Hi Guys,
> I have been trying to upgrade to version 4 since my Pi decided to throw a
> strop.
> Anyway, it's been fairly hardwork.
>
> I have this message continuous in the logs:
> DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid literal
> for int() with base 16: ''
> just coming every 1s or so.
>
> I also have some other issue which I can't seem to find:
> ERROR weewx.cheetahgenerator: Generate failed with exception ' 'TypeError'>'
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Ignoring template /home/weewx/skins/Standard/index.html.tmpl
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Reason: '>' not supported between instances of 'NoneType' and 'float'
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> File "_home_weewx_skins_Standard_index_html_tmpl.py", line 1378, in respond
> Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: 
> TypeError: '>' not supported between instances of 'NoneType' and 'float'
>
> My wind vein has blown off the roof, so wind direction and speed are
> probably both None.
> Whether this is something to do with it I don't know, but I can't get the
> index template generated.
> Thanks
> Chris
>
> --
> 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/dd2cd2fd-515b-47b3-a8c5-cb1692508eb8n%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM23cWPZgnBZWwfMd-HytFUrnwO2vps%2BsQRR9zThFs5Sj0A%40mail.gmail.com.

[weewx-user] ultimeter driver

[Chris Thompstone]

Hi Guys,
I have been trying to upgrade to version 4 since my Pi decided to throw a 
strop.
Anyway, it's been fairly hardwork.

I have this message continuous in the logs:
DEBUG weewx.drivers.ultimeter: Decode failed for '': invalid literal 
for int() with base 16: ''
just coming every 1s or so.

I also have some other issue which I can't seem to find:
ERROR weewx.cheetahgenerator: Generate failed with exception ''
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/Standard/index.html.tmpl
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:  Reason: 
'>' not supported between instances of 'NoneType' and 'float'
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
unicode_string = compiled_template.respond()
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator: File 
"_home_weewx_skins_Standard_index_html_tmpl.py", line 1378, in respond
Apr  9 14:45:16 weewx weewx[868] ERROR weewx.cheetahgenerator:   
TypeError: '>' not supported between instances of 'NoneType' and 'float'

My wind vein has blown off the roof, so wind direction and speed are 
probably both None.
Whether this is something to do with it I don't know, but I can't get the 
index template generated.
Thanks
Chris

-- 
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/dd2cd2fd-515b-47b3-a8c5-cb1692508eb8n%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Christian Gruber]

should this still work with weewx 4.5.1 ?

i updated and my full day charts are gone

Manfred Maier schrieb am Montag, 15. Juni 2020 um 11:12:27 UTC+2:

> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>
> The trick is quite simple: I just had to define an aggregation for the 
> daily charts. I.e. adding the following two lines to the graphs.conf:
>
> aggregate_type = max
>
> aggregate_interval = 300
>
>
>
>

-- 
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/3ec51a00-2343-4b9e-81c1-ea4f3ed02a4en%40googlegroups.com.