Iris 3210-L2 Z-Wave being stubborn

Automation Central Automation Hardware
#1

Has anyone run into this issue with Iris 3210-L2 plugs? I am slowly bringing them over and for the most part it has been painless (zigbee side has been COMPLETLEY painless), but for some reason this one plug is being very stubborn about the interview process.

When I first paired it, everything looked okay, all of the metadata was filled in as it should (minus it reporting 3210-L not L2, but that doesn’t really matter) and then I checked today and it reported as dead, so I tried a replace action which went through, but now it is not reporting it’s metadata properly (screenshot).

Fast forward a couple hours, I have tried multiple factory resets, multiple excludes, replaces, and adds and they all end in the same place: the interview being successful, but no data is actually coming through as I expect. If you guys have any ideas that would be great.

My current theory is that maybe the firmware on my stick is a bit buggy.

image
image1892×386 73 KB

Interview Log:

Sep 17 15:19:59.652412 Collective-Core conmon[118390]: 2022-09-17 15:19:59.650 INFO ZWAVE: Calling api refreshInfo with args: [ 13, { resetSecurityClasses: false }, [length]: 2 ]
Sep 17 15:19:59.660056 Collective-Core conmon[118390]: 2022-09-17 15:19:59.659 INFO ZWAVE: Node 13: interview started
Sep 17 15:19:59.673473 Collective-Core conmon[118390]: 2022-09-17 15:19:59.672 INFO ZWAVE: Success zwave api call refreshInfo undefined
Sep 17 15:19:59.705875 Collective-Core conmon[118390]: 2022-09-17 15:19:59.704 INFO ZWAVE: Node 13: interview stage PROTOCOLINFO completed
Sep 17 15:19:59.707896 Collective-Core conmon[118390]: 2022-09-17 15:19:59.706 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453199706, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:19:59.774582 Collective-Core conmon[118390]: 2022-09-17 15:19:59.773 INFO ZWAVE: Node 13: interview stage NODEINFO completed
Sep 17 15:19:59.776534 Collective-Core conmon[118390]: 2022-09-17 15:19:59.775 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453199774, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:19:59.783155 Collective-Core conmon[118390]: 2022-09-17 15:19:59.782 INFO ZWAVE: Node 13: metadata updated: 38-0-Up
Sep 17 15:19:59.785536 Collective-Core conmon[118390]: 2022-09-17 15:19:59.784 INFO ZWAVE: Node 13: metadata updated: 38-0-Down
Sep 17 15:20:00.878724 Collective-Core conmon[118390]: 2022-09-17 15:20:00.877 INFO ZWAVE: Node 13: interview stage COMMANDCLASSES completed
Sep 17 15:20:00.880537 Collective-Core conmon[118390]: 2022-09-17 15:20:00.879 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453200878, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:20:00.882912 Collective-Core conmon[118390]: 2022-09-17 15:20:00.882 INFO ZWAVE: Node 13: interview stage OVERWRITECONFIG completed
Sep 17 15:20:00.884527 Collective-Core conmon[118390]: 2022-09-17 15:20:00.883 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453200883, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:20:00.886726 Collective-Core conmon[118390]: 2022-09-17 15:20:00.885 INFO ZWAVE: Node 13: interview stage COMPLETE completed
Sep 17 15:20:00.888486 Collective-Core conmon[118390]: 2022-09-17 15:20:00.887 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453200886, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:20:00.895297 Collective-Core conmon[118390]: 2022-09-17 15:20:00.894 INFO ZWAVE: Node 13: value added 13-38-0-targetValue => undefined
Sep 17 15:20:00.896753 Collective-Core conmon[118390]: 2022-09-17 15:20:00.895 INFO ZWAVE: Node 13: value added 13-38-0-duration => NaNs
Sep 17 15:20:00.899523 Collective-Core conmon[118390]: 2022-09-17 15:20:00.897 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/38/0/duration: {
Sep 17 15:20:00.899555 Collective-Core conmon[118390]:   time: 1663453200897,
Sep 17 15:20:00.899573 Collective-Core conmon[118390]:   value: Duration {
Sep 17 15:20:00.899588 Collective-Core conmon[118390]:     unit: 'seconds',
Sep 17 15:20:00.899602 Collective-Core conmon[118390]:     _value: undefined,
Sep 17 15:20:00.899616 Collective-Core conmon[118390]:     [value]: [Getter/Setter]
Sep 17 15:20:00.899631 Collective-Core conmon[118390]:   }
Sep 17 15:20:00.899645 Collective-Core conmon[118390]: } with options { qos: 1, retain: true }
Sep 17 15:20:00.903784 Collective-Core conmon[118390]: 2022-09-17 15:20:00.902 INFO ZWAVE: Node 13: value added 13-38-0-currentValue => undefined
Sep 17 15:20:00.905162 Collective-Core conmon[118390]: 2022-09-17 15:20:00.904 INFO ZWAVE: Node 13: value added 13-38-0-Up => undefined
Sep 17 15:20:00.906601 Collective-Core conmon[118390]: 2022-09-17 15:20:00.905 INFO ZWAVE: Node 13: value added 13-38-0-Down => undefined
Sep 17 15:20:00.913204 Collective-Core conmon[118390]: 2022-09-17 15:20:00.912 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453200907, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
Sep 17 15:20:00.916406 Collective-Core conmon[118390]: 2022-09-17 15:20:00.915 INFO ZWAVE: Node 13 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
Sep 17 15:20:00.918910 Collective-Core conmon[118390]: 2022-09-17 15:20:00.917 INFO ZWAVE: Node 13: interview COMPLETED, all values are updated
Sep 17 15:20:00.920946 Collective-Core conmon[118390]: 2022-09-17 15:20:00.919 DEBUG MQTT: Publishing to zwave/Great_Room/GR_-_Pace_5268_Z-Wave_Repeater/status: { time: 1663453200919, value: true, status: 'Alive', nodeId: 13 } with options { qos: 1, retain: true }
#2

