Same here
2 Likes
So, I'm not losing my mind, lol.
Found another one.
I now have to go through and create separate "turn on" and "turn off" rules. That is, if I don't want the wife to get pissed off, again. Or, until this gets fixed.
edit: A second rule, a "turn off", work with turn off after x minutes.
edit2: I've got a few of these. Hopefully, I can do work arounds until bug is fixed.
Blue works. Red does not.
Can’t find the thread right now, but I thought I read where someone said they had to set the number of minutes to a value greater than zero to make this work.
That was the one below. Didn't work for me.
Try it yourself and see.
Thing is, just like the sunset thing, this is a very common usage-not exotic at all.
https://community.hubitat.com/t/bug-2-2-4-147-motion-and-mode-lighting-apps/56863/5
This one, motion sensor (vs contact sensor) with delay of 3 minutes works.
Maybe a clue is in the different formats, lol. But seriously, something changed.
I tried it with zero off delay after motion and that worked as well.
Something is definitely afoot here and here.
Changing the timeout as I had first thought doesn't actually help; the back garden lights are still blazing away out there.
Our problems are similar though.
For me, if I make apps to turn things off, using only the blue circled parts, things work. So I can still get in a delay that way.
And for me, motion still works.
Oddly, if I have an opening contact sensor trigger the closing of a switch, it works fine.
Still not working with .148
@bravenel , @bcopeland or someone, could you please look into this when you have the chance?
This seems to have been fixed in .151 (I've become a beta tester only because things aren't working too great elsewhere, lol).
Thanks.
great .. anxiously waint for .151 then to test with my setup with the same issues.. did they say what was changed.
z-wave stuff
Thing is I changed a lot of rules from starting with turn something on, to turn something off, only because that worked. Now, should I change them back? lol
1 Like
so does contact open
(door or motion) with ecolink to turn on lights work consitently now in .151 with no delays or are you not sure yet? As you know the problem was intermittant like something intermittantly spamming the zwave mesh and delaying crap. With nothing relevant showing up in the logs ... of course.
Intermittant. Usually after a few hours of inactivity. I personally am not optimistic, but we'll see over time. I can't see it being the ecolink since logs show the door opening and closing in real time.
And the fact that the same setup, (sensors and devices)
work fine in 2.2.3 points to some of the zwave signaling and stability changes they made in 2.2.4
I wish there was a little more transparancy as to whether they found the issue and are addressing it or ignoring it because not many people have it or are not reporting it! I have had a couple of other issues since going back to 2.2.3 I think due to the restore etc., but not once a contact sensor opening with a delay turning on the light. I had to remove my resume/pause rule machine rule due to intermittant errors in the logs and change it to a virtual switch that i check whether or not to signal that the rule is "paused".
Well, you can't blame me for not blabbing about it.
At least this simple to fix problem is solved.
On a side note, we just had a momentary power flicker in the high winds here near Albany, NY. Maybe I'll do another backup.
1 Like
