I have 43 devices listed. There are some skipped numbers (23, 24, skip, 26…). Will these skipped/deleted device numbers get re-issued, or can I choose assignment of unused device nmbers?
Same for scenes.
And for z-wave devices, I read the limit is 230 per ‘network’. Is this limit in any way related to the Vera device number, or does that matter? If I keep goofing around, and the device assignment keeps incrementing, and I add a real z-wave switch that becomes device # 300 but I only have 200 real devices, is this a problem?
There is a node limit of 232 actual devices.
Missing node / device numbers happens when there is corruption of data during the include process or by deleting devices.
I’ve never seen or heard of anyone having the node numbers being recycled (unless you reset the network) but I hear that’s what happens. I’ve had device numbers in the triple digits, so the numbering system is not an issue.
*Edit. I meant to say triple zero’s but wrote “triple digits” as @guessed points out below (4-digits or higher)
Also, you cannot choose which numbers get assigned, it’s done logically in ascending order.
@Intrepid,
The device number is internal to Vera, so probably doesn’t matter. The ID for Z-Wave devices is the NodeID. My guess would be it can’t be higher than 232.
@JOD,
Do you have Z-Wave devices with an ID > 232? (I believe the NodeID is an 8-bit value in Z-Wave.)
ZWave has nodes, and there’s a limit of 232 nodes in a Z-Wave Network.
Vera/MiOS has devices, and I’ve not seen the limit documented, but they go quite high.
When a ZWave node is represented in a Vera/MiOS system, it has both it’s ZWave nodeId (allocated by the Primary) as well as it’s MiOS deviceId (allocated by Vera)
So it won’t matter if you have lots of MiOS device’s, and go into 4-digit (or higher) MiOS deviceId’s since they’re unrelated to ZWave nodeId’s.
Folks,
I heard a rumor that when you do a Zwave network refresh or heal, that the DEVICEID is changed.
I find that hard to believe.
On the other hand, i can see NodeIDs changing on refresh/heal of zWave.
The reason i ask is because we have LUUP code that depends on DeviceID, and we do not want to worry about a zwave-network-heal breaking the code.
Any comments?
Also, how does alt-ID come into play?
Regards
Sean
Dont worry, the DeviceID only changes upon deleting and reinstalling device or in/exclusion.
Maybe this helps to better understand healing and routing: http://forum.mios.com/index.php?topic=6898.0
Dont know about altid, but i think thats the same. someone else might chip in on that…
Best, Henk
[quote=“smilligan, post:5, topic:168286”]Folks,
I heard a rumor that when you do a Zwave network refresh or heal, that the DEVICEID is changed.
I find that hard to believe.
On the other hand, i can see NodeIDs changing on refresh/heal of zWave.
The reason i ask is because we have LUUP code that depends on DeviceID, and we do not want to worry about a zwave-network-heal breaking the code.
Any comments?
Also, how does alt-ID come into play?
Regards
Sean[/quote]
On the other hand, i can see NodeIDs changing on refresh/heal of zWave.
I don't expect that to happen either (nor have I seen it). Not sure a NodeID can be changed on the fly, without the node being in inclusion mode. Also, it would be a nightmare to keep all (battery-operated) secondary controllers and nodes that support association in sync.
Also, how does alt-ID come into play?
It shouldn't. AFAIK [tt]alt-id[/tt] and [tt]ID[/tt] (in the device's tabs) are the same thing, and they are the Z-Wave NodeID; a Z-Wave property, limited by the maximum number of nodes, 232.
I see the [tt]Device#[/tt] as a Vera internal identifier for any device, Z-Wave or not. Most Luup references this.
The GE Wall Controller #45631, needs NODES no higher than 32. If you can recover lost or missing NODE ID’s then, you can possibly use the wall controller in those instances when you purchased the wall controllers AFTER you had a well established network
I know, sour grapes and laziness in re-bulding a 40 device network —
[quote=“oTi@, post:3, topic:168286”]@Intrepid,
[…] The ID for Z-Wave devices is the NodeID. My guess would be it can’t be higher than 232.[/quote]
Confirmed: 232 is in fact the highest NodeID; after that, Vera assigns the lowest free NodeID next.
I have an iRule/Micasa Verde Home Automation system that during the process of installing/learning/adding/removing I’ve wound up with numerous unused node numbers.
I have numerous unused Node #'s below 50. This is of concern because the device drivers for iRule are grouped 1-50, 51-100. Has anyone determined a way to change a node number without crashing the system that is doable for a moderate skill level?
[quote=“charterdog, post:10, topic:168286”]Resurrecting this thread.
I have an iRule/Micasa Verde Home Automation system that during the process of installing/learning/adding/removing I’ve wound up with numerous unused node numbers.
I have numerous unused Node #'s below 50. This is of concern because the device drivers for iRule are grouped 1-50, 51-100. Has anyone determined a way to change a node number without crashing the system that is doable for a moderate skill level?[/quote]
Agreed. I have maybe 10 devices and I’m already into node id 19 or 20 and device id 35 or so. I want to bring these numbers back down and fill empty slots. Is there any way?
q: is it detrimental to the system to have high node ID’s and device ID’s when lower numerical values are free. if so and if the only way is to reset zwave network and re add devices > is this recommended?
[quote=“LightsOn, post:13, topic:168286”]just reading this as relevant to me also.
q: is it detrimental to the system to have high node ID’s and device ID’s when lower numerical values are free. if so and if the only way is to reset zwave network and re add devices > is this recommended?[/quote]
No, the number or order of numbers is irrelevant to the Z-Wave network. Z-Wave networks can support a maximum of 232 devices(Node ID). There are a few cheap Z-Wave remotes, and possibly other devices, that cannot address anything higher than 32.
Also, Vera basically appears to give out the next [tt]nodeID[/tt] until 232 is reached and then starts over again, so ‘empty spots’/‘holes’ will get filled. The [tt]deviceID[/tt]s just keep incrementing, it appears.
