doncaruana
(Don Caruana)
February 22, 2017, 11:04pm
22
The difference is probably that this is a secure inclusion. FWIW, these have been working non-secure for me for a bit. Only the secure ones aren’t working.
wakeup interval:
zw device: B9, command: 9881, payload: 00 84 06 00 38 40 01
wakeup capabilities:
zw device: B9, command: 9881, payload: 00 84 0A 00 00 F0 FF FF FF 00 00 00 00 00 F0
duncan
(Duncan)
February 23, 2017, 4:32pm
23
You’re right, it isn’t fixed – I wasn’t testing with the encapsulated case.
I’m having trouble figuring out what’s going on because it works with the exact same string in unit tests. I’ll need to consult a java/groovy expert.
2 Likes
doncaruana
(Don Caruana)
February 24, 2017, 7:08pm
24
duncan:
You’re right, it isn’t fixed – I wasn’t testing with the encapsulated case.
I’m having trouble figuring out what’s going on because it works with the exact same string in unit tests. I’ll need to consult a java/groovy expert.
Well, the good thing is it’s an easy code-around until it gets fixed. I just built my own secure wakeupinterval handler and intercept the description in parse and send it off to my handler.
Barkis
(John C)
July 5, 2017, 9:49pm
25
Anything further on this fix, @duncan ? Thanks
1 Like
duncan
(Duncan)
July 6, 2017, 4:30pm
26
Someone else supposedly fixed this but it never got tested. Sorry I forgot to circle back.
Is it still broken?
1 Like