-
Notifications
You must be signed in to change notification settings - Fork 780
thingUpdated() gets called during initialize() #3351
Comments
Pitty, was no one yet able to make progress on this, it's blocking openhab/openhab2-addons#2019 Was it confirmed to happen, do we have any call traces where the calls actually come from, because the code I see in openhab/openhab2-addons#2019 does do an async initialization. And the documentation (which can of course be incorrect or outdated) states that
So that actually means that it should not even be called before the async initialization was finished. |
Yes, I think I know what the problem is here:
It's all a bit tricky, therefore I can't promise to fix it immediately, but I will have a look into this in the next couple of days. |
...by also using the lock. fixes eclipse-archived#3351 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
fixes eclipse-archived#3351 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
...by also using the lock. fixes #3351 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
fixes #3351 Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
As observed in /~https://github.com/openhab/openhab2-addons/pull/2019#issuecomment-298440882 and https://www.eclipse.org/forums/index.php/t/1085852/ it seems that
ThingHandler.thingUpdated()
gets called while the handler is still inThingHandler.initialize()
. This puts the unnecessary burden of handling synchronization on bindings and is not intended.The text was updated successfully, but these errors were encountered: