Before writing a whole new binding for these services, please make sure the information you are pulling out of them cannot be obtained using the HTTP binding with a transform (XSLT, REGEX, etc.). There are already sooo many bindings and it is difficult to keep track of, update, and maintain them all. It is actually counter productive to create new bindings that do not do anything that one can use some other binding to easily implement.
Obviously I don’t know these services but if they require special authentication to get the data from them, an API key, only support HTTPS, etc then that would make them a good candidate for a new binding. But if it is just screen scraping a public web page the HTTP binding with a transform is more appropriate. You can post your parser on the wiki in the examples section.
Also, if you do end up making a new binding, be sure to create it following the OH 2 approach. You can find out more on that on the Eclipse SmartHome project.
I will check if I can do a simple transform.
All these site have no machine-to-machine API, I parse HTML and/or images.
I used a lot of JQuery like parsing, not the kind of stuff you can do easily with a regexpr.
The goal is not to make an official binding in OpenHab repo but to advise this plugin exist and is maintained elsewhere.
For a local usage there is no need to involve the whole community.
I hope the topic and the source code will motivate other devs to integrate local service or open-data for their own usage.
Is the HTML you are parsing well formed so that XSLT transforms could be performed on it? If so, then the HTTP binding could be configured to poll and cache, so each item could use a different XSLT transform to scrape the values you want.