More likely the device is suffering. Those dual radios have a history of that behavior. You can never know if it’ll be OK. I had one spamming my network for a time. That’s an at your own risk thing… dragons be here.

#3

So you think it might just be bum hardware?

If that is the case, no issues, I have plenty of others than are unused right now that can take it’s place that I got from someone, though I can’t remember who right now :wink:

1 Like
#4

Oh ya. Then there’s probably a bum one in there for zwave. I never paired them zwave after i had one flood my network.

#5

Actually I am not sure if hardware really is to blame, like I guess it technically could be an issue, but this is not one of yours, this is one of the units I got from teamequip.com that came new in original retail box and shipping box with original seals. So like I guess it could have gone bad, but that seems unlikely.

It is just weird because I swear that it interviewed properly at least once. Another weird part is that the plug just above it was another plug in that same shipment from teamequip, also another L2 plug, but it is working fine.

#6

Dragons. You’ll get mixed reviews on them. Firmware matters on them

1 Like
#7

You have to ask: if they were so great, why has no one else manufactured them?

#8

Because why sell one device when you can sell two (:

#9

But you could mark up the price. Pay for convenience.

#10

Or you can just do both, but idk if smart home is in a place yet where convenience markups would be allowed. You see it kind of starting with homekit products, but in general people seem to like to get the best bang for your buck.

1 Like
#11

Because centralite is still in business, and still releases several versions of them under their own brand name. The Iris plugs were simply rebranded as iris for lowes.

That being said the L2 were only capable of handling 12A of power not 15A like the L1. So the L2 are more prone to burn out/failure due to pulling to much current through them.

From what I understand the Zwave side is crap on these, and should be avoided if possible, but the zigbee side has been rock solid for me.

2 Likes
#12

Oh interesting, I thought both L and L2 were rated at 12 amps, not an issue in this case btw, only load is a network gateway that is rarely on.

#13

The thing is if i remember they only repeat Z-Wave. They’re great little plugs. I just don’t know that pairing the Z-Wave side is really worth it.

#14

Yeah they are Z-wave repeaters only, plug side is zigbee and those are working great in Z2M (both L2 and L variants)

I wonder how many of these are related to the hardware, or if they are actually related to HE’s implementation because I assume most people’s foul opinion of ZW comes from an HE background, like mine.

1 Like
#15

Ya, they do that well. I recommend that if you don’t need them for ZW, then abstain. You just might be thankful you did.

#16

Unfortunately, other than a EVA LOGIK ZW97 outdoor plug, they are my only mains powered z-wave devices, so I was basically using them as the backbone of both my zigbee and z-wave network.

#17

I think beyond that a lot of peoples issues with zwave comes down to how the levels of security affect what a router can route.

#18

That was another interesting thing that I noticed, they paired without any security, but they are ZW+. Does that mean that they can’t repeat for any S0 or S2 devices like locks?

#19

What other devices do you have on Z-Wave?

#20

An August pro lock that was beyond useless on HE and I hope to be better on core, and some smoke detectors. I am mostly a Zigbee house for this very reason. Also the outdoor plug ZW97, but that is mains.