weewx

[Graham Eddy]

as an experiment to test ease of migration, i installed weewx, copied my wview-archive.sdb to weewx.sdb and ran it.

looks like old wview values might upset weewx...

pebble:weewx $ ./bin/weewxd weewx.conf

Traceback (most recent call last):e: 2009-08-07 14:30:00 AEST (1249619400)

  File "./bin/weewxd", line 64, in <module>

    weewx.engine.main(options, args)

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 865, in main

    engine = engine_class(config_dict)

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 77, in __init__

    self.loadServices(config_dict)

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 141, in loadServices

    self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 491, in __init__

    self.setup_database(config_dict)

  File "/Users/Shared/weewx/bin/weewx/engine.py", line 604, in setup_database

    _nrecs, _ndays = dbmanager.backfill_day_summary() # @UnusedVariable

  File "/Users/Shared/weewx/bin/weewx/manager.py", line 1437, in backfill_day_summary

    day_accum.addRecord(rec, weight=weight)

  File "/Users/Shared/weewx/bin/weewx/accum.py", line 242, in addRecord

    func(self, record, obs_type, add_hilo, weight)

  File "/Users/Shared/weewx/bin/weewx/accum.py", line 301, in add_value

    self[obs_type].addSum(val, weight=weight)

  File "/Users/Shared/weewx/bin/weewx/accum.py", line 88, in addSum

    self.sum     += val

TypeError: unsupported operand type(s) for +=: 'float' and 'unicode'

____________

Graham Eddy

[Chris Alemany]

Thank you for looking into this.  I am also considering the switch as there appear to be a few compatibility issues cropping up in wview as other software is updated.

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

[Jeff]

Graham - I like this idea.   It looks like support for wview is gone.  Please keep us posted, and I may attempt the same.

Jeff

[Chris Alemany]

One thing that seems to be missing from weewx currently is support for a serial-server.  Perhaps I am the only person in the world who actually used this feature in wview though, I don’t know. :+). But I do hope a reasonable workaround is out there.

Cheers,

Chris

On Nov 17, 2017, at 8:52 AM, Jeff <blu...@gmail.com> wrote:

Graham - I like this idea.   It looks like support for wview is gone.  Please keep us posted, and I may attempt the same.

Jeff

[Alan Jackson]

Have the weewx folks fixed/avoided the usb port failure problem?

--

| Alan K. Jackson            | To see a World in a Grain of Sand      |

| al...@ajackson.org          | And a Heaven in a Wild Flower,         |

| www.ajackson.org           | Hold Infinity in the palm of your hand |

| Houston, Texas             | And Eternity in an hour. - Blake       |

[mongoose]

Chris - I have been watching this thread with interest.  By serial-server do you mean a terminal-server?  i.e. serial to ethernet bridge?  If so, there are two of us out there :)

It may be time for me to start looking at this too.

--Joe

[Chris Alemany]

That I don’t know.

I am using a serial server, which ended up working just fine in WeeWX… it just wasn’t obvious from the outset that it was supported, but it is there.

[Chris Alemany]

Yes, to be clear, I am using the GW21E Serial Server as outlined in the wview Manual.  It has served me very well, and it now continues to without any change needed under weewx.

Cheers,

Chris

[mongoose]

Chris,

Interesting.  Thanks.  I was using one from lantronix for many years until it died.  I am now using one from Moxa (I use many of them at work) and it operates very well.  Since this topology works "out of the box" with weewx then it is time for me to stand a separate server and proto this.

Thanks for doing the leg work on this one as I too could not see from the weewx doc that this was supported.

It does cause me pain to consider this as WView has served me incredibly well for over 10 years.  WView ran on Unix at a time when all you could find were Windows based products.  Its stability is a testament to Mark.  I do hope all is well with him.

If you have any other tips to share about your migration, I am all ears.

Thanks again.

--Joe

[Chris Alemany]

Joe,

