CLOSED --- Z-Wave 500 Series Beta

[Broyd]

I just picked up the new dongle ... I must say I was disappointed with the packaging; there was no antistatic bag and it was in a plain bubble envelope - nothing to protect it from crushing actions. Just saying.

[Scott847]

2 hours ago, blueman2 said:

Can you confirm that the ISY reliably updates with lock/unlock status when the door is manually locked/unlocked?  I can control mine, but it only occasionally updates on the ISY when I lock it by hand.  

Just tried a couple of times and the ISY didn't catch an unlock - still showed Locked in the console. I'll test more thoroughly tomorrow and monitor with a Z-Wave Toolbox device that can listen in on Z-Wave traffic.

[cyberk]

I didn't see an entry for the 500 series beta in the wiki, so I went ahead and created one. Those of you with access to maintain the wiki, please feel free to update it as needed.

[cyberk]

Just a heads up, although this was an existing issue for us prior to the beta, it looks like joining the ISY to an existing z-wave network still doesn't allow communication with already existing secure z-wave devices. If anyone has the ability to test this, I'd like to see if the issue is widespread, or just limited to open-zwave.

[cyberk]

13 hours ago, drprm1 said:

After installing the new dongle is it okay to specify “query at restart” again, or do we leave it off? 

@Michel Kohanim

[MWareman]

Just a heads up, although this was an existing issue for us prior to the beta, it looks like joining the ISY to an existing z-wave network still doesn't allow communication with already existing secure z-wave devices. If anyone has the ability to test this, I'd like to see if the issue is widespread, or just limited to open-zwave.

I believe this is generally the case with all zwave (it’s not an ISY thing, but a zwave thing...). The crypto secret exchanged during enrolling is between the controller and device. No other device is aware of it.

If you transfer primary - the new primary does not know the key and secure devices need reenrolling.

I’m hoping that the key material is backed up with the full backup - so when we change the board and restore the key material is preserved. UDI will confirm (or refute!) I’m sure...

It could be that the secret can never leave the chip...

[cyberk]

Not from what I've seen or read, UDI has confirmed this is an issue in the past, however, it could be with openzwave and not necessarily UDI. There's an experiment I need to perform to see if i can view the ISY secure key in the other controller, I need to get around to it.

On other news, I am seeing that for every "Synchronize nodes All" that I initiate, random ghost sensors get created each time, not a lot, just a few each time. I'll have confirmation on this from another ISY sometime tomorrow, but if anyone cares to test in the meantime, that'd be cool

[blueman2]

38 minutes ago, cyberk said:

On other news, I am seeing that for every "Synchronize nodes All" that I initiate, random ghost sensors get created each time, not a lot, just a few each time. I'll have confirmation on this from another ISY sometime tomorrow, but if anyone cares to test in the meantime, that'd be cool

This is not a dongle issue, but rather came about when multi-channel was implemented.  UDI decided to err on the side of adding nodes which are phantoms, rather than missing ones that are real.  This happens big time with my multi-channel pool controller (Intermatic MultiWave) which has 10 real nodes and about 15 or 20 phantom nodess.  I have created a folder to keep all these phantom nodes in.  If you delete them, they will come back, so just keep them.  

[cyberk]

This is not a dongle issue, but rather came about when multi-channel was implemented.  UDI decided to err on the side of adding nodes which are phantoms, rather than missing ones that are real.  This happens big time with my multi-channel pool controller (Intermatic MultiWave) which has 10 real nodes and about 15 or 20 phantom nodess.  I have created a folder to keep all these phantom nodes in.  If you delete them, they will come back, so just keep them.  

Thanks for the heads up, I went ahead and enabled the “Freeze ISY Nodes” option, hopefully that helps alleviate the issue. I guess my issue is happening with Aeotec Multisensors, I was going to test more but you saved me time


Sent from my iPhone using Tapatalk

[Michel Kohanim]

Hello everyone,

Thanks so much for all the testing and feedback. Extremely helpful especially those related to security. To answer some of your questions:

1. After everything is OK, you can check query at restart

2. Yes secure material are restored. This said we will verify again

There are a couple of new things in the 500 series. One of them is signal to noise ratio below which the dongle starts having communication problems. This is something we can check.

So, based on all the feedback, it seems the issues are mostly related to secure devices.

Thanks again and we shall keep you posted with whatever we find.

With kind regards,

Michel

[MWareman]

Well - something fixed itself - likely by me stopping messing with it.

My locks found routes (Yeah explorer frames!) - and are now reachable, controllable and sending status back to ISY...

Quote

