Re: [weewx-user] Re: Problem with RTG max and min stats when using software driver

[gjr80]

Yes that appears to be what is happening. I have spent some time looking at 
your site/data and running rtgd on my test system (which uses software 
record generation) and daily min/max updates as it should. I have a few 
more questions below that might help pinpoint what is/is not happening:

1. What is the rtgd version number, you will find it in rtgd.py around line 
400 there will be RTGD_VERSION = 
2. I note your JSON output includes a field 'server_time', that field is 
not used anywhere in rtgd.py so I guess you have made some modifications to 
the code. What changes have you made to the code, no matter how trivial? 
Might be easiest to email me the rtgd.py that you are actually using. At 
least that way I can be testing the same code you are using.
3. When did you last start weeWX, searching your log for 'engine: 
Initializing weewx version' might be easiest
4. Can you capture a log extract with debug=3
- edit weewx.conf and set debug=3, save weewx.conf
- do a weeWX config reload (ie sudo systemctl reload weewx or sudo 
service weewx reload) - don't do a stop/start
- the log will be quite chatty, would be interested in the log over an 
archive period end/start, say 30 seconds before the end of the archive 
period until 30 seconds after the end of the archive period
5. If you stop then start weeWX does the day min/max obs come good?

Gary

On Sunday, 15 April 2018 21:29:33 UTC+10, Alec Bennett wrote:
>
> It looks like what's happening is that the max and min aren't resetting 
> each day. 
>
>
>
> On Fri, Apr 13, 2018 at 1:06 AM Alec Bennett  > wrote:
>
>> > I'll have a look at it, in the meantime is the offending gauges page 
>> available publicly?
>>
>> Thanks that would be great. You can see the rtg data file here:
>>
>> sinkingsensation.com/live_data/live_data.json
>>
>> The regular reports are here:
>>
>> sinkingsensation.com/weather
>>
>> Let me know if you need any other data or tests.
>>
>>
>>
>>
>>
>>
>>
>> On Thursday, April 12, 2018 at 6:41:32 PM UTC-7, gjr80 wrote:
>>>
>>> Alec,
>>>
>>> That being said it should not be affected by the record generation 
>>> setting, the rtgd extension just runs off the loop packets though there may 
>>> be some optimisations in there that are misbehaving. I'll have a look at 
>>> it, in the meantime is the offending gauges page available publicly?
>>>
>>> Gary
>>>
>>
>>>
>>> On Friday, 13 April 2018 06:13:24 UTC+10, Alec Bennett wrote:

 My weather station is in an area with unstable power and internet, and 
 I found that often after an internet outage I'd need to clear the console 
 memory on my Vantage Pro2 before it would start sending data again. I 
 switched over to the software record generation 
 (record_generation=software) and haven't had an outage in months now. 

 The only problem I'm having now is with the real time gauge (RTG) 
 extension's daily maximum and minimum stats. For example the day's maximum 
 wind gust (wgustTM), daily maximum temperature (tempTH), and daily minimum 
 temperature (tempTL) are all locked on some data in the past. 

 However the reports generated by the cheetah engine have the correct 
 daily maximums and minimums. 

 Before I dig farther into the RTG, I was wondering if anyone might have 
 some insight off-hand?


 -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/IzxgW2_uMFg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Android weather app for weeWx users

[John Smith]

On Tuesday, 17 April 2018 22:20:12 UTC+10, John Burricelli wrote:
>
> This is working great for me.  Thank you for creating this.
>
> https://www.warrenskywarn.org/settings.txt
>

Thanks for posting your settings URL, I ended up spotting a minor bug and 
tweaked the max/min times to be 24 hour time so that the lines on the stats 
page don't wrap 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Looking for help with Oregon Scientific WMR 89

['Rod Avery' via weewx-user]

Dani,

You are quite right, obvious when pointed out!

I think its correct to assume that FFFE part of the packet means there has 
been rainfall in the last hour. I have just run another test:

b111003f0e01010c00011d = 0 rain fall in the last hour (some in 
the last 24 hours)

b111fffe0008000800470e01010c000332 = 0.08in / 2ml in the last hour.

I'm going to have a look through it all now and see if I can work it out.



