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. Announcements
  3. Converting a sketch from 1.5.x to 2.0.x

Converting a sketch from 1.5.x to 2.0.x

Scheduled Pinned Locked Moved Announcements
52 Posts 21 Posters 31.9k Views 26 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.
  • Maurizio ColluM Maurizio Collu

    @martinhjelmare Thanks a ot.
    Is there any guide/manual where all these messages are explained?

    Plus, is there anywhere written what all these terms mean?

    TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

    Kind Regards

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

    @Maurizio-Collu do you mean except the link martinhjelmare provided?

    Maurizio ColluM 1 Reply Last reply
    0
    • mfalkviddM mfalkvidd

      @Maurizio-Collu do you mean except the link martinhjelmare provided?

      Maurizio ColluM Offline
      Maurizio ColluM Offline
      Maurizio Collu
      wrote on last edited by
      #44

      @mfalkvidd Yes, basically this part (I'm sure it is explained somewhere, but I can't find where)

      255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

      SOrry for my newbieness...

      1 Reply Last reply
      0
      • Maurizio ColluM Maurizio Collu

        @martinhjelmare Thanks a ot.
        Is there any guide/manual where all these messages are explained?

        Plus, is there anywhere written what all these terms mean?

        TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

        Kind Regards

        tekkaT Offline
        tekkaT Offline
        tekka
        Admin
        wrote on last edited by tekka
        #45

        @Maurizio-Collu Yes, the doc is in preparation, the meaning of these messages is described here (this is a PR that harmonizes the log message and will be pushed to 2.0.1).

        In brief:

        TSP:MSG:SEND 255-255-0-0 s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:
        
        

        TSP:MSG:SEND refers to message sending function in the transport state machine

        255-255-0-0 is the routing information, i.e. sender-last-next-destination

        s=255,c=3,t=3,pt=0,l=0,sg=0,ft=0,st=ok:

        • s=sensor ID (255 = internal)
        • c=command (3 = C_INTERNAL)
        • t=type (3 = I_ID_REQUEST)
        • pt=payload type (0 = P_STRING)
        • l=message length (0)
        • sg=signature flag (0 = not signed)
        • ft=failed transmission counter (0 = no failed uplink transmission at this* oint)
        • st=send status (OK)
        • : actual message (empty)

        => Your node has no assigned ID (=255) and is requesting a new ID from the controller.

        Please refer to the serial protocol or API for additional information.

        Good luck!

        1 Reply Last reply
        3
        • pndgt0P Offline
          pndgt0P Offline
          pndgt0
          wrote on last edited by
          #46

          Hi,
          I was trying to implement the irrigation controller but realized that was not migrated to MySensors 2.0.
          I followed the instructions provided in the first post and arrived to a version that compiles with no errors. Nonetheless, as I am newbie, I would appreciate if someone could review some changes that I am not sure about. Those changes are related with the original sketch which has direct calls to process() in several while statements. First I tried to change the process() with _process() but several errors appeared, so finally I removed all the calls to process() but am not sure. I have the modified code here IrrigationController.ino in which I commented the lines added / deleted / modified. Any help / direction would be greatly appreciated.

          Boots33B 1 Reply Last reply
          0
          • pndgt0P pndgt0

            Hi,
            I was trying to implement the irrigation controller but realized that was not migrated to MySensors 2.0.
            I followed the instructions provided in the first post and arrived to a version that compiles with no errors. Nonetheless, as I am newbie, I would appreciate if someone could review some changes that I am not sure about. Those changes are related with the original sketch which has direct calls to process() in several while statements. First I tried to change the process() with _process() but several errors appeared, so finally I removed all the calls to process() but am not sure. I have the modified code here IrrigationController.ino in which I commented the lines added / deleted / modified. Any help / direction would be greatly appreciated.

            Boots33B Offline
            Boots33B Offline
            Boots33
            Hero Member
            wrote on last edited by
            #47

            @pndgt0

            The sketches that require external libraries are not included in the V2 install anymore but they are available here in the new V2 format. You will find the irrigation sketch there.

            pndgt0P 1 Reply Last reply
            0
            • Boots33B Boots33

              @pndgt0

              The sketches that require external libraries are not included in the V2 install anymore but they are available here in the new V2 format. You will find the irrigation sketch there.

              pndgt0P Offline
              pndgt0P Offline
              pndgt0
              wrote on last edited by
              #48

              @Boots33 Great! Thank you for the quick response and the URL. I took that version. Just wanted to let you know that to successfully compile it was needed to remove the #include <LiquidCrystal.h> and probably an update to that sketch would be needed at Github respository.
              Thank you again!

              Boots33B 1 Reply Last reply
              0
              • pndgt0P pndgt0

                @Boots33 Great! Thank you for the quick response and the URL. I took that version. Just wanted to let you know that to successfully compile it was needed to remove the #include <LiquidCrystal.h> and probably an update to that sketch would be needed at Github respository.
                Thank you again!

                Boots33B Offline
                Boots33B Offline
                Boots33
                Hero Member
                wrote on last edited by
                #49

                @pndgt0 That may be because you do not have the LiquidCrystal library installed. They have the external libraries there as well

                1 Reply Last reply
                0
                • paqorP Offline
                  paqorP Offline
                  paqor
                  wrote on last edited by
                  #50
                  This post is deleted!
                  1 Reply Last reply
                  0
                  • siodS Offline
                    siodS Offline
                    siod
                    wrote on last edited by siod
                    #51

                    I built a 2.0 MQTT gateway and am experimenting with a sensor using 1.5 library. I can see incoming data in the serial monitor, but the data is a bit different then when I was using the 1.5 MQTT gateway. In openhab I used this:

                    {mqtt="<[mysensor:MyMQTT/3/2/1/V_TRIPPED:state:CLOSED:1],<[mysensor:MyMQTT/3/2/1/V_TRIPPED:state:OPEN:0]"}
                    

                    But now I must skip the V_Tripped part to make it work like this:

                    {mqtt="<[mysensor:mygateway1-out/3/2/1/0/16:state:OPEN:1],<[mysensor:mygateway1-out/3/2/1/0/16:state:CLOSED:0]"}
                    

                    Is this how it is supposed to be or do I have to make the sensor node 2.0 compatible first? I thought the payload is saved in the V_TRIPPED variable, but it doesn´t seem to work in the new 2.0 library. Pls advise-

                    edit:

                    Ok, digged a bit deeper: if I understand it right, I don´t need "V_TRIPPED" or any other value in my controllers code (which is openhab actually) anymore but still in my sensor node code of course. So the gateway will transform "V_Tripped" into sub-typ "16". Correct? So all I´ll have to change is my openhab code, right?

                    still learning...

                    YveauxY 1 Reply Last reply
                    0
                    • siodS siod

                      I built a 2.0 MQTT gateway and am experimenting with a sensor using 1.5 library. I can see incoming data in the serial monitor, but the data is a bit different then when I was using the 1.5 MQTT gateway. In openhab I used this:

                      {mqtt="<[mysensor:MyMQTT/3/2/1/V_TRIPPED:state:CLOSED:1],<[mysensor:MyMQTT/3/2/1/V_TRIPPED:state:OPEN:0]"}
                      

                      But now I must skip the V_Tripped part to make it work like this:

                      {mqtt="<[mysensor:mygateway1-out/3/2/1/0/16:state:OPEN:1],<[mysensor:mygateway1-out/3/2/1/0/16:state:CLOSED:0]"}
                      

                      Is this how it is supposed to be or do I have to make the sensor node 2.0 compatible first? I thought the payload is saved in the V_TRIPPED variable, but it doesn´t seem to work in the new 2.0 library. Pls advise-

                      edit:

                      Ok, digged a bit deeper: if I understand it right, I don´t need "V_TRIPPED" or any other value in my controllers code (which is openhab actually) anymore but still in my sensor node code of course. So the gateway will transform "V_Tripped" into sub-typ "16". Correct? So all I´ll have to change is my openhab code, right?

                      YveauxY Offline
                      YveauxY Offline
                      Yveaux
                      Mod
                      wrote on last edited by
                      #52

                      @siod correct. The conversion of value code to text has been removed in the 2.0.0 implementation, so now the raw values codes are reported in the topic.

                      http://yveaux.blogspot.nl

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


                      13

                      Online

                      11.7k

                      Users

                      11.2k

                      Topics

                      113.0k

                      Posts


                      Copyright 2019 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