Aercus WS3083 - is it ws type 3080 or 1080?

290 views
Skip to first unread message

Pavel Reich

unread,
Feb 22, 2015, 1:10:26 PM2/22/15
to py...@googlegroups.com
Hello,

I ordered two days ago and received today weather station AERCUS WS3083 http://www.amazon.co.uk/gp/product/B00C9MFQ1A?ref_=tnp_email_TE_AMZLdp_1
and it seems to work in general, I first tried it with my windows laptop using Cumulus program that reported to wunderground rainfall/solar/light. Then I connected the station to my raspberry pi, but I'm not sure what ws type to use.
For 1080 it reports
17:57:09:pywws.LiveLog:'illuminance'
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pywws/LiveLog.py", line 84, in LiveLog
    hourly_data, daily_data, monthly_data)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 721, in Process
    start = generate_hourly(logger, calib_data, hourly_data, start)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 585, in generate_hourly
    acc.add_raw(data)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 271, in add_raw
    self.retval[key] = data[key]
KeyError: 'illuminance' 

for 3080
it also fails
18:02:01:pywws.weather_station:old data {'status': 0, 'hum_out': 95, 'wind_gust': 6.5, 'uv': 0, 'wind_ave': 3.4000000000000004, 'rain': 7.5, 'temp_in': 21.400000000000002, 'illuminance': 0, 'abs_pressure': 993.4000000000001, 'delay': 0, 'hum_in': 52, 'temp_out': 5.7, 'wind_dir': 14}
18:02:01:pywws.weather_station:new data {'status': 0, 'hum_out': 95, 'wind_gust': 4.1000000000000005, 'uv': 0, 'wind_ave': 1.7000000000000002, 'rain': 7.5, 'temp_in': 21.3, 'illuminance': 0, 'abs_pressure': 993.7, 'delay': 0, 'hum_in': 52, 'temp_out': 5.800000000000001, 'wind_dir': 6}
18:02:01:pywws.weather_station:delay 0, pause 0.5
18:02:02:pywws.weather_station:avoid 5.77534294128
18:02:08:pywws.weather_station:live_data new ptr: 000538
18:02:09:pywws.DataLogger:5 catchup records
18:02:09:pywws.Process:Generating summary data
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:02:00 0:13:56
18:02:09:pywws.Process.HourAcc:2015-02-22 17:02:00 rain reset 5.1 -> 3.9
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:16:00 0:14:00
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:19:00 0:03:00
18:02:09:pywws.Process.HourAcc:2015-02-22 17:19:00 rain reset 16.2 -> 6.0
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:41:00 0:02:00
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:48:04 0:05:04
18:02:09:pywws.Process.HourAcc:2015-02-22 17:48:04 rain reset 7.2 -> 0.0
18:02:09:pywws.Process:unexpected data interval 2015-02-22 17:53:04 0:03:00
18:02:09:pywws.Process.HourAcc:2015-02-22 17:57:04 rain jump 0.0 -> 7.5
18:02:09:pywws.LiveLog:'illuminance'
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pywws/LiveLog.py", line 84, in LiveLog
    hourly_data, daily_data, monthly_data)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 721, in Process
    start = generate_hourly(logger, calib_data, hourly_data, start)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 585, in generate_hourly
    acc.add_raw(data)
  File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line 271, in add_raw
    self.retval[key] = data[key]
KeyError: 'illuminance'

What am I doing wrong and how can I fix it?


Thanks and thanks for the software, the alternative raspberry pi+pywws is so much better!

Regards,
Pavel.

Jim Easterbrook

unread,
Feb 22, 2015, 1:33:52 PM2/22/15
to py...@googlegroups.com
On 22/02/15 18:10, Pavel Reich wrote:
>
> I ordered two days ago and received today weather station AERCUS
> WS3083 http://www.amazon.co.uk/gp/product/B00C9MFQ1A?ref_=tnp_email_TE_AMZLdp_1
> and it seems to work in general, I first tried it with my windows laptop
> using Cumulus program that reported to wunderground
> rainfall/solar/light. Then I connected the station to my raspberry pi,
> but I'm not sure what ws type to use.

The console pictured on your Amazon link includes a "light" display, so
(assuming this actually works) it should be a 3080 type.

> For 1080 it reports
> 17:57:09:pywws.LiveLog:'illuminance'
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/dist-packages/pywws/LiveLog.py", line
> 84, in LiveLog
> hourly_data, daily_data, monthly_data)
> File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line
> 721, in Process
> start = generate_hourly(logger, calib_data, hourly_data, start)
> File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line
> 585, in generate_hourly
> acc.add_raw(data)
> File "/usr/local/lib/python2.7/dist-packages/pywws/Process.py", line
> 271, in add_raw
> self.retval[key] = data[key]
> KeyError: 'illuminance'