On Tuesday, 17 April 2018 14:34:04 UTC+1, Dani Macías Perea wrote:
>
> Hi Rob,
>
> Regarding the rain faill per hour, I am not sure if what you proposed is 
> correct. What you are doing in your code, if I understood you correctly, is 
> the following:
>
> if packet[2:4].encode('hex')!='fffe':
>Rh = None
>  else:
>Rh = (256*ord(packet[2])+ord(packet[3]))*2.54/100 
>
> So in your else branch, you will always have packet[2]=ff and 
> packet[3]=fe. Of course, you are now getting output regarding the rain 
> but the Rh will always be 1664.56, isn't? 
>
> As it is not saved in DB, I don't use the Rh and have never checked its 
> values. I don't have neither an UV sensor, so I can't help in your second 
> question.
>
>
>
> 2018-04-17 11:40 GMT+02:00 'Rod Avery' via weewx-user <
> weewx...@googlegroups.com >:
>
>> Hello all,
>>
>> I have been using the driver posted by fcauwe for a little while and am 
>> getting data through from the WMR89. 
>>
>> I did notice that it was not reporting rain fall per hour. Looking 
>> through the code I found the following if statement under *def 
>> _wmr89_rain_packet(self, packet):*
>>
>>  if packet[2:4].encode('hex')=='fffe':
>>Rh = None
>>  else:
>>
>>
>> Looking at the output from the WMR89 it looks like having output in the 
>> packet containing *fffe* means there is rain data not that there isn't 
>> rain data. So I modified the code to NOT EQUAL :
>>
>>  if packet[2:4].encode('hex')*!=*'fffe':
>>Rh = None
>>  else:
>>
>>
>> I am now getting correct output with regards to rain.
>>
>> I have also taken Daniels suggestion and added the code from his post.
>>
>> On a side issue, I am getting the following:
>> Apr 17 10:34:30 weatherstation weewx[27499]: wmr89: Invalid data packet 
>> (b3050100b9).
>>
>> Does anyone know what this packet is? I have a UV sensor connected so 
>> could it be for that?
>>
>> Big thank you to all involved in writing the driver for the WMR89 - Very 
>> helpful!
>>
>> Rod.
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/FxNx6am2MgM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Web page auto-refresh

[w7hd.rh]

In /etc/weewx/skins/Standard/index.html.tmpl I added the line for refresh.

It now auto-updates the web page once per minute.


http://www.w3.org/2005/10/profile;>

## This choice should match the #encoding directive above



**

--

Ron W7HD - NAQCC#7587 OMISS#9898 KX3#6966 LinuxUser#415320
Editor OVARC newsletter

--
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.
For more options, visit https://groups.google.com/d/optout.

RE: [weewx-user] Re: weewx crashes with error: unpack requires a string of len 104

[Graham Seward]

Hi Susan

I’m at a loss to understand where the problem lay but as it’s working fine with 
a loop delay of 15 I’m happy to leave it at that. 

 

Thank you for the note about the router advertisements and soliciting a DHCPV6 
lease – I’ve fixed the problem and the syslog files are a lot easier to read 
now.

 

Once again thanks for your help

Graham

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
vk3...@gmail.com
Sent: 12 April 2018 04:42
To: weewx-user 
Subject: [weewx-user] Re: weewx crashes with error: unpack requires a string of 
len 104

 

Hello Graham,

 

I've not been able to come up with anything so far but I'm still looking at 
this. It is a real puzzle because there should be log file entries from WeeWx 
if my code was exiting or encountering a fault etc.. Instead there is nothing 
in the log file.

 

I'm still looking into this

 

By the way, I noticed a number of messages in your syslog file from wlan0 about 
router advertisements and soliciting an DCHPV6 lease. I used to get a number of 
those as well and I found that it was my system running its own DHCP server 
(dhcpd) on that interface as well as the main DHCP server in my router. I 
stopped the dhcpd service on the system and those all went away. Not what you 
were after but might help in other areas anyway.

 

Susan

-- 
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 
 .
For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WS-2902

[Jim Myers]

