BTT Remote for iOS won't hold connection to BTT for macOS

BTT Remote for iOS (which has always been reliable in the past) won't consistently display available connections. I can make it work for a time, but it'll always stop working again until the settings are manually re-toggled (see below).

I can fix this if I go to BTT's (macOS) System Preferences > BTT Remote > Uncheck then recheck Enable BTT Remote Support. However this only works until the next time the computer goes to sleep or restarts (not sure exactly what makes it lose the connection, but it always does).

Other things tried: Using the BTT Alpha version, uninstalling and reinstalling on iOS and macOS, restarting.

macOS Catalina 10.15.2
iOS 13.3
BTT (macOS) 3.219
BTT Remote (iOS) 2.3.1

Same problem here.

MacOS/iOS: Latest versions.

Same here, and now even manual entry is failing for me.
My instinct is that Big Sur has put something in the way, or rendered BTTRemote incompatible.
(also, now subscribing through Setapp, and wonder if that is complicating matters)

MBP 15, latest OS and iOS

Same problem with current versions MacOSX and iOS...

Really want this to work cuz It was great when it did.
Also I have 2 seats. It would be good to be able to select which Mac I want to use it on.

in newer versions of BTT you need to enable the BTT Remote server in the settings before you can use it.

Apart from that just make sure to not block BTT with a firewall

Works!!! Thanks!

Hi Andreas

BTT MacOs systematically starts the Remote service only upon startup or rechecking the setting. After Wifi breakdown or other Network changes, the Remote service dies.

Steps to reproduce:

  1. Start BTT MacOs --> Remote service is on
  2. Disconnect MacOs from Wifi
  3. Reconnect McOs to Wifi
    As a result, the remote service will be down, unfortunately.

As Wifi is often an unstable thing (especially when traveling, hotel Wifi etc), my wish is to have more stability here. I.e. BTT should automatically check for Network connection changes every x seconds or so and then reenable the service if needed.

Please consider for implementation. It is probably up to the users to classify this issue as "feature request" or as "bug" :slight_smile: