-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use loxone knx/eib elements in openhab #9
Comments
Could you tell what functional blocks you are trying to operate (e.g. eib blinds)? There is nothing about knx in Loxone api documentation. I suspect these blocks are visible as regular other blocks, but we need to see in practice. I don’t have knx in my installation, so appreciate your help. |
Hi, I also use Loxone to control my KNX components. eg The dimmer This is the JSON element:
|
@xeobit this is not documented in the API at all. It looks like it may be similar to regular dimmer, but there are no min/max/step states to indicate the boundaries of the dimmer. Do you know how they are determined? In case of a regular dimmer, they are needed to map the OH standard dimmer range of 0-100 to the range that Loxone understands. |
I'd be interested in the EIBDimmer as well, cause I used i frequently and it be great to have it in openhab. |
@ge-ger can you give a try for this test jar: https://www.dropbox.com/s/6kzb00w4trttmod/org.openhab.binding.loxone-3.1.0-2-SNAPSHOT.jar?dl=0 |
@ppieczul I've replaced the original .jar with the one provided and restarted openhab. Unfortunately there's no changed behaviour. |
First thing to check is that the new jar is used. You can do it going to openhab-cli console and running bundle:list | grep Loxone |
@ppieczul removing the old binding was the trick. Now it works ! Perfect ! Thank you ! |
Great! Please use it for a few days and let me know if it is ready to commit to the baseline. |
Runs since a week - everything perfect ! |
No channels are created automatically for knx/eib devices present in miniserver.
How can I add them?
The text was updated successfully, but these errors were encountered: