Rule machine - as per the app developer, this app is no longer available for new installs, distribution, or support

After, I suspect the change occurred with the firmware.

The closest I’ve seen to what you guys have posted is 4 setLevel 99% to the same switch within a few seconds, which looks like it’s triggered by a rule firing based on motion.

Oh yeah this is only for device type ā€˜z wave switch’ stock handler. I switched mine to dimmer switch to stop the device/physical.

Hrm… ok - I only have a small # of those in the house, and I’m only using Smart Lighting for one of those (Master Closet Light, which I don’t go into very much).

Ok, there it is… with Smart Lighting and a Stock Z-wave switch. It’s happening about every 15 min (as in your example), but is that enough to be having consistency/speed issues from the Cloud? I’m not sure if that’s the source of my issues - but, agreed that it’s definitely a bug! :slight_smile:

Update - never mind - it’s definitely on all my Zwave switch device types, even with RM controlling them. Hrm… will keep an eye on this. Thanks for pointing it out @SBDOBRESCU.

Oh yeah, I forgot about the device handler part. I haven’t changed any of mine.

@SBDOBRESCU dies changing the device type to dimmer change the behaviour of the switch in any way at all?

It does, I changed several of mine and the flooding stopped immediately.

Not sure if it would effect you too much.

But I have 41 Zwave on/off switches installed using that device type.

I guess I’ll start changing them over.

Did you have to change all of them?

I only changed those that are part of Master Rules to prevent lights from turning back on. I am not concerned as much about lag and server overload as I am about my lights coming on again in the middle of the night.

That’s what is crazy… Your lights are actually turning on… Mine aren’t. But our logs are the same.

Sad to see RM pulled out. I fully support Bruce on his decision. ST support is no where close to being a helpful support. Do ST support even listening to the community?

I saw a post about ST v3. Same old promises. No delivery. Whats up Samsung. Very disappointing.

The post you quoted was someone (not a SmartThings staff member) making a joke. There has been no announcement of a new SmartThings Hub V3.

Maybe Discourse forums need a big red sarcasm tag for people who skim messages but don’t read the whole context? :slight_smile:

Thanks @Mike_Maxwell for doing this all done with taking the survey

Go***mnit. Come on, ST… I just moved into a new house…

I have to admit I use 1.9.0a/1.9.1e and since I have redone some of the rules and since the recent platform update everything works as should and I’m quite happy actually - the only thing thats a bit odd is when I change rules it seems the rules apply while editing rather than when committing the changes which on the other hand helps to determine if the rule/triggers etc work as designed … Wondering if Bruce dropped out a bit too soon …

Well, I missed a very basic scheduled RM rule this morning for the very first time ever for this one.

At 6:00am only on Sat/Sun, change mode from Night to Home

The log shows it ran but the mode never changed. I do see the duration was longer than most, wonder if it timed out.

As it has been suggested, I could move it to xmins ± from the hour, however it has been running fine since Dec when I set this rule up

And what’s with the funny entry in the scheduled Jobs section ā€œScheduleā€ Most if not all of my scheduled jobs have this type of entry

Thanks in advance
Rick

@Toy4Rick
I’ve had this happen a couple of times. The actions for the mode change occur as well as other rules that only occur in the new mode, but the system doesn’t reflect the mode. The logs even say it happened.

I submitted a ticket to support. They responded that it’s a bug and they are working on it.

So, I don’t think it’s rule machine.

I recommend you submit a ticket.