Constant bluetooth disconnects after upgrading to v3.0 about adv360-pro-zmk

[ReFil]

What operating system are you using?

[jamesgour]

@ReFil Both systems are running Windows 11

[JuanPabloMF]

Same here, with OS X High Sierra. And can't connect also to Pop OS (ubuntu 22.04)

[ReFil]

@jamesgour are they both using intel wireless cards by any chance. There's a known issue with the latest Intel driver update breaking things

[ReFil]

@JuanPabloMF this is likely a different issue. Something you can try is removing these lines from adv360_left_defconfig #262 (comment) . Please also ensure that the Bluetooth profile led is fast flashing and the host you're trying to pair to hasn't been paired to another profile on the keyboard.

[jamesgour]

@ReFil One is using an Intel wireless card, and the other one is using a Realtek card. The behavior seems very similar though on both PCs.

[ReFil]

Interesting, thank you. When you try and pair do you get an error saying "couldn't connect, try connecting again"? It might be worth trying the same troubleshooting steps I recommended to the other user (removing the lines in defconfig and ensuring every profile is clear)

[JuanPabloMF]

@JuanPabloMF this is likely a different issue. Something you can try is removing these lines from adv360_left_defconfig #262 (comment) . Please also ensure that the Bluetooth profile led is fast flashing and the host you're trying to pair to hasn't been paired to another profile on the keyboard.

Just tried and updated my keyboard, and it didn't work (not with Pop OS nor with OS X)

[ReFil]

@JuanPabloMF please open a new issue for your problem

[jamesgour]

@ReFil Okay I will try that fix when I get home, thanks for the idea :).

If it doesn't work, is the guidance to just go back to the v2.0 firmware? I never had any issues when I was using that.

Also, is there any ETA on when the fixes will be in place if the issue is coming from the intel wireless card?

[ReFil]

You should be able to revert the merge commit, we keep v2.0 base branch online so users can still build changrs

[jamesgour]

Okay thanks! I'll keep an eye out for when things even out in v3.0 :)

[ReFil]

Thank you for your understanding. One last thing that might be worth trying is manually clearing each Bluetooth profile of any residual information using mod+1-5 and mod+win on the stock layout

We're working hard to improve the Bluetooth experience with continual firmware updates and improvements. If there's any major changes that have the potential to improve the experience with windows I will reply to this issue again

[jamesgour]

@ReFil can you link the v2.0 base branch please? I can't seem to find it in the repo anymore? Thank you!

[ReFil]

Looking at your repo you still have v2.0 branch setup and available, if you change to pushing to this branch you can edit things as per normal

https://github.com/jamesgour/Adv360-Pro-ZMK/tree/V2.0

[jamesgour]

@ReFil Yes, I rolled back to v2.0 using an old commit I had from back then.

Unfortunately, after rolling back now the keyboard won't even connect to my Windows 11 machine (Intel Bluetooth / Intel Wireless card).

I keep getting "Try connecting your device again".

I was thinking I should update my v2.0 branch to try the final commit to see if it fixes this new issue, but that's when I noticed the v2.0 branch is gone.

[ReFil]

Ah I see, it shouldn't make a difference because the Bluetooth code doesn't get updated with the config repo. Please double check every profile has had the residual pairing information cleared out as it definitely seems like that could be the issue

[jamesgour]

@ReFil All BT profiles cleared and still no love, unfortunately. It's odd because I never had pairing issues before on that old branch, but perhaps the newer BT drivers have caused something. When/where does bluetooth code get updated?

Have you seen this "Try connecting your device again" issue before? I'm debating getting another bluetooth adapter dongle or something but it would be really nice to at least connect after all of this headache.

[ReFil]

The "couldn't connect, try connecting again" error is indicative of the board rejecting the pairing attempt from the pc, which can happen for a few different reasons but is usually a security key exchange problem

[jamesgour]

@ReFil Hmmm okay any other ideas on what to try to resolve a security key exchange issue?

Or do you think I need to just try another Bluetooth adapter?

[ReFil]

Have you tried pairing it to a phone or some other Bluetooth device to ensure the keyboard is working properly?

[jamesgour]

Good idea, yes I just paired it to my phone and I was able to pair it to my other computer running windows 11. That computer does not have an Intel wireless card though.