I've noticed that when I enable or disable a custom device (via the GUI checkbox), I get two calls to deviceUpdated. For enabling, the first one turns enabled on (old=off, new=on), and the second one just seems to represent no change. Conversely, when disabling, I get one call with no apparent change, followed by another that actually turns .enabled off.

The has-any-config-changed filter logic eliminates the duplicates well enough (I had a bug in mine, which is how I realized this), but is there a reason for the two calls? Should the seemingly superfluous one mean something to me?

Cheers
-- perry

It is superfluous and will be optimized out in beta 10.