Sun 07/15/2018 00:30:59 : [UZW-CMD 51      ] [ZWCMD cmd.51]

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ] ----------------------------------------------

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ] ZW 014 Kwikset Door Lock

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ] ZW014_1 uid=14 type=4.64.3 mid=144 tid=1 pid=1 model=4

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x72  V1   MANUFACTURER_SPECIFIC

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x86  V1   VERSION

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x98  V1   SECURITY

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ] - Secure

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x72  V1  MANUFACTURER_SPECIFIC

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x86  V1  VERSION

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x98  V1  SECURITY

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x80  V1  BATTERY

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x85  V1  ASSOCIATION

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION

Sun 07/15/2018 00:31:02 : [ZW-SHOW         ]    -  x75  V1  PROTECTION

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x62  V1  DOOR_LOCK

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x63  V1  USER_CODE

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x4E  V2  SCHEDULE_ENTRY_LOCK

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x4C  V1  DOOR_LOCK_LOGGING

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x71  V1  NOTIFICATION

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x8B  V1  TIME_PARAMETERS

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  x20  V1  BASIC

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -  xEF  V0  MARK

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ] 

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ] Last working route from ISY to Node  14 - ZW 014 Kwikset Door Lock

Sun 07/15/2018 00:31:03 : [ZWAVE-TX        ] [010400920E67]                          REQ ZW_GET_LAST_WORKING_ROUTE 

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Node  27 - ZW 027 Multilevel Sensor

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ] 

Sun 07/15/2018 00:31:03 : [ZWAVE-TX        ] [010700800E0000FD8B]                    REQ ZW_GET_ROUTING_INFO 

Sun 07/15/2018 00:31:03 : [ZWAVE-TX        ] [010700800E0100FE89]                    REQ ZW_GET_ROUTING_INFO 

Sun 07/15/2018 00:31:03 : [ZWAVE-TX        ] [010700800E0001FF88]                    REQ ZW_GET_ROUTING_INFO 

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ] Node  14 - ZW 014 Kwikset Door Lock has the following neighbors

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    -          - Node   1 - [This ISY]

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node   5 - ZW 005 On-Off Power Switch

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node   9 - ZW 009 Thermostat

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  18 - ZW 018 On-Off Power Switch

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  20 - ZW 020 On-Off Power Switch

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  22 - ZW 022 Siren

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  23 - ZW 023 Siren

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  26 - ZW 026 Multilevel Sensor

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  27 - ZW 027 Multilevel Sensor

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  28 - ZW 028 Binary Switch

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  30 - ZW 030 Multilevel Sensor

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ]    - Repeater - Node  31 - ZW 031 On-Off Power Switch

Sun 07/15/2018 00:31:03 : [ZW-SHOW         ] 

Sun 07/15/2018 00:31:03 : [ZWAVE-TE        ] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x0E

Sun 07/15/2018 00:31:03 : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E

Sun 07/15/2018 00:31:05 : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[FA99B3262A58711E] ACK,AUTO,EXPLORE From=0x0E

Sun 07/15/2018 00:31:05 : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E

Sun 07/15/2018 00:31:05 : [ZWAVE-TX        ] ...

Sun 07/15/2018 00:31:05 : [ZWAVE-RD        ] [010A00130E038506012500A2]              REQ ZW_SEND_DATA 

Sun 07/15/2018 00:31:05 : [ZW-SHOW         ] Node  14 - ZW 014 Kwikset Door Lock has 1 association group

Sun 07/15/2018 00:31:05 : [ZWAVE-TE        ] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x0E

Sun 07/15/2018 00:31:05 : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E

Sun 07/15/2018 00:31:05 : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[C31505D7A4FB3F61] ACK,AUTO,EXPLORE From=0x0E

Sun 07/15/2018 00:31:06 : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E

Sun 07/15/2018 00:31:06 : [ZWAVE-TX        ] ...

Sun 07/15/2018 00:31:06 : [ZWAVE-RD        ] [010D00130E068503010100012500B9]        REQ ZW_SEND_DATA 

Sun 07/15/2018 00:31:06 : [ZW-SHOW         ]    Associations for group 001 of ZW014_1 ZW 014 Kwikset Door Lock

Sun 07/15/2018 00:31:06 : [ZW-SHOW         ]    Max Associations = 1 

Sun 07/15/2018 00:31:06 : [ZW-SHOW         ]       - Node   1 - [This ISY] 

Sun 07/15/2018 00:31:06 : [ZW-SHOW         ] 

Sun 07/15/2018 00:31:06 : [ZW-SHOW         ] ----------------------------------------------

ZW_027 is an Aeotec Multisensor 5 securely enrolled. It appears to have taken on duty of repeating the connection to my locks. I have to say - the diagnostic info now in the logs is fantastic...

