PROBLEM end of SYNC with AN158 Everspring and Z Stick GEN5

Hello
I recently decided to change from my old Z Stick S2 to a new Z Stick GEN5 by a transfer from a controller to an other one using HS ZEE and Danfoss soft. After changing associations from the previous ID 1 to the new one ID 188 of my new Z Stick GEN5 controller, I begun to have some ack problems with AN158 evers ping devices. I have 10 AN158 devices. Some are working well and some other no. For those which are not working well with ack problems or lack of energy report,I tried to exclude and re include but the process of inclusion stops after the association to the controller (see below) and the message "device must be asleep or unreachable" appears.
Any idea ?
Thanks a lot
Patrice

Z-Wave Syncing - started for "Prise Mur Piano LED"
Z-Wave Syncing - retrieved module neighbors list: 2, 7, 9, 11, 12, 17, 22, 24, 48, 80, 81, 82, 83, 84, 85, 87, 91, 92, 109, 111, 114, 119, 120, 122, 123, 125, 126, 128, 129, 130, 131, 132, 133, 139, 140, 143, 145, 147, 154, 155, 159, 162, 165, 222, 228
Z-Wave Syncing - assigning return route to "141 - Prise Mur Piano LED"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Everspring - 0060, Appliance Module (AN158) - 00040002
Z-Wave Syncing - retrieved protocol version 2.64, app version 1.01
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 85v1 86v1 27v1 72v1 70v1 32v2 25v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved group 1 associations: [188]
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)

26 mars 2018 à 23:45:52
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "141 - Prise Mur Piano LED". Module might be asleep, or is unreachable.

[matt (support)]

If you temporarily plug the AN158 into an outlet close to the Z-Stick can the sync complete?

If you temporarily plug the AN158 into an outlet close to the Z-Stick can the sync complete?

Hello Matt
I did it but unfortunately it’s the same. I’ve using zwave with indigo for many and this is the first time I have such problem with this relay
I have many others kind of relays (Fibaro) for example which are working and sync well but 7 on my 10 AN158 have the same issue
Thanks again for your help
Patrice

[matt (support)]

Does it always fail at the same part in the sync? Try turning on Indigo's Z-Wave debug logging checkbox (via the Interfaces->Z-Wave->Configure... menu item), then sync a couple of them that are failing again. Copy/paste the results of both and we'll see if we can get any more information about the failures.

Hello Matt
Here the result with another AN158 which is not syncing until the end
Thanks a lot
Patrice


