Hello Matthew, I went ahead and started with the IP100 driver as a guide as after all the suggestions, there really wasn't a better one to start with. Before even asking, I'd looked through the source of a number of drivers but found that none of the drivers that ship with WeeWX use XML as an input as they are all much more low level.
Instead of taking the easier approach as you suggested, I dove in and went the harder route porting it to Python3/WeeWX4 at the same time as migrating the driver. At this point, I'm probably 80% done. Just discovered I misunderstood how the mapping works from the station and implemented it myself instead of using the logic in the constructor that also handles mapping from the weewx.conf file. As the input XML has over 50 values (many are aggregates), I wanted to only return the relevant ones which is less than 20 but now I'll simplify the parsing to return a dictionary that's more or less what's in the XML file. If all goes well, I hope to be able to run stand-alone against test input files soon. Thanks for the help, -Bill On Saturday, February 22, 2020 at 9:11:26 AM UTC-5, mwall wrote: > > bill, > > i would suggest that you start with weewx3 and python2, and use the ip100 > driver as a guide. > > it is trivial to update the ip100 to python3/weewx4 compatibility > > and by the time you are ready for that, weewx4 should be out of beta, so > your upgrade path will be painless > > (i would do the ip100 update right now, but i've got to take care of some > installer issues for the weewx4 release) > > m > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/12ec5fdc-e6e8-4c5e-a98f-5bb14fde4052%40googlegroups.com.