No problem.  Yes, just look for the IP address options when you are doing your initial configuration of the weewx service and it will all work much like it does with wview.

Weewx is a big change in terms of architecture, the python structure really does allow for a huge amount of simple, though not non-trivial, customization.  There are some gaps in terms of direct compatibility with what wview allowed me to do (like spit out a complete list of all parameters into a file) without much work.  But it’s just a learning curve and I can see a much brighter future with weewx.

I too appreciate wview’s yeoman service.  It served me for 12 years, on multiple platforms, really without fail.  It is an extremely robust system.  I had my differences with Mark over time, but always respected the quality he demanded of his product.  I hope he is well, and he should be proud of his contribution to the global amateur weather scene. 

Cheers,

Chris

[Jim Bradbury]

Chris, et al,

I second your comments about the quality of Mark's work and his contribution. 

I just switched from wview to weewx when my system hardware main board crashed a little over a month ago. Chris, if you get some code to work to write a parameters.txt file, I'd appreciate a copy. I have scripts that I wrote using that file on my wview platform that I can't use now.  I'm also having problems getting php to work in weewx. I don't know if I have a bad php configuration or if the python pre-processing of the web page is messing with php, but the php that worked in wview doesn't work for me now in weewx.

-= Jim =-

[jfiddler]

Serial servers (as in a socket connection from the computer running weewx to a serial-ethernet converter) is supported, though not well documented.  I'm using an original VantagePro, with the console connected to a lantronix serial-ethernet converter, and it works fine. Check out the weewx user group forum for details.

Also, I think that import of your full wview db is still supported, though I had a bit of trouble with mine of about 15 years.  I think I'll get it across when I have a couple hours to figure out what the prob is.

[Tom Keffer]

Graham,

I just saw this message (I don't check the wview group very often these days).

This problem is usually caused by editing the sqlite database with a visual editor, then deleting a datum. Rather than inserting a NULL value, the editor inserts a null string. Hence the type incompatibility. It's basically a schema problem: a string has been inserted where a number was expected.

Fortunately, it's easily fixed using the weeWX utility wee_database with the --check-strings and --fix-strings options.

I concur about Mark's efforts. He is a pioneer. Long before IoT became a household abbreviation, he made it easy to put your station on the web. 

-tk

[Graham Eddy]

thanks, i shall investigate. i do vaguely recall using sqlitebrowser 7-8 years ago to fix something in the database

mark teel is a hero for open weather station software. it is the IBM OS/360 equivalent - 24/7 reliable, bullet proof, scarey to fiddle under the hood.

everything else at the time was shallow, closed, for-sale, windoze-based, fragile stuff (*ahem* i was using VWS on windoze with custom power supplies until 2005 - that was as good as windoze platform permitted)

weewx is the next generation of wview. it even uses same database schema.

the extensible architecture reflects a lot of learnings since wview was created. (i have a lot of customisations to re-implement…)

weewx is much slower, uses a lot more memory, but hardware performance has increased dramatically since wview introduction

and easy flexibility is a much bigger factor now, with the new hardware making that feasible

i might not have looked closely enough to see it, but i would like to see mark teel included in the copyrights for weewx

____________

Graham Eddy

[mongoose]

Graham,

  I can confirm that on my dev instance of weewx, I was able to import my wview database cleanly without any errors by just coping the database over.  weewx took about 4min to generate monthly and yearly archive reports from the data.  My database goes back to Feb 2006 so there is a good amount of data there.

  I have played with a few of the skins and I kind of like what I see.  Steel Series is there and looks pretty good.  I need to get over to that group and post a question concerning CPU load when running the real time gauge extension.  But other than that it seems to run well.  I also like a skin called exfoliation.

  I love to see that you describe "windoze" properly  :)

  I breaks my heart to consider leaving view behind.  12 years of reliable service.  Thank you again Mark.  With OS vulnerabilities requiring frequent patching, it is harder to keep wview running, still I just cannot seem to pull the trigger and go live....