All my Multisensors are reporting in, as is my thermostat and the locks. I'll take another look in the morning - but at this point all looks very good.

Thank you Michel and all at UDI!

[skunkiechris]

On 7/13/2018 at 9:50 PM, Michel Kohanim said:

Hi all, 

For those who haven't installed yet, please do not do a Network Heal initially. Please test everything as is and do a Network Heal if and only if necessary.

We are testing a few scenarios here.

Michel

Ha, that post was just a few hours too late. ?  I did do a heal, and lost connectivity with several wireless devices, mostly Dome motion sensors oddly.  Their neighbors all showed them correctly, but triggering them did nothing - no entries in the log at all.  After manually waking them up and showing all info, it showed correct neighbors, but for last route to ISY it showed no route (or something to that effect).  After doing a repair links, it immediately showed updates pending to write to device.  After writing updates, each started working again...so all seems to be well now.

[Broyd]

Hi MWareman

I have noticed that all of your zwave device displays [ZW-SHOW         ]   start with  [UZW-CMD 51      ] [ZWCMD cmd.51]

Where does that UZW command come from? When I do one of these displays (Z-Wave > Show information in event viewer)  , it starts with [ZW-SHOW         ] . Am I missing something when I get this Z-Wave device information? Thanks!

[skunkiechris]

Two Kwikset locks here, no issues after the upgrade - statuses are being reported, no errors in the log associated with them (at least that I've noticed) and they are reliably controllable.

[Bumbershoot]

I just had a chance to install the new board this morning.  It took 3 attempts to successfully perform a Z-Wave restore, but all is well now.  No discernible differences.

Edit: If it's interesting, I excluded and included my Schlage deadbolt while it remained in the door, and it appears to have excluded/included just fine.  It has a new Z-Wave number, but it seems to be securely included, and as far as I can tell, it's working entirely as intended.  I have several Z-Wave repeaters between it and the ISY.

[Scott847]

An update... The Schlage manual lock/unlock status updates aren't getting to the ISY because of some kind of routing error.

Below is a packet trace from a Z-Wave Toolbox showing this. Device #45 is the Schlage BE469NX lock and Device #7 is an Aeotec DSB28-ZWUS Energy Meter and both are securely included. The "Routed Error" message is coming from the Energy Meter back to the lock and it appears nothing is coming from the ISY.

Michel, what should I do to troubleshoot further? I haven't done a heal yet per your note above.

Z-Wave Toolbox Packet Trace
*** 2018-07-15 13:29:10.417 RSSI 50, Source 45, Destination 1, Route (45)>7-(1), Command "Z-Wave Protocol Command 60"
*** 2018-07-15 13:29:11.212 RSSI 57, Source 7, Destination 45, Route (7)>(45), Command "ACK"
*** 2018-07-15 13:29:12.711 RSSI 58, Source 45, Destination 1, Route (45)-7>(1), Command "Z-Wave Protocol Command 60"
*** 2018-07-15 13:29:13.727 RSSI 57, Source 45, Destination 1, Route (45)-7>(1), Command "Z-Wave Protocol Command 60"
*** 2018-07-15 13:29:13.757 RSSI 58, Source 45, Destination 1, Route (45)-7>(1), Command "Z-Wave Protocol Command 60"
*** 2018-07-15 13:29:13.785 RSSI 57, Source 1, Destination 45, Route (45)<7-(1), Command "Routed Error (2nd hop)"
*** 2018-07-15 13:29:13.812 RSSI 57, Source 1, Destination 45, Route (45)<7-(1), Command "Routed Error (2nd hop)"
*** 2018-07-15 13:29:13.840 RSSI 57, Source 1, Destination 45, Route (45)<7-(1), Command "Routed Error (2nd hop)"

 

21 hours ago, blueman2 said:

Can you confirm that the ISY reliably updates with lock/unlock status when the door is manually locked/unlocked?  I can control mine, but it only occasionally updates on the ISY when I lock it by hand.  

 

18 hours ago, Scott847 said:

Just tried a couple of times and the ISY didn't catch an unlock - still showed Locked in the console. I'll test more thoroughly tomorrow and monitor with a Z-Wave Toolbox device that can listen in on Z-Wave traffic.

 

14 hours ago, Michel Kohanim said:

So, based on all the feedback, it seems the issues are mostly related to secure devices.

 

[blueman2]

I reinstalled my Series 500 dongle today and let it 'settle' for a while.  After about 4 hours, still not connecting well to many of my z-wave devices that were working fine with old dongle.  Interesting is that my Front Door Lock (Schlage BE469) has four V6 repeaters between it and the ISY, yet it sees none of them and is using a weird routing using non-v6 repeaters that are much, much further away.  As a result, the front door lock works less than 10% of the time right now.  The ISY can see all four of the V6 repeaters that are very close to the door, but the door will not use them in the route.

See below that all the repeaters that the door sees are non-V6 devices.  I have 5 V6 repeater devices in my house, and the front door sees none of them.    

 

Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] ----------------------------------------------
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] ZW 047 Front Door
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] ZW047_1 uid=47 type=4.64.3 mid=59 tid=25409 pid=20548 model=2
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x22  V1   APPLICATION_STATUS
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x72  V1   MANUFACTURER_SPECIFIC
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x7A  V2   FIRMWARE_UPDATE_MD
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x98  V1   SECURITY
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x86  V1   VERSION
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] - Secure
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x5D  V2  ANTITHEFT
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x85  V1  ASSOCIATION
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x20  V1  BASIC
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x80  V1  BATTERY
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x62  V2  DOOR_LOCK
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x71  V3  NOTIFICATION
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  x63  V1  USER_CODE
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    -  xEF  V0  MARK
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] 
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] Last working route from ISY to Node  47 - ZW 047 Front Door
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    - Node  56 - ZW 056 Repeater Garage
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] 
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] Node  47 - ZW 047 Front Door has the following neighbors
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    - Repeater - Node  14 - ZW 014 Den Subwoofer Amp
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    - Repeater - Node  26 - ZW 026 Living Room TV-DVR
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    - Repeater - Node  48 - ZW 048 Aeon Repeater LR
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ]    - Repeater - Node  56 - ZW 056 Repeater Garage
Sun 07/15/2018 01:08:06 PM : [ZW-SHOW         ] 
Sun 07/15/2018 01:08:13 PM : [ZW-TX-FAILED] enc=Ok uid=47.0 cmd=0x85.05 ASSOCIATION
Sun 07/15/2018 01:08:18 PM : [ZW-TX-FAILED] enc=Fail uid=47.0 cmd=0x85.05 ASSOCIATION
Sun 07/15/2018 01:08:23 PM : [     ZW047_1]      ERR   1
Sun 07/15/2018 01:08:23 PM : [ZW-TX-FAILED] enc=Ok uid=47.0 cmd=0x85.05 ASSOCIATION
Sun 07/15/2018 01:08:23 PM : [ZW-SHOW         ] Node  47 - ZW 047 Front Door cannot retrieve association groups
Sun 07/15/2018 01:08:23 PM : [ZW-SHOW         ] 
Sun 07/15/2018 01:08:23 PM : [ZW-SHOW         ] ----------------------------------------------

 

