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
_

__guillaume

@__guillaume
About
Posts
4
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • st=fail on reboot
    _ __guillaume

    Hi there,
    For some reasons I have to send a reboot request to one of my node (with id:1).

    When I send this message from my controller:
    1;255;3;0;13;
    I got this log from the GW :
    0;0;3;0;9;send: 0-0-1-1 s=255,c=3,t=13,pt=0,l=0,st=fail:
    And I don't have the expected reboot on node #1.

    What st=fail: means ?
    Any idea that can block the node from rebooting ?

    Thx,
    G.

    Troubleshooting

  • Network discovery sequence ?
    _ __guillaume

    Thx TimO, John, great answers !

    Can you shed some light on these msg please

    172;255;3;0;11;Humidity + Temp + Relay //<< is the controller that define the 'Humidity + Temp + Relay' ?
    
    172;255;3;0;6;0 //Seems to be an internal::I_CONFIG but why 0 is sent ? shouldn't be I or M ?
    
    172;0;0;0;7;1.4.1
    172;1;0;0;6;1.4.1
    172;2;0;0;38;1.4.1
    172;3;0;0;3;1.4.1
    //these are presentation msg but Is the '1.4.1' define in your sketch ? Same as this example 12;6;0;0;3;My Light I don't really understand where the 'My Light' come from
    
    Controllers

  • Network discovery sequence ?
    _ __guillaume

    ok so that means the gateway must be online before the sensors start.

    You shouldn't really need to care about how the actual gateway/sensors communicate between each other.
    I absolutely agree.

    Few points I don't really understand are :

    • In the communication examples the msg 12;6;0;0;3;My Light\n is, as described, node id=12, sensor id=6, message-type =presentation, for a sub-type=S_LIGHT. But how the 12 and 6 are set ? From the doc I can see that there is I_ID_REQUEST sub-type, so I'm guessing that the controller provide the gateway with a node-id to set on sensor. So before the presentation msg, is there a kind of setup between the sensor and the gateway (In this process the GW may send internal msg w/ a subtype I_ID_REQUEST) ?
    • Still with the 12;6;0;0;3;My Light\n example, is the 6 provided by the GW ?
      Is the My Light hard coded on the sensor management program ?
    • How can we detect if a sensor is not on the grid anymore ? Has the GW got a routine so it periodically check if all kown nodes / sensors are still available ?

    Thx,
    G.

    Controllers

  • Network discovery sequence ?
    _ __guillaume

    Hi all,
    I'm about to write my own controller as a personal eduction purpose project.

    I read the serial api doc, but I can't find a description how the communication / protocol is organised and more specifically the discovery of all sensors / new sensor occure.

    When starting the gateway, is there a broadcast packet sent so that all sensors can answer and notify there online presence ?
    How new sensor are discovered ? or notify the gateway ?

    Actually, is there a kind of flowchart explaining the communication?

    Thank you,
    G.

    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