--Joe

[Jeff]

I can also confirm that the database comes over cleanly.   I'm ready to switch, but having trouble with the alarm features of wview.  Any pointers?

Type = DayRain

Upper Bound = Yes

Threshold = .1

Abatement = 86400

Alarm execute = /etc/wview/alarms/dayrain (a shell script)

[Graham Eddy]

i’m no help as yet.

i am still banging my head against steelseries customisations i require (gauges for other data, some external to vp2) - i’ve been “nearly there” for several days now, river depth gauge still doing odd things...

after which i have to look how to provide the data steelseries needs from weewx. some from extra vp2 sensors, some external to vp2 with separate db.

then i’ll worry about cleaning up my wview db to be compatible with weewx

then my steel skin for all the other graphs, which is a total css and html re-write

and i need more than the 10 alarms wview offered

please note: i have a massive amount of customisations. most people have no customisations necessary, just a tweak of the config. don’t let me put people off who have standard configuratiions!

in the meantime, wview chugs along, reliable as ever...

____________

Graham Eddy

[Graham Eddy]

note: yes i have been using steelseries gauges for some years on wview, but that was before weewx and wview support, so it was customised to the billy-o from an early base (subsequently rolled into wview as a skin by a kind developer). i am now working from the latest version which supports wview and weewx to re-implement all my old changes for weewx

____________

Graham Eddy

[Robert M. Jones]

After following this thread, I also bit the bullet and switched from wview to weewx. I have been running wview since 2007 and had over 10 years of archive data. It has been a good run with wview and my hat is off to Mark Teal for his work. The database switch was easy, just copied wview-archive.sdb  to weewx.sdb. I installed the Steel Series Gauges via the wee-extension utility. That only left my Carter Lake/Saratoga web pages which were highly modified. I discovered the wee-extension WD which produces a testtags.php (vs WVtags.php). I only had to change Settings-Weather.php to reference testtags.php instead of WVtags.php. I also had to edit weewx.conf to specify US units instead of metric. I am currently sending data to wunderground, CWOP, and PWS. The site is http://www.w4lcs.com

Bob

  File "/Users/Shared/weewx/bin/ weewx/engine.py", line 865, in main

    engine = engine_class(config_dict)

  File "/Users/Shared/weewx/bin/ weewx/engine.py", line 77, in __init__

    self.loadServices(config_dict)

  File "/Users/Shared/weewx/bin/ weewx/engine.py", line 141, in loadServices

    self.service_obj.append( weeutil.weeutil._get_object( svc)(self, config_dict))

  File "/Users/Shared/weewx/bin/ weewx/engine.py", line 491, in __init__

    self.setup_database(config_ dict)

  File "/Users/Shared/weewx/bin/ weewx/engine.py", line 604, in setup_database

    _nrecs, _ndays = dbmanager.backfill_day_ summary() # @UnusedVariable

  File "/Users/Shared/weewx/bin/ weewx/manager.py", line 1437, in backfill_day_summary

    day_accum.addRecord(rec, weight=weight)

  File "/Users/Shared/weewx/bin/ weewx/accum.py", line 242, in addRecord

    func(self, record, obs_type, add_hilo, weight)

  File "/Users/Shared/weewx/bin/ weewx/accum.py", line 301, in add_value

    self[obs_type].addSum(val, weight=weight)

  File "/Users/Shared/weewx/bin/ weewx/accum.py", line 88, in addSum

    self.sum     += val

TypeError: unsupported operand type(s) for +=: 'float' and 'unicode'

____________

Graham Eddy

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

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

[Graham Eddy]

steelseries: because i am having to walk through most lines of the code, found three bugs so far, none major (all relating to changing units)

____________

Graham Eddy

[Alan Jackson]

Well, I did the switch. It was quite easy, really. I have documented my experience on http://www.adelieresources.com

The largest task I set myself was cleaning up the database first. I found a few surprises there.