z-wave 7.1 association issue.

Posted on
Sun Oct 29, 2017 3:19 am
shapa offline
Posts: 483
Joined: Sep 08, 2014
Location: Swindon

z-wave 7.1 association issue.

From 7.1, Indigo started to show strange association information - some random device (one) is always added (181 on first screen, 198 on second) , plus "0 unknown ID".
In case I'm deleting this fake device - another will appear.

Additionality, multichannel association is not shown at all (227)

Tried to check association info with Z-Wave.Me software - no issues, everything is correct, no "fakes"

Screenshots attached (the same device with ID 3 - Scene Panel)
Attachments
Screenshot 2017-10-29 09.09.35.png
Screenshot 2017-10-29 09.09.35.png (369.31 KiB) Viewed 2336 times
Screenshot 2017-10-29 09.09.18.png
Screenshot 2017-10-29 09.09.18.png (371.09 KiB) Viewed 2336 times
Screenshot 2017-10-29 08.56.44.png
Screenshot 2017-10-29 08.56.44.png (457.1 KiB) Viewed 2336 times

Posted on
Sun Oct 29, 2017 9:06 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: z-wave 7.1 association issue.

Indigo doesn't support multi-channel associations yet directly in the UI. You can send the raw Z-Wave commands to add/remove those associations but that is obviously not user friendly in the least. Improving this is on the feature request list.

As for the other random associations, what happens if you re-sync the device in Indigo? Indigo reads all of the associations out when it re-syncs. Do the associations still show incorrectly? If so, copy/paste the contents of the Event Log window results of the re-sync (for node ID 3) into a reply for me.

Image

Posted on
Sun Oct 29, 2017 12:29 pm
shapa offline
Posts: 483
Joined: Sep 08, 2014
Location: Swindon

Re: z-wave 7.1 association issue.

Matt, it seems I found the reason

Indigo is not fully compatible with the latest UZB stick firmware (5.27) which I upgraded to after device disappearance. Downgrade back to 5.07 helped to resolve the issue with a "ghost" associations

Yes, resync did not helped.

Razpberry and openzwave didn't saw any wrong associations with the same stick (verified today), only Indigo.

Posted on
Sun Oct 29, 2017 12:34 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: z-wave 7.1 association issue.

When/If you upgrade the UZB firmware again I would be interested in seeing a debug log of a sync with a problem node (3?) both before and after the upgrade so I can see what the difference is in what is sent by the UZB both before and after the firmware update.

Image

Posted on
Tue Nov 14, 2017 2:58 pm
shapa offline
Posts: 483
Joined: Sep 08, 2014
Location: Swindon

Re: z-wave 7.1 association issue.

Matt, tried to revive Remotec and updated firmware again (just to verify)

So "fake" associations (181 and 0) with the latest UZB firmware