I have a Raspberry Pi 3 B+ running weewx, connecting to my router via WiFi. 
Currently I have an AcuRite system plugged into the USB. This weekend I 
will be changing to the Ambient WS-2902. Can anyone tell me how to 
configure the interceptor driver to work with the WS-2902 and my current 
Raspberry Pi network setup?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Looking for help with Oregon Scientific WMR 89

[Dani Macías Perea]

Hi Rob,

Regarding the rain faill per hour, I am not sure if what you proposed is
correct. What you are doing in your code, if I understood you correctly, is
the following:

if packet[2:4].encode('hex')!='fffe':
   Rh = None
 else:
   Rh = (256*ord(packet[2])+ord(packet[3]))*2.54/100

So in your else branch, you will always have packet[2]=ff and packet[3]=fe. Of
course, you are now getting output regarding the rain but the Rh will
always be 1664.56, isn't?

As it is not saved in DB, I don't use the Rh and have never checked its
values. I don't have neither an UV sensor, so I can't help in your second
question.



2018-04-17 11:40 GMT+02:00 'Rod Avery' via weewx-user <
weewx-user@googlegroups.com>:

> Hello all,
>
> I have been using the driver posted by fcauwe for a little while and am
> getting data through from the WMR89.
>
> I did notice that it was not reporting rain fall per hour. Looking through
> the code I found the following if statement under *def
> _wmr89_rain_packet(self, packet):*
>
>  if packet[2:4].encode('hex')=='fffe':
>Rh = None
>  else:
>
>
> Looking at the output from the WMR89 it looks like having output in the
> packet containing *fffe* means there is rain data not that there isn't
> rain data. So I modified the code to NOT EQUAL :
>
>  if packet[2:4].encode('hex')*!=*'fffe':
>Rh = None
>  else:
>
>
> I am now getting correct output with regards to rain.
>
> I have also taken Daniels suggestion and added the code from his post.
>
> On a side issue, I am getting the following:
> Apr 17 10:34:30 weatherstation weewx[27499]: wmr89: Invalid data packet
> (b3050100b9).
>
> Does anyone know what this packet is? I have a UV sensor connected so
> could it be for that?
>
> Big thank you to all involved in writing the driver for the WMR89 - Very
> helpful!
>
> Rod.
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/FxNx6am2MgM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Looking for help with Oregon Scientific WMR 89

['Rod Avery' via weewx-user]

Hello again.

Through further testing I think it is the UV sensor. 

For example: 

b3050100b8 -> ignore b3, gives 5 : 1 : 0 : 185
b3050200ba -> ignore b3, gives 5 : 2 : 0 : 186

So bit 1 always gives 5 - Could be battery status not sure
Bit 2 seems to tally with what the WMR89 is displaying on its screen
Bit 3 is always 0
Bit 4 is 184 plus bit 2

I have added the following to the driver and am getting what looks to be 
sensible readings:

def _wmr89_uv_packet(self, packet):
## 0   1   2   3   4
## b3  05  00  00  b8
## b3  05  01  00  b9
## b3  05  02  00  ba

## looks like 2 is the UV reading although 4 is 184 + UV reading at 
the moment

#Get readings from the packet to print out to syslog for testing
num1=ord(packet[1])
num2=ord(packet[2])
num3=ord(packet[3])
num4=ord(packet[4])

Send readings to the syslog
logdbg("UV1 : " + str(num1) + "  UV2 : " + str(num2) + "  UV3 : " + 
str(num3) + "  UV4 : " + str(num4))

_record = {'uv': ord(packet[2]),
   #'battery_status_uv': packet[0] >> 4,
   'dateTime': int(time.time() + 0.5),
   'usUnits': weewx.METRIC
}

return _record


To get it all working and to help people like me who have no real idea on 
how to code you'll need to add the following to the driver:

class WMR89(weewx.drivers.AbstractDevice):
"""Driver for the Oregon Scientific WMR89 console.

The connection to the console will be open after initialization"""

DEFAULT_MAP = {
'barometer': 'barometer',
'pressure': 'pressure',
...
'windchill': 'windchill',
'UV': 'uv'}

...


and in  *def genLoopPackets(self):*

 elif decode[i][0].encode('hex')=='b5':#T/Hum  OK
