Shelly Cloud integration: devices show status but commands time out (started yesterday)

Hi all, hoping someone can help or confirm whether this is a wider issue.

Symptoms
Two Shelly Dimmer 2 units (kitchen and dining) stopped responding to commands from SmartThings yesterday afternoon. Both work perfectly via the physical wall switches and via the Shelly Smart Control app. In SmartThings, the devices show as connected, status updates from the Shelly app are reflected correctly in SmartThings (so state is syncing one way), but when I tap on/off in SmartThings the spinner just runs until it times out. No error message.

What I’ve already tried

  1. Updated firmware on both Shellys (kitchen needed it, dining was already current).
  2. Rebooted both Shellys.
  3. Disconnected and re-added the Shelly Cloud integration in SmartThings.
  4. Confirmed both devices are online with good signal in the Shelly app.
    None of it changed the behaviour.

Setup details
• Hub: SmartThings V3_HUB, firmware 000.060.00012, Hub app 1.0.49-13
• SmartThings app: 1.7.45 (iOS, updated about 2 weeks ago)
• Shelly Smart Control app: 1.8.2 (updated 3 days ago)
• Devices: 2x Shelly Dimmer 2 (SHDM-2), firmware 20230913-114008/v1.14.0-gcb84623 on both
• Integration: Shelly Cloud (cloud-to-cloud), no Edge driver or local setup
• Both Shellys on the same WiFi network, signal reported as Good

Question
Is anyone else seeing this with Shelly Cloud right now? Is it likely a Shelly Cloud side issue, a SmartThings cloud issue, or worth me trying something else like deleting and re-adding the individual devices, or rolling the Shelly app back? Happy to provide logs or anything else useful.
Thanks.

Hi @Tim_Miller

Thank you again for the detailed report.

To continue with the investigation, could you please help us with the following:

  • Please replicate the issue and share the exact timestamps (including your timezone) when the issue occurred

  • Grant us access to your account so we can review it from our side

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM.
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (â‹®) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

More info about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

Hello

I have the same issue. I got the same HUB V3 and I use Shelly Dimmer PM1 devices.

Everything worked fine untill af few days ago.
Like Tim, the Smartthings App reflect the correct status of my dimmer, but I am unsable to turn on or off, but I am able to dim the dimmer through smartthings app if the dimmer is already active, so the connection is there.

When I try to turn on/off the dimmer through smartthings web connection (smartthings advanced) I get this error: Error running command “on”. 424 Schema validation for partner response failed

Like Tim, I have tried the same things regarding reconnecting Shelly Clould to Smartthings and update alle shelly firmware.

I really hope for at fix :slight_smile:

- Oliver

Hi @Itati thanks for the reply. I’ve just tested it now at 08:20 a.m. UK time, on both the kitchen lights and dining lights. I’ve used the same email address here as I have on my SmartThings accounts, and I’ve granted you support access. I look forward to hearing any thoughts on how we can sort this out. Many thanks.

Same bug with Shelly 1PM Gen4, SmartThings V3_HUB, firmware 000.060.00012, android Shelly Smart Control app, Matter over wifi, fixed ip

Résolution:

How I restarted my Shelly 1PM Gen4 using the Shelly app (Matter workaround):

In the Shelly Smart Control app, I went to Matter settings, then unchecked (disabled) Matter, and checked it again.
After re‑enabling Matter, the app automatically prompted me to restart the device, which I confirmed.
The Shelly then rebooted successfully.

offline → online

I have the same setup as Tim and Oliver, multiple Shelly devices in SmartThings controlled via linked account to Shelly Cloud - all are dimmers (2PM Pro, Gen 2, Gen 3) not supporting Matter via Shelly (most on 1.75, tried 2.0)
Same timeframe (last 2-3 days) the devices report status but can’t be controlled. Happy to share logs etc, tried re-linking, refresh etc. Shelly app works fine.

Hello! Same issue for me with multiple Shelly dimmer 2 devices.

It’s working to control the devices via the Shelly app and it works to change dimmer level via Smartthings app but not control on/off via Smartthings app. Is this the same behavior for you?

And since the Smartthings app does not work my physical keyfob remote does not work to control on/off either.

Best regards, Peter

Same, turn on in Shelly app and the dimmer level can be controlled in SmartThings but try to switch off and it says network or server error.

It’s working to switch on/off in Google Home which would suggest the issue is due to an update in Smartthings somehow.

Same thing here, have tried all the recommendations found on the web, mainly delinking the Shelly Cloud in SmartThings and re-linking. Receiving network/server error message. Shelly app communicates well with the device (RGBW 2). Hope someone has a fix to this.

Hi everyone,

We’ve received an update from the team confirming that the issue has been resolved.

Could you please try again and let us know if you’re still experiencing any problems?

Hi, thanks for the update, looks good for me now. No re link needed, works again.

Ideal would be Shelly bring Matter support to these devices. Thanks for the help.

Yay, it’s working again!

Was the fix made in the Smartthings cloud service or in the Hub firmware?

Your hub and it’s firmware have nothing to do with cloud connected devices. You don’t even need a hub for cloud connected devices.

Thanks a lot, mine works again as well, no re-link required!