@nayelyz , @taustin @orangebucket @Automated_House
I have been talking with some developer friends of mine who have been looking into recent Bluetooth issues for other systems. I’m going to pass along what they said just in case it’s relevant to what’s happening with the smartthings app. Could be just a coincidence, but it’s the same timing.
This appears to be a case of Apple saying “and this time we mean it.“
Part of the Bluetooth spec for apple has always defined how the Interval Max and Min would be handled when a Bluetooth device was connecting to the iOS device, but apparently they never enforced it until iOS 16.
Now they are enforcing it, and the result is that some Bluetooth devices, maybe including the smartthings hub, are timing out in situations where they didn’t used to time out.
People who have this problem likely have it over and over again because of the configuration and what they are trying to do. But there will also be quite a few people who don’t have the problem.
Some device makers, like the manufacturers of the Whistle GPS tracker, are fixing the issue by putting out new versions of their apps which comply with recommended practices. others are waiting and hoping Apple goes back to the old strategy.
We are developing a device which communicates with our iOS/watchOS apps via Bluetooth LE and has to stream a lot of sensor data for an extended time period (hours). Everything works fine under iOS 15.x, but we’ve found out that iOS 16 betas (and the RC) changed something in the negotiation process: previously we’ve used 15 ms Connection Interval, but iOS 16 (and watchOS 8) most of the time negotiates 24 ms, which is too wide for our bandwidth. The long connection interval causes packet loss (9-33%), and after 3 failed retries (3x30 sec) our hardware drops the connection.
Here’s a discussion of the fact that the Apple spec hasn’t changed, but the enforcement has.
iOS 16 changed Bluetooth LE Connection Interval - Stack Overflow
even if it was in the spec I never saw this behavior during countless hours of testing until iOS 16 and now multiple customers are reporting.
It’s like a township suddenly enforcing a 25 mile an hour speed limit when they used to let people get by with 30 to 32 and now a bunch of people are showing up late to work. But the ones who always drove under 30 don’t see any change. And the street signs haven’t changed. Just the enforcement.
Again, I’m not 100% sure this is what’s happening to smartthings users with regard to adding a new hub or some device discovery, but it might be related.