Also for some reason the deice has conflicting is Long Range is/isNot enabled logs. LongRange and isLR.

The profile may need to be removed from eisy prior to adding again. So the steps would be remove profile from ZWave page which will present QR Scan, Factory Reset Z-Wave Device, then same steps to add again. Download log on failure

55 minutes ago, Javi said:

Perfect, for some reason S2 Security is failing for this device, not sure of the reason. What is the MFG and model? Also if you have a link to purchase to verify that would be great.
What is the dongle, Z-Matter?

[2026-10-23 19:10:52.979] [D] [...] Security S2 inclusion timeout event
...

[2026-10-23 19:10:52.979] [W] [...] Node 300:0 CC SecurityS2: Security S2 key negociation with node 300 failed, KEX fail reason: Unknown Security S2 KEX failure reason (0)

....

[2026-10-23 19:10:53.011] [I] [...] Node 300:0 CC SecurityS2: SmartStart inclusion failed, trying to remove this device

Nice device, two separately controlled outlets...

Yeah, I was going to suggest that you buy one from Amazon and, if you don't have good success with it, return it within 30 days.
ZooZ double plug ZOOZ model Zen14 800LR
Search: USA link: outdoor double plug ZOOZ model Zen14 800LR

Founf this link:

https://www.amazon.com/Z-Wave-Outdoor-Required-Assistant-Hubitat/dp/B0BHC73DLB/ref=sr_1_1?crid=31HS6DJ2YWKL&dib=eyJ2IjoiMSJ9.wgFyIGxmzfquXbdXdGUNYktDfVv0N7gM7HOfhfjXC2NUYBD_br4cYdwj1U2w5B7unInSJ35CtKyiJKDunjmNRKvvSksJBio0ff0UMc73OeA.S-xthUsdjgOc6IbVtL199RaJCsucuQoaEnQEhUkQjWA&dib_tag=se&keywords=outdoor+double+plug+ZOOZ+model+Zen14+800LR&qid=1792812438&sprefix=outdoor+double+plug+zooz+model+zen14+800lr%2Caps%2C197&sr=8-1

7 hours ago, johnstonf said:

I didn't have to check off the long-range option...

The parameters seem to be inaccessible and grayed out, how did you do it?

1 hour ago, Javi said:

Also for some reason the deice has conflicting is Long Range is/isNot enabled logs. LongRange and isLR.

The profile may need to be removed from eisy prior to adding again. So the steps would be remove profile from ZWave page which will present QR Scan, Factory Reset Z-Wave Device, then same steps to add again. Download log on failure

What is the procedure to remove the profile?

10 hours ago, johnstonf said:

The parameters seem to be inaccessible and grayed out, how did you do it?

What is the procedure to remove the profile?

👍

1 hour ago, johnstonf said:

👍

They went through the whole process again, same outcome. I ran this through Claude, and this is what it came back with. Does this help?

To be honest, this whole Zwave (mesh and LR) has been a disaster on the EISY. I have had trouble tickets logged about my locks, and I don't 'reply in time' so the ticket gets closed... big waste of time to go thru the rigeramo when I'm nuts busy... this ain't supposed to be my full-time gig. I thought LR would be figured out. Anyways with my locks disaster (they were working fiine on my ISY994 (WTF?), I moved my two most critical locks over to a Raspberry Pi with a battery backup, running Home Assistant just on Wi-Fi. Just a simple test, a the time, and I've kept it that way because it works so pristinely. I just added this ZooZ LR, and it took me less than 60 seconds for it to be added. I can't believe the time it is taking on this EISY to get things set up. I'm a wee bit of a hacker, but this is getting ridiculous.

Anyways, I have a couple of pictures up to show my quick little setup that I did two months ago that I've never stopped using because it works so well. It just sits on my dining room table and runs and runs and runs.

Edited Saturday at 04:58 PM1 day by johnstonf

I understand your frustration. Technology is great, when it works.

Just a thought (and something to try): try turning off "Secure Inclusion" in the Z-Wave screen, and retry adding it again to see if that succeeds.

You could also try changing the Communication Speed and Interview timeout settings.

Edited Saturday at 06:57 PM1 day by Guy Lavoie

Thanks... but still dead-ended...

