Not save ID
-
Is there any way to make the node not save the ID, so making them request an ID every reboot?
-
Yeah. I think that should work! However, I think it should be an option to choose if you want to save or not the ID.
-
@hek would be possible implement some option that makes the node always requests a "new id"? Like DHCP.
-
Won't a new I'd on every startup wreak havoc with the controller? That is, you will get a "new" sensor device on every startup?
-
@Anticimex
If you use an algorithm like DHCP, you won't get a new ID every node startup/restart. If there is few time since the node was seen on that network, the controller should give the same ID.@hek
Well, I know that 253 nodes is a lot of nodes. However, just thinking in worst case, if you reach the limit and remove a node A, and a new node B, so will get the A id, and after that (some months later?) you remove a node C and put A on its place. So, there is a problem because A already have an ID (same B's ID). Then, you have an ID conflict. Or I am wrong? -
Right...
-
Oh...yeah...you are right! Maybe you can change ID in production? =x
-
Yeah. I know that, but if you insert the old node, it would have the old ID stored. So, it would be an ID conflict.
I don't have my controller yet. I am actually creating my own and getting some ideas.