Simple Automations bug

[Evilborg]

Anyone else seeing this behavior?

When you add/edit your devices to control What do you want to do? * always changes to turn on and set colour, see video of this. Happens in Google Chrome even in incognito.

https://www.awesomescreenshot.com/video/411213?key=6915815b0f01b382ffb4a4f663209fc9

@bravenel

[ritchierich]

I had something similar, on 2.2.1.116, where any SA rule that has a dimmer in the selection the choice would default to/change to turn on and set level. Even for rules that were previously turn off. I had to verify every SA rule I had on all my hubs because things were going nuts. Unfortunately I never reported it to support as I was heading out of town.

[bravenel]

Would you post the screenshot of the rule so I can try to reproduce the failure?

[Evilborg]

[Evilborg]

@ritchierich

where any SA rule that has a dimmer in the selection the choice would default to/change to turn on and set level

Yup seeing this also -- if it has a RGB light then it switches to turn on and set colour

Normal on/off switches do not have this problem if the list only has those in it.

[ritchierich]

@Evilborg

Normal on/off switches do not have this problem if the list only has those in it.

Same here

[Evilborg]

Good cause I thought I was going nuts here since no one else was posting about it.

[bravenel]

I've found this bug. Fix will be in next release, most likely a hot fix to 2.2.2.

Thanks for bringing my attention to it.

[Ken_Fraleigh]

This is actually the third separate post since 2.2.1. I figured 2.2.2 would have fixed it.

"Turn on and Set Color" bug in Simple Automation Rules?

Greetings, From my admittedly minimal testing, I think I've found a problem with the "Turn on and set color" action (new in 2.2.1) in Simple Automation Rules after a comment from an Inovelli forum member prompted me to try to replicate it. With an Inovelli LZW42 (color bulb) and this setup: [image] I can consistently replicate this error: [image]

Error text for screen readers or people using the search function:

org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast obje…

Issue with a few simple automation “off” rules after update to 2.2.1

See attached post

[Evilborg]

Thanks @bravenel

[Evilborg]

The first link is unrelated to this bug. The second one is.

[Ken_Fraleigh]

Sorry, thought I was grabbing this one

Rule changed by itself?

I have a Simple Automation rule to turn two lights on at sunset and off at sunrise. It's been running fine. On June 25 I upgraded the hub firmware, and enabled Google Home and set it up. I played around with Home by telling my Google Home hub to turn lights on and off. Went to bed with the lights on, and next morning they were still on. I checked the log, and saw this: 2020-06-26 06:10:02.474 am infoDriveway Light is on [digital] 2020-06-26 06:10:00.860 am infoTurn Off Porch Light, Drivew…

We both replied to it and I chalked it up as to be taken care of. Apparently Bruce is human. I’m glad he found the issue.

[ritchierich]

@bravenel

hot fix to 2.2.2

@bravenel does the latest hot fix .123 have this fix? I didn’t see it called out in @bcopeland’s release notes.

[Evilborg]

yes it does

[ekraus]

Generic Dimmer
With a Simple Automation Rule
At Sunset
Set Level Dimmer Level 65.
Device console, "POWER":"ON","Dimmer":65
Just after that.
On the device console I get a
POWER":"ON","Dimmer":31
I cant find what is sending it. Its not set anywhere I can find.
Is this the same bug?
Is there any way to see the code that the Simple Automation Rule generates for a device?

[Evilborg]

Not the same bug...

See if the device is linked to another app by going to the dimmer device in question then scroll down and make sure its not triggered by another rule.

[ekraus]

It is only set in one rule