UPDATE: Recent SmartThings User Experience & Platform Performance

I’m seeing battery issues too.

I’m seeing lots of issues today too… My env has been pretty stable until now. I’ve seen several of my rules in RM get hosed today. I’m seeing lights not light even though there is motion registering. Etc…

Ok glad to hear that I don’t have to go change out my smoke detectors just yet. I just got notified that both of them are low when they were at 95% yesterday.

Nagganahappen, as was expected. :wink:

You saw this, right?

You’re right. What about all of the zigbee corruption? Renaming and then renaming back shouldn’t be a real solution (but it works - I now use it every damn day).

Are you looking at the database corruption affecting the zigbee devices too (rename x2 solution)?

I agree with you that the two are linked, because for me, they both started on the same day.

Yeah, it tells that that was a funny as hell post.

Hue should be green again.

I bet on Monday now :wink:

Optimist… … …

This thread is getting pretty long winded and several issues are starting to blend together.

Delay Issue

The delay issue has a fix but will require a platform release. I thought that this release was going out today but it has been pushed back. The fix is going out with the next platform release and once I know for sure when that is I will try and give another update.

Hue Issue

The hue device type was changed and the icon went from being green while on to blue. This was confusing to our customers and we were able to quickly fix the device type without changes to the platform. If you still have blue icons for your hue bulbs, log out and back into the mobile app.

Developers

Join our discussion that starts in 5 minutes and give us your feedback.

I thought we settled on blue now…

What about the data integrity issue where “headless rules” are basically crippling the most used and useful smartapp out there, Rule Machine?

We were sadly misled :cry:

The blue is supposed to chill everyone out

Me too!!!

This morning I lost the state of a simulated switch. It’s used as a flag in a rule and it is checked for off/on. Even though the switch was off (I checked), it didn’t know it (the rule checks for off but came it back false - because it was neither on nor off - causing the wrong result from the rule. I toggled the switch and force-ran the rule again and it ran properly.

I wish this thing would be closed down. I can’t figure out if anyone has said anything about the fix being rolled out and don’t want to read through all the messages.

Did the fix get rolled out for SHM?