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
F

fabien007

@fabien007
About
Posts
2
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Raspberry controller: where is sensor auto id assignment code?
    F fabien007

    ok, thanks for the explanation!
    I'll implement features I need in my own implementation of MyGateway then.

    Controllers

  • Raspberry controller: where is sensor auto id assignment code?
    F fabien007

    Hello,
    sorry for what seams naive question, but after having looked at latest 1.4 mysensor github raspberry controller code, I couldn't find where sensor id autoassignment code is.
    i.e. I didn't find where code handling internal messages coming from sensors (possibly relayed by node in "repeater" mode) of type "I_ID_REQUEST".

    I expected to find this code either in MyGateway or less probably in parent class MySensor, but it seams nothing is done for internal/I_ID_REQUEST message, and therefore it is handled by default message callback function pointer, which by default just pingpongs back the message to sensor node.

    What did I miss? Are we supposed to implement it ourself in a gateway implementation? I would have thought some basic logic e.g. auto increment in gateway could do the trick quite generically.

    Thanks for your support!

    Controllers
  • Login

  • Don't have an account? Register

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