Classic App defaulting to new ADT Hub instead of existing Smartthings Hub 2.0 after adding ADT for security

With Lowe’s Iris’ recent retirement, I decided to consolidate into a 100% Smartthings system by adding Smartthings ADT products. I installed the ADT Hub as a secondary hub in the same Location as my Smartthings 2.0 Hub. So far, so good.

What I did not expect based on my research was that my Android Classic app would default to the new ADT Hub instead of keeping the Smartthings Hub that it had been using for more than a year now. While I can still access and control devices on the original Smartthings Hub from within the Classic App, I can no longer do things like add non-ADT devices (since the app tries to add them to the ADT hub) and it appears to be having difficulty doing tasks like the Replace feature for devices that are struggling.

I called Samsung and they said that you cannot choose a default hub in the Classic app.

If I add a new device using the new app, it prompts me to choose a hub to which I want to assign the device, so that works fine. However, the new app does not handle troubleshooting with as much granularity, offering only to delete a device that has gone haywire vs repair or replace in the Classic app, for example. The IDE also lacks some functionality that seems only available in the Classic app.

I realize that Samsung is trying to make the app experience simpler for novice users and I don’t mind bouncing back and forth between the two apps and the IDE to manage what is still a relatively high-maintenance system, but I do want to figure out how to have the Classic app default to my Smarrthings Hub instead of the ADT Hub so I can use the functionality that is unique to that app.

If anyone has any guidance on how to do set a default hub in the Classic app, please let me know.

Isn’t possible. The classic app isn’t designed to handle two hubs on one location. It was never possible to do this until the new app and even then still isn’t recommended.