forum

Posted: **19 Oct 2022 01:11**

I get S2 timeout straight away when trying to add a new device.

Go here for logs:
https://www.dropbox.com/s/28nqfpes5mg0o ... r.log?dl=0

The new node has number 64

Edit: I got it associated with S2 now when I selected to use only S2 inclusion and not S0+S2
New log:
https://www.dropbox.com/s/w3ac3c4qkvyue ... .log2?dl=0

Edit2: It seems to be a intermittent error as I get timeout now again for node 69
Logs:
https://www.dropbox.com/s/dtpa0ji35wso5 ... .log3?dl=0

Posted: **23 Oct 2022 02:39**

[2022-10-19 00:03:04.537] [I] [zway] Job 0x13 (Security S2 KEX Get to node 64): Not delivered to recipient

Only 1.5 s after the inclusion the device is already asleep? Or the connection is weak?

Posted: **23 Oct 2022 02:59**

It was connected just a few centimetres apart from the station. Signal strength -45
It's a powered device so it shouldn't go to sleep.

Posted: **31 Oct 2022 01:12**

Well, if it is not reachable anymore and it is a mains powered, then it forgot it's ID after reboot. This should be memory problem

S2 timeout