Time based events failing?

[Mr_Lucky (Bob)]

There are at least three other threads besides this one, all describing bits and pieces of similar problems:

Frustrated by the state of things

My smart apps and devices are failing randomly and frequently. ST just reported issues with Mobile App, logging was broken the last time I tried to debug some code. Scheduled events were reported to be broken a few days ago and they hardly ever work anyway. Polling has been broken ever since I bought my hub and ST seems to not care at all. Which boggles my mind because what good are sensors that are not being polled ? Anyway felt the need to vent a little because another one of my devices has suddenly stopped working and the system failed to fire my smart app schedule causing my heat to remain on instead of turning off on schedule. What good is home automation that works…sometimes…

New Trouble With Modes & Routines (related to setlevel for dimmers/thermostats?)

I have my system set up to switch modes when I’m away and fire off the routines based on my presence. It used to work pretty well with the old app and hub. Lately when I come home: My presence is not updated until I go into the app and manually refresh Once I refresh and the mode changes to Home, none of my motion sensors turn on the lights. They are seeing motion but are not triggering the lights to come on. I first have to turn all the lights in a room off and then the motion sensor seems to work. It seems like the motion sensors are not really waking up quickly enough. Most of the time I have to stand in front of them and wave my hands to get them to respond. I have an Aeon Multi, a Fibaro motion 2 ST 1st gen motion and 3 Monoprice motion sensors. Any ideas on why this stuff is…

Routines Not Working that include dimmer switch setting

I noticed that about 10 hours ago some of my routines stopped working correctly. I created a new routine slowly adding everything that one of the malfunctioning routines had and narrowed it down to the dimmer switch set-point. The routine works perfectly until the dimmer set-point is used. I changed “I’m back” by removing the dimmer set-point and it’s now working again. Has anyone else had this?

As if this weren’t bad enough, there is little to no involvement by ST in any of the threads, and Support (when they finally get around to responding) seems to be operating in a vacuum. I’ve read in these various threads of people with the same or similar issues that are actively involved with Support in troubleshooting, yet the person I’m dealing with is still in the discovery mode. Not faulting him, but honestly… there seems to be no communication at ST – either externally to suffering customers, or internally amongst themselves. Multiple people working on similar issues, seemingly unaware of what the other is doing. This is insane!

Okay, I feel better now.
Just to end on semi high note, and for the benefit of people who are looking for something to try, here what works (temporarily) for me.

1. Delete all Routines that involve the failing mode
2. Remove all reference to the failing mode in configured smartapps
3. Delete the failing mode
4. Recreate the mode you just deleted
5. Add back Routines and smartapp references in the same order you removed them (not sure if the order actually matters, but it works).

This is specifically for modes that fail to change as a result of a time-scheduled Routine. In my case, other actions that are part of the Routine execute… only the Mode change fails. Of course, things scheduled to happen as a result of the Mode change will also fail.
NOTE Re #3, above: Yesterday I encountered a situation where I could not delete the mode within the IDE. It produced this error:

However, I was able to delete it from the mobile app.

My open ticket is #154180. If you have a similar issue, please reference the number to Support, so that we may possibly get the same people involved working on them.