Hi,
I noticed something earlier tonight with a rule I was working with and thought may be worth mentioning... It's not stopping me achieving what I want, so no urgency to get a fix...
When I setup a rule triggered by a change in the custom attribute mediaSource on a chromecast device, the rule does not fire when the mediaSource attribute changes back to 'None', the rule only fires when the mediaSource goes from 'None' to something else.
If you want any screenshots or logs let me know and I can provide them.
Thanks,
Simon
Simon, I just performed a test with a Changed trigger to mediaSource and it worked both whit a value and with “None”. (The first time I ran the rule, it didn’t run but it did when tried afterwards.)
What platform version are you on?
Have you tried deleting the trigger and re-creating it?
1 Like
Hmmm, maybe I need to re-create it then. I set it up probably 2-3 weeks ago, so was probably on an earlier version, but am up-to-date now in terms of HE firmware. I added some extra logic earlier this evening to handle it (the additional trigger on mediaSource=None):
Looks like re-creating the rule resolved it.... strange... Thanks for prompting me to look at it again @Sebastien
1 Like
No worries. Glad it worked for you!
