Issues/conflicts between Bluetooth rtl8761 dongle and SkyConnect v1.0 dongle as of 2024.11.0

[HomeAssistantPim]

Describe the issue you are experiencing

I've upgraded HA Green from 10.4 to 12.0 and HAOS (presumably) from 13.1 to 14.0.
Presumably, because backups in the UI no longer work and thus I have no history to check.
Due to issues I downgraded HA 12.2 ->10.4 -> 11.0 -> 11.3, while still being on HAOS 14.0.
Downgrading HA helped a bit, but never as good as it was.
Initially with 12.2 ZHA became unstable after hours-day the ApplicationController appeared not to working anymore.
Only a reboot would get ZHA back up for another hours-day.
Experiences to far after downgrading is that I got home assistant stable with core 11.0 only the bluetooth dongle was no longer detected due to a timeout on startup. Upgraded to core 11.3 hoping it would fix this, no such luck,
However the bluetooth dongle suddenly started working again after about a week and multiple restarts.
As this happened, ZHA problems started to become unstable again as it was with 12.x.
I removed the bluetooth dongle and so far (a day now). ZHA has not given any issues since.
So this seems related as of HAOS version 14.0, as the previous setup 13.1+10.4 was running fine for a long time.

As I've been going back and fort and HA is not getting much better, this has become a serious problem now.
Not eager to more to HAOS 14.1 latest either because with all the problems I experience with every update, I'm getting afraid it will only make things worse.

My older post about the bluetooth dongle not working: home-assistant/core#133080

Please advice if this is a known issue and wheter 14.1 will solve it?
Happy to provide more info if needed, love to have a proper HA again.

I'm considering to create an automation to reboot HA when ZHA devices don't have a recent update (if possible).

What operating system image do you use?

HA Green (form seems to reset this value if submit fails)

What version of Home Assistant Operating System is installed?

14.0

Did the problem occur after upgrading the Operating System?

No

Hardware details

HA Green
rtl8761 realtek USB Bluetooth dongle
SkyConnect v1.0 zigbee dongle
ZWave Aeotec 5gen

Steps to reproduce the issue

0. core 10.4 / os 13.1: happy, ZHA only requires occassional reboot every few weeks
1. upgrade core 10.4->12.0
2. upgrade haos 13.1?->14.0
   (issues)
3. downgrade core > 10.4: bluetooth unstable, ZHA ok
4. downgrade core > 11.0: bluetooth unstable, reinstalled blue integration no longer finds dongle, ZHA ok
5. downgrade core > 11.3: bluetooth no longer finds dongle, ZHA ok
6. nothing but a week latter: bluetooth found and working, ZHA ApplicationController issue hours after restarts

Anything in the Supervisor logs that might be useful for us?

Only thing I could find on HAOS logging (other lines seemed fine):
2024-12-19 07:36:09.840 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/e8f36dda.tar: "filename './backup.json' not found"

Anything in the Host logs that might be useful for us?

