"Tap to pair with null."

For about a month now, every few days, my Android Pixel 7 phone and Bangle.js 2 get into a strange state: the phone makes a "ping" sound and pops up a notification that says "Pairing request\nTap to pair with null." This happens once per minute until I reboot both the phone and the watch.

Curiously, after I reboot, the watch has disappeared from the list of paired devices. I use Device Unlock to keep the phone unlocked when my watch is near. Because the watch is no longer paired, I have to set that up again.

I'm not sure where to start debugging this problem. I haven't changed the watch's software in a long time, so I'm wondering whether an update to Gadgetbridge or Android is the cause.

That is a strange one - can't see I've seen that before. Is there ant heading on the Tap to pair with null menu? Like is it from Gadgetbridge, or Android itself?

One thing you could try is to re-add the watch to Gadgetbridge, but if you were previously adding it as a 'companion device' to not do that, and just add it normally. I think the device unlock functionality will still work with it