Device to another device - doesn't work with "Changes and Becomes Any Value"

[Guest]

Hi Spud.
See attached image.
I can set device to other device if I use range of value but not if I select changes and becomes any value. Is there something I did wrong there?
PS - I am using to sync my cooper accessory switches, but it also failed on setting a lamp to pots as well so it isn't just the accessory sync.

[randy]

I haven't used the Easy Trigger Trigger, but I do use the actions - they work great. I use the basic HomeSeer trigger. The wait in the event was used when I has Jasco dimmers, which were slow reporting their dim level. I essentially "commented" it out with the "Never" option when I replaced the dimmers with Coopers. The Wait action will still work with Cooper dimmers, but it is not necessary. This event works very reliably
.

[Guest]

Thanks Randy. I was able to get it to work your way as well. Just wasn't sure why it failed on my first attempt. Seems like a bug.
It sure is a handy tool and beats scripts for syncing!

[randy]

Thanks Randy. I was able to get it to work your way as well. Just wasn't sure why it failed on my first attempt. Seems like a bug.
It sure is a handy tool and beats scripts for syncing!

Spud will have to answer your initial question,because it seems it should work. If I get the time I will see what happens with the Easy Trigger Version.

[spud]

Spud will have to answer your initial question,because it seems it should work. If I get the time I will see what happens with the Easy Trigger Version.

what Easy Trigger version? From the screenshots, it looks like Jim used only native triggers.

Jim, for the case where it didn't work, did the event was actually fired? (You should be able to see that in the logs)

[randy]

what Easy Trigger version? From the screenshots, it looks like Jim used only native triggers.

Jim, for the case where it didn't work, did the event was actually fired? (You should be able to see that in the logs)

You're absolutely correct, I don't know what I thought I saw when I first looked at his screenshots. Obviously it is a HomeSeer and not an Easy Trigger issue, because with a different native trigger he said the event works fine. So it is a problem with the HomeSeer "Device changes and becomes "Any Value"" trigger. I'm not sure what the purpose of that trigger is when they have "This device has a value that just changed". If I have time I will experiment.

[Guest]

what Easy Trigger version?

Jim, for the case where it didn't work, did the event was actually fired? (You should be able to see that in the logs)

Spud - Easytrigger version: 3.0.0.21
The event didn't fire either. Perhaps another indication it is an HS3 issue is that I couldn't collapse that line of event either.

Either way, appreciate yours and Randy's response and I do have it working perfectly!

[randy]

Spud - Easytrigger version: 3.0.0.21
The event didn't fire either. Perhaps another indication it is an HS3 issue is that I couldn't collapse that line of event either.

Either way, appreciate yours and Randy's response and I do have it working perfectly!

Just to check if the HomeSeer trigger you first used was working or not, I built an event using it, it worked fine. I don't know what was wrong with yours. If a trigger will not collapse,it is not complete or valid so there was definitely something wrong. Below are two screenshots using each of the triggers. They both functioned properly.
.