[Scyto]

@blueman2what tests are you doing on the BE schlage, my locks have NEVER worked when using nenighbours to reach them for certain actions (like incusion or user code changes), i had to take them physically next to the ISY.  ISY support never  solved this and I gave up as i have secondary controllers that work just fine with them.  (those actions work finde when using the secondary controller like a Vera or HomSeer Key.  I was hoping this new module was going to fix that issue.  My new radio arrives tomorrow, what tests could i perform before then....?

[MWareman]

Hi MWareman
I have noticed that all of your zwave device displays [ZW-SHOW         ]   start with  [uZW-CMD 51      ] [ZWCMD cmd.51]
Where does that UZW command come from? When I do one of these displays (Z-Wave > Show information in event viewer)  , it starts with [ZW-SHOW         ] . Am I missing something when I get this Z-Wave device information? Thanks!

That may be from another command - not sure. I did manually remove some log entries from what I posted because they were for other devices not related to the post - I could have missed this one. I’ve no idea where it came from.

[blueman2]

@Scyto,  All my Schlage locks required them to be right next to the ISY when they were included.  This was on the old z-wave dongle.  So I am not sure about the new dongle.  Once included, I have always been able to use repeaters to help get the signal across the house when using the old dongle.  With the new 500 Series, the repeaters do not appear to be working correctly, but I am not sure.  

 

[MWareman]

I just had a chance to install the new board this morning.  It took 3 attempts to successfully perform a Z-Wave restore, but all is well now.  No discernible differences.
Edit: If it's interesting, I excluded and included my Schlage deadbolt while it remained in the door, and it appears to have excluded/included just fine.  It has a new Z-Wave number, but it seems to be securely included, and as far as I can tell, it's working entirely as intended.  I have several Z-Wave repeaters between it and the ISY.

Perhaps one of the nice features of the 500 series chip - network wide inclusion.

[Bumbershoot]

2 hours ago, blueman2 said:

@Scyto,  All my Schlage locks required them to be right next to the ISY when they were included.  This was on the old z-wave dongle.  So I am not sure about the new dongle.  Once included, I have always been able to use repeaters to help get the signal across the house when using the old dongle.  With the new 500 Series, the repeaters do not appear to be working correctly, but I am not sure.  

 

I don't know much about Z-Wave, but I did an exclude/include on my lock while it was in place, and it included securely.  After a network heal, all the neighbors showed up as expected.  I don't know what significance the 'association groups' have.

Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] ----------------------------------------------
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] ZW 002 Schlage Door Lock
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] ZW002_1 uid=2 type=4.64.3 mid=59 tid=25409 pid=20548 model=2
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x22  V1   APPLICATION_STATUS
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x72  V1   MANUFACTURER_SPECIFIC
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x7A  V2   FIRMWARE_UPDATE_MD
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x98  V1   SECURITY
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x86  V1   VERSION
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] - Secure
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x5D  V2  ANTITHEFT
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x85  V1  ASSOCIATION
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x20  V1  BASIC
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x80  V1  BATTERY
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x70  V1  CONFIGURATION
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x62  V2  DOOR_LOCK
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x71  V3  NOTIFICATION
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  x63  V1  USER_CODE
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    -  xEF  V0  MARK
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] 
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] Last working route from ISY to Node   2 - ZW 002 Schlage Door Lock
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Node  13 - Master Fan Switch
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Node  12 - East Auto Door
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] 
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] Node   2 - ZW 002 Schlage Door Lock has the following neighbors
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node   7 - ZW 007 Siren
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node   8 - ZW 008 Multilevel Sensor
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node   9 - ZW 009 Multilevel Sensor
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node  10 - ZW 010 Water Cop
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node  11 - West Auto Door
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node  12 - East Auto Door
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ]    - Repeater - Node  14 - Office Dimmer Switch
Sun 07/15/2018 17:37:31 : [ZW-SHOW         ] 
Sun 07/15/2018 17:37:46 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION
Sun 07/15/2018 17:37:53 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION
Sun 07/15/2018 17:37:53 : [ZW-SHOW         ] Node   2 - ZW 002 Schlage Door Lock cannot retrieve association groups
Sun 07/15/2018 17:37:53 : [ZW-SHOW         ] 
Sun 07/15/2018 17:37:53 : [ZW-SHOW         ] ----------------------------------------------

 

[rlcrook]

I received the new dongle yesterday at same time I received brand new ISY to replace one that a storm took out. After getting the new ISY up and running  on 5.0.13 I added all my insteon devices, and all is well on that front. this morning I put the new dongle in and proceeded to add my z-wave devices starting by doing a factory reset on aeotec repeater located about 5 ft away from the ISY and was successful adding that. Next up was my go control GC-TBZ48 thermostat. I tried removing /excluding it multiple times with no success, ultimately having to really hunt down instructions on how to do a factory reset on t-state. Once reset to factory defaults, the ISY was able to find and add it very quickly.

I have a go-control dimmer and GE z-wave dimmer that no matter what I do, I can't seem to either get the ISY to exclude or to factory reset the switches so I then add them to the ISY. I know I must be missing something, but I'm not sure what is. Any suggestions on how I can get these into my ISY?

 

[blueman2]

@Michel Kohanim, not sure if this is meaningful, but I have noticed several of my z-wave devices have 2 identical association groups.  Both are between the device and the ISY.  Just wanted to mention that in case it is relevant.  

Sun 07/15/2018 03:57:12 PM : [ZW-SHOW         ] Node  51 - ZW 051 V6 Plug MBR has 2 association groups
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]    Associations for group 001 of ZW051_1 ZW 051 V6 Plug MBR
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]    Max Associations = 5 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]       - Node   1 - [This ISY] 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ] 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]    Associations for group 002 of ZW051_1 ZW 051 V6 Plug MBR
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]    Max Associations = 5 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ]       - Node   1 - [This ISY] 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ] 
Sun 07/15/2018 03:57:20 PM : [ZW-SHOW         ] ----------------------------------------------

 

[cyberk]

@blueman2

Review the documentation for your Z-wave devices. Each device has its own set of parameters and association groups. Different association groups do different things, but usually, every zwave device has at least one association group, and that is the lifeline group.

The nodes in that group are the ones that will receive instant status of changes, although from what I understand, they’re no longer needed in zwave+ (500) devices since they all support HAIL by default.

So it’s possible your devices have 2 association groups, and that each association group does something else. But we won’t know for sure until we see the documentation for that specific device.


Sent from my iPhone using Tapatalk