Justin Hammond

Target Handling is implemented for those newer devices. Old Devices should use the VerifiedChanged flags.

> Here's a full log of toggling the switch on and off. With the 4 second transition it takes 7 seconds to complete. OZW seems to be stuck too many...

Ok - I've added some code to backoff the initial validation check when verified change is enabled, and we will only check every 250ms. Might have to play with those...

The presence of the Security CC does not indicate if encryption is enabled (only that the device possibly supports encryption). Please see index 1 of the Security CC (label is...

Yeah - This is Legacy, but agree it should be fixed. I'll aim todo it towards the end of the 1.7 Dev Cycle.

> [ozw.mqtt.publisher] [debug]: Publishing Event valueAdded: 562952802893846 I'm gathering that the hundreds of these messages, the number is changing? If so, yes, I have a idea. We are not yielding...

Thanks. Will review soon.

Logs please. If this is OZW 1.4, it’s not supported anymore. Please use 1.6 if you can.

Node 87? >2020-01-28 21:10:52.844 Detail, Node087, Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x57, 0x07, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x03, 0xff, 0x12 2020-01-28 21:10:52.844 Detail, 2020-01-28 21:10:52.844 Info, Node087, Received...

Can you post a new log file with ozwcache removed before starting? Lets double check - But smells like a problem with the device unfortuantly. Lets confirm.