Smartthings unable to load samsung ac device

I am writing to report a persistent issue with the SmartThings mobile app on my Pixel devices. After switching to a new Pixel 10 Pro, the app fails to load the detailed control panel for my three air conditioners, which are connected directly to my Wi-Fi. The app gets stuck on a loading screen when I try to open the specific device controls.

Summary of the issue

  • Problem: The device control panel for three Wi-Fi-connected air conditioners gets stuck in a loading state within the SmartThings app.

  • Affected devices: A new Pixel 10 Pro and a Pixel Tablet. The problem began on the Pixel 10 Pro and subsequently affected the tablet after I attempted a full app and account reset.

  • Working functionality:

    • I can turn the air conditioners on and off using the simple button on the main device page in the SmartThings app.

    • The air conditioners are correctly reported as “Online” in both the app and the my.smartthings.com web portal.

    • I can fully see and control the devices via the my.smartthings.com web portal.

    • Google Home can also perform basic on/off actions.

  • Non-working functionality: The app fails to load the full interactive control panel for setting modes, fan speed, temperature, etc.

  • Device profile: The ACs use the device profile DA-AC-RAC-100001.

  • App version: SmartThings version 1.8.37.23, SDK Matter version 1.4-0.

Steps already taken

  1. Reinstalled the app: I uninstalled and reinstalled the SmartThings app on both my Pixel 10 Pro and Pixel Tablet.

  2. Cleared app data: I cleared the cache and storage for the SmartThings app on both devices.

  3. Deleted and re-registered devices: I “exited” SmartThings and deleted the devices from my account. I then re-registered the air conditioners.

  4. Confirmed network connectivity: My phones and ACs are all on the same Wi-Fi network.

  5. Rebooted everything: I have power-cycled the phones, the air conditioners, and my network router.

  6. Confirmed online status: The my.smartthings.com web portal correctly shows the devices as online and fully controllable.

The issue appears to be a bug in how the mobile app processes and loads the full control interface for these specific Wi-Fi devices. Since the web portal works, the problem seems to be limited to the app’s display of the control panel, not the cloud service itself.

Could you please assist me in resolving this issue?

Thank you,

Luca

Somebody have idea how can I better debug this issue?¿?

Hello everyone,

I’m hoping someone can help me figure out this problem. I found a Galaxy S21 and configured smartthings on it, with the same account, and obviously, it works perfectly. It’s fast and responsive. On my Google Pixel, it still fails to load the device’s details.

I took a Wireshark capture on my fritzbox to see the difference:

1. The Working Flow (Galaxy S21): From the capture, I can see the AC units maintaining a stable connection to the SmartThings cloud. When I use the S21, it maybe try somethings in CoAP), and then it immediately starts a direct TCP stream with the AC’s local IP address.

2. The Failing Flow (Google Pixel): With the Pixel, the app never starts the direct TCP connection to the AC.

Capturing directly on Pixel, it talks a lot with cloud (I could see DNS request vs *smartthings.com and the tcp threeshake) but nothing When I run a packet capture directly on the Pixel, I can confirm it’s communicating with the SmartThings cloud. What’s strange is that I can successfully turn my AC on and off, but the capture shows this is all happening via the cloud.

Even when the ON/OFF command works, I see zero direct traffic between the Pixel and the AC’s local IP.

My S21 proves a direct local connection (on port 5050) is possible and faster. My Pixel proves it can control the device, but it’s only using the cloud.

Does anyone actually know what the intended workflow for the SmartThings app is? Why would it force my Pixel into a “cloud-only” mode and refuse to use the local connection that is clearly available?"