Did you check the binding regarding the new authentication?
Loxone OpenHAB Binding
Einklappen
X
-
-
Kommentar
-
Finally success :-)
I had to install a complete new openhabian, then I was able to see the "new" interface which Rar9 posted.
Additionally the java.security file had to be modified but this is discriped in the docu.
Many thanks to Rar9, without the knowledge that both tools are compatible I would not have continued! -
HALLO01 Welcome.
As I myself still didn't have too much time to test all, perhaps you can update me regrading controlling roller/blinds or get status like windows open.
My light/dimmers work already, but controlling it it in multiple rooms is a bit stupid as google home still doesn't know if I´m asking from mykitchen / Mobile phone or other rooms that have GH. This make it quite complicated to fast turn on/off lights in the dedicated room, as ceiling light will appear for each room.
Looking forward to some starter hints to best setup GH/Loxone to controll the full house. -
I am using Alexa as speech control. I have only one box in the livingroom, so I do not have the usecase of multiroom.
Blinds are working fine, at least you have to accept the "limited" usemodel. It is not possible to say blinds down or up, they accept a percentage value (100% = close, 0% = open).
Currently it is not possible to get the status out of the box. As a workaround I am using the Amzon Echo Control Binding.
Release Candidate and Support Thread This thread tries to give you support with the released version of the amazon echo control binding. Also relative stable (sometimes more stable then the offical version) can be downloaded from here. Please jump to the Preview and Beta: Amazon Echo Control Binding thread to get the latest features if you want do a beta test. FAQ and Hints When I have to remove and recreate things for a binding upgrade? Check When I have to remove and recreate things for a ...
I tell Alexa "switch status on" and implemented a rule in openhab which says via the binding the amount of open doors/window - I use the remind function of the binding
-
-
i have a value of a dimmer within openhub, but if the value changes, it is not shown within loxone.
why is this?Kommentar
-
So habe nun endlich Zeit für Openhab2 gefunden, Loxone eingebzúnden läuft soweit. Nun habe ich bemerkt das die KNX Dimmer nicht automatisch eingebunden werden, ist das normal oder habe ich einen Fehler in der installation?
PS: Die KNX Schalter werden automatisch eingebunden.
Loxone 9.3.xx
binding-loxone - 2.4.0.SNAPSHOT
Kommentar
-
Problem has been addressed and solved on the openHAB board.
Followed these instructions again but with the sudo in it wget http://cdn.azul.com/zcek/bin/ZuluJCEPolicies.zip unzip ZuluJCEPolicies.zip cd ZuluJCEPolicies sudo cp *.jar /usr/lib/jvm/zulu-embedded-8-armhf/jre/lib/security reboot And it works 😄 😄 😄 Thanks all for the help
Gesendet von meinem Aquaris X Pro mit Tapatalk
Kommentar
-
-
@PaploPaplo
I'm having trouble that the loxone binding that is not reacting. On Paper Ui its telling me that the loxone connection ist fine, but when when trying to turn things on/off nothing happens.
This mostly happens when i flash a new firmware or save a updated config.
I most often have to fully reboot my openhabian for things to work again.
In addition my 2nd miniserver (slave) keeps getting found also it was put into the Ignore list.
What might u need to get thus fixed.
Obenhab 2.4.0
Loxone last betaKommentar
-
Du musst nur Deine Java Version updaten damit diese die Java cryptography unlimited strength unterstützt. Erst dann wird die Verschlüsselte Kommunikation unterstützt.Kommentar
-
Welche Java Version nutzt du denn?
Die neusten Versionen sollen die Verschlüsselung schon unterstützten order.
Dann google einfach nach "Java cryptography unlimited strength"
Hier was für oracle java - https://www.attachmate.com/documenta...a/b1gdutii.htmKommentar
-
Hallo,
ich wollte gerade einmal das Loxone - Bindung im openhab ausprobieren, aber es funktioniert nicht.
Ich bekomme folgenden Fehler ... hier ist ein Log - Auszug von dem Anmeldeversuch an der Loxone
openhab.log:2022-01-07 13:24:35.310 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] NOT sending command: keepalive
openhab.log:2022-01-07 13:24:35.316 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] Server connecting to web-socket
openhab.log:2022-01-07 13:24:35.320 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] connect() web-socket
openhab.log:2022-01-07 13:24:35.341 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] Firmware version: 12.2.11.5
openhab.log:2022-01-07 13:24:35.345 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] Forcing HTTP websocket connection.
openhab.log:2022-01-07 13:24:35.349 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] HTTPS session: false
openhab.log:2022-01-07 13:24:35.353 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] Connecting to server : ws://10.1.1.70:80/ws/rfc6455
openhab.log:2022-01-07 13:24:35.358 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] Sleeping for 240 seconds.
openhab.log:2022-01-07 13:24:35.368 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] Websocket connected (maxBinMsgSize=3145728, maxTextMsgSize=524288)
openhab.log:2022-01-07 13:24:35.376 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] Closing session
openhab.log:2022-01-07 13:24:35.380 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] Session closed
openhab.log:2022-01-07 13:24:35.380 [DEBUG] [.binding.loxone.internal.LxWebSocket] - [5] Websocket connection closed with code 1000 reason : normally closed
openhab.log:2022-01-07 13:24:35.383 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] set offline code=INTERNAL_ERROR reason=Enable Java cryptography unlimited strength (see binding doc).
openhab.log:2022-01-07 13:24:35.385 [DEBUG] [ding.loxone.internal.LxServerHandler] - [5] received offline request with code CONFIGURATION_ERROR, but thing already offline.
Bei mir läuft das Openhab auf einem Docker - Container auf einem Raspberry Pi.
- openhab version 3.1
- java Version ist:
openjdk version "11.0.11" 2021-04-20 LTS
OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
OpenJDK Client VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)
- Java scheint nicht auf unlimited zu stehen, ich weiß aber nicht wie ich das korrigieren kann:
Check for unlimited crypto policies
Java version: 11.0.11+9-LTS
restricted cryptography: true Notice: 'false' means unlimited policies
Security properties: limited
Max AES key length = 128
Vielleicht habt Ihr ein Tip wie ich mein Problem lösen kann, oder was für einen Fehler ich gemacht habe (Konfiguration, ...).
Grüße
JürgenKommentar
Kommentar