Inability to include any new Z-Wave device

Discussions about Z-Way software and Z-Wave technology in general
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Re: Inability to include any new Z-Wave device

Post by PoltoS »

Can you show the zbk file? Please send it to me
cdogg76
Posts: 49
Joined: 28 Sep 2014 23:13

Re: Inability to include any new Z-Wave device

Post by cdogg76 »

Hello,

This is an old thread, but I'm experiencing this same problem. I can't include any devices--the device fails to get into inclusion mode. Exclusions work. I've tried restarting the device (power disconnect), as well as API soft reset. I've also tried taking a backup and restoring that backup (but not factory resetting) and the backup fails to restore. (I didn't want to end up in a state where I couldn't add nor restore a backup as happened with this person here.)

When I start inclusion, the red light on the Razberry lights for a second, then turns off. In the job queue, it shows that the "Add/re-include node to network" job, then it says it failed and stop done.

Here is the log of an attempt to start inclusion:

Code: Select all

[2022-01-04 15:32:56.544] [D] [zway] SETDATA controller.data.smartStart.includingDSK = byte[0]
[2022-01-04 15:32:56.545] [D] [zway]   ( zero-length buffer )
[2022-01-04 15:32:56.545] [I] [zway] Adding job: Add/re-include node to network
[2022-01-04 15:32:56.549] [D] [zway] SENDING (cb 0x16): ( 01 05 00 4A C1 16 67 )
[2022-01-04 15:32:56.550] [D] [zway] RECEIVED ACK
[2022-01-04 15:32:59.329] [D] [zway] RECEIVED: ( 01 13 00 04 00 2D 0A 32 02 21 74 00 00 00 00 00 00 C9 00 00 63 )
[2022-01-04 15:32:59.330] [D] [zway] SENT ACK
[2022-01-04 15:33:01.006] [D] [zway] RECEIVED: ( 01 07 00 4A 16 07 00 00 A3 )
[2022-01-04 15:33:01.006] [D] [zway] SENT ACK
[2022-01-04 15:33:01.007] [I] [zway] Job 0x4a (Add/re-include node to network): Failed
[2022-01-04 15:33:01.007] [D] [zway] Job 0x4a (Add/re-include node to network): fail
[2022-01-04 15:33:01.007] [I] [zway] Removing job: Add/re-include node to network
[2022-01-04 15:33:01.007] [D] [zway] SETDATA controller.data.controllerState = 0 (0x00000000)
[2022-01-04 15:33:01.007] [I] [zway] Adding job: Add/re-include node to network
[2022-01-04 15:33:01.007] [D] [zway] SENDING (cb 0x00): ( 01 05 00 4A 05 00 B5 )
[2022-01-04 15:33:01.009] [D] [zway] RECEIVED ACK
[2022-01-04 15:33:01.009] [I] [zway] Job 0x4a (Add/re-include node to network): Stop done
[2022-01-04 15:33:01.009] [D] [zway] Job 0x4a (Add/re-include node to network): success
[2022-01-04 15:33:01.009] [I] [zway] Removing job: Add/re-include node to network
[2022-01-04 15:33:01.009] [D] [zway] SETDATA controller.data.controllerState = 0 (0x00000000)
And here is the controller info:

Code: Select all

Role in Network
Node Id:	1
Home Id:	0xe653397f
Primary Role:	Yes
Primary Capability:	Yes
SUC/SIS in network:	153 (SIS)
Hardware
Vendor:	RaZberry by Z-Wave.Me
Vendors Product ID:	1024 / 2
Z-Wave Chip:	ZW0500
Firmware
Library Type:	Static Controller
SDK Version:	6.82.01
Serial API Version:	05.39
Capabillities:
UUID:	ad94258c2886c9956be7d746010df993
Subvendor:	0x0000
Nodes limit:	Unlimited
Controller Static API	X
Allow max RF power	X
Backup/Restore	 X
Battery save on sleeping	X
Advanced network diagnostics	X
Z-Wave Long Range	X
Fast communications	X
Change vendor ID	X
Promiscuous mode (Zniffer)	X
Full Zniffer	X
RF jamming detection	X
Capabillities:	SlM
Software Information
Version number:	v3.2.2
Compile-ID:	101045968be0f00797fdc4d1a70e2955271fe4e7
Compile-Date:	2021-11-29 15:40:21 +0300
UI
UI version	v1.5.7
Built date	26-11-2021 01:37:55
Any ideas on what I can try? I need to re-add nodes and it is now impossible.

