I started this test with my working production system (with the newer ipcamera jar).
Uninstalled the newer jar and went back to the merged ipcamera binding and it kept working which I expected.
Restarted just openHAB, and it still kept working with all cameras enabled which I did not expect to occur.
Full reboot and also a cache clean, still it keeps working.
I then messed with the Netty libs and broke the mqtt binding in the process as it uses Netty.
Because mqtt did not start, changing the order the bindings start in, the issue now returned to my system.
uninstall and reinstall of MQTT binding, fixed the mqtt not starting, but now the zigbee issue remained on my system.
Uninstalled merged ipcamera binding and reboot fixed the zigbee issue.
Dropped back in the newer ipcamera jar into the addons folder, did a reboot and the issue is fixed again.
Decided I needed to double confirm by breaking and fixing twice.
Uninstalled the MQTT binding.
Now that all bindings that use Netty were uninstalled (addons jars do not count) netty was not getting installed automatically so the ipcamera failed to start.
Installed newer Netty jars in console.
Restarted and I could not reproduce the issue with zigbee, all works.
Installed mqtt binding again and updated the netty libs it used to make sure only 1 version is in use and not a mixture.
Restarted multiple times and zigbee keeps working.
I changed multiple things so the result was different.
Conclusion: Nothing conclusive. Appears to make a difference in which order the bindings get installed in or perhaps the order they show up in when you do a bundle:list I think it is worth upgrading Netty as that will place it last in the bundle:list and perhaps you currently have netty getting loaded before the zwave binding or very close to it? Just a theory.
Commands that worked to upgrade netty AFTER first bundle:uninstall xxx using the number from the first column when you do a bundle:list.
bundle:install https://repo1.maven.org/maven2/io/netty/netty-buffer/4.1.67.Final/netty-buffer-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-codec/4.1.67.Final/netty-codec-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-codec-http/4.1.67.Final/netty-codec-http-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-common/4.1.67.Final/netty-common-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-handler/4.1.67.Final/netty-handler-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-resolver/4.1.67.Final/netty-resolver-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-transport/4.1.67.Final/netty-transport-4.1.67.Final.jar
Next ones are for mqtt binding:
bundle:install https://repo1.maven.org/maven2/io/netty/netty-codec-socks/4.1.67.Final/netty-codec-socks-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-handler-proxy/4.1.67.Final/netty-handler-proxy-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-transport-native-epoll/4.1.67.Final/netty-transport-native-epoll-4.1.67.Final.jar
bundle:install https://repo1.maven.org/maven2/io/netty/netty-transport-native-unix-common/4.1.67.Final/netty-transport-native-unix-common-4.1.67.Final.jar
I would be interested to hear your findings as to where the zwave binding is in relation to the Netty libs and the ipcamera binding when you do bundle:list
Then after upgrading Netty and messing with the order of installing bindings if you get a different result.