Hi all, thanks for the excellent job you are doing on this binding.
I have a simple question , do we have any chance to have this working with K4500 Gateway in the future ? My system is based on this and now the only way I have is to pass via Alexa.
I don’t know if port 20000 is correct (I left it by default) and also the password 12345 … I’m not aware of any password on my K4500 Gateway.
I left Discovery by Activation in OFF.
Shall I conclude that K4500 is not compatible with this ?
Hallo,
a new milestone version of OH 3.0 is out today (3.0.0.M5) with some bugfixings for the official OpenWebNet binding that were already integrated in 3.0.0.M4 (see M4 release notes for a list).
The same bugfixes have been backported so they will be available in OH 2.5.11 too (not released yet).
Here I give you some information for the near future of the OpenWebNet binding:
the old unofficial (beta/testing) version of the binding, after popular demand, will be released in a final version with no expiration limit: it will probably be named 2.5.0.TESTING.
This unofficial version will not be supported in any way in the future, will not be ported and will not work with OH3
the official 2.5.x version will receive backports of bugfixes, but no new features/enhancements (this is a policy that OH maintainers apply for all 2.5.x bindings)
for the official 3.0 version I am involving other volunteers to help develop it further
To know which features are most important for you, I invite you to respond to the following polls (will close the polls in 1 week).
Ciao,
Massi
POLL 1 - Which missing feature do you consider more useful for the official OpenWebNet binding (OH3) ? (max 3 selections, only Basic+ community users can answer)
POLL 2 - Regarding OH and the OpenWebNet binding, what is your plan for the near future (next 6 months)? (max 2 selections, only Basic+ community users can answer)
will stay with OH2 and the unofficial (testing) binding
will move to OH3 and the official binding, but only when feature XYZ will be supported
will move to OH3 and the new official binding ASAP, even if not all feature are supported yet
Yes, I have read several discussion about that and I trust this is the only way.
I anyhow make it difficult to understand why the Gateway BUS cannot be intercepted before to go in the cloud; at the end this is connected to an IP of the same network shared by OH.
May be this is related to the fact that Legrand is not sharing the gateway ICD and this induce the job to become very complicate.
Hey guys great work on the binding so far.
I would really like to control the f502 amplifiers.
Is there any way i can contribute?
Programming is something i do on a regular base but the whole openhab system is still a little bit unknown to me. Long story short, with some guidance, i would like to setup the sound system for this binding. I have the complete bticino myhome so i can test those things as well.
Hallo Rocky and welcome to the community.
I suggest to start having a look to the OH developers documentation and start setting up the Dev environment, and test one of the bindings.
the first thing I would try is to change the tag from [“Blinds”] to [“PercentageController.percentage”] and control the shutter by telling alexa the percentage of closure (e.g. “Alexa set the shutters to 0%” for a full open and “Alexa set the shutters to 100%” for a full close.
As you can see OH 2.5.11 is out: it includes some bugfixes for the openwebnet binding related to dimmer lights mgmt and the USB Zigbee part.
I want to encourage you to respond to the 2 polls about new features for the official openwebnet binding: that’s an opportunity to express what is more important for you and should be prioritized.
I think 23 answers are not enough: there are many more users using the binding!
setup the 2.5.11 , then all of my F521 aren not initialized :
OpenWebNet BUS/SCS Energy Management Central Unit. BTicino models: F521 .
back to 2.5.10.jar all run fine
Energy Management is not supported by official v2.5.10-11, see: https://www.openhab.org/addons/bindings/openwebnet/.
And it will never be: at this point new features for the official openwebnet binding are only possibile to be added in OH v3.0.x.
You can vote in the polls if you are interested, and add a new issue for this here