Iris 3210-L2 "Group 1 not found, configure device!"

Get Help Devices
#1

So I am using this driver for my Iris Plugs to get additional tools for the Z-Wave Repeater portion.

It seems to be communicating fine, but under the Z-Wave Table for HE after a reboot, these devices are never communicated with, but the moment I force communication via the driver it responds fine. The interrogation of the device shows this:
image
image

Any ideas what is causing the "Group 1 not found, configure device!"? I tried clicking the configure on the device page but that does not seem to do anything.

Any help would be appreciated.

Lowes Iris Zigbee Devices Available
#2

Pressed the configure button after changing the driver?

1 Like
#3

Yeah, even changed the driver to generic one and then back and spammed config. Did not seem to do anything.

Debug Log:

dev:18592020-10-26 03:21:30.814 pm infoPeriodic health check is enabled but bypassed in the code.
dev:18592020-10-26 03:21:30.804 pm traceSending command... AssociationSet(groupingIdentifier:1, nodeId:1)
dev:18592020-10-26 03:21:30.798 pm traceSending configuration commands to Iris Smart Plug...
dev:18592020-10-26 03:20:44.563 pm traceDevice Interrogation: Phase 0 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:39.689 pm infoDevice is online
dev:18592020-10-26 03:20:39.669 pm debugASSOCIATION GROUP REPORT V2: Great Room - Pace 5268 Gateway Z-Wave Repeater in Group #1 with nodes: []
dev:18592020-10-26 03:20:39.650 pm debugParsing zw device: 15, command: 8503, payload: 01 05 00 , isMulticast: false
dev:18592020-10-26 03:20:39.560 pm traceDevice Interrogation: Phase 6 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:39.504 pm traceSending command... AssociationGet(groupingIdentifier: 1)
dev:18592020-10-26 03:20:34.599 pm infoDevice is online
dev:18592020-10-26 03:20:34.590 pm debugASSOCIATION GROUP NAME REPORT V1: Great Room - Pace 5268 Gateway Z-Wave Repeater belongs to group Lifeline
dev:18592020-10-26 03:20:34.582 pm traceReceived: AssociationGroupNameReport(groupingIdentifier:1, lengthOfName:8, name:[76, 105, 102, 101, 108, 105, 110, 101])
dev:18592020-10-26 03:20:34.540 pm debugParsing zw device: 15, command: 5902, payload: 01 08 4C 69 66 65 6C 69 6E 65 , isMulticast: false
dev:18592020-10-26 03:20:34.452 pm traceDevice Interrogation: Phase 5 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:34.412 pm traceSending command... AssociationGroupNameGet(groupingIdentifier:1)
dev:18592020-10-26 03:20:29.481 pm infoDevice is online
dev:18592020-10-26 03:20:29.458 pm debugMANUFACTURER SPECIFIC V2: Manufacturer ID: 0246, Manufacturer Name: null, Product Type ID: 0001, Product ID: 0001
dev:18592020-10-26 03:20:29.445 pm debugParsing zw device: 15, command: 7205, payload: 02 46 00 01 00 01 , isMulticast: false
dev:18592020-10-26 03:20:29.356 pm traceDevice Interrogation: Phase 4 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:29.315 pm traceSending command... ManufacturerSpecificGet()
dev:18592020-10-26 03:20:24.531 pm infoDevice is online
dev:18592020-10-26 03:20:24.522 pm debugFIRMWARE METADATA REPORT V1: Great Room - Pace 5268 Gateway Z-Wave Repeater is running firmware ID: 0000 with checksum: 0000
dev:18592020-10-26 03:20:24.416 pm debugParsing zw device: 15, command: 7A02, payload: 02 46 00 00 00 00 , isMulticast: false
dev:18592020-10-26 03:20:24.333 pm traceDevice Interrogation: Phase 3 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:24.288 pm traceSending command... FirmwareMdGet()
dev:18592020-10-26 03:20:19.343 pm infoDevice is online
dev:18592020-10-26 03:20:19.326 pm debugVERSION REPORT V1: Great Room - Pace 5268 Gateway Z-Wave Repeater is running firmware version: 1.2, Z-Wave version: 0.0, Library type: 6
dev:18592020-10-26 03:20:19.283 pm debugParsing zw device: 15, command: 8612, payload: 06 00 00 01 02 01 01 01 00 , isMulticast: false
dev:18592020-10-26 03:20:19.205 pm traceDevice Interrogation: Phase 2 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:19.170 pm traceSending command... VersionGet()
dev:18592020-10-26 03:20:14.244 pm infoDevice is online
dev:18592020-10-26 03:20:14.241 pm debugPOWER LEVEL REPORT V1: Transmit power for Great Room - Pace 5268 Gateway Z-Wave Repeater is NOMINAL.
dev:18592020-10-26 03:20:14.208 pm debugParsing zw device: 15, command: 7303, payload: 00 00 , isMulticast: false
dev:18592020-10-26 03:20:14.120 pm traceDevice Interrogation: Phase 1 of 6; Attempt 1 of 3...
dev:18592020-10-26 03:20:14.084 pm traceSending command... PowerlevelGet()
dev:18592020-10-26 03:20:14.035 pm traceInterrogating device...
dev:18592020-10-26 03:19:55.731 pm infoPeriodic health check is enabled but bypassed in the code.
dev:18592020-10-26 03:19:55.722 pm traceSending command... AssociationSet(groupingIdentifier:1, nodeId:1)
dev:18592020-10-26 03:19:55.716 pm traceSending configuration commands to Iris Smart Plug...
dev:18592020-10-26 03:19:13.127 pm infoPeriodic health check is enabled but bypassed in the code.
dev:18592020-10-26 03:19:13.081 pm traceSending command... AssociationSet(groupingIdentifier:1, nodeId:1)
dev:18592020-10-26 03:19:10.983 pm traceSending configuration commands to Iris Smart Plug...

