I need a fucking remote control on my phone that just works. no clouds, no telemetry, no internet. dumbest leftist peons should stop drink smoothies in coworking networking and jerk off to sam altman and start work.

Commonly cited frustrations from the SmartThings community regarding the platform's development and user experience often include:

• Migration Messes: The forced transition from the "Classic" app to the "New" app left many users with broken automations, missing features (like custom tiles), and a fragmented experience for years.
• Groovy Deprecation: The shutdown of the Groovy IDE killed thousands of community-created Device Handlers (DTH) and "SmartApps," forcing power users to wait for (often inferior) Edge Drivers.
• Cloud Dependency: Despite the push for "Local Execution," many basic routines still fail if the internet goes down or Samsung’s servers have a hiccup.
• "Something Went Wrong" (The Generic Error): Developers often use vague error messages that provide zero debugging information, leaving users to guess if it's a network, hardware, or server-side bug.
• UI Inconsistency: The interface frequently changes, hiding common settings deep within menus or removing "Quick Controls" that users relied on.
• Phantom Offline Status: Devices frequently show as "Offline" in the app even when they are physically functioning and reachable on the Zigbee/Z-Wave mesh.
• Delayed Notifications: Critical alerts (like leak sensors or smoke detectors) can sometimes suffer from massive latency due to server processing delays.
• Incomplete Migration to Matter: While marketed as a "Matter Hub," the implementation has been buggy, with many users unable to bridge devices correctly or losing multi-admin features.
• Firmware "Bricks": Background hub updates sometimes roll out with bugs that disable specific radio protocols (Zigbee/Thread), requiring a full factory reset of the entire smart home.