Problem with controlling new device

[firstone]

So, I have a brand new ISY and trying to add a Leviton plug-in on/off module. Devices seems to be added successfully. But I don't have on/off buttons. Only All On / All Off. Sending All On  or All On produces failure. 

Thu 11/21/2019 01:05:04 PM : [ZWAVE-TX ZW002_1] [27/04] CC=0x27 cmd=0x04 [] ACK,AUTO,EXPLORE To=0x02
Thu 11/21/2019 01:05:07 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02
Thu 11/21/2019 01:05:11 PM : [ZWAVE-WAIT      ] Waiting 24 ticks for retry 1 of 2
Thu 11/21/2019 01:05:13 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02
Thu 11/21/2019 01:05:18 PM : [ZWAVE-WAIT      ] Waiting 24 ticks for retry 2 of 2
Thu 11/21/2019 01:05:19 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02
Thu 11/21/2019 01:05:24 PM : [ZW-TX-FAILED] 2.0/0x86.13
Thu 11/21/2019 01:05:31 PM : [        Time] 13:05:41 0(0)
 

Pressing a button on plug-in module doesn't seem to do anything either. 

Thu 11/21/2019 01:06:41 PM : [ZWAVE-RX ZW002_1] [82/01] Hail ACK,AUTO,EXPLORE From=0x02
Thu 11/21/2019 01:06:41 PM : [D2D EVENT   ] Event [ZW002_1] [HAIL] [0] uom=0 prec=-1
Thu 11/21/2019 01:06:41 PM : [     ZW002_1]     HAIL   0
 

I feel like I'm missing something basic but not sure what it is. Could something be defective?

I've tried removing it, resetting ISY z-wave board to factory default and adding it back. Still the same.

[lilyoyo1]

What is the model number

[simplextech]

Restart the java admin console.  Close it and re-open and see if the device profile/commands is updated.

[firstone]

2 hours ago, lilyoyo1 said:

What is the model number

Same one you've tried to help me with in firmware thread = Leviton Vizia plugin (VRC0P), which is a different issue. Z-Wave version 6.81.00, FW 5.0.16.

[firstone]

1 hour ago, simplextech said:

Restart the java admin console.  Close it and re-open and see if the device profile/commands is updated.

 

Didn't help.

[firstone]

Also, upgrade z-wave firmware fails. But I've read in another thread it's normal and not necessary. Not sure.

[lilyoyo1]

36 minutes ago, firstone said:

Same one you've tried to help me with in firmware thread = Leviton Vizia plugin (VRC0P), which is a different issue. Z-Wave version 6.81.00, FW 5.0.16.

Are you sure you are using the right product? Your previous issue was with a dimmer with the same model number but now its an on/off module with the same model#. Levitons dimmers and on/off modules have different part numbers than what you provided. According to levitons website, the device you are trying to add is a serial interface module which would explain your issues.

Model # you provided: https://www.leviton.com/en/products/VRC0P-1LW

Leviton dimmer: https://www.leviton.com/en/products/dzpd3-2bw

Leviton On/off: https://www.leviton.com/en/products/dzpa1-2bw

[firstone]

20 hours ago, lilyoyo1 said:

Are you sure you are using the right product? Your previous issue was with a dimmer with the same model number but now its an on/off module with the same model#. Levitons dimmers and on/off modules have different part numbers than what you provided. According to levitons website, the device you are trying to add is a serial interface module which would explain your issues.

Model # you provided: https://www.leviton.com/en/products/VRC0P-1LW

Leviton dimmer: https://www.leviton.com/en/products/dzpd3-2bw

Leviton On/off: https://www.leviton.com/en/products/dzpa1-2bw

Typo on my part. It's VRP03.

[Chris Jahn]

There is an issue with some Leviton Z-Wave products where it says it supports the VERSION command class, but does not support some of its mandatory features.  We've added some custom code to ISY as a workaround to this deficiency in the Leviton products.  It will be available in the next build.

[firstone]

41 minutes ago, Chris Jahn said:

There is an issue with some Leviton Z-Wave products where it says it supports the VERSION command class, but does not support some of its mandatory features.  We've added some custom code to ISY as a workaround to this deficiency in the Leviton products.  It will be available in the next build.

Thank you. As a side note, not sure if you've seen my different comment in firmware thread - it appears when ISY doesn't any ANY nodes, you cannot add z-wave device. It's adding it to z-wave nodes but fails crating ISY node. Once I've added insteon device, it worked fine as far as adding z-wave devices goes.

[simplextech]

I have an ISY that I test with that only has z-wave devices and has never been connected to a PLM.

[firstone]

14 minutes ago, simplextech said:

I have an ISY that I test with that only has z-wave devices and has never been connected to a PLM.

Mine was also fresh from UDI and I've upgraded to 5.0.16 before I've attempted to add anything. Not sure if any of those are factors. But it is/was entirely reproducible. I've done it 3 or 4 times with the same result.

[Chris Jahn]

3 minutes ago, firstone said:

Mine was also fresh from UDI and I've upgraded to 5.0.16 before I've attempted to add anything. Not sure if any of those are factors. But it is/was entirely reproducible. I've done it 3 or 4 times with the same result.

Have you tried factory resetting the ISY Z-Wave dongle first?  I've tried this several times with a Leviton RZP03 and it works every time.

[firstone]

3 minutes ago, Chris Jahn said:

Have you tried factory resetting the ISY Z-Wave dongle first?  I've tried this several times with a Leviton RZP03 and it works every time.

