Disabling a parent device (or app) does not disable the child devices (or apps), unless something in the child device (or app) needs to flow through the parent due to how the code was written. So, that's not surprising.
I would still be curious why that error is/was occurring and if anything like removing and re-adding the integration would help. Disabling the device is something I suggested more for troubleshooting than a permanent "fix", though if you don't plan to add new Bond devices, I'm not sure what effect it has beyond that...
I'd also be more curious if your other issues were actually fixed as opposed to just the error disappearing; I suppose you'll need some time to tell.
I encountered the same error with bond well over a year ago (maybe longer) using the built in integration. I tried on multiple occasions to get help with the error and didn't get anywhere trying to resolve it. I even tried tagging Copeland. I ended up going back to the community integration and it runs error free.
The speed did get better, but I'm still having problems, that I'm having problems tracking. I have a Group of lights that are to all come one and go off together, but randomly one light will not respond. I have all the lights setup to retry 5 times, in this case I received a warning that 5 retrys were made and failed. I ran configure on the light and tried again and it works fine. The in the same group a different light failed the next day. I checked the log and the rule didn't even try to control that light to turn it on. So there are still glitches.
When the Child device activated the did throw the same error, only once, but did turn the lights on and off.
I’m no z-wave expert, but if you don’t remove the ghost, you might find that some of the issues you’re facing never resolve.
I'm working on it.. I have 3 ghosts to get rid of. I'm going to physically take 2 of the switches out of the wall and disconnect power and see if I can remove the ghost. I'm going to attempt to get the Silicon labs software hooked up as well to help. The third is a sensor that showed up twice, I'm going to exclude it and re-include it to get that out. It is frustrating every time I restart the hub, somethings work better some thing stop working and it takes about 2 weeks for everything to work consistently again. The concern is that my second hub doesn't have any ghosts and has similar issues.
I was able to remove all the ghosts. And for awhile everything got much better, I thought that I had it all working. The issues I have are when the hub is rebooted, all the motion sensors are severely delayed and don't react to run the rules, it's minutes, but once they react a couple of time they work fine. The issue I had this morning is a ran a rule that has been working fine. turn on a physical switch and it runs a room scene, but today I hit the switch and it just turned on the like connected to the physical switch, then I had to hit it again and again until all the lights came on, but the log shows no errors. This happened with 3 other switches that are connected to scenes this morning. When last night all worked fine for turning them off. Here are the logs:
