Now, here's the extra-funny part: if I choose other attributes from the list for awhile, I can get RM to treat chime like different types of variables...
What device is this? How was the attribute "chime" defined? Chances are it was incorrectly defined as something that doesn't exist or maybe boolean isn't working. I couldn't find an example of it anywhere on a google 'site:github.com "hubitat" "bool" "attribute"' search.
I most often see attributes defined as type "string", "enum", or "number" but "bool" should work according to this.
I was about to enter a similar issue, restoring an device from a variable. Jump up store, store sound device volume & mute state into local vars,
Set Volume to TV Room volume
Set Sound to TV Room mute
This works as expected, but RM does not allow setting attribute from the vars..
Thx
That worked. I was writing a driver and when testing the rule was blank for the bool. I spent some time trying to figure out what I did wrong. Then came here and found the answer. I changed to enum and all is well.
Boolean is not a supported type for an attribute in a driver, as far as I know. RM asks the driver of the custom attribute device for its supported attributes, so it won't return Boolean. I'll have to check on this tomorrow, but that's what I think is going on. RM itself doesn't know what the attributes are, only what the driver tells it.