-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[velux] Various bug fixes and enhancements #5833
Conversation
|
If the plan is to create an OH2 binding, that should be done in the OH2 repo. |
Yes, it will be fully OH2 compliant with a separate initialization module for dealing with things. This bug fix is necessary as OH2 calls the configuration method with a null pointer instead of an empty Dictionary. |
… vs. HouseStatusMonitoring). [binding.velux] fix: prevent invalid parameters when running under OH2 with compat layer. [binding.velux] fix: adapt library path for JSON helper library (eliminating wrning during startup). [binding.velux] fix: waiting too long when no scenes are defined. Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/velux-new-openhab2-binding-feedback-welcome/32926/130 |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/use-velux-binding-in-oh-1-x/71975/20 |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/velux-new-openhab2-binding-feedback-welcome/32926/298 |
|
Hopefully one of the maintainers is reading this: the list of changes is mentioned/updated in the initial comment. |
[binding.velux] Bugfix: HTTP/JSON communication.
[binding.velux] Bugfix: Aborting connection after sending error.
[binding.velux] Bugfix: Firmware revision properly returned.
[binding.velux] Bugfix: Close connections during binding shutdown/removal.
[binding.velux] Bugfix: String representation and handling of ip addresses.
[binding.velux] Bugfix: Invalid use of myJsonBridge eliminated in case of LAN/WLAN config.
[binding.velux] Bugfix: Initial refresh of data for item added, handling of BRIDGE_REFRESH_MSECS fixed.
[binding.velux] Bugfix: Refresh only readable items.
[binding.velux] Bugfix/enhancement: Adapted logging (more infos, less warnings).
[binding.velux] Enhancement: Comments for activation with OH2, more infos about debug settings in README, more detailed configuration in README added.
[binding.velux] Enhancement: More information during actuator state modification for debugging, more infos in loglevel trace.
[binding.velux] Enhancement: New channel timestamp.
[binding.velux] Enhancement: New channel Reload for retrieving all infos from bridge.
[binding.velux] Enhancement: Optional handling for inversed actuators.
[binding.velux] Enhancement: Eliminating usage of org.apache.commons.lang.StringUtils.isNotBlank.
[binding.velux] Enhancement: Proper handling of unknown config items.
[binding.velux] Enhancement: Provide infos about WLAN config.
[binding.velux] Enhancement: Better error handling for unknown scenes (virtual rollershutters).
[binding.velux] Enhancement: Intensive logging for recognition of Somfy devices.
[binding.velux] Enhancement: Handling bad serial numbers (Somfy).
Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
Were those somehow lost again? I see a lot of non-standard license texts and EPLv1 mentioned in them. Could you check and possibly re-run a |
I am not fully clear on what that means. As it is a 1.x binding, it must not refer to Things etc., so I do nut understand why you have added things files here and removed the binding configuration.
This PR seems to do much more that this bugfix by now... |
Unfortunatelly rhe re-run of a |
Yes, of course: Due to the [feedback] (https://community.openhab.org/t/velux-new-openhab2-binding-feedback-welcome/32926/354) of users with OH1 and OH2, this PR contains nine bugfixes and ten extensions since 16/03/2019 in addition. |
…ed for Somfy devices. Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
Thanks for this notice: Now, those files are manually adapted. |
|
Thanks for the quick update, looks much better now.
|
The separation of the binding configuration into things files originated in the strange behaviour of paperUI which does not handle this 1.x binding properly. This part of the change (which came from the adoptions towards a full 2.x binding) could be skipped as it did not resolve this issue completely. |
Yes, I would suggest this as Thing files must not be part of any 1.x binding and all configuration must be done on the binding level (as it is before this PR). |
…NF/binding/binding.xml Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
Adapted as suggested. |
kaikreuzer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, looks pretty good now!
Just 2 small comments to address, then we can merge.
bundles/binding/org.openhab.binding.velux/ESH-INF/i18n/velux_de.properties
Outdated
Show resolved
Hide resolved
… to the distribution) Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
Signed-off-by: Guenther Schreiner <guenther.schreiner@smile.de>
kaikreuzer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thank you!
|
Thanks, @kaikreuzer, a lot! |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/velux-new-openhab2-binding-feedback-welcome/32926/364 |
|
first of all, thanks for the merge of the #5833.
Sorry to bother you but after removing the ESH/things stuff the PaperUI does not provide any thing information for this compat binding. Therefore, having eliminated the bridge and thing declaration, the config-file-based configuration is the only way to handle it with PaperUI. An ideas? Best regards, Guenther |
|
That's exactly how 1.x bindings work. Note that the main feature of 2.x bindings is to bring thing & Paper UI support, which does not exist in 1.x. |
|
Hi Guenter @gs4711 — How are you getting on with your Velux OH v2 binding? In the meantime, I have migrated the v1 version of the NeoHub binding to v2, and also written a completely new v2 binding for Siemens smart thermostats. And now the only equipment in my home which is not on OH v2 are the Velux roof windows. So I have some skills, some motivation, and the test equipment (KLF200 and windows), to help you with the v1 -> v2 migration. Do you already have a beta of the v2 binding somewhere that I can play with? |
|
Hello Andrew,
the oh2 binding is about to be finished in the next days (PR#2531 has already run successfully through Jenkis).
The oh2 features like discovery are not yet stable so that I will dig deeper into it before announcing it to the list.
But, in fact, with PaperUI it already looks good to me ;-)
Regards, Guenther
Von: Andrew Fiddian-Green <notifications@github.com>
Gesendet: Donnerstag, 8. August 2019 16:38
An: openhab/openhab1-addons <openhab1-addons@noreply.github.com>
Cc: Guenther Schreiner <guenther.schreiner@smile.de>; Mention <mention@noreply.github.com>
Betreff: Re: [openhab/openhab1-addons] [Velux] Bugfixes (Empty list of items, HTTP/JSON, sending error, binding shutdown/removal, channel values) plus Enhancements (documentation, new channels timestamp+reload, optional inversed actuator values, support of Somfy d
Hi Guenter @gs4711 <https://github.com/gs4711> — How are you getting on with your Velux OH v2 binding? In the meantime, I have migrated the v1 version of the NeoHub binding to v2, and also written a completely new v2 binding for SIemens smart thermostats. And now the only equipment in my home which is not on OH v2 are the Velux roof windows. So I have some skills, some motivation, and the test equipment (KLF200 and windows), to help you with the v1 —v2 migration. Do you already have a beta of the v2 binding somewhere that I can play with?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#5833?email_source=notifications&email_token=ADDOI2FZJOWSIU6YZB2KFH3QDQVS7A5CNFSM4G657JTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD332MTA#issuecomment-519546444> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ADDOI2BAB5CP5FQ7I5YHW5LQDQVS7ANCNFSM4G657JTA> . <https://github.com/notifications/beacon/ADDOI2HVNEGIZO2HHPCNRODQDQVS7A5CNFSM4G657JTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD332MTA.gif>
|
|
I notice that PR#4416 seems also to be an OH2 binding for Velux equipment ?? - is there some coordination with that? |
The following changes are provided:
Bugfix: Handle empty list of items properly.
Bugfix: HTTP/JSON communication.
Bugfix: aborting connection after sending error.
Bugfix: firmware revision properly returned.
Bugfix: close connections during binding shutdown/removal.
Bugfix: string representation and handling of ip addresses.
Bugfix: invalid use of myJsonBridge eliminated in case of LAN/WLAN config.
Bugfix: initial refresh of data for item added, handling of BRIDGE_REFRESH_MSECS fixed.
Bugfix: refresh only readable items.
Bugfix/enhancement: adapted logging (more infos, less warnings).
Enhancement: comments for activation with OH2.
Enhancement: more information during actuator state modification for debugging.
Enhancement: new channel timestamp.
Enhancement: intensive logging for recognition of Somfy devices.
Enhancement: optional handling for inversed actuators.
Enhancement: eliminating usage of org.apache.commons.lang.StringUtils.isNotBlank.
Enhancement: proper handling of unknown config items.
Enhancement: more infos about debug settings in README.
Enhancement: more infos in loglevel trace.
Enhancement: provide infos about WLAN config.
Enhancement: more detailed configuration in README added.
Enhancement: better error handling for unknown scenes (virtual rollershutters).
Enhancement: handling bad serial numbers (Somfy).
Enhancement: reload action for retrieving all infos from bridge.