Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

[Velux] Add support for KLF200 firmware v2 #5690

Merged
merged 5 commits into from
Feb 16, 2019
Merged

[Velux] Add support for KLF200 firmware v2 #5690

merged 5 commits into from
Feb 16, 2019

Conversation

gs4711
Copy link
Contributor

@gs4711 gs4711 commented Oct 31, 2018

The Velux 2.x firmware provide full access to any IO-Home compatible devices not limited to Velux and includes an important feature: It is now possible to manipulate the settings of any IO-Home controled device explicitely without the previous scene definition.

@9037568 9037568 changed the title [velux] Support for KLF200 firmware v2 added [Velux] Add support for KLF200 firmware v2 Nov 25, 2018
@openhab-bot
Copy link
Collaborator

This pull request has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/velux-oh1-binding-with-full-control-of-any-io-home-controled-device-beta-tester-wanted/55434/2

@openhab-bot
Copy link
Collaborator

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/90

@mira2000
Copy link

mira2000 commented Jan 2, 2019

Binding updated:

  • functionality: full support and both Velux firmware versions v1 and v2
  • update: support for openhab1-addons 1.14.0-SNAPSHOT
  • update: copyright adapted for new year
  • fixed: memory leak within product refresh
  • fixed: length of serial numbers

@9037568
Copy link
Contributor

9037568 commented Jan 4, 2019

A few brief comments while I continue to review...

All classes should have @author and @since attributes
public code units can't be changed to private
public code units can't be removed, but need to be marked as deprecated
all code needs to be run through the Eclipse formatter

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 4, 2019

thanks for the quick response. Some questions regarding your comment:

(a) Refering to discussion Usage of @since tags in JavaDocs I was not aware about the @since attribute. Shall I re-introduce it within any file?

(b)+(c) question: due to the new functionality of the Velux bridge, the code has got many changes due to restructuring for supporting two different protocols. Is your comment regarding compatibility to the latest version - or do I miss your point?

(d) Yes, every code segment has gone through the Eclipse formatter. But there are special settings (i.e. 4 spaces instead of tabs) coming from the OH2 guideline.

@9037568
Copy link
Contributor

9037568 commented Jan 5, 2019

I wasn't aware of the change in recommendation surrounding @since. Thanks for the pointer.

Many changes: no problem. Destroying public code: problem. You need to preserve the existing public units and mark them deprecated.

The formatting is improved with your latest push. But there are still a number of changes when the Eclipse formatter is run on the code base.

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 5, 2019

Regarding "Destroying public code: problem": will have to check the refactoring against thr recent version.

Regarding formatting: sorry for the inconvenience - could you please give me a clue (any pointer appreciated!) how to check it on my own?

BTW there is a problem (dangling constraints) with the Eclipse openHAB installer with the lastest version - do you know where to mention?

@9037568
Copy link
Contributor

9037568 commented Jan 8, 2019

Regarding formatting: sorry for the inconvenience - could you please give me a clue (any pointer appreciated!) how to check it on my own?

All this should take is a Source -> Format in Eclipse.

BTW there is a problem (dangling constraints) with the Eclipse openHAB installer with the lastest version - do you know where to mention?

I'd start in the forum, probably.

@9037568
Copy link
Contributor

9037568 commented Jan 16, 2019

Looks like you committed some files outside of the Velux binding. You'll need to remove those changes.
I hope to finish this review in the next couple of days...

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 20, 2019

Looks like you committed some files outside of the Velux binding. You'll need to remove those changes.

Hopefully fixed. In addition, the new year is set again within the copyrights.
But, now, some new issues with the OSGI-INF occur....

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 20, 2019

But, now, some new issues with the OSGI-INF occur....

due to tabulator instead of spaces... fixed.

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 20, 2019

sigh, now, an error occurs within the official part of the openHAB Weather Binding....

@9037568
Copy link
Contributor

9037568 commented Jan 20, 2019

sigh, now, an error occurs within the official part of the openHAB Weather Binding....

You don't need to worry about those.

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 21, 2019

What about the new copyright statements (EPLv1 towards EPLv2)? Is this considerable as well?

@9037568
Copy link
Contributor

9037568 commented Jan 22, 2019

As far as I know, there's no need to do anything with EPL either.

Copy link
Contributor

@9037568 9037568 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't forget to remove the extraneous changes to files outside the Velux binding.

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 24, 2019

Thank you, Chris, @9037568, for the intensive review and feedback. I do really appreciated your heavy work on it!

All but six comments are resolved now: Next commit/push will still include the trailing three comment lines in most of the file like

/**
 * end-of-VeluxProductReference.java
 */

which will be eliminated in all files in the additional push following.

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 24, 2019

As last time, the openHAB Weather Binding prevented the full run of Jenkins:

16:14:37 [INFO] openHAB Weather Binding ............................ FAILURE [ 0.824 s]

Shall I eliminate this binding for the time being from pom.xml ?

@gs4711 gs4711 closed this Jan 25, 2019
…ub: gs4711).

Integrated code harmonisation (thanks to @9037568 for the intensive review and feedback).
Removal of any trailing three comment lines.
@gs4711 gs4711 reopened this Jan 25, 2019
Copy link
Contributor

@9037568 9037568 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few final changes.
Also, please run the Eclipse formatter again after changes are completed. Thanks!

@gs4711
Copy link
Contributor Author

gs4711 commented Jan 28, 2019

And completely run through Eclipse 2018-09 formatter. Thanks!

@gs4711
Copy link
Contributor Author

gs4711 commented Feb 4, 2019

A few final changes.

Hello Chris, is there anything I still should address?

@openhab-bot
Copy link
Collaborator

This pull request has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/velux-oh1-binding-with-full-control-of-any-io-home-controled-device-beta-tester-wanted/55434/6

@9037568
Copy link
Contributor

9037568 commented Feb 11, 2019

Hello Chris, is there anything I still should address?

I need to make one more pass through to review your latest changes.

@9037568 9037568 merged commit 9b9a344 into openhab:master Feb 16, 2019
@9037568
Copy link
Contributor

9037568 commented Feb 16, 2019

Thanks, @gs4711 !

@9037568 9037568 added this to the 1.14.0 milestone Feb 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants