NIF not treated as wakeup anymore

mtryfoss · October 13, 2016, 6:38pm

Hello!

@chris, I wonder what’s the reason behind this commit:

I was struggling a lot with the newly added device recognized as a sigma wall controller (device entry 431). It never sent at normal Wake-up after inclusion (not even after days). After I tested to revert this change on my local checkout it intialized perfectly after a few NIF’s.

chris · October 13, 2016, 6:40pm

Please check the related issue.

github.com/openhab/org.openhab.binding.zwave

NIF being used as wakeup is not reliable

opened 08:16AM - 24 Sep 16 UTC

closed 11:36AM - 09 Oct 16 UTC

cdjackson

bug

The binding uses the NIF in the same way as a wakeup notification, but some devi…ces at least don't expect this. The WALLC-S for example sends a NIF, and this causes the binding to start sending queued messages, but the device is not ready. The device then sends the wakeup notification, but as the binding is already sending a message, the message times out. https://community.openhab.org/t/my-struggle-with-zwave-heeeeelp/14113/60 ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38117634-nif-being-used-as-wakeup-is-not-reliable?utm_campaign=plugin&utm_content=tracker%2F38372182&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F38372182&utm_medium=issues&utm_source=github). </bountysource-plugin>

mtryfoss · October 13, 2016, 6:50pm

Sorry, I missed that.

I guess we’ve got at least one device which needs to treat NIF as wake-up then
This might be an issue since the device is not yet identified, which again makes an option for this more difficult?

chris · October 13, 2016, 7:48pm

Yes - some do, some don’t. That’s standards for you ;).