A lot of:
2024-12-18 21:51:25.873 homeassistant bluetoothd[445]: No matching connection for device
And some: 
2024-12-18 07:32:27.743 homeassistant kernel: cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
2024-12-17 23:10:04.213 homeassistant kernel: Bluetooth: hci0: ACL packet for unknown connection handle 16
2024-12-17 19:41:13.136 homeassistant systemd[1]: docker-2477242476e44075e6e1d01501b35e0bf518fdb45db038895a8c98a8a7537493.scope: Deactivated successfully.
2024-12-17 19:41:13.139 homeassistant systemd[1]: docker-2477242476e44075e6e1d01501b35e0bf518fdb45db038895a8c98a8a7537493.scope: Consumed 2min 31.051s CPU time.
2024-12-17 19:41:13.143 homeassistant kernel: audit: type=1334 audit(1734464473.130:1175): prog-id=30 op=UNLOAD
2024-12-17 19:41:13.177 homeassistant dockerd[530]: time="2024-12-17T19:41:13.177222411Z" level=info msg="ignoring event" container=2477242476e44075e6e1d01501b35e0bf518fdb45db038895a8c98a8a7537493 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
2024-12-17 19:41:13.273 homeassistant kernel: vethaf43a39: renamed from eth0
2024-12-17 19:41:13.323 homeassistant kernel: hassio: port 4(veth7e7c080) entered disabled state
2024-12-17 19:41:13.405 homeassistant NetworkManager[444]: <info>  [1734464473.4044] manager: (vethaf43a39): new Veth device (/org/freedesktop/NetworkManager/Devices/40)
2024-12-17 19:41:13.435 homeassistant kernel: hassio: port 4(veth7e7c080) entered disabled state
2024-12-17 19:41:13.435 homeassistant kernel: veth7e7c080 (unregistering): left allmulticast mode
2024-12-17 19:41:13.436 homeassistant kernel: veth7e7c080 (unregistering): left promiscuous mode
2024-12-17 19:41:13.436 homeassistant kernel: hassio: port 4(veth7e7c080) entered disabled state
2024-12-17 19:41:13.436 homeassistant kernel: audit: type=1700 audit(1734464473.410:1176): dev=veth7e7c080 prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
2024-12-17 19:41:13.583 homeassistant kernel: audit: type=1300 audit(1734464473.410:1176): arch=c00000b7 syscall=206 success=yes exit=32 a0=d a1=40000575e0 a2=20 a3=0 items=0 ppid=1 pid=530 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
2024-12-17 19:41:13.583 homeassistant kernel: audit: type=1327 audit(1734464473.410:1176): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
2024-12-17 19:41:13.646 homeassistant systemd[1]: var-lib-docker-overlay2-98fbf3512a0be494a78dd8bf8b0e81146abae5cd1d8ac82cd65a3e13be47fbbe-merged.mount: Deactivated successfully.
2024-12-17 19:41:13.647 homeassistant systemd[1]: mnt-data-docker-overlay2-98fbf3512a0be494a78dd8bf8b0e81146abae5cd1d8ac82cd65a3e13be47fbbe-merged.mount: Deactivated successfully.
2024-12-17 19:41:13.913 homeassistant kernel: audit: type=1334 audit(1734464473.900:1177): prog-id=33 op=UNLOAD
2024-12-17 19:41:14.682 homeassistant systemd[1]: var-lib-docker-overlay2-4e57ad2dfe62dcb7c0369cb2fda3f4889c717f00fe57344d8824028023ff97ea\x2dinit-merged.mount: Deactivated successfully.
2024-12-17 19:41:14.684 homeassistant systemd[1]: mnt-data-docker-overlay2-4e57ad2dfe62dcb7c0369cb2fda3f4889c717f00fe57344d8824028023ff97ea\x2dinit-merged.mount: Deactivated successfully.
2024-12-17 19:41:14.803 homeassistant kernel: hassio: port 4(vetha133354) entered blocking state
2024-12-17 19:41:14.803 homeassistant kernel: hassio: port 4(vetha133354) entered disabled state
2024-12-17 19:41:14.803 homeassistant kernel: vetha133354: entered allmulticast mode
2024-12-17 19:41:14.813 homeassistant kernel: vetha133354: entered promiscuous mode
2024-12-17 19:41:14.813 homeassistant kernel: audit: type=1700 audit(1734464474.790:1178): dev=vetha133354 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
2024-12-17 19:41:14.813 homeassistant kernel: audit: type=1300 audit(1734464474.790:1178): arch=c00000b7 syscall=206 success=yes exit=40 a0=d a1=40006b1d70 a2=28 a3=0 items=0 ppid=1 pid=530 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
2024-12-17 19:41:14.813 homeassistant kernel: audit: type=1327 audit(1734464474.790:1178): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
2024-12-17 19:41:14.814 homeassistant NetworkManager[444]: <info>  [1734464474.8114] manager: (veth6558a94): new Veth device (/org/freedesktop/NetworkManager/Devices/41)
2024-12-17 19:41:14.834 homeassistant NetworkManager[444]: <info>  [1734464474.8325] manager: (vetha133354): new Veth device (/org/freedesktop/NetworkManager/Devices/42)
2024-12-17 19:41:15.219 homeassistant systemd[1]: Started libcontainer container 9f59f1aa6ed03d50931a4c439cac5fa384d0931b5764225510255dc0bdacb702.
2024-12-17 19:41:15.283 homeassistant kernel: audit: type=1334 audit(1734464475.270:1179): prog-id=250 op=LOAD
2024-12-17 19:41:15.283 homeassistant kernel: audit: type=1334 audit(1734464475.270:1180): prog-id=251 op=LOAD
2024-12-17 19:41:15.663 homeassistant kernel: eth0: renamed from veth6558a94
2024-12-17 19:41:15.712 homeassistant NetworkManager[444]: <info>  [1734464475.7118] device (vetha133354): carrier: link connected
2024-12-17 19:41:15.713 homeassistant kernel: hassio: port 4(vetha133354) entered blocking state
2024-12-17 19:41:15.713 homeassistant kernel: hassio: port 4(vetha133354) entered forwarding state
2024-12-17 19:44:06.863 homeassistant bluetoothd[445]: No matching connection for device

System information

No response

Additional information

No response

[HomeAssistantPim]

Updated to HAOS 14.1 and plugged in my usb bluetooth dongle again.
Within 4 hours ZHA no longer worked given the same old message that the Application Controller is not running.
Can I help some how?
Any update on this please?