Yes my "how should I say" hate is too strong and distrust is too weak is how I feel about shearwater... I like my data and up until last year in october my dives were now do not laugh ... grease pen and slate with a runtime plan off multideco and two bottom timers + a depth gauge and a datalogger fob [ReefNet Inc. | Sensus Ultra]. once on the surface i would download the reefnet FOB and compile my data...Thank you for this great analysis, that explains the issues we had all these years! Actually I've added the "Unpair and re-pair" option for Shearwaters in the end in my software and this finally fixed the problem on Windows.
when the fobs went from 50 usd to 250.00 I held out as long as possible as my last one died in october 2023..
That was my dive computer which I replaced with a Garmin Mk2 and then picked up a Perdix2 for a backup and added two AI units.. funny fact Garmin is a sync master to subsurface not so much with the shearwater perdix2 so I started down this path to hell Oct 24th 2023.
In my journey the following was discovered about the kludge implementaiton of BlueToothLE by sheawater and pairing issues if multiple bluetooth radios are present compounded by subchannels and inability to use paired keys properly
At first I thought it was OS based and the shearwater Applications were "required" ( they are workarounds for a horrible failure in firmware for bluetooth or a hardware issue ) this issue hits with peterel HS data path and Perdix line using the bluetoothLE implementaiton
due to the (slowness of shearwaters implementaiton) compunded by reques speeds of systems not writing through to the cloud... )