Would you mind submitting a PR so the binding can become an official part of OH ?
Thanks for your contribution.
Unfortunately it’s a lot more effort to get a binding into openHAB than just getting a binding done that works. If someone wants to work on that I’m more than happy to share what I have. It’s not in a state where it can be merged yet, so whoever wants to work on it will need to do changes.
Why dont you just publish the code you created on github - initial release - alpha - use at own risk.
Maybe we discovergy users are just few but we might be nerds 
And - support from OH commutity is great as well.
As the binding never really worked good for me (because I was on an OH version ahead or behind) I installed and configured FHEM (which has a working binding) to publish to mqtt and grabbed the values in OH. A true performance killer on RPI3 and FHEM config was a nightmare for me. So I even tried to disassemble your module to recompile and better integrate it. Spent quite a few hours on that till I realised how stupid this was.
Not sure - but maybe my time could have been spent better if your source code was public…
It doesn’t matter if you’re ahead or behind a version. Only major version jumps broke it (and I’ve released a new version soon-ish afterwards to address this).
At the moment the API is broken anyways…
1 Like
API is working.
Not yet perfect again for historical data but I get what I need
Array
(
[0] => Array
(
[meterId] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[manufacturerId] => ESY
[serialNumber] => xxxxxx
[fullSerialNumber] => xxxxxxxxxxxxxxx
[printedFullSerialNumber] => xxxxxxxxxxxx
[location] => Array
(
[street] => xxxxxxxxxxxxxxx
[streetNumber] => x
[zip] => xxxxx
[city] => xxxxxx
[country] => DE
)
[administrationNumber] => DE000xxxxxxxxxxxxxxxxxxxxx
[type] => ESY
[measurementType] => ELECTRICITY
[loadProfileType] => SLP
[scalingFactor] => 1
[currentScalingFactor] => 1
[voltageScalingFactor] => 1
[internalMeters] => 1
[firstMeasurementTime] => 1697184377595
[lastMeasurementTime] => 1698110015584
)
)
Does anyone know what energy1 and energy2 readings from api are?
I have the following fields from GET call on api at /field_names:
[
“energy”,
“energy1”,
“energy2”,
“energyOut”,
“power”,
“phase1Power”,
“phase2Power”,
“phase3Power”,
“phase1Voltage”,
“phase2Voltage”,
“phase3Voltage”
]
others get:
[
"energy",
"energyOut",
"power",
"power1",
"power2",
"power3",
"voltage1",
"voltage2",
"voltage3"
]Hi,
I also asked myself why @Flole didn’t publish the binding somewhere on any “git”-platform? It would be much easier to collaborate for who is interested in.
I’m not into openhab developing nor do I really know the underlying karaf/OSGi architecture. But the possibility to read the code makes many things much easier than dealing with a black box.
So +1 from me for publishing the code for the standalone binding, please 
1 Like
Will there be an update to use the binding in OH 4.3 ?
Hello,
Discovery changed the API URL:
EN: Important note for all API users: We still have users who access the old domain api.discovergy.com. For technical reasons, we will be changing this on 4 September 2025 so that the API redirects to api.inexogy.com. Most API clients should be able to process this transparently and continue to function without disruption. In individual cases, however, users may need to adjust their configuration from api.discovergy.com to api.inexogy.com.
DE: ein Wichtiger Hinweis für alle API-Nutzer: Wir haben immer noch Benutzer, die auf die alte Domain api.discovergy.com zugreifen. Aus technischen Gründen stellen wir das zum 4.9.2025 nun so um, dass die API hier einen Redirect auf api.inexogy.com macht. Die meisten API-Clients dürften das transparent verarbeiten und ohne Störung weiter funktionieren. In Einzelfällen kann es aber sein, dass die Benutzer dann ihre Konfiguration von api.discovergy.com auf api.inexogy.com anpassen müssen.
I’m still on 4.3 because missing 64bit OS on my Raspi.
Is it possible to change the API URL in the Discovery Binding.
Thanks
Ronald
That needs to be changed, yes…. I just noticed that the binding stopped working.
Anyone can help … open a GitHub issue with openhab-addons and if possible, provide the PR yourself.
Well not really since the binding is still closed source and only I have the source code of it 
(The reason for that is, that back when I wrote this binding it was incredibly complicated and it took a long time for a PR to be reviewed, then changes were requested and so on, so for this one I simply didn’t bother as I wrote it for myself and only decided to publish it after there were a few requests)
@Ronald_Schulz I have updated the jar file, please re-download it and overwrite the old one. The link is still org.openhab.binding.discovergy-4.0.0-SNAPSHOT.jar - FloleCloud
Thank you for the update.