I’m a bit surprised that just “disabling” the service will immediatly drop anything because AFAIK disabling a service doesn’t stop on it until you explictly do with sudo systemctl stop deconz-gui or reboot.
Regarding this error I guess that it’s related to the previous database locked trouble, and then relatied to a communication trouble with WifI access point.
If you don’t use it I suggest you to deactivate this option : Phoscon App.
If it’s still present after a reboot you can stil try to disable disable it sudo systemctl disable deconz-wifi (Deconz-wifi service usefulness with Conbee II - #6 by Marbaf)