# Best practice to debugging Z-Wave

**URL:** <https://community.openhab.org/t/best-practice-to-debugging-z-wave/133347>\
**Category:** Bindings\
**Tags:** zwave1\
**Created:** [February 15, 2022, 11:26pm UTC](https://community.openhab.org/t/best-practice-to-debugging-z-wave/133347 "2022-02-15T23:26:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [February 15, 2022, 11:43pm UTC](https://community.openhab.org/t/best-practice-to-debugging-z-wave/133347/2 "2022-02-15T23:43:39Z")

</div>

You gonna get a lot of advice. There is a good post [here](https://community.openhab.org/t/solved-unresponsive-z-wave-network-tools-and-approaches-to-track-down-the-issues/122446).

My advice is to get a zniffer. It is talked about in that post. You can guess around the problem or you can know. Plus you can watch in real time versus Debug, then viewer.

By the way I do not think 9000 ms delay is possible. The messages have a five second limit.

My 2 cents good luck

Bob

---

_[View the full topic](https://community.openhab.org/t/best-practice-to-debugging-z-wave/133347)._