It appears that it's trying to process data that has been captured in
3080 mode so includes illuminance and UV data, but it isn't expecting it
because you've set it to 1080 mode.
I think it's now got the opposite problem, but I can't be sure.

As the station still has all its logged data (I assume) I think it's
probably best to clear your data (back it up to somewhere else) but keep
weather.ini. Set the type to 3080, then run 'python -m pywws.LogData
data_dir' to get all the data with the correct 3080 type interpretation.
http://pythonhosted.org/pywws/en/html/api/pywws.LogData.html

If that worked OK, run 'python -m pywws.Process data_dir' to generate
all the summary data.
http://pythonhosted.org/pywws/en/html/api/pywws.Process.html

If that all worked, start up live logging again.
--
Jim Easterbrook <http://www.jim-easterbrook.me.uk/>

Pavel Reich

unread,
Feb 22, 2015, 4:44:11 PM2/22/15
to py...@googlegroups.com
Thanks, now it doesn't fail in the same way. However I can see it has problems uploading to underground, underground_rf is fine however.
I get the extended Unexpected error message after I modified prepare_data function in toservice.py 
      prepared_data = dict()
        try:
          prepared_data = eval(data_str)
        except:
          print "Unexpected error:", data_str, sys.exc_info()[0]

21:39:09:pywws.Process:monthly: 2015-01-31 21:00:00
21:39:09:pywws.Template:Unknown processing directive: #illuminance  "'solarradiation' : '%.2f'," "" "illuminance_wm2(x)"#
Unexpected error: {
'dateutc'        : '2015-02-22 17:57:04','winddir'        : '135','windspeedmph'   : '3.80','windgustmph'    : '9.84','humidity'       : '95','tempf'          : '42.1','baromin'        : '29.6274', <type 'exceptions.SyntaxError'>
21:39:12:pywws.ToService(underground):action=updateraw&softwaretype=pywws&ID=ILONDON422&PASSWORD=mypassword
21:39:13:pywws.ToService(underground):<b>RapidFire Server</b><br><br>
21:39:13:pywws.ToService(underground):<b>usage</b><br>
21:39:13:pywws.ToService(underground):action [action = updateraw]<br>
21:39:13:pywws.ToService(underground):ID [ID as registered by wunderground.com]<br>
21:39:13:pywws.ToService(underground):PASSWORD [PASSWORD registered with this ID]<br>
21:39:13:pywws.ToService(underground):dateutc - [YYYY-MM-DD HH:MM:SS (mysql format)]<br>
21:39:13:pywws.ToService(underground):winddir - [0-360]<br>
21:39:13:pywws.ToService(underground):windspeedmph - [mph]<br>
21:39:13:pywws.ToService(underground):windgustmph - [windgustmph ]<br>
21:39:13:pywws.ToService(underground):humidity - [%]<br>
21:39:13:pywws.ToService(underground):tempf - [temperature F]<br>
21:39:13:pywws.ToService(underground):rainin - [rain in]<br>
21:39:13:pywws.ToService(underground):dailyrainin - [daily rain in accumulated]<br>
21:39:13:pywws.ToService(underground):baromin - [barom in]<br>
21:39:13:pywws.ToService(underground):dewptf- [dewpoint F]<br>
21:39:13:pywws.ToService(underground):weather - [text] -- metar style (+RA) <br>
21:39:13:pywws.ToService(underground):clouds - [text]  -- SKC, FEW, SCT, BKN, OVC<br>
21:39:13:pywws.ToService(underground):softwaretype - [text] ie: vws or weatherdisplay<br>
21:39:13:pywws.ToService(underground):None

Jim Easterbrook

unread,
Feb 22, 2015, 5:14:10 PM2/22/15
to py...@googlegroups.com
On 22/02/15 21:44, Pavel Reich wrote:
> Thanks, now it doesn't fail in the same way. However I can see it has
> problems uploading to underground, underground_rf is fine however.
> I get the extended Unexpected error message after I modified
> prepare_data function in toservice.py
> prepared_data = dict()
> try:
> prepared_data = eval(data_str)
> except:
> print "Unexpected error:", data_str, sys.exc_info()[0]
>
> 21:39:09:pywws.Process:monthly: 2015-01-31 21:00:00
> 21:39:09:pywws.Template:Unknown processing directive: #illuminance
> "'solarradiation' : '%.2f'," "" "illuminance_wm2(x)"#

This suggests your data doesn't have illuminance values, so the template
processing fails. I don't understand why underground_rf worked though,
except it's using new data whereas this might be catching up with old data.
Reply all
Reply to author
Forward
0 new messages