Closed Markkuuss closed 2 years ago
No, I don't think it's related to the port. Looks like a bug in the discovery service implementation.
Can you please try the following (on the karaf console):
update org.smarthomej.binding.deconz https://download.smarthomej.org/org.smarthomej.binding.deconz-3.2.12-SNAPSHOT.jar
I have rewritten the part that looks suspicious.
Can you please try the following (on the karaf console):
update org.smarthomej.binding.deconz https://download.smarthomej.org/org.smarthomej.binding.deconz-3.2.12-SNAPSHOT.jar
Unfortunately, this does not work for me. After the update all things are offline. When I try to restart the binding, I get an error message.
openhab> bundle:update org.smarthomej.binding.deconz https://download.smarthomej.org/org.smarthomej.binding.deconz-3.2.12-SNAPSHOT.jar
openhab> bundle:restart org.smarthomej.binding.deconz
Error executing command: Error restarting bundles:
Unable to start bundle 336: Could not resolve module: org.smarthomej.binding.deconz [336]
Unresolved requirement: Import-Package: org.smarthomej.commons; version="[3.2.12,3.3.0)"
My fault. Give me a minute
Please install
install https://download.smarthomej.org/org.smarthomej.commons-3.2.12-SNAPSHOT.jar
Do not use update on that bundle, it might cause issues.
Thanks a lot, I'll test it right away.
I just made a new realization. It could also be due to my installation.
Maybe the problem is that I migrated one Deconz installation to another. Currently both instances are still running. The search in openHAB now shows sometimes the one and sometimes the other instance is shown with the same ID.
Yes, that could be a problem.
Can you please try the following (on the karaf console):
update org.smarthomej.binding.deconz https://download.smarthomej.org/org.smarthomej.binding.deconz-3.2.12-SNAPSHOT.jar
I have rewritten the part that looks suspicious.
Unfortunately, this does not fix the error. But when I close my second instance, the error is gone.
I guess it's really my fault, because I exported the configuration from one Deconz installation and imported it at the new Deconz installation. I guess these two instances can't be clearly distinguished enough?
This is currently only a temporary solution anyway. I will close the second instance. Sorry for the effort.
I didn't realize it was bridge thing. The handling of these discovery results is not done by the binding but by a core component. The UDN is the property which is used to identify different devices and it is the same here (because it's essentially the same instance). Each different configuration (like the port) then updates the discovery result.
In the log file I continuously get the following messages. I have already ignored the Thing in the inbox - did not bring any success. Is it maybe because deconz is running on port 8081, which is not the default port?