Can't get most nodes interviewed.

[scyto]

I have 14 devices, they are having terrible trouble being interviewed.
I have fw v3.1.2

I see some are the AssociationGroupInformation node issue and i know how to bypass that.

The others get stuck on all sorts of command classes like power, secuity, S2 interview (generates a Unable to update data. devices[14].instances[0].commandClasses[159].Interview()), etc. My locks wont be recognized as locks.

Sometimes i can help it along by forcing a reinterview of just the failing class.

How normal is this? this seems a little fragile, but my previous controllers didn't have this much control and insight so I am not sure if what i am seeing is normal or not?

[seiken]

it can be really hard to include a device on this controller, what i noticed is, if don't have the controller in the same height and basically touching the device it won't include it if using s2. iven 5cm from it won't include it. this is very noticeable on qubino device.
when including a id lock 101 it took like 5 hours for it to finish the include.

[micky1500]

I think they missed something out when they included S2 on 3.0.0
I tried to add an old battery Light switch 2 days ago.
Failed the interview probably 20 times.
Removed, and re-added about 10 times.
Forced the interview to pass "Association" with a command.
But Association page said the device didn't support Association.
I need the Association feature.

Forced another interview, and the monitor screen rushed passed 10 pages of activity.
Now its working.

So.
Why did it take me 2 hours to add a simple device ?

[PoltoS]

Please show us logs so we can understand your issues.

[scyto]

I fixed the issue.

I moved to a SLUSB001A controller and all my issues disappeared instantly.

Locks that would not include in zwave.me or zwavejs2mqtt with the razberry hat worked perfectly with the USB dongle.
Locks that included but wouldn't report any info or work, worked perfectly.
Love the hat, its a nice neat solution and well built (though i wish the antenna mount was std) and the zwave.me software has really interesting sniffer options. I plan to still use the hat on my PC via USB bridge and simplicity studio, maybe as a dedicated sniffer for example.

But at this point i have no plans to move backwards from my series 700 device to a series 500 device. To be clear i saw issue with these locks on ISY994i and its series 500 zwave board. I see all the the threads on hubitat and smart things where some people have issues with older zwave 1 devices like the BE469NX and FE599NX - my gut is the 500 either doesn't handle old crappy v1 device (that may be non spec compliant) ... but thats a guess.

Log attached as i want to help, love the product you built.

--edit--
log is too large to attach, should i PM it?

[PoltoS]

you can send a link in PM or by mail

[Vovven]

I have the same experience, inclusion is a nightmare since v3.
After many, many retries it eventually succeeds, but not always.
It doesn't seem to help to move the device close to the controller.
Security command classes are very prone to fail but they are not the only ones.
Stability is not the name of the game here.

I had a new device some months ago which I really needed to get included but it kept failing.
I then reverted to 2.3.8, where inclusion was not a problem.
But it's a cumbersome process to go back to 2.3.8 each time you run into inclusion problems.

[PoltoS]

We need logs to check it. It is very stable in our side

[micky1500]

@PoltoS
I have emailed you my latest logs.
It's been a nightmare to Interview non S2 devices since 3.0.0 - July 2019.
It doesn't fail ! Just takes 30 attempts !
Timeout threshold's seem to be too tight..
?