I have seen instances in the SDK Release notes where there are lockups (or unresponsive state) in the ZWave SDK.

How can we trust that the watchdog is being utilized properly in the library when the following IDs have resulted in lockups in the past and have been subsequently fixed?

ID# 463149, 679455, 472564, 501141

In the example projects, the WDOG is enabled and disabled in different places.

There are, however, ZERO WDOG feeds. Is this intentional?

Was there an intended place to put the Feeds and it just got left out?

Yes, this is TRIAC but SiLabs TRIACDRV does not seem to be extensible to this implementation.

We do not use ACMP nor do we need to.

TRIACDRV does no use PWM but only a set action.

We use only the positive going interrupt (this is much better in implementation).

If it would be easier, we would like to do the SET action on the TRIAC in CC0 and CC2 and the CLEAR action on CC1 and OF.

You should not need any pictures for that.

Yes, this is TRIAC but SiLabs TRIACDRV for the Series 1 does not seem to be extensible to this implementation.

We do not use ACMP nor do we need to.

TRIACDRV does no use PWM but only a set action.

We use only the positive going interrupt (this is much better in implementation).

If it would be easier, we would like to do the SET action on the TRIAC in CC0 and CC2 and the CLEAR action on CC1 and OF.

You should not need any pictures for that.

We have devices in the field since 3/20 which have 7.12.2 SDK. IT looks like 7.13.3 fixed "sticky" LWR routes.

Was wondering if there was anything the controller could do until we put out a FW update with the new SDK.

What is happening is that the LWR for the nodes (or whatever you call it) is not being used and the devices are sending out explorer frames all the time.

We know we need to update the SDK but what can be done NOW by the controller software to "hide" this issue until we release newer  FW.

We have devices in the field since 3/20 which have 7.12.2 SDK. IT looks like 7.13.3 fixed "sticky" LWR routes.

Was wondering if there was anything the controller could do until we put out a FW update with the new SDK.

What is happening is that the LWR for the nodes (or whatever you call it) is not being used and the devices are sending out explorer frames all the time.

We know we need to update the SDK but what can be done NOW by the controller software to "hide" this issue until we release newer  FW.