Thanks!
seattleneil
Posts: 172
Joined: 02 Mar 2020 22:41

Re: Inability to include any new Z-Wave device

Post by seattleneil »

The controller info you provided shows:
"SUC/SIS in network: 153 (SIS)"

This looks strange to me. The SIS is responsible for assigning new node IDs and it looks like your controller is configured to use Z-Wave node ID 153 for the SIS. I can't explain why the SIS is set to use node ID 153. Do you recall including a second controller onto your Z-Wave network (where it was assigned node ID 153)? Assuming your RaZberry is the SIS (which should be the case unless you have another Z-Wave controller acting as the SIS), try using the expert UI->Network->Control->SUC/SIS management and assign node 1 as the SIS. Next, re-check the controller info using the expert UI->Network->Controller Info and see if the SIS has been configured to node 1. If yes, then try to repeat the inclusion step. Note that you may need to stop and re-start z-way-server for the SIS change to take effect.
cdogg76
Posts: 49
Joined: 28 Sep 2014 23:13

Re: Inability to include any new Z-Wave device

Post by cdogg76 »

Unfortunately, I can't Assign SUC. Those buttons are grayed out.
AssignSUC.png
AssignSUC.png (11.51 KiB) Viewed 2458 times
I have not ever had this as a secondary controller. I did have a different Razberry (an older model), but the two were never online at the same time. Also, it worked fine to include all of my devices when I first set up this Razberry.

Any ideas on other ways to update the SUC ID? A lower-level means of getting it in?

Thanks for your help!
seattleneil
Posts: 172
Joined: 02 Mar 2020 22:41

Re: Inability to include any new Z-Wave device

Post by seattleneil »

Hmmm. You have me stumped. Here's what I see (not greyed out):
SUC_SIS.JPG
SUC_SIS.JPG (43.47 KiB) Viewed 2457 times

Perhaps clicking on the "Get SUC node ID" button or the "Request network updates from SUC/SIS" button might re-enable the options.

Have you modified the Defaults.xml config file (nominally, /opt/z-way-server/config/Defaults.xml)? The following line should be present:
<TryToBecomeSIS>1</TryToBecomeSIS><!-- Shall Z-Way try to become SIS -->

There is a Z-Way API call (SetSUCNodeId) that you could try, but I suspect it may not be successful since that's what the GUI uses. If you want to give it a try, run the following command:
curl -u admin:[YOUR ADMIN PASSWORD] --globoff 'http: //127.0.0.1:8083/JS/Run/zway.SetSUCNodeId(1,1,1)'
lanbrown
Posts: 279
Joined: 01 Jun 2021 08:06

Re: Inability to include any new Z-Wave device

Post by lanbrown »

Is there a device at node ID 153?
cdogg76
Posts: 49
Joined: 28 Sep 2014 23:13

Re: Inability to include any new Z-Wave device

Post by cdogg76 »

Seattleneil,

Thanks for all of your help! Although the buttons for SUC/SIS management didn't work, your JS API _did_ work and I was able to set the SUC back to node 1, and then everything started working normally again!

I have no idea why that got changed to node 153. Also, the next device I included ended up with a node ID of 180, whereas the highest node I had before was 53...

So, Ianbrown, no, I didn't have anything at node ID 153.

Thanks again!
seattleneil
Posts: 172
Joined: 02 Mar 2020 22:41

Re: Inability to include any new Z-Wave device

Post by seattleneil »

Happy to hear the good news. My understanding is that Z-Way will re-use unused nodeIDs once you hit 232. In other words, I wouldn't be concerned about the number Z-Way assigns - it just needs to be a unique number (i.e., 2 devices must not share the same node ID).

It's concerning that the Z-Way configuration got mangled without an explanation. Out of an abundance of caution, please consider backing up your SD card (you can google for various methods), backing up your Z-Way network information (use expert UI->Network->Control->Backup and Restore) and backing up your Z-Way configuration (use smarthome UI->Settings->Backup & Restore). Since you tried to do a Z-Way backup and a restore and the restore failed, it seems particularly prudent to do the 2 Z-Way backups - the process is fast and easy.
cdogg76
Posts: 49
Joined: 28 Sep 2014 23:13

Re: Inability to include any new Z-Wave device

Post by cdogg76 »

Hello,

Yes, I use Paragon Backup on Windows to back up the SD card. I also take both backups from Z-way when I make changes, and I just tested a backup and restore of the ZBK and it all works normally now!

But, yes, I have no idea why the SUC node id got changed. Hopefully no other data is corrupted that may cause issues.

Thanks again!
Post Reply