-
-
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
[kostalinverter] Fix using binding together with z-wave binding #11002
[kostalinverter] Fix using binding together with z-wave binding #11002
Conversation
Signed-off-by: Christian Bandowski <[email protected]>
3d3dfc9
to
c6452c2
Compare
By curiosity, using a grep command, I checked if other bindings are not defining 3 parts and I found that:
For pulseaudio, the config seems to be unused ! And for other bundles:
So potentially a lot of fix to apply.... |
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.
Excellent, thanks for the fix!
@chris922 : to clearly understand, what was the link with the Z-Wave binding? |
I have now standardized the URI everywhere in bindings. I am just waiting an answer from the maintainer of the pulseaudio binding (unused config to be removed IMHO). Now remains all the io/persistence/voice bundles with 2 segments config URI. @kaikreuzer : do you thing we should update them ? |
@lolodomo I am not sure - we don't have concepts like "thing-type" etc there what could be used for the URIs, so I wouldn't know how we should update them. Using the addon id as a first segment does not look too bad imho. If this causes issues with the Z-Wave binding because it fails parsing those, I guess that should then rather be fixed in the Z-Wave binding. Wdyt? |
First, I would like to understand why exactly this leads to problems with the Z-Wave binding. I hope @chris922 can explain that. Then, I used myself the openhabcloud and voicerss bindings in combination with the Z-Wave binding without problem, so I really doubt we need to change these URI. In case we would like to change them anyway, I could propose to add "config" as thrid segment, like for example "voice:voicerss:config" or "io:openhabcloud:config". |
@lolodomo : When the z-wave binding is active adding a kostal-inverter thing failed. An exception occurred here: Seems that the z-wave binding has a hooks into a more general place and tries to parse the thing-type URI to get the information which type of binding the thing belongs to as this information is usually available in the thing-type URI... but it fails to parse the URI if it doesn't consist of three parts. Few lines before the mentioned one there is an if-clause that restricts parsing the URIs for |
In this case, it looks to me like a bug in the Z-wave binding. The binding should first check that |
…hab#11002) Signed-off-by: Christian Bandowski <[email protected]> Signed-off-by: dw-8 <[email protected]>
…ng (openhab#11002)" This reverts commit 6ae30cd.
…hab#11002) Signed-off-by: Christian Bandowski <[email protected]> Signed-off-by: dw-8 <[email protected]>
…ng (openhab#11002)" This reverts commit 6ae30cd. Signed-off-by: dw-8 <[email protected]>
Hi, I still have the problem. ZWave is working fine but if I try to add any kostal-plenticore binding, the system is going into a infinite loop. |
Hi, just to sort things out, so no solution found so far. After #7090 is PIKOIQ42.xml as , and in After #11002 is PIKOIQ42.xml as , and in |
Hi, the problem appears when I try to add any Plenticore binding. After clicking the button in the menu, the system is going into a infinite loop. I'm not able to configure thingTypeIDs or something else because I'm not able to get to this point at any time. |
Hi, I can also see this problem, and it's regarded to as described above. So I assume we have to figure out how the syntax in PIKOxxx.xml will look like, and then use the right working syntax for all different invertertypes. |
…hab#11002) Signed-off-by: Christian Bandowski <[email protected]>
…hab#11002) Signed-off-by: Christian Bandowski <[email protected]>
…hab#11002) Signed-off-by: Christian Bandowski <[email protected]>
Fixes using the kostalinverter binding together with the z-wave binding (#7090)
According to the example in the documentation the kostalinverter binding seems to use an invalid format for the
config-description
URI. The value must consist of three parts separated by:
and not just two.The z-wave binding expects this format and crashes when an invalid one is given.
I verified the fix by building a new JAR and dropping it into my openHAB 3.1.0 instance.
This solution is similar to the one proposed in #7090, but I used the binding name as the first identifier and not already a name related to the config or thing itself.