Hmm trying to figure out a way to handle this in the code without having to rewrite the apps in a month.
Does the DTH expose the attribute valve currently (without the patch)? i.e by specifying capability valve will that automatically return true for the API hasAttribute(“valve”)?
the safest method is to rely on the contact events. we are not taking that away.
right now, only the valve devices running in the cloud are generating both the events. (without the patch/18.x)
Correct, but other community handler for newer valve devices will start using valve and one needs to accommodate that.
Okay one neat way around this is to check if either contact or valve meet the criteria, that way if/when the device handler switches over from contact to valve or even has both it will still work.