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. [SOLVED] My node fails to send

[SOLVED] My node fails to send

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 3 Posters 1.2k Views 3 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.
  • D Offline
    D Offline
    David Muller
    wrote on last edited by Yveaux
    #1

    Hello everyone, I'm new here.
    I built my first project with the MySensors framework, and I don't know why I have communication issues.
    Here's the hardware configuration :

    • Sensor node : arduino nano with a DS18B20 and a NRF24L01+ (with 47µF cap on Vcc Gnd)
    • Gateway : ESP8266 and NRF24L01+ (send MQTT message via wifi)
    • Message decoder : Raspberry Pi 3B with node red

    I can see on my Raspberry incomming MQTT messages when I subscribe to the topic, but the payload is always empty !
    When I check the nodes console log, I see always the same error at the same moment.
    Here is what I get in the console (sensor node)

    16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.3.0
    25 TSM:INIT
    26 TSF:WUR:MS=0
    33 TSM:INIT:TSP OK
    35 TSM:FPAR
    37 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
    331 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
    336 TSF:MSG:FPAR OK,ID=0,D=1
    2046 TSM:FPAR:OK
    2048 TSM:ID
    2049 TSM:ID:REQ
    2052 TSF:MSG:SEND,255-255-0-0,s=1,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
    4059 TSM:ID
    4060 TSM:ID:REQ
    4062 TSF:MSG:SEND,255-255-0-0,s=220,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
    6070 TSM:ID
    6071 TSM:ID:REQ
    6073 TSF:MSG:SEND,255-255-0-0,s=183,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
    8081 TSM:ID
    8082 TSM:ID:REQ
    8084 TSF:MSG:SEND,255-255-0-0,s=146,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
    10092 !TSM:ID:FAIL
    10093 TSM:FAIL:CNT=1
    10095 TSM:FAIL:DIS
    10097 TSF:TDI:TSL
    20100 TSM:FAIL:RE-INIT
    20102 TSM:INIT
    20109 TSM:INIT:TSP OK
    20111 TSM:FPAR

    Here is the failed line using the log parser : "Transition to Failure state, consecutive failure counter is 1"

    So I think this is why I never get a payload in my MQTT messages, the sensor node does'nt even send the sensor data, but I don't know why !

    Have someone ever had the same situation ?

    Thanks for your help.

    Y 1 Reply Last reply
    0
    • D David Muller

      Hello everyone, I'm new here.
      I built my first project with the MySensors framework, and I don't know why I have communication issues.
      Here's the hardware configuration :

      • Sensor node : arduino nano with a DS18B20 and a NRF24L01+ (with 47µF cap on Vcc Gnd)
      • Gateway : ESP8266 and NRF24L01+ (send MQTT message via wifi)
      • Message decoder : Raspberry Pi 3B with node red

      I can see on my Raspberry incomming MQTT messages when I subscribe to the topic, but the payload is always empty !
      When I check the nodes console log, I see always the same error at the same moment.
      Here is what I get in the console (sensor node)

      16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.3.0
      25 TSM:INIT
      26 TSF:WUR:MS=0
      33 TSM:INIT:TSP OK
      35 TSM:FPAR
      37 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      331 TSF:MSG:READ,0-0-255,s=255,c=3,t=8,pt=1,l=1,sg=0:0
      336 TSF:MSG:FPAR OK,ID=0,D=1
      2046 TSM:FPAR:OK
      2048 TSM:ID
      2049 TSM:ID:REQ
      2052 TSF:MSG:SEND,255-255-0-0,s=1,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
      4059 TSM:ID
      4060 TSM:ID:REQ
      4062 TSF:MSG:SEND,255-255-0-0,s=220,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
      6070 TSM:ID
      6071 TSM:ID:REQ
      6073 TSF:MSG:SEND,255-255-0-0,s=183,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
      8081 TSM:ID
      8082 TSM:ID:REQ
      8084 TSF:MSG:SEND,255-255-0-0,s=146,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=OK:
      10092 !TSM:ID:FAIL
      10093 TSM:FAIL:CNT=1
      10095 TSM:FAIL:DIS
      10097 TSF:TDI:TSL
      20100 TSM:FAIL:RE-INIT
      20102 TSM:INIT
      20109 TSM:INIT:TSP OK
      20111 TSM:FPAR

      Here is the failed line using the log parser : "Transition to Failure state, consecutive failure counter is 1"

      So I think this is why I never get a payload in my MQTT messages, the sensor node does'nt even send the sensor data, but I don't know why !

      Have someone ever had the same situation ?

      Thanks for your help.

      Y Offline
      Y Offline
      Yveaux
      Mod
      wrote on last edited by
      #2

      @david-muller hi and welcome to the forum!
      Your sensor node should either have a fixed node ID, or your controller should hand one out on request by the node.
      As you're using node-red the easiest solution is to hardcore the node ID in the sensor node :

      #define MY_NODE_ID 1
      

      and place it before #include <MySensors.h>

      http://yveaux.blogspot.nl

      1 Reply Last reply
      2
      • T Offline
        T Offline
        tbowmo
        Admin
        wrote on last edited by
        #3

        @David-Muller

        If you don't want to hardcode node ID's then there is the option of using node-red-contrib-mysensors, and the MysController node within that package, as it can hand out node ids for you.

        1 Reply Last reply
        0
        • D Offline
          D Offline
          David Muller
          wrote on last edited by
          #4

          Beautiful, I added the define and it works very good now !
          Big thanks to you !!!

          1 Reply Last reply
          1

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          15

          Online

          12.1k

          Users

          11.2k

          Topics

          113.4k

          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