My one switch is now Node 15!

Did a lot of newbie adding and removing my one switch.
It's now node 15.
Does this count towards the total number of devices attached, or will nodes 2-14 be assigned at some point in the future?
This isn't the ghost issue, is it?

On a C7 hub, 1-5 are reserved, and cannot be used. So you can ignore those.

For all the other slots/nodes, it doesn't really matter what number they start at. You didn't lose a slot, it can be reused later from what I understand. But the likelihood of needing all the Zwave slots would be pretty rare. I think there are 230-something available slots?

1 Like

Thanks. Hopefully each new device won't take as many tries. Is this indeed the ghost issue I've read (a little) about?

No, it's not the ghost issue. Casper is not in the house. :wink:

3 Likes

This is just how z-wave does it, it's annoying :-1: it really bugs me when there are gaps it's messy :rofl:

1 Like

Yep many of use have OCD when it comes to resources and labeling. I used to hate DHCP when it first came out because of the way it assigned IP addresses but now I learned to pick my battles.

2 Likes

Well then consider it free OCD desensitization therapy. :slight_smile:

As that's the way it works, and is nothing other than cosmetic.

3 Likes

My OCD likes you.

1 Like

With DHCP reservations you can assign them the way you like, just in case you didn't know.

Oh believe me I know about static assignments but the dynamic randomness drives me crazy. Originally the RFC implemented would start at the beginning of the pool and work though it. But then they switched to a more random address from the pool based on MAC address which would resolve some duplicative IP/MAC binding issues.

1 Like

I think one could argue that sequential is not random :wink:

Thank god, it's not just me...