Z-Wave Syncing - started for "024 - Relay Power Switch"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 18 01 01 61
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 62 6C 23 10 10 80 00 08 00 80 D7 0C 00 50 C2 36 1A 5C 05 46 16 00 20 00 00 00 00 10 18 3F
Z-Wave Debug . . getNodeNeighbors: nodeId 024, neighbors: 2, 6, 7, 11, 12, 14, 15, 17, 18, 22, 29, 37, 48, 60, 80, 81, 82, 83, 85, 87, 88, 91, 92, 109, 111, 114, 119, 120, 122, 123, 125, 126, 130, 132, 133, 139, 140, 141, 143, 145, 147, 154, 155, 159, 162, 163, 165, 182, 221, 228, 229
Z-Wave Syncing - retrieved module neighbors list: 2, 6, 7, 11, 12, 14, 15, 17, 18, 22, 29, 37, 48, 60, 80, 81, 82, 83, 85, 87, 88, 91, 92, 109, 111, 114, 119, 120, 122, 123, 125, 126, 130, 132, 133, 139, 140, 141, 143, 145, 147, 154, 155, 159, 162, 163, 165, 182, 221, 228, 229
Z-Wave Syncing - assigning return route to "024 - Relay Power Switch"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 18 BC 18
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 EB 4E
Z-Wave Debug RCVD nodeInfoFrame: 01 11 00 49 84 18 0B 04 10 01 25 20 72 86 27 85 32 70 34
Z-Wave Debug . . nodeInfoFrame: node 024, combined class list: 20v1 85v1 86v1 27v1 72v1 70v1 32v1 25v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 18 02 72 04 25 EC 40
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 18 08 72 05 00 60 00 04 00 02 F4
Z-Wave Debug . . requestManufactureInfo: node 024, manufacturerId 0060, productId 00040002
Z-Wave Debug . . requestManufactureInfo: Everspring, Appliance Module (AN158)
Z-Wave Syncing - retrieved manufacture and model names: Everspring - 0060, Appliance Module (AN158) - 00040002
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 18 08 72 05 00 60 00 04 00 02 F4
Z-Wave Debug . . requestManufactureInfo: node 024, manufacturerId 0060, productId 00040002
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 18 02 86 11 25 ED A0
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 18 07 86 12 06 02 40 01 01 39
Z-Wave Debug . . requestVersInfoGen: node 024, protoVers 2.64, appVers 1.01
Z-Wave Syncing - retrieved protocol version 2.64, app version 1.01
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 18 03 86 13 32 25 EE 91
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 18 04 86 14 32 02 4F
Z-Wave Debug . . requestVersInfoCmdClass: node 024, class command 32 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 024, combined class list: 20v1 85v1 86v1 27v1 72v1 70v1 32v2 25v1
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 85v1 86v1 27v1 72v1 70v1 32v2 25v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 18 02 85 05 25 EF B5
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 18 03 85 06 02 68
Z-Wave Debug . . requestAssociationGroupCount: node 024, group count: 2
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 07 06 31 05 04 22 00 03 E7
Z-Wave Debug . . requestVarSensorStatus: node 007, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.3 W (float: 0.300000)
Z-Wave Debug received "Prise Lave Vaisselle" power load to 0.3 W
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 18 03 85 02 01 25 F0 AE
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 18 06 85 03 01 01 00 BC D3
Z-Wave Debug . . requestAssociations: node 024, group: 1, num associations: 1, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 1, associations: [188]
Z-Wave Syncing - retrieved group 1 associations: [188]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 18 03 85 02 02 25 F1 AC
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 18 05 85 03 02 04 00 6D
Z-Wave Debug . . requestAssociations: node 024, group: 2, num associations: 0, max associations: 4, replies left: 0
Z-Wave Debug . . requestAssociations: node 024, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug SENT requestMeterInfo: 01 09 00 13 18 02 32 03 25 F2 19
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 07 06 31 05 04 22 00 00 E4
Z-Wave Debug . . requestVarSensorStatus: node 007, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.0 W (float: 0.000000)
Z-Wave Debug received "Prise Lave Vaisselle" power load to 0.0 W
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 06 08 32 02 21 12 00 00 00 00 F8
Z-Wave Debug . . requestMeterLevel: node 006, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 0 W (float: 0.000000)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestMeterInfo: 01 09 00 13 18 02 32 03 25 F3 18
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 0B 08 32 02 21 12 00 01 00 00 F4
Z-Wave Debug . . requestMeterLevel: node 011, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 1 W (float: 1.000000)
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 12 08 32 02 21 12 00 01 00 00 ED
Z-Wave Debug . . requestMeterLevel: node 018, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 1 W (float: 1.000000)
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 07 06 31 05 04 22 00 03 E7
Z-Wave Debug . . requestVarSensorStatus: node 007, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.3 W (float: 0.300000)
Z-Wave Debug received "Prise Lave Vaisselle" power load to 0.3 W
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 07 06 31 05 04 22 00 00 E4
Z-Wave Debug . . requestVarSensorStatus: node 007, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.0 W (float: 0.000000)
Z-Wave Debug received "Prise Lave Vaisselle" power load to 0.0 W
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 11 08 32 02 21 12 00 05 00 00 EA
Z-Wave Debug . . requestMeterLevel: node 017, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 5 W (float: 5.000000)
Z-Wave received "Prise Lave et Seche Linge" power load to 5 W
Z-Wave Debug RCVD requestMeterLevel: 01 10 00 04 00 50 0A 32 02 21 44 00 00 00 27 00 00 C3
Z-Wave Debug . . requestMeterLevel: node 080, endpoint None, meterType 01, raw value 4400...
Z-Wave Debug . . requestMeterLevel: 0.39 kWh (float: 0.390000)
Z-Wave Debug . . requestVarSensorStatus: ignored (no device found for dispatch)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestMeterInfo: 01 09 00 13 18 02 32 03 25 F4 1F
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 B8 08 32 02 21 12 00 00 00 00 46
Z-Wave Debug . . requestMeterLevel: node 184, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 0 W (float: 0.000000)
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 3C 08 32 02 21 12 00 00 00 00 C2
Z-Wave Debug . . requestMeterLevel: node 060, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 0 W (float: 0.000000)
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 07 06 31 05 04 22 00 03 E7
Z-Wave Debug . . requestVarSensorStatus: node 007, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 0.3 W (float: 0.300000)
Z-Wave Debug received "Prise Lave Vaisselle" power load to 0.3 W
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 90 08 32 02 21 12 00 00 00 00 6E
Z-Wave Debug . . requestMeterLevel: node 144, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 0 W (float: 0.000000)
Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 90 08 32 02 21 12 00 00 00 00 6E
Z-Wave Debug . . requestMeterLevel: node 144, endpoint None, meterType 01, raw value 1200...
Z-Wave Debug . . requestMeterLevel: 0 W (float: 0.000000)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug maximum retry count exceeded waiting reply from module
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "024 - Relay Power Switch". Module might be asleep, or is unreachable.

[matt (support)]

I will look into this in more detail next week. It looks like the module is replying but it either isn't exactly what Indigo is requesting, or there is an Indigo bug. I'll post more details within a few days.

Thanks
NIce we

Hello Matt
Do you have some news for my problem
Thanks in advance
Patrice

[matt (support)]

Hi Patrice,

Not yet, but I hope to look into it soon.

Hello Matt
I come back to you if you had time to look at my problem
Thanks
Patrice

[matt (support)]

I've looked over the details of your Event Log and that AN158 is not responding to the command Indigo sends (SENT requestMeterInfo) to get information about what type of energy/power data the module is capable of sending. Instead of responding with the correct information, the module is responding with the actual energy and power values (should be information about what is supported – not the current levels). I'm pretty confident this is a bug in the AN158. I believe it is in a bad state. It might be sending the information to the old controller node ID (1) instead of the new ID (188) which would explain why Indigo never receives the reply. Or maybe it just doesn't like it when the controller isn't node 1. There are other modules that have similar bugs that only crop up when the controller isn't node 1. I guess they just don't QA that case as often as they should.

Most modules perform a factory reset when they are excluded and re-included (which I know you've done), but sometimes modules have different steps to perform a complete reset. So check the documentation for the AN158 to see if there are any additional steps you can try to get the module fully reset.

On the Indigo side I've tweaked the logic just a bit so that if the module doesn't respond to the requestMeterInfo command Indigo will continue on with the sync process instead of failing and stopping the sync process. I'm not confident that will solve all the problems, but it will let Indigo at least complete the sync process. That change will be in the next bug fix release of Indigo (7.1.2).

Thanks Matt for your reply
Unfortunately I’ve followed the reset procedure many times but the problem is still here
There is no way to change the node number of the controller except a full reset ?
Actually I’ve removed all the AN158 from my network and using only FIBARO

[matt (support)]

Unfortunately, I know of no way to change the node ID of the controller except a full reset (then re-inclusion / sync of all modules).