Zooz Power Switch missing voltage

[krlaframboise]

Zooz Power Switch missing voltage

[krlaframboise]

If 2 handlers support the Voltage Measurement capability and you switch from one handler to the other, the voltage events generated by the first handler don't get lost because they're attached to the device and not the handler.

When isStateChange is not specified, SmartThings won't create the event if the new value is the same as the old value, but it will create the event if there isn't an old value. That list is originally empty so if an attribute had to be in the list in order for it to create the event then no events would ever get created when isStateChange is not specified.

Tapping refresh, possibly more than once, most likely would have solved the problem without having to make that change. There are also several other factors that could have played a role in what you were seeing, but no one else has reported this problem so it's not worth spending time trying to figure it out.

I'm closing the issue, but I appreciate you taking the time to create it and if the problem comes up again I'll consider re-opening it.

[chucko88]

Thanks for looking at this. When it happened, I played with it for over an hour and a half, setting refresh rate down to one minute and watching it over and over. I changed just about every setting and would watch to see if it registered voltage. The old device handler I used didn't have a state variable for voltage so it wasn't there to disappear. I read all all your noteson changes so I just thought I would add that one back to see if there was any effect and the voltage state variable immediately popped up and was populated so I just thought I'd let you know what I saw happen in case anyone else may also note something similar. Thanks for all your work that you share. Chuck

…

On Thu, Jun 6, 2019, 4:11 PM Kevin LaFramboise ***@***.***> wrote: If 2 handlers support the Voltage Measurement capability and you switch from one handler to the other, the voltage events generated by the first handler don't get lost because they're attached to the device and not the handler. When isStateChange is not specified, SmartThings won't create the event if the new value is the same as the old value, but it will create the event if there isn't an old value. That list is originally empty so if an attribute had to be in the list in order for it to create the event then no events would ever get created when isStateChange is not specified. Tapping refresh, possibly more than once, most likely would have solved the problem without having to make that change. There are also several other factors that could have played a role in what you were seeing, but no one else has reported this problem so it's not worth spending time trying to figure it out. I'm closing the issue, but I appreciate you taking the time to create it and if the problem comes up again I'll consider re-opening it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#37?email_source=notifications&email_token=AIN5CQU3DSBMWYXHNTRRYWTPZF4QPA5CNFSM4HIQPWN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXEFRPI#issuecomment-499669181>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIN5CQXIQI7ZAH3VEXT7S5DPZF4QPANCNFSM4HIQPWNQ> .