Z-Wave Syncing - started for "Move Office Desk Up"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 18 01 01 61
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 18 7C 1F A8 00 20 AD 47 00 92 90 82 08 04 62 00 90 28 00 00 40 2C 90 00 09 00 7A 8C 12
Z-Wave Debug . . getNodeNeighbors: nodeId 024, neighbors: 12, 13, 19, 20, 21, 22, 23, 25, 26, 27, 28, 29, 36, 38, 40, 54, 57, 59, 60, 62, 64, 65, 66, 67, 71, 82, 85, 88, 93, 96, 98, 104, 108, 115, 122, 126, 127, 141, 144, 148, 150, 175, 179, 180, 182, 189, 192, 201, 204, 218, 220, 221, 222, 223, 227, 228, 232
Z-Wave Syncing - retrieved module neighbors list: 12, 13, 19, 20, 21, 22, 23, 25, 26, 27, 28, 29, 36, 38, 40, 54, 57, 59, 60, 62, 64, 65, 66, 67, 71, 82, 85, 88, 93, 96, 98, 104, 108, 115, 122, 126, 127, 141, 144, 148, 150, 175, 179, 180, 182, 189, 192, 201, 204, 218, 220, 221, 222, 223, 227, 228, 232
Z-Wave Syncing - assigning return route to "024 - Move Office Desk Up"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 18 01 A5
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 024, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 18 24 6C C9
Z-Wave Debug RCVD nodeInfoFrame: 01 16 00 49 84 18 10 04 10 01 72 86 70 85 8E 60 25 27 7A 73 EF 25 60 77
Z-Wave Debug . . nodeInfoFrame: node 024, combined class list: 20v1 60v1 25v1 86v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 85v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 18 02 72 04 25 6D C1
Z-Wave Debug RCVD requestManufactureInfo: 01 10 00 04 00 18 08 72 05 01 0F 02 00 10 0A B6 00 2C
Z-Wave Debug . . requestManufactureInfo: node 024, manufacturerId 010F, productId 0200100A
Z-Wave Debug . . requestManufactureInfo: Fibaro System, Double Relay Switch (FGS221)
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Double Relay Switch (FGS221) - 0200100A
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 18 02 86 11 25 6E 23
Z-Wave Debug RCVD requestVersInfoGen: 01 0F 00 04 00 18 07 86 12 03 03 2A 02 01 B6 00 E0
Z-Wave Debug . . requestVersInfoGen: node 024, protoVers 3.42, appVers 2.01
Z-Wave Syncing - retrieved protocol version 3.42, app version 2.01
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 18 03 86 13 60 25 6F 42
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0C 00 04 00 18 04 86 14 60 02 B3 00 A8
Z-Wave Debug . . requestVersInfoCmdClass: node 024, class command 60 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 024, combined class list: 20v1 60v2 25v1 86v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 85v1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : Relay Power Switch (04 : 10 : 01, base 25)
Z-Wave Syncing - retrieved command classes: 20v1 60v2 25v1 86v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Debug SENT requestMultiEndPointInfo: 01 09 00 13 18 02 60 07 25 70 CD
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 0C 00 04 00 18 04 60 08 40 02 B6 00 77
Z-Wave Debug . . requestMultiEndPointInfo: node 024, numEndPoints 2, sameClass True, notStatic False
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 18 03 60 09 01 25 71 C1
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 0E 00 04 00 18 06 60 0A 01 10 01 25 B0 00 04
Z-Wave Debug . . requestMultiEndPointDetails: node 024, endPoint 1, notStatic False, class hierarchy 10 : 01
Z-Wave Debug . . requestMultiEndPointDetails: node 024, combined multi-endpoint types: 1:(10 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 024, combined multi-endpoint classes: 1:[25]
Z-Wave Debug . . requestMultiEndPointDetails: node 024, combined multi-endpoint types: 1:(10 : 01), 2:(10 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 024, combined multi-endpoint classes: 1:[25], 2:[25]
Z-Wave Syncing - retrieved multi-endpoint types: 1:(10 : 01), 2:(10 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[25], 2:[25]
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 18 02 85 05 25 72 28
Z-Wave Debug RCVD requestAssociationGroupCount: 01 0B 00 04 00 18 03 85 06 03 B3 00 D8
Z-Wave Debug . . requestAssociationGroupCount: node 024, group count: 3
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 18 03 85 02 01 25 73 2D
Z-Wave Debug RCVD requestAssociations: 01 0E 00 04 00 18 06 85 03 01 05 00 01 B5 00 DD
Z-Wave Debug . . requestAssociations: node 024, group: 1, num associations: 3, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 1, associations: [1, 181, 0]
Z-Wave Syncing - retrieved group 1 associations: [1, 181, 0]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 18 03 85 02 02 25 74 29
Z-Wave Debug RCVD requestAssociations: 01 0E 00 04 00 18 06 85 03 02 05 00 01 B5 00 DE
Z-Wave Debug . . requestAssociations: node 024, group: 2, num associations: 3, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 2, associations: [1, 181, 0]
Z-Wave Syncing - retrieved group 2 associations: [1, 181, 0]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 18 03 85 02 03 25 75 29
Z-Wave Debug RCVD requestAssociations: 01 0E 00 04 00 18 06 85 03 03 01 00 01 B5 00 DB
Z-Wave Debug . . requestAssociations: node 024, group: 3, num associations: 3, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 3, associations: [1, 181, 0]
Z-Wave Syncing - retrieved group 3 associations: [1, 181, 0]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 2 association to interface already exists (skipping)
Z-Wave Syncing - group 3 association to interface already exists (skipping)
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 18 03 70 05 0E 25 76 D5
Z-Wave Debug RCVD requestConfigVal: 01 0D 00 04 00 18 05 70 06 0E 01 01 B1 00 22
Z-Wave Debug . . requestConfigVal: node 024, parm index 14, value 1 (size 1)
Z-Wave Syncing - retrieved parameter 14 "Enable switch toggle type (bi-stable)" is true
Z-Wave Debug . . requestConfigVal: node 024, combined config vals: 14:1
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 18 03 70 05 10 25 77 CA
Z-Wave Debug RCVD requestConfigVal: 01 0D 00 04 00 18 05 70 06 10 01 01 B6 00 3B
Z-Wave Debug . . requestConfigVal: node 024, parm index 16, value 1 (size 1)
Z-Wave Syncing - retrieved parameter 16 "Power up to last known state" is true
Z-Wave Debug . . requestConfigVal: node 024, combined config vals: 16:1 14:1
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 18 03 70 05 04 25 78 D1
Z-Wave Debug RCVD requestConfigVal: 01 0E 00 04 00 18 06 70 06 04 02 00 00 B3 00 28
Z-Wave Debug . . requestConfigVal: node 024, parm index 4, value 0 (size 2)
Z-Wave Syncing - retrieved parameter 4 "Relay 1 off delay" is 0 * 100 milliseconds
Z-Wave Debug . . requestConfigVal: node 024, combined config vals: 16:1 4:0 14:1
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 18 03 70 05 05 25 79 D1
Z-Wave Debug RCVD requestConfigVal: 01 0E 00 04 00 18 06 70 06 05 02 00 00 B5 00 2F
Z-Wave Debug . . requestConfigVal: node 024, parm index 5, value 0 (size 2)
Z-Wave Syncing - retrieved parameter 5 "Relay 2 off delay" is 0 * 100 milliseconds
Z-Wave Debug . . requestConfigVal: node 024, combined config vals: 16:1 4:0 5:0 14:1
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 18 03 70 05 03 25 7A D4
Z-Wave Debug RCVD requestConfigVal: 01 0D 00 04 00 18 05 70 06 03 01 00 B3 00 2C
Z-Wave Debug . . requestConfigVal: node 024, parm index 3, value 0 (size 1)
Z-Wave Syncing - retrieved parameter 3 "Enable immediate auto-off manual override (both relays)" is false
Z-Wave Debug . . requestConfigVal: node 024, combined config vals: 16:1 3:0 4:0 5:0 14:1
Z-Wave Syncing - complete
Z-Wave Debug SENT requestRelayStatus: 01 0D 00 13 18 06 60 0D 01 01 25 02 25 7B EB
Z-Wave sent "Move Office Desk Up" status request
Z-Wave Debug RCVD multiEndPointPacket: 01 0F 00 04 00 18 07 60 0D 01 01 25 03 FF B3 00 EC
Z-Wave Debug . . multiEndPointPacket: node 024, endPoint 1
Z-Wave Debug RCVD requestRelayStatus: 01 0B 00 04 00 18 03 25 03 FF B3 00 FF
Z-Wave Debug . . requestRelayStatus: node 024, endpoint 1, value 255
Z-Wave received "Move Office Desk Up" status update is on
Z-Wave Debug SENT requestRelayStatus: 01 0D 00 13 18 06 60 0D 01 02 25 02 25 7C EF
Z-Wave sent "Move Office Desk Down" status request
Z-Wave Debug RCVD multiEndPointPacket: 01 0F 00 04 00 18 07 60 0D 02 01 25 03 00 B3 00 10
Z-Wave Debug . . multiEndPointPacket: node 024, endPoint 2
Z-Wave Debug RCVD requestRelayStatus: 01 0B 00 04 00 18 03 25 03 00 B3 00 FF
Z-Wave Debug . . requestRelayStatus: node 024, endpoint 2, value 0
Z-Wave Debug terminatingSyncUI
Z-Wave Debug RCVD basicReportState: 01 0B 00 04 00 2A 03 20 03 FF BF 00 BA
Z-Wave Debug . . basicReportState: node 042, endpoint None, value 255 (no node dispatch)
Z-Wave Debug polling status of node "082 - Front Door LED Stripe Composite" (post-activity energy request)
Z-Wave Debug SENT requestMeterLevel: 01 0A 00 13 52 03 32 01 00 25 7D DC
Z-Wave Debug RCVD requestMeterLevel: 01 12 00 04 00 52 0A 32 02 21 44 00 00 06 68 00 00 AE 00 24
Z-Wave Debug . . requestMeterLevel: node 082, endpoint None, meterType 01, raw value 4400...
Z-Wave Debug . . requestMeterLevel: 16.40 kWh (float: 16.400000)
Z-Wave Debug SENT requestMeterLevel: 01 0A 00 13 52 03 32 01 10 25 7E CF
Z-Wave Debug RCVD requestMeterLevel: 01 12 00 04 00 52 0A 32 02 21 32 00 50 00 00 00 00 AD 00 6F
Z-Wave Debug . . requestMeterLevel: node 082, endpoint None, meterType 01, raw value 3200...
Z-Wave Debug . . requestMeterLevel: 8.0 W (float: 8.000000)
Z-Wave Debug RCVD nodeAwake: 01 0A 00 04 00 56 02 84 07 A5 00 83
Z-Wave Debug . . nodeAwake: node 086
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 56 02 80 02 25 7F 69
Z-Wave Debug . . nodeAwake: inhibit count++ to 1
Z-Wave Debug . . nodeAwake: started inhibit sleep timer
Z-Wave Debug RCVD requestBatteryLevel: 01 0B 00 04 00 56 03 80 03 51 A7 00 D0
Z-Wave Debug . . requestBatteryLevel: node 086, level 81
Z-Wave received "086 - Kitchen Motion Sensor" status update battery level 81%
Z-Wave Debug . . nodeAwake: inhibit count-- to 0
Z-Wave Debug . . nodeAwake: stopping inhibit sleep timer
Z-Wave Debug SENT goToSleep: 01 09 00 13 56 02 84 08 24 80 99
Z-Wave Debug RCVD packet: 01 18 00 13 80 00 00 01 00 7F 7F 7F 7F 7F 00 01 03 00 00 00 00 02 01 00 00 0B (hex)
Z-Wave Debug RCVD multiEndPointPacket: 01 14 00 04 00 66 0C 60 0D 02 02 31 05 01 44 00 00 0B 60 CA 00 38
Z-Wave Debug . . multiEndPointPacket: node 102, endPoint 2
Z-Wave Debug RCVD requestVarSensorStatus: 01 10 00 04 00 66 08 31 05 01 44 00 00 0B 60 CA 00 FF
Z-Wave Debug . . requestVarSensorStatus: node 102, endpoint 2, type 1, raw value 4400...
Z-Wave Debug . . requestVarSensorStatus: 29.12 °C (float: 29.120000)
Z-Wave received "Boiler Room Temperature" sensor update to 29.12 °C
Z-Wave connection reset requested
Schedule Driveway Motion Detected (delayed action)
Action Group Front Door LED Green
Z-Wave connected to Z-Wave 4.61 static controller interface on /dev/cu.u

Posted on
Fri Nov 17, 2017 11:52 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: z-wave 7.1 association issue.

I'm not sure what is going wrong. I just manually decoded this packet:

Z-Wave Debug RCVD requestAssociations: 01 0E 00 04 00 18 06 85 03 02 05 00 01 B5 00 DE
Z-Wave Debug . . requestAssociations: node 024, group: 2, num associations: 3, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 2, associations: [1, 181, 0]

And it does look like the module is returning that it has 3 associations with the hex values: 01, B5 (181 in decimal), and 00. Or at least the UZB is reporting the module returned those 3 values (maybe it is the UZB that is munging something and not the module, given you get different results depending on the firmware version of the UZB).

Image

Posted on
Mon Jan 08, 2018 1:04 pm
iblis offline
Posts: 75
Joined: Sep 16, 2014

Re: z-wave 7.1 association issue.

Same problem here after upgrading the UZB1 firmware from 5.07 to 5.23.

After the upgrade you can no longer include secure devices either (tried on my doorlock ZM1702).

If you downgrade back to 5.07 everything is working find.

I believe z-wave.me are doing some heavy work on the S2 security implementation and the new firmware has some new security features that confuses Indigo.

One thing I do know for sure is that when upgrading UZB1 to 5.27 you can access the new diagnostic screen in Z-Way Expert UI where you can measure network noise, sniff packages etc. If you go back to firmware 5.07 that feature in Z-Way is unavailable.

Posted on
Fri Feb 07, 2020 2:07 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: z-wave 7.1 association issue.

Indigo 7.4.1 is now available and includes support for the USB Stick (ZME UZB1).

Image

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 4 guests