-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bluetooth.hdpowerview] New binding using Bluetooth Low Energy #17099
Conversation
3a06e65
to
60b2c9b
Compare
Initial contribution Signed-off-by: Andrew Fiddian-Green <software@whitebear.ch>
7ab1bb2
to
2148126
Compare
Note: CI build is failing due to an error in 'deconz' binding. |
@jlaur can I ask your opinion concerning a dependency in this binding on a class in the other 'hdpowerview' binding's namespace? This is a bluetooth binding so it is (must be) hosted in the I am concerned about having two separate, but supposed to be identical, clones of this class, since I think there may be a maintenance issue in future if HD would introduce new shade models with different types and capabilities. I wonder if you have any thoughts about this? We could in theory put 'ShadeCapabilitiesDatase' in a common feature so that both bindings could use it. But I am not sure then how that feature would be distributed or loaded? => WDYT? EDIT one solution would be for this binding EDIT 2 .. or I could use Maven to copy the Java file over during the build process.. EDIT 3 .. the last commit is using Maven to copy the shade capabilities database file prior to compiling the jar. |
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
@lsiepel .. |
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.
Found some last moment issues.
bundles/org.openhab.binding.bluetooth.hdpowerview/src/main/resources/OH-INF/thing/thing.xml
Show resolved
Hide resolved
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
Signed-off-by: AndrewFG <software@whitebear.ch>
Failed tests are not related. |
@lsiepel do I need to change something in the Hue binding? |
No it is fixed by upgrading jmdns in another PR. It should all be good. Now, you could add your binding's logo to the openHAB website. See https://next.openhab.org/docs/developer/addons/#add-your-add-on-s-logo-to-the-openhab-website-and-the-ui |
|
…ab#17099) * [bluetooth.hdpowerview] initial contribution Signed-off-by: AndrewFG <software@whitebear.ch>
…ab#17099) * [bluetooth.hdpowerview] initial contribution Signed-off-by: AndrewFG <software@whitebear.ch> Signed-off-by: Patrik Gfeller <patrik.gfeller@proton.me>
…ab#17099) * [bluetooth.hdpowerview] initial contribution Signed-off-by: AndrewFG <software@whitebear.ch>
…ab#17099) * [bluetooth.hdpowerview] initial contribution Signed-off-by: AndrewFG <software@whitebear.ch>
Resolves #16992
HD Powerview Gen 3 shades can be monitored/controlled either via a Gateway (over IP) or directly via Bluetooth Low Energy (BLE). The OH HD Powerview binding currently only supports the former. This PR adds a new binding that supports the latter.
Signed-off-by: AndrewFG software@whitebear.ch