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. Upgrade 1.4 to 2.3.1 relay node

Upgrade 1.4 to 2.3.1 relay node

Scheduled Pinned Locked Moved Troubleshooting
3 Posts 3 Posters 505 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.
  • A Offline
    A Offline
    allysmith
    wrote on last edited by
    #1

    I have just upgraded my serial gateway from 1.4 to 2.3.1. All my 1.4 sensors seem to be working fine. So that gives me a good starting point to upgrade them all.

    However I have two relay sensors which I can't get to work.

    I believe its down to the changes in message sent from the gateway to the sensor

    The 1.4 message was - 0-0-1-1 s=7,c=1,t=2,pt=0,l=1,st=ok:1

    node-id(1);child-sensor-id(7);message-type(1 Set);ack(0);sub-type(2 V_LIGHT);payload(1 On)\n

    The 2.3.1 message is 0-0-1-1,s=7,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:1
    The following extra data "sg=0,ft=0".

    I guess that the node will have to be updated for it to work, but can someone point me in the direction of the documentation on the changes of the message structure for the "sg=0,ft=0" .

    many thanks.

    mfalkviddM 1 Reply Last reply
    0
    • A allysmith

      I have just upgraded my serial gateway from 1.4 to 2.3.1. All my 1.4 sensors seem to be working fine. So that gives me a good starting point to upgrade them all.

      However I have two relay sensors which I can't get to work.

      I believe its down to the changes in message sent from the gateway to the sensor

      The 1.4 message was - 0-0-1-1 s=7,c=1,t=2,pt=0,l=1,st=ok:1

      node-id(1);child-sensor-id(7);message-type(1 Set);ack(0);sub-type(2 V_LIGHT);payload(1 On)\n

      The 2.3.1 message is 0-0-1-1,s=7,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:1
      The following extra data "sg=0,ft=0".

      I guess that the node will have to be updated for it to work, but can someone point me in the direction of the documentation on the changes of the message structure for the "sg=0,ft=0" .

      many thanks.

      mfalkviddM Offline
      mfalkviddM Offline
      mfalkvidd
      Mod
      wrote on last edited by mfalkvidd
      #2

      @allysmith there have been 1336 commits to MySensors since v1.4. So pinpointing the exact changes will likey require a lot of digging. While you might be able to find a solution, finding a solution will probably require substantially more time than upgrading the node to 2.x.

      sg indicates signing (0 means off)
      ft is failed uplink transmission counter

      These are just part of the debug output, they are not included in the message

      See https://www.mysensors.org/apidocs/group__MyTransportgrp.html for documentation

      skywatchS 1 Reply Last reply
      0
      • mfalkviddM mfalkvidd

        @allysmith there have been 1336 commits to MySensors since v1.4. So pinpointing the exact changes will likey require a lot of digging. While you might be able to find a solution, finding a solution will probably require substantially more time than upgrading the node to 2.x.

        sg indicates signing (0 means off)
        ft is failed uplink transmission counter

        These are just part of the debug output, they are not included in the message

        See https://www.mysensors.org/apidocs/group__MyTransportgrp.html for documentation

        skywatchS Offline
        skywatchS Offline
        skywatch
        wrote on last edited by
        #3

        @allysmith You can't take a 1.4 code as it is and use it with 2.3.1 - As @mfalkvidd says there are a lot of changes.

        Post your code and you might be able to get some pointers as to what needs to change.

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


        18

        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