Samsung Smartthings - Light Switch / Aqara Blind

Has anything changed to the Smartthings API?

I know it’s unusual config bit the Smart Blind was showing as a “Light Switch” … if on, was opened… if off, was closed.

I’ve had this running 12+ months which would close as sunset, now its stopped working (no config changes my side).

On refreash Smartthings Integration…

Logger: homeassistant.helpers.service
Source: helpers/
First occurred: 21:45:01 (1 occurrences)
Last logged: 21:45:01

Unable to find referenced entities light.landing_blind or it is/they are currently not available

When “turning on the light”

Logger: homeassistant.components.websocket_api.http.connection
Source: components/smartthings/
Integration: Home Assistant WebSocket API ([documentation](, [issues](
First occurred: 09:02:12 (9 occurrences)
Last logged: 21:34:47

 "error": {"code": "ConstraintViolationError", "message": "The request is malformed.", "details": [{"code": "NotValidValue", "target": "commands[0].capability", "message": "switch is not a valid value.", "details": []}]}}

What do those entities say they’re reporting they’re not available.

Yes plenty is changing on the SmartThings side they’re in the final stages of shutting down the IDE and with it - anything that used a legacy Groovy DTH. (final date for that is Jul10 I believe) Have you ensured everything on the ST side is still operating as expected? (until they stabilize im blaming everything on ST first.)

1 Like

I get the below error.
The device has two entities…

  1. A on/off switch which is now disabled
  2. A “up” and “down” button which does nothing

I’m Smartthings, I have a button and the up down…
The button works but not the up/down (opposite to HA, which no longer works)

I could only assume the ST driver has automatically changed but I thought it couldn’t do that.

This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.

If the entity is no longer in use, you can clean it up by removing it.

DTH to driver yes - EDGE driver not supposed to. BUT that said the last three weeks shrugs no clue. Lets just say there’s a reason I moved two years ago. Make sure it’s working as you expect in ST first - then we can go back and see what kind of result HA sees.

1 Like

Yeah that’s the plan.
I have a spare Roller Blind so I’ll see if it’s another driver.

I have seen this before with ST to HA.
ST has a sensor/state that isn’t pushed to HA.

Just remember you’re currently on the Groovy retirement week - so who knows what’s happening / going to happen. TBH, with SmartThings for the next few weeks, I’m at the point of waiting a few weeks to see if it stabilizes before trying to fix anything