(Have you actually added LR devices this way? }

I'll try your other suggestions...

Edited Saturday at 08:13 PM1 day by johnstonf

1 hour ago, Guy Lavoie said:

I understand your frustration. Technology is great, when it works.

Just a thought (and something to try): try turning off "Secure Inclusion" in the Z-Wave screen, and retry adding it again to see if that succeeds.

You could also try changing the Communication Speed and Interview timeout settings.

Yay, by setting the timeout to 3 minutes and the speed to 10, I was able to get it through, I don't know what other parameter values would work, but these did work. It actually went pretty fast, so I'm thinking maybe the speed helped.
Thanks!

Welcome to the LR camp!

Now you can share your experiences in the LR thread I just started 🙂

21 minutes ago, Guy Lavoie said:

Welcome to the LR camp!

Now you can share your experiences in the LR thread I just started 🙂

Maybe you can move this post over to there.

6 minutes ago, johnstonf said:

Maybe you can move this post over to there.

No, the intent of the new thread is to discuss the performance of LR (once you get it working). My first post will give you the idea)

Sounds good 👍

2 hours ago, johnstonf said:

Yay, by setting the timeout to 3 minutes and the speed to 10, I was able to get it through, I don't know what other parameter values would work, but these did work. It actually went pretty fast, so I'm thinking maybe the speed helped.
Thanks!

Perfect, I just noticed the communication speed was not at default in a previous screenshot. Was this changed for a specific reason previously?
I'm also wondering if it would have worked in using default. I have not experienced any zwave inclusion failures since eisy-ui integration in my testing. I have only seen 3 others failures in our tickets that could not be explained by an external factor. A zwave lock (still open), a device that took over a minute to commission (if the commissioning window was left open for a few seconds longer it completed), and a user trying to use SmartStart without security (the reason we added the error you seen when trying to do the same).

17 hours ago, johnstonf said:

Yay, by setting the timeout to 3 minutes

Quick note of commiseration: I've also had to set my Z-Wave interview timeout to 2min or 3min, NOT "default". In my case, I have some Z-Wave devices that partially-include, but may have had missing end-points or present-but-non-functioning endpoints. Implicated Z-Wave devices are:

Zooz outdoor switched outlets

Zooz motion-sensors

Ecolink motion sensors

Leviton plug-in outlet switches

Leviton wired-in dimmer switches

Even with this extended interview timeout, I've resigned myself to having to include - exclude - factory_reset - include a couple of times, for my Z-Wave stuff to work properly. But after all this, things seem solid.

I am glad we both found that extending the interview timeout worked.

And like Javi mentions - during my includes, once I see the device end-points appear, I must wait another several minutes for the actual inclusion to successfully complete. When the screen says something like "Timeout" and "Download Log" + "Skip", it's really not finished ... I go and make coffee or something, to give it an additional (5???) minutes to do whatever it's doing behind-the-scenes.

Edited 11 hours ago11 hr by GPritchard

9 minutes ago, GPritchard said:

Quick note of commiseration: I've also had to set my Z-Wave interview timeout to 2min or 3min, NOT "default". In my case, I have some Z-Wave devices that partially-include, but may have had missing end-points or present-but-non-functioning endpoints. Implicated Z-Wave devices are:

Zooz outdoor switched outlets

Zooz motion-sensors

Ecolink motion sensors

Leviton plug-in outlet switches

Leviton wired-in dimmer switches

Even with this extended interview timeout, I've resigned myself to having to include - exclude - factory_reset - include a couple of times, for my Z-Wave stuff to work properly. But after all this, things seem solid.

I am glad we both found that extending the interview timeout worked.

And like Javi mentions - during my includes, once I see the device end-points appear, I must wait another several minutes for the actual inclusion to successfully complete. When the screen says something like "Timeout" and "Download Log" + "Skip", it's really not finished ... I go and make coffee or something, to give it an additional (5???) minutes to do whatever it's doing behind-the-scenes.

Thanks, I think the dialog will need to be changed to match that timeout parameter. I could not replicate on my side as I have no test cases.

Added issue to synchronize the user specified timeout with the dialog timeout. Z-wave inclusion dialog needs to match Z-Wave Timeout. ID /eisy-ui/issues/134