Is this issue following the installation of Zigbee2Mqtt at your place?
I had the same problem when connecting my Zigbee key and activating the integration.
I would say yes and no
I first installed z2m before Bluetooth (if I remember correctly) and Bluetooth worked until 5 days ago.
After that, it is possible that there is a link.
But if that’s the case, I feel like I’m back on my good old Gladys 3, where when one service fails, the rest fails.
But for me, @pierre-gilles has well isolated each service so that when one service is down, the rest works.
It’s still the same physical machine, if zigbee2mqtt and bluetooth step on each other (at the OS level), Gladys can’t do anything about it.
Otherwise, I think there is a Bluetooth issue in any case, you are not the first to have it, and I have already found a possible cause in another topic on the forum. It’s a lifecycle issue.
The problem is not clearly identified, the lifecycle problem story is my feeling based on what I’ve seen in other messages, but personally I can’t reproduce it. I don’t have a Zigbee key at home so it’s impossible to reproduce the effect between the two services.
There are other bugs on the fire on Gladys core that are clearly identified and are currently taking my attention
For a workaround, not knowing the source of the bug, I don’t know.
Edit: I investigated a bit more, I invite you to see the topic below