Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Troubleshooting
  3. How does the gateway hand out IDs?

How does the gateway hand out IDs?

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 2 Posters 78 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    biffhero
    wrote on last edited by
    #1

    I am thinking I would like to assign IDs to each of my nodes. Upon first boot of two Sensebender Micro boards, they were assigned ID 2 and 3. OK, it seems to be sequential. However, when I brought up my first PIR motion sensor on an Arduino, it was assigned ID 105. I was expecting to see it assigned 4.

    zboblamontZ 1 Reply Last reply
    0
    • B biffhero

      I am thinking I would like to assign IDs to each of my nodes. Upon first boot of two Sensebender Micro boards, they were assigned ID 2 and 3. OK, it seems to be sequential. However, when I brought up my first PIR motion sensor on an Arduino, it was assigned ID 105. I was expecting to see it assigned 4.

      zboblamontZ Offline
      zboblamontZ Offline
      zboblamont
      wrote on last edited by
      #2

      @biffhero The Gateway doesn't hand out Node IDs the Controller does unless you define it at the Node. Your Controller set the Node ID to 1 as it was an available number, the 5 is the Child ID you assigned.
      My own preference is to assign the Node ID in the sketch and label the sketch with that Node ID and increment the version numbers in both to make it easier to track which one has been programmed at the Node. It also saves on figuring out which Node ID has been assigned by the Controller. YMMV...

      B 1 Reply Last reply
      1
      • zboblamontZ zboblamont

        @biffhero The Gateway doesn't hand out Node IDs the Controller does unless you define it at the Node. Your Controller set the Node ID to 1 as it was an available number, the 5 is the Child ID you assigned.
        My own preference is to assign the Node ID in the sketch and label the sketch with that Node ID and increment the version numbers in both to make it easier to track which one has been programmed at the Node. It also saves on figuring out which Node ID has been assigned by the Controller. YMMV...

        B Offline
        B Offline
        biffhero
        wrote on last edited by
        #3

        @zboblamont Thank you for the explanation. I think that's a good idea with one ID per node, saving each with the node ID and the version number. Do you have one sketch for each of the types of node, or do you have one sketch per node? Do you use physical labels on the nodes or their cases?

        zboblamontZ 1 Reply Last reply
        1
        • B biffhero

          @zboblamont Thank you for the explanation. I think that's a good idea with one ID per node, saving each with the node ID and the version number. Do you have one sketch for each of the types of node, or do you have one sketch per node? Do you use physical labels on the nodes or their cases?

          zboblamontZ Offline
          zboblamontZ Offline
          zboblamont
          wrote on last edited by
          #4

          @biffhero List of sketches on the folder eg Node8BoilerT3vWNrtc3 tells me it's Node 8, BoilerT tells me it's the Central Heating Boiler temperature monitor, 3vWN is the voltage and Node device, rtc means it has one, and finally the version number 3.
          By embedding the sketch name and version number in the sketch, Domoticz always holds the current sketch and version it's programmed with, as at one point I was switching programs around and lost track which one was on it. :confounded:
          So, some old sketches I retain as they feature a different technique or method which may come in useful later, but usually old versions are deleted if satisfied with the final.
          It's easy enough to find the sketch in the folder as they follow in sequence.
          Just my methodology but hope this helps...

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          20

          Online

          11.7k

          Users

          11.2k

          Topics

          113.1k

          Posts


          Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • MySensors
          • OpenHardware.io
          • Categories
          • Recent
          • Tags
          • Popular