As of April 7, most people in this forum have not yet been migrated to the new app, so we can’t answer a lot of questions about it yet as it works quite differently from the Classic app.
If you have the new app and need help with something the forum has not been able to answer, try the official help channel.
If you have the Classic app, do not install the new app until you have received an individual message from support that they are ready for you to use the new app or you can run into multiple problems.
That is easier said then done actually. The Samsung connect app is baked into the phone. The only way to not log in is to not log into your samsung account on the phone at all. It is also used to manage things other then smartthings so if you have any bluetooth devices they will likely use samsung connect as well.
Is there any basic adaptations to do to self developed DTH so they can work with the Samsung SmartThings app installed on my S9+
Seems all devices work except those I wrote the DTH and of course they work fine using the old SmartThings app.
it says “Can’t connect to device. Check and try again”
Thanks I checked but except the fingerprint that I don’t implement and the ocfDeviceType that seems to be used but doesn’t solve the issue after implementation,I did not find a specific difference between an old fashion DTH and a new version that works with the new app. Will wait for more information, as long as the old app exists, I am not in trouble and my DTH users either.
The TP-Link Smart App and Device handlers are finally ported to the new Samsung Connect. They work great in the classic app and pretty well in Samsung Connect - except:
Remote Links. If I use a remote link to call data or icons, and data/icon is not available, the Smart App cashes out with a network error in the app (no log). Issue is long-term, using remote links, if github is off-line then this becomes a failure mode for Samsung Connect. (The classic app just gives a blank icon or page of data, does not crash.)