I've tried factory resetting z-wave dongle as well as leviton module multiple times. 

[Chris Jahn]

2 minutes ago, firstone said:

I've tried factory resetting z-wave dongle as well as leviton module multiple times. 

Have you tried factory resetting the ISY itself?

[firstone]

4 minutes ago, Chris Jahn said:

Have you tried factory resetting the ISY itself?

No, but since I don't have much connected yet I don't mind trying.

[firstone]

30 minutes ago, Chris Jahn said:

Have you tried factory resetting the ISY itself?

Resetting ISY didn't do anything. But I've played with it a little more and I only unable to add z-wave device when ISY was brought up with no PLM connected and it said it was running in safe mode. So if that's caused by safe mode, I guess it works as intended. I've figured z-wave functionality would be separate from Insteon. 

Once PLM is plugged in and ISY rebooted, I was able to add z-wave device. Although it's still missing profile and I cannot control it. 

At one point, during my experiment, it was created with profile at one point. But even then, it wouldn't respond to on/off commands.

If you think this is a bug in Leviton that you're going to put workaround for, I'll wait for it. Kind of just want to make sure it's not defective Leviton module or z-wave dongle.

Here's the log just in case, again.

Fri 11/22/2019 04:40:18 PM : [UZW-CMD 1       ] Start Include

Fri 11/22/2019 04:40:18 PM : Listening for Z-Wave devices to add to the network

Fri 11/22/2019 04:40:31 PM : Z-Wave device detected, retrieving info 2

Fri 11/22/2019 04:40:31 PM : Z-Wave device detected, retrieving info 3

Fri 11/22/2019 04:40:31 PM : Z-Wave device detected, retrieving info 5

Fri 11/22/2019 04:40:31 PM : [ZWAVE-TX        ] [0105004A85EDD8]                        REQ ZW_ADD_NODE_TO_NETWORK 

Fri 11/22/2019 04:40:31 PM : Adding Z-Wave devices stopped

Fri 11/22/2019 04:40:32 PM : [ZWAVE-TX        ] [01030020DC]                            REQ MEMORY_GET_ID 

Fri 11/22/2019 04:40:32 PM : [ZWAVE-TX        ] [01030002FE]                            REQ SERIAL_API_GET_INIT_DATA 

Fri 11/22/2019 04:40:32 PM : [ZWAVE-TX        ] [01030005F9]                            REQ ZW_GET_CONTROLLER_CAPABILITIES 

Fri 11/22/2019 04:40:32 PM : Device 2 of type 4.17.4 included into Z-Wave network

Fri 11/22/2019 04:40:32 PM : [ZWAVE-TX     2.0] [72/04] CC=0x72 cmd=0x04 [] ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:32 PM : [ZWAVE-RX     2.0] [72/05] CC=0x72 cmd=0x05 [001D0202030B] ACK,AUTO,EXPLORE From=0x02

Fri 11/22/2019 04:40:32 PM : Adding ISY node(s) for new Z-Wave device 2 type 4.17.4

Fri 11/22/2019 04:40:32 PM : [ZWAVE-TX ZW002_1] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:32 PM : [ZWAVE-RX ZW002_1] [85/06] Assoc Groupings Report supported=0x01 ACK,AUTO,EXPLORE From=0x02

Fri 11/22/2019 04:40:33 PM : [ZWAVE-TX ZW002_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:33 PM : [ZWAVE-RX ZW002_1] [85/03] Assoc Report grp=0x01 max=0xE8 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x02

Fri 11/22/2019 04:40:33 PM : Adding additional nodes for new Z-Wave device 2

Fri 11/22/2019 04:40:33 PM :   ...addNodes(uid=2,SWITCH_MULTILEVEL,cc=38,ver=0,sec=F)

Fri 11/22/2019 04:40:33 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:38 PM : [ZWAVE-WAIT      ] Waiting 25 ticks for retry 1 of 2

Fri 11/22/2019 04:40:39 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:44 PM : [ZWAVE-WAIT      ] Waiting 20 ticks for retry 2 of 2

Fri 11/22/2019 04:40:45 PM : [ZWAVE-TX ZW002_1] [86/13] CC=0x86 cmd=0x13 [26] ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:50 PM : [ZW-TX-FAILED] 2.0/0x86.13

Fri 11/22/2019 04:40:50 PM : [ZWAVE-TX ZW002_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:50 PM : [ZWAVE-RX ZW002_1] [85/03] Assoc Report grp=0x01 max=0xE8 frames=0x00 nodes= ACK,AUTO,EXPLORE From=0x02

Fri 11/22/2019 04:40:50 PM : [ZWAVE-TX ZW002_1] [85/01] Assoc Set grp=0x01 nodes=0x01 ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:50 PM : [ZWAVE-TX ZW002_1] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x02

Fri 11/22/2019 04:40:50 PM : [ZWAVE-RX ZW002_1] [85/03] Assoc Report grp=0x01 max=0xE8 frames=0x00 nodes=0x01 ACK,AUTO,EXPLORE From=0x02

Fri 11/22/2019 04:40:50 PM : [All         ] Writing 0 bytes to devices

Fri 11/22/2019 04:40:50 PM : [All         ] Writing 0 bytes to devices

 

[Chris Jahn]

Yes, that is definitely it.  If ISY is in safe mode then most functionality is unavailable.  As for the other issue, based on the log it should work fine with next build.