Z-Wave Table after reboot:

image
image1920×1690 260 KB

Note: The unused repeaters are not plugged in, the first 5 are 3210-L and the last 10 are 3210-L2, it is weird that the Pace 5268 Gateway Repeater is normally responding even though it is a L2 model, but none of the other L2 models are normally responding. But at the same time, this device has the same issue and says "Group 1 not found, configure device!" after interrogation.

#4

Anyone have any ideas? @srwhite @bobbyD I don't particularly like tagging people not in the conversation but I am at a loss.

#5

I have 20 of these and 2 of them no matter what I did I couldn't get them to configure the lifeline group. For those two I just removed them from the zwave mesh. I suspect they have a different firmware but it's just a guess.

#6

Yeah idk, if I trust what the driver says, not a single one of the 6/10 I have plugged in from the new set of 10 I got can join the lifeline group, I feel like that is statistically unlikely. Were the trouble plugs for you L2 or just L models?

#7

They are all 3210-L2's

#8

Yeah that is very odd, everything I have read has said that the L2 models was a refresh in basically firmware only, and supposedly they are rock solid when compared to the L models. Apparently not though...

Do you know any way to force them into the lifeline? Maybe through a Zniffer?

#9

That association is done when you pair them.

#10

Nope, let me know if you find one, but I doubt there is. I've looked around for a while.

#11

Do you think maybe just excluding and re-including would help anything?

#12

Probably not, but can't hurt unless you end up with a failed pair. If you got a uzb or z stick not a big deal if you do end up with a ghost node since you can remove em easily.

#13

Looks like these are working well now with the Generic Z-Wave Repeater driver on 2.2.4.148.

#14

Yeah so I forgot to update this but I managed to fix my issue. I think when I was initially pairing them, I was doing it via extension cord so I could do it quickly, and I am guessing I unplugged them too quick before doing all of the proper initialization. I excluded all of the offending devices and re-included them and now everything is fine.

Download the Hubitat app