ST outages are not being reported? (Again)

It looks like the ST backend is non operational… yet the ST status page says everything is just fine?

My SmartApp, which monitors the status of the Front Door and associated Z-Wave lock, has not changed. Yet, when it reads a closed door and unlocked lock, it sends a “lock” command to the Z-Wave lock. The Z-Wave lock never receives this command, as you can see from the lock events, until several hours later. Again this morning, the same unresponsive condition, lock command sent, lock still is Unlocked.

The locks’ battery status is good, hub is Online and home internet is excellent. But I’m guessing the ST PLATFORM CLOUD has issues AGAIN… I even tried to send the “Lock” command from the Things, no response.

I wonder which will happen first over the next few weeks, a reply to my repeated requests for help to support@smartthings.com or the ST Cloud Platform will eventually come back online and tell the hub to lock the lock?

This is frustrating to me on so many levels! :rage:

Current States
battery: 80 %
lock: unlocked
codeReport:

2 Likes

The cynical part of me is tempted to say that’s because failure is expected and accepted behavior at SmartThings. But in actuality, it could just as easily be that you have a marginal or intermittently marginal Z-wave signal to your lock. The problem is that the tools available to us for troubleshooting (logs and scheduler) only allow to surmise the cause of a problem, not definitively identify it (like ping measurements or real-time signal strength readings would allow).

Maybe performing a Z-wave repair would be a good first step.

1 Like

Working here just fine, anyone else having problems?

About 9:30am, the Z-Wave lock magically accepted the “lock CMD” from the Hub as well as from SmartTiles. I am confident that there were unreported regional issues with the ST cloud platform, because when I tried to perform a Network Repair at 7am, the IDE Realtime Log screen did not show any messages pertaining to any repair activities as it has in the past when I perform this function. Also, a subsequent IDE Hub reboot command did not cause the V2 hub to be rebooted. At 8am, I went as far as to remove the batteries and power to the hub and rebooted, but no luck. Lock was unresponsive to requests to lock from Things & SmartTiles.

My V2 hub is 10 feet from the front door with the Z-Wave lock, so signal strength is not an issue.

The lock is working now as it has on/off for over a year since I had a V1 hub. My main complaint is that within the last few months with V2 hub & backend ST platform issues, this has made this lock non functioning.

I have, as of this morning, engaged the AUTO-LOCK firmware on the lock, rather than depend on SmartThings to notice that the open/close sensor has fired and ignore the “lock command” from the SmartApp. This is a sad state of affairs for my investment in SmartThings.

I have yet to hear back from SmartThings Support other than their robotic response about being TOO BUSY…


battery: 100 %
lock: locked
codeReport:
codeChanged: 2

Date Source Type Name Value User Displayed Text
2015-12-05 8:22:12.732 AM EST
8 hours ago DEVICE lock locked Front Door Lock lock is locked
2015-12-05 8:17:51.638 AM EST
8 hours ago APP_COMMAND lock Front Door Control sent lock command to Front Door Lock
2015-12-05 8:11:15.614 AM EST
8 hours ago APP_COMMAND lock Front Door Control sent lock command to Front Door Lock
2015-12-05 8:04:28.328 AM EST
8 hours ago APP_COMMAND lock Lock Me After I Close sent lock command to Front Door Lock
2015-12-05 8:03:19.096 AM EST
8 hours ago APP_COMMAND lock Lock Me After I Close sent lock command to Front