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. Hardware
  3. v2.2 node and v1.4 pi gw

v2.2 node and v1.4 pi gw

Scheduled Pinned Locked Moved Hardware
6 Posts 3 Posters 1.1k 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.
  • T Offline
    T Offline
    Toyman
    wrote on last edited by
    #1

    I have a fully working MYS system consisting of 5 v1.5 nodes and v1.4 pi gw (the only pi gw available before v2.1 was introduced)

    Everything is working fantastic. Recently, I started to experiment with nrf52DK that naturally drove me to creating a v2.2 node.

    The node is not recognized by my current pi gw (expected), BUT! if I briefly power on v2.2 serial GW based on Nano, then not only Nano GW recognizes the node, but my old pi gw starts getting messages from it, EVEN if I power off v2.2 gw later on.

    So, I assume when I switch on the v2.2 gw, something happens (like handshaking) at the node level so it actually starts sending messages.

    The question is: can I implement this "something" via #defines and omit powering on v2.2 gw to kick-start the node.

    My current defines:

    MY_NODE_ID xx
    MY_PARENT_NODE_ID 0
    MY_PARENT_NODE_IS_STATIC
    

    I also tried:

    MY_REGISTRATION_FEATURE (false)
    MY_CORE_COMPATIBILITY_CHECK (false)
    

    with no sucess.

    Before I switch on v2.2gw I've got the following debug from the node:

    24167 !TSM:UPL:FAIL
    24168 TSM:FPAR
    24170 TSM:FPAR:STATP=0
    24172 TSM:ID
    24173 TSM:ID:OK
    24174 TSM:UPL
    
    1 Reply Last reply
    0
    • tbowmoT Offline
      tbowmoT Offline
      tbowmo
      Admin
      wrote on last edited by
      #2

      When your v2.2 node starts up, it starts a handshake sequence. This is only supported on a v2.2 gateway. If not answered correctly, then the Node assumes that no gateway is available, and will not communicate with your v1.4 gw

      When you start your GW based on nano, the node completes it's handshake sequence, and can communicate with your older gateway afterwards

      T 1 Reply Last reply
      0
      • tbowmoT tbowmo

        When your v2.2 node starts up, it starts a handshake sequence. This is only supported on a v2.2 gateway. If not answered correctly, then the Node assumes that no gateway is available, and will not communicate with your v1.4 gw

        When you start your GW based on nano, the node completes it's handshake sequence, and can communicate with your older gateway afterwards

        T Offline
        T Offline
        Toyman
        wrote on last edited by
        #3

        @tbowmo thx. that;s what I thought. Is there any way to "simulate" the handshaking?
        And logical question: obviously, my strategic route is to upgrade the pi gw to v2. What are the chances it will read my v1.5 nodes correctly as upgrading them is PITA?

        1 Reply Last reply
        0
        • tbowmoT Offline
          tbowmoT Offline
          tbowmo
          Admin
          wrote on last edited by
          #4

          @Toyman

          If I remember right, the GW can be upgraded to v2.2, and still communicate with nodes with earlier library versions. (Actually it works for me, as I haven't updated all my nodes in a long time, and the GW is updated recently)

          sundberg84S 1 Reply Last reply
          0
          • tbowmoT tbowmo

            @Toyman

            If I remember right, the GW can be upgraded to v2.2, and still communicate with nodes with earlier library versions. (Actually it works for me, as I haven't updated all my nodes in a long time, and the GW is updated recently)

            sundberg84S Offline
            sundberg84S Offline
            sundberg84
            Hardware Contributor
            wrote on last edited by
            #5

            If I remember right, the GW can be upgraded to v2.2, and still communicate with nodes with earlier library versions.

            Works for me as well. GW with 2.2 and nodes with everything from 1.4 up to 2.2.

            Controller: Proxmox VM - Home Assistant
            MySensors GW: Arduino Uno - W5100 Ethernet, Gw Shield Nrf24l01+ 2,4Ghz
            MySensors GW: Arduino Uno - Gw Shield RFM69, 433mhz
            RFLink GW - Arduino Mega + RFLink Shield, 433mhz

            1 Reply Last reply
            0
            • T Offline
              T Offline
              Toyman
              wrote on last edited by
              #6

              Thank you guys, I will just update the gw without messing with the node

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


              21

              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