_record = self._wmr89_temp_packet(decode[i])
 elif decode[i][0].encode('hex')=='b3': #UV ?
_record = self._wmr89_uv_packet(decode[i])
 else:

...



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Android weather app for weeWx users

[John Burricelli]

This is working great for me.  Thank you for creating this.

https://www.warrenskywarn.org/settings.txt

On Tuesday, April 10, 2018 at 5:01:46 AM UTC-4, John Smith wrote:
>
> Just to give some background I made an android app similar to Pocket PWS. 
> I liked the app, but it was closed source so I couldn't do anything to add 
> new features.
>
> With Tom's blessing I named the app weeWx Weather App and I have published 
> it to google play 
> https://play.google.com/store/apps/details?id=com.odiousapps.weewxweather
>
> To use the app there needs to be some small changes made to weeWx, to 
> automate some of the steps needed I created a pair of weeWx extensions, one 
> for metric and one for imperial units.
>
> I've outlined the installation steps on github: 
> https://github.com/evilbunny2008/weeWxWeatherApp/wiki#concise-instructions
>
> All comments and requests about the app should go to github 
> https://github.com/evilbunny2008/weeWxWeatherApp/issues
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Any Netatmo cloud users working?

[Andrew Milner]

It may be helpful to others if you could tell us exactly what sudo 
wee_config --reconfigure does not do correctly, and what you had to then 
manually edit in weewx.conf to make weewx work correctly




On Tuesday, 17 April 2018 13:48:45 UTC+3, José-Manuel Anguita wrote:

> I think that I've found the problem.
>
> You should edit */etc/weewx/weewx.conf *manually and add the four Netatmo 
> parameters to this file. 
>
> The problem appears to be that *sudo wee_config --reconfigure* doesn't setup 
> the driver right.
>
> This worked for me.
>
> El domingo, 12 de noviembre de 2017, 0:26:14 (UTC+1), mwall escribió:
>>
>> On Saturday, November 11, 2017 at 4:23:22 PM UTC-5, Robert Brown wrote:
>>>
>>> Yes, that's what made me look up the api reference. 
>>>
>>
>> so does it work when you use .com instead of .net?
>>
>> please post the log when debug=1
>>
>> if the netatmo server is not lying to you, then a response of 400 means 
>> that the request was not structured or formatted correctly.  the url, data, 
>> and header lines from the log will tell us exactly what weewx posted.
>>
>> m
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Any Netatmo cloud users working?

[José-Manuel Anguita]

I think that I've found the problem.

You should edit */etc/weewx/weewx.conf *manually and add the four Netatmo 
parameters to this file. 

The problem appears to be that *sudo wee_config --reconfigure* doesn't setup 
the driver right.

This worked for me.

El domingo, 12 de noviembre de 2017, 0:26:14 (UTC+1), mwall escribió:
>
> On Saturday, November 11, 2017 at 4:23:22 PM UTC-5, Robert Brown wrote:
>>
>> Yes, that's what made me look up the api reference. 
>>
>
> so does it work when you use .com instead of .net?
>
> please post the log when debug=1
>
> if the netatmo server is not lying to you, then a response of 400 means 
> that the request was not structured or formatted correctly.  the url, data, 
> and header lines from the log will tell us exactly what weewx posted.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Any Netatmo cloud users working?

[José-Manuel Anguita]

It doesn't work

El domingo, 12 de noviembre de 2017, 0:26:14 (UTC+1), mwall escribió:
>
> On Saturday, November 11, 2017 at 4:23:22 PM UTC-5, Robert Brown wrote:
>>
>> Yes, that's what made me look up the api reference. 
>>
>
> so does it work when you use .com instead of .net?
>
> please post the log when debug=1
>
> if the netatmo server is not lying to you, then a response of 400 means 
> that the request was not structured or formatted correctly.  the url, data, 
> and header lines from the log will tell us exactly what weewx posted.
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Looking for help with Oregon Scientific WMR 89

['Rod Avery' via weewx-user]

Hello all,

I have been using the driver posted by fcauwe for a little while and am 
getting data through from the WMR89. 

