I’ve forked the OilFox binding from here. Many thanks to the author for his work. Unfortunately, there hasn’t been an update to current APIs in 6 years.
I adapted the fork to the current OpenHAB API and the new Oilfox API. These are the informations provided by the new OilFox API (German screenshot):
You can find the OilFox binding on GitHub.
If you want to build the binding yourself use the Branch 4.3.x for openHAB 4.3.x and the branch master for openHAB 5.0.0.
You can download the .jar file from GitHub Releases (sorry, as a new user I am only allowed to post max 2 links) .
If you encounter any issues with the binding, please enable debug log in Karaf console log:set DEBUG org.openhab.binding.oilfox
and post the debug log as new issue on GitHub.
There are no private data (email…) in the log.
Hello Thomas, this sounds great! I will test it soon since some years i am runing on this solution Fox Oil Sensor - Curl API ... How?
It works well reading the data once a day.
Best regards
Hello Simon,
I had a bash script that set the items once a day via the REST API. It worked, but it wasn’t already integrated.
You can test in parallel with the Curl API. My binding handles it if the tokens becomes invalid due to access from another application with the same user.
Best regard
Thomas
Are there any documentation how the build from marketplace works ?
I installed my binding from marketplace on OH4 and OH5. On OH5 it worked but on OH4 the binding are not loaded.
2025-05-05 16:25:56.143 [WARN ] [rketplace.MarketplaceBundleInstaller] - The marketplace bundle was successfully installed but doesn’t start: Could not resolve module: org.openhab.binding.oilfox [269]
Unresolved requirement: Import-Package: com.google.gson; version=“[2.11.0,3.0.0)”
openhab> bundle:list | grep OilFox
269 x Installed x 80 x 5.0.0.202505041734 x openHAB Add-ons :: Bundles :: OilFox Binding
I fixed it for OH4 by removing the download link for the OH5 jar file.
Is it not possible to provide different jar files for OH4 and OH5 ?
Right now, you have to create separate posts for different versions of the binding. You’ll notice most of the posts have a version range as part of the title: (e.g. [4.0.0;5.0.0)). This controls which versions of OH “see” the post . You’ll need to create one post for OH 4 and another for OH 5 and set the version ranges for each.