Closed 5iver closed 3 years ago
Interesting, and also possibly the cause of this for bindings that have thing actions.
https://github.com/openhab/openhab-core/issues/1265#issuecomment-580219877
I believe the root cause is here: https://github.com/openhab/openhab-core/issues/1322#issuecomment-576351187
Refreshing bundles where we do use declarative services (as far I know) is not needed..
I think I see the same strange beahviour last week when I uninstalled the Freebox binding, meaning other bindings were restarted. I can't say if all or only a part of the other bindings were restarted. This is at least a major bug.
It is a major bug, and critical issue imho.
I believe this is a symptom of issues reported in the forum, where zigbee or zwave are no longer working after upgrading to 2.5. Logs show cyclic binding uninstalls, which is what I am seeing too. When uninstalling an addon, there are other addons being stopped and started. Included in these are zigbee and zwave. Zigbee does not behave well to binding restarts and usually requires an OH restart to get it working properly. Zwave handles binding restarts OK, but it is a resource hog and responsiveness in the zwave network will be much reduced. If this happens repeatedly, then I can understand why people think 2.5 is broken.
I was recently looking into the new icalendar binding and needed to remove the 1.x caldav-command to test something. I noticed in the log and figured it was time to report this. I suspect that zwave and zigbee are restarting due to org.openhab.core.config.serial being restarted. Here is the log...