I did notice that it was not reporting rain fall per hour. Looking through 
the code I found the following if statement under *def 
_wmr89_rain_packet(self, packet):*

 if packet[2:4].encode('hex')=='fffe':
   Rh = None
 else:


Looking at the output from the WMR89 it looks like having output in the 
packet containing *fffe* means there is rain data not that there isn't rain 
data. So I modified the code to NOT EQUAL :

 if packet[2:4].encode('hex')*!=*'fffe':
   Rh = None
 else:


I am now getting correct output with regards to rain.

I have also taken Daniels suggestion and added the code from his post.

On a side issue, I am getting the following:
Apr 17 10:34:30 weatherstation weewx[27499]: wmr89: Invalid data packet 
(b3050100b9).

Does anyone know what this packet is? I have a UV sensor connected so could 
it be for that?

Big thank you to all involved in writing the driver for the WMR89 - Very 
helpful!

Rod.



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WU Import failed

[Andre]

Gary, here again: thank you very much for your fast support!
Regards, Andre

Am Samstag, 14. April 2018 14:42:53 UTC+2 schrieb gjr80:
>
> Andre,
>
> I have not yet been able to resolve my GitHub issues so I have emailed you 
> some updated files just now.
>
> Gary
>
> On Saturday, 14 April 2018 21:15:35 UTC+10, Andre wrote:
>>
>> Gary, thanks. This sounds good and I'll waiting for your release.
>>
>> Andre
>>
>> Am Freitag, 13. April 2018 03:44:37 UTC+2 schrieb gjr80:
>>>
>>> Andre,
>>>
>>> I have reworked wee_import and have it here on my test system importing 
>>> data from your WU station without issue. Just having a few GitHub issues, 
>>> once I sort them out later today I will post some instructions for you or 
>>> failing that I will email you the updated wee_import file(s).
>>>
>>> Gary
>>>
>>> On Wednesday, 11 April 2018 21:56:08 UTC+10, Andre wrote:

 Gary, I wish you a speedy recovery.
 I know that as well. Unfortunately.

 Regards, Andre

 Am Dienstag, 3. April 2018 17:16:46 UTC+2 schrieb Andre:
>
> Hi,
>
> First I have to say I'm not Linux professional and all my 'know-how' 
> is based on reading a lot of tutorials.
>
> My weather station is a Davis Vantage Vue. WeeWX is running on a 
> Raspberry Pi 2. This setup is running and all data are fine.
>
> My problem is I can't import any data from WU with wee_import.
>
> ---log---
> wee_import --import-config=/var/tmp/wu.conf --from=2018-01-01T00:30 --
> to=2018-01-31T00:00 --dry-run
> Starting wee_import...
> Observation history for Weather Underground station 'INORDERS99' will 
> be imported.
> Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Observations timestamped after 2018-01-01 00:30:00 CET (1514763000) 
> and up to and
> including 2018-01-31 00:00:00 CET (1517353200) will be imported.
> This is a dry run, imported data will not be saved to archive.
> * radiation: cannot convert '---' to float at timestamp 
> '2018-01-01 00:30:00 CET (1514763000)'.*
>  Nothing done, exiting.
> ---log---
>
> What does it mean "radiation: cannot convert '---' to float at 
> timestamp '2018-01-01 00:30:00 CET (1514763000)'?
> Is there data mismatch on WU? What can I do to solv this issue?
>
> Regards, Andre
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Pillow + Mac OSX 10.11.X and earlier

[Alan Klein]

Just a heads up for others that are trying to install weewx on Mac OS X 
10.11.X and earlier releases and are using Pillow instead of PIL, or if you 
recently updated Pillow to 5.1.0 and use an older version of Mac OS X

There is currently an issue with the Pillow 5.1.0 release not being 
compatible with the older versions of Mac OS as it was built for Mac OS X 
10.12.
https://github.com/python-pillow/Pillow/issues/3068

The good news is that this is planned to be fixed in release 5.1.1 of 
Pillow.

Until resolved, run the following when installing Pillow to pull in version 
5.0.0 which was compatible with older versions of Mac OS X.

sudo pip install Pillow==5.0.0


Hope this helps others!

-- 
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.
For more options, visit https://groups.google.com/d/optout.