Inconsistent behavior after firmware update to 61.6

Specific devices—such as door sensors, guest bathroom lights, and scenes associated with them—are all Zigbee-based. In some cases, Zigbee temperature sensors for the “refrigerators” are also used.

Thanks @nayelyz !

I agree, it is very strange. As I mentioned, I use the Shelly Scanner and the Shelly App to monitor things too: Both immediately get their Input State updated immediately upon the Open/Close Contact changing states. It’s only the SmartThings App that gets a delayed or no update at all. I can “toggle” the Toggle Setting in the SmartThings Device Card, then SmartThings updates the Input State immediately. As well, I dropped in a SharpTools Rule that refreshes it and it gets updated immediately.

I only did that on 1 of 5 Shelly Switches in an attempt to troubleshoot (removed the existing Device; Scanned; Re-Added; Etc.) But it continues to behave randomly like the other 4.

Hi @nayelyz

Just checking in to see if there has been any progress on this front. I haven’t heard anything back from SmartThings.

For what/it’s/worth… A.I noted below. Do you have any confirmation of said “hub-level socket bug”?

Personally, I discovered what seemed to be a bad Aeotec Multisensor 7 in my setup - as soon as I took it offline, everything went back to working normally again.

She has not posted on the forum in over three weeks. She may no longer be around. Her photo was also removed. Same for @Itati except for photo.