Skip to content
  • 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. 💬 Building a Raspberry Pi Gateway
  • Getting Started
  • Controller
  • Build
  • Hardware
  • Download/API
  • Forum
  • Store

💬 Building a Raspberry Pi Gateway

Scheduled Pinned Locked Moved Announcements
1.1k Posts 173 Posters 422.4k Views 131 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.
  • gohanG gohan

    Well, if I have communication working it means the node should be encrypting data. I'll have to try with clear eeprom and try flashing sketch again

    AnticimexA Offline
    AnticimexA Offline
    Anticimex
    Contest Winner
    wrote on last edited by
    #780

    @gohan not if there is no encryption at all. You could try to use simple password option on a node with various passwords and see if it is detected by your gw at all.

    Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

    1 Reply Last reply
    0
    • AnticimexA Anticimex

      @gohan have you verified your communications are actually encrypted?

      gohanG Offline
      gohanG Offline
      gohan
      Mod
      wrote on last edited by
      #781

      @anticimex I guess you were right... the gw and node aren't using the AES key. So where am I supposed to add it in the gateway?

      AnticimexA 1 Reply Last reply
      0
      • gohanG gohan

        @anticimex I guess you were right... the gw and node aren't using the AES key. So where am I supposed to add it in the gateway?

        AnticimexA Offline
        AnticimexA Offline
        Anticimex
        Contest Winner
        wrote on last edited by
        #782

        @gohan you set that with the configure arguments I suspect, but I can't see it in the documentation. @marceloaqno perhaps knows how the rPi port handles this. I'm on a phone so I can't check the code easily. But you should be able to find it in the transport driver for rPi. On the rPi it can probably be defined in the code as it does not have a personalizer.

        Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

        gohanG 1 Reply Last reply
        0
        • AnticimexA Anticimex

          @gohan you set that with the configure arguments I suspect, but I can't see it in the documentation. @marceloaqno perhaps knows how the rPi port handles this. I'm on a phone so I can't check the code easily. But you should be able to find it in the transport driver for rPi. On the rPi it can probably be defined in the code as it does not have a personalizer.

          gohanG Offline
          gohanG Offline
          gohan
          Mod
          wrote on last edited by
          #783

          @anticimex It doesn't read it from the mysonfig.h for sure as it is where I always put it

          AnticimexA 1 Reply Last reply
          0
          • gohanG gohan

            @anticimex It doesn't read it from the mysonfig.h for sure as it is where I always put it

            AnticimexA Offline
            AnticimexA Offline
            Anticimex
            Contest Winner
            wrote on last edited by
            #784

            @gohan MyConfig.h does to my knowledge not have a define value for that. You cannot add new definitions to it and expect them to have an effect. If there is one already defined in there, as a comment or not, and it does not have an effect, please report a bug on it.

            Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

            1 Reply Last reply
            0
            • M macvictor

              @marceloaqno Thank's for you help. I have other question.. general I try configure my gateway to work with security & signing, but they doesn't work. Where is problem? On the bottom i send point what it do it:

              Gateway:

              1. ./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-mqtt-password=PASS --my-mqtt-user=USER --my-rf24-encryption-enabled --my-signing=software --my-signing-request-signatures --my-signing-request-gw-signatures-from-all
              2. make
              3. sudo make install
              4. sudo systemctl enable mysgw.service
              5. sudo systemctl start mysgw.service
              6. sudo mysgw --gen-soft-hmac-key
              7. sudo mysgw --set-soft-hmac-key=02417628BC1573CC380...
              8. sudo mysgw --gen-soft-serial-key
              9. sudo mysgw --set-soft-serial-key=00762CD152B868F7EB
              10. sudo mysgw --gen-aes-key
              11. sudo mysgw --set-aes-key= A790AD78B2D8B4DBBB5B2C4B9DD6DAF3

              Node:

              1. Load script SecurityPersonalizer.ino
              2. Uncomment and send sketch to arduino
              #define USE_SOFT_SIGNING
              #define STORE_SOFT_KEY
              #define USER_SOFT_KEY
              #define STORE_SOFT_SERIAL
              #define STORE_AES_KEY
              #define USER_AES_KEY
              
              #define MY_SOFT_HMAC_KEY 0X2,0X41,0X76,0X28,0XBC,0X15,0X73,0XCC,0X38...
              #define MY_AES_KEY 0XA7,0X90,0XAD,0X78,0XB2,0XD8...
              
              1. Read all value from EPROM (test save):
              Personalization sketch for MySensors usage.
              -------------------------------------------
              EEPROM configuration:
              SOFT_HMAC_KEY | 02417628BC1573CC380DE0FADF7C87D7D3C77272A783E6E438786A07C3A8C6CF
              SOFT_SERIAL   | 39BB1370C289643251
              AES_KEY       | A790AD78B2D8B4DBBB5B2C4B9DD6DAF3
              --------------------------------
              Personalization is now complete.
              
              1. Send sample sketch to arduino:
              //!< Enable debug prints to serial monitor
              #define MY_DEBUG
              //!< Enable signing related debug prints to serial monitor
              #define MY_DEBUG_VERBOSE_SIGNING
              // Enable NRF24L01 radio type
              #define MY_RADIO_NRF24
              
              // Select soft signing
              #define MY_SIGNING_SOFT
              
              // Enable lockdown of node if suspicious activity is detected
              //-->> #define MY_NODE_LOCK_FEATURE
              
              // Enable node whitelisting
              //#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = GATEWAY_ADDRESS,.serial = {0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01}}}
              
              // Enable this if you want destination node to sign all messages sent to this node.
              #define MY_SIGNING_REQUEST_SIGNATURES
              
              // SETTINGS FOR MY_SIGNING_SOFT
              #define MY_SIGNING_SOFT_RANDOMSEED_PIN 7 //!< Unconnected analog pin for random seed
              
              // Add repeater function to this sensor
              #define MY_REPEATER_FEATURE
              
              
              #include <SPI.h>
              #include <MySensors.h>
              #include <Bounce2.h>
              
              #define RELAY_PIN  4    // Arduino Digital I/O pin number for relay 
              #define BUTTON_PIN  3   // Arduino Digital I/O pin number for button 
              #define CHILD_ID 1      // Id of the sensor child
              #define RELAY_ON 1
              #define RELAY_OFF 0
              
              Bounce debouncer = Bounce();
              int oldValue = 0;
              bool state;
              
              MyMessage msg(CHILD_ID, V_LIGHT);
              
              void setup()
              {
                // Setup the button
                pinMode(BUTTON_PIN, INPUT);
                // Activate internal pull-up
                digitalWrite(BUTTON_PIN, HIGH);
              
                // After setting up the button, setup debouncer
                debouncer.attach(BUTTON_PIN);
                debouncer.interval(5);
              
                // Make sure relays are off when starting up
                digitalWrite(RELAY_PIN, RELAY_OFF);
                // Then set relay pins in output mode
                pinMode(RELAY_PIN, OUTPUT);
              
                // Set relay to last known state (using eeprom storage)
                state = loadState(CHILD_ID);
                digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);
              }
              
              void presentation()  {
                // Send the sketch version information to the gateway and Controller
                sendSketchInfo("Relay & Button", "1.0");
                
                // Register all sensors to gw (they will be created as child devices)
                present(CHILD_ID, S_LIGHT, "Switch Secure Sensor", false);
              }
              
              /*
                 Example on how to asynchronously check for new messages from gw
              */
              void loop()
              {
                debouncer.update();
                // Get the update value
                int value = debouncer.read();
              //  if (value != oldValue && value == 0) {
                  send(msg.set(state ? false : true), true); // Send new state and request ack back
              //  }
              //  oldValue = value;
                delay(5000);
              }
              
              void receive(const MyMessage &message) {
                // We only expect one type of message from controller. But we better check anyway.
                if (message.isAck()) {
                  Serial.println("This is an ack from gateway");
                }
              
                if (message.type == V_LIGHT) {
                  // Change relay state
                  state = message.getBool();
                  digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);
                  // Store state in eeprom
                  // saveState(CHILD_ID, state);
              
                  // Write some debug info
                  Serial.print("Incoming change for sensor:");
                  Serial.print(message.sensor);
                  Serial.print(", New status: ");
                  Serial.println(message.getBool());
                }
              }
              

              And finally in Arduino Serial Monitor I see:

              0 MCO:BGN:INIT REPEATER,CP=RNNRAS-,VER=2.1.1
              4 TSM:INIT
              5 TSF:WUR:MS=0
              11 TSM:INIT:TSP OK
              13 TSF:SID:OK,ID=105
              15 TSM:FPAR
              16 Will not sign message for destination 255 as it does not require it
              58 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
              2065 !TSM:FPAR:NO REPLY
              2067 TSM:FPAR
              2068 Will not sign message for destination 255 as it does not require it
              2110 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
              4117 !TSM:FPAR:NO REPLY
              4119 TSM:FPAR
              4120 Will not sign message for destination 255 as it does not require it
              4162 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
              6169 !TSM:FPAR:NO REPLY
              6171 TSM:FPAR
              6172 Will not sign message for destination 255 as it does not require it
              6214 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
              8221 !TSM:FPAR:FAIL
              8222 TSM:FAIL:CNT=1
              8224 TSM:FAIL:PDT
              

              and in gateway i see:

              sudo mysgw -d
              mysgw: Starting gateway...
              mysgw: Protocol version - 2.1.1
              mysgw: MCO:BGN:INIT GW,CP=RNNG-S-,VER=2.1.1
              mysgw: TSF:LRT:OK
              mysgw: TSM:INIT
              mysgw: TSF:WUR:MS=0
              mysgw: TSM:INIT:TSP OK
              mysgw: TSM:INIT:GW MODE
              mysgw: TSM:READY:ID=0,PAR=0,DIS=0
              mysgw: MCO:REG:NOT NEEDED
              mysgw: MCO:BGN:STP
              mysgw: MCO:BGN:INIT OK,TSP=1
              mysgw: Attempting MQTT connection...
              mysgw: connected to 127.0.0.1
              mysgw: MQTT connected
              mysgw: Sending message on topic: mysensors-out/0/255/0/0/18
              mysgw: TSF:MSG:READ,171-107-54,s=221,c=2,t=131,pt=4,l=25,sg=0:-1418183441
              mysgw: !TSF:MSG:PVER,3=2
              mysgw: TSF:MSG:READ,135-23-172,s=20,c=3,t=200,pt=7,l=25,sg=0:-0.00000178
              mysgw: !TSF:MSG:PVER,1=2
              mysgw: TSF:MSG:READ,34-66-89,s=168,c=1,t=9,pt=1,l=25,sg=0:56
              mysgw: !TSF:MSG:PVER,1=2
              mysgw: TSF:MSG:READ,223-46-240,s=112,c=5,t=192,pt=5,l=11,sg=1:1407647670
              mysgw: TSF:MSG:REL MSG
              mysgw: !TSF:RTE:240 UNKNOWN
              mysgw: !TSF:MSG:SEND,223-0-240-240,s=112,c=5,t=192,pt=5,l=11,sg=1,ft=0,st=NACK:1407647670
              mysgw: TSF:MSG:READ,183-139-129,s=37,c=6,t=155,pt=1,l=21,sg=0:48
              mysgw: !TSF:MSG:PVER,0=2
              mysgw: TSF:MSG:READ,139-214-233,s=61,c=3,t=193,pt=7,l=0,sg=1:0.00000000
              mysgw: TSF:MSG:REL MSG
              mysgw: !TSF:RTE:233 UNKNOWN
              mysgw: !TSF:MSG:SEND,139-0-233-233,s=61,c=3,t=193,pt=7,l=0,sg=1,ft=0,st=NACK:0.00000000
              mysgw: TSF:MSG:READ,83-33-7,s=179,c=2,t=27,pt=4,l=25,sg=1:-2057270722
              mysgw: !TSF:MSG:PVER,3=2
              mysgw: TSF:MSG:READ,110-148-67,s=113,c=0,t=158,pt=1,l=9,sg=1:251
              mysgw: !TSF:MSG:PVER,1=2
              mysgw: TSF:MSG:READ,75-209-102,s=204,c=7,t=25,pt=1,l=11,sg=1:52
              mysgw: !TSF:MSG:PVER,0=2
              mysgw: TSF:MSG:READ,184-209-235,s=58,c=1,t=140,pt=6,l=23,sg=1:1DC404A5401119FACF0000000000000000000000000000
              mysgw: !TSF:MSG:PVER,3=2
              mysgw: TSF:MSG:READ,172-203-51,s=140,c=2,t=173,pt=0,l=1,sg=1:?
              mysgw: TSF:MSG:REL MSG
              mysgw: !TSF:RTE:51 UNKNOWN
              mysgw: !TSF:MSG:SEND,172-0-51-51,s=140,c=2,t=173,pt=0,l=1,sg=1,ft=0,st=NACK:?
              

              Where is problem?

              rajeev2301R Offline
              rajeev2301R Offline
              rajeev2301
              wrote on last edited by
              #785

              @macvictor
              I followed all the step that you mentioned in your post to establish the serial gateway. However I am still not able to receive the message from arduino. Could you please what to do?

              import RPi.GPIO as GPIO
              from lib_nrf24 import NRF24
              import time
              import spidev

              GPIO.setmode(GPIO.BCM)

              pipes = [[0xE8, 0xE8, 0xF0, 0xF0, 0xE1], [0xF0, 0xF0, 0xF0, 0xF0, 0xE1]]
              radio = NRF24(GPIO, spidev.SpiDev())

              radio.begin(0,8)

              radio.setPayloadSize(32)
              radio.setChannel(0x76)
              radio.setDataRate(NRF24.BR_1MBPS)
              radio.setPALevel (NRF24.PA_MAX)
              radio.setAutoAck(True)
              radio.enableDynamicPayloads()
              radio.enableAckPayload()
              radio.openReadingPipe(1 ,pipes[1])
              radio.printDetails()
              radio.startListening()
              radio.GPIO.cleanup()

              Please find below my raspberry code..can you please suggest , if there is any issue with code or am I missing anything ?

              mfalkviddM 1 Reply Last reply
              0
              • rajeev2301R rajeev2301

                @macvictor
                I followed all the step that you mentioned in your post to establish the serial gateway. However I am still not able to receive the message from arduino. Could you please what to do?

                import RPi.GPIO as GPIO
                from lib_nrf24 import NRF24
                import time
                import spidev

                GPIO.setmode(GPIO.BCM)

                pipes = [[0xE8, 0xE8, 0xF0, 0xF0, 0xE1], [0xF0, 0xF0, 0xF0, 0xF0, 0xE1]]
                radio = NRF24(GPIO, spidev.SpiDev())

                radio.begin(0,8)

                radio.setPayloadSize(32)
                radio.setChannel(0x76)
                radio.setDataRate(NRF24.BR_1MBPS)
                radio.setPALevel (NRF24.PA_MAX)
                radio.setAutoAck(True)
                radio.enableDynamicPayloads()
                radio.enableAckPayload()
                radio.openReadingPipe(1 ,pipes[1])
                radio.printDetails()
                radio.startListening()
                radio.GPIO.cleanup()

                Please find below my raspberry code..can you please suggest , if there is any issue with code or am I missing anything ?

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

                @rajeev2301 please don't split our effort to help you into multiple threads. It wastes people's time when some information is in one thread and some in another thread.

                1 Reply Last reply
                1
                • wesW Offline
                  wesW Offline
                  wes
                  wrote on last edited by
                  #787

                  To upgrade to the latest release, can I use git pull, or is it better to delete the directory and start again?

                  Blog: https://www.wes.id.au/
                  Nodes: Arduino Pro Mini ATMega328P 3.3V 8MHz, RFM69 433MHz, Canton Power CE024 0.8-3.3V regulator & single AA battery
                  Gateway & Controller: Raspberry Pi 3 + Home Assistant

                  AnticimexA 1 Reply Last reply
                  1
                  • wesW wes

                    To upgrade to the latest release, can I use git pull, or is it better to delete the directory and start again?

                    AnticimexA Offline
                    AnticimexA Offline
                    Anticimex
                    Contest Winner
                    wrote on last edited by
                    #788

                    @wes you can pull. Just as long as you verify that your working directory is clean or only contains changes you intend to have. And you have the appropriate branch or tag checked out.

                    Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

                    S 1 Reply Last reply
                    2
                    • M macvictor

                      @marceloaqno Thank's for you help. I have other question.. general I try configure my gateway to work with security & signing, but they doesn't work. Where is problem? On the bottom i send point what it do it:

                      Gateway:

                      1. ./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-mqtt-password=PASS --my-mqtt-user=USER --my-rf24-encryption-enabled --my-signing=software --my-signing-request-signatures --my-signing-request-gw-signatures-from-all
                      2. make
                      3. sudo make install
                      4. sudo systemctl enable mysgw.service
                      5. sudo systemctl start mysgw.service
                      6. sudo mysgw --gen-soft-hmac-key
                      7. sudo mysgw --set-soft-hmac-key=02417628BC1573CC380...
                      8. sudo mysgw --gen-soft-serial-key
                      9. sudo mysgw --set-soft-serial-key=00762CD152B868F7EB
                      10. sudo mysgw --gen-aes-key
                      11. sudo mysgw --set-aes-key= A790AD78B2D8B4DBBB5B2C4B9DD6DAF3

                      Node:

                      1. Load script SecurityPersonalizer.ino
                      2. Uncomment and send sketch to arduino
                      #define USE_SOFT_SIGNING
                      #define STORE_SOFT_KEY
                      #define USER_SOFT_KEY
                      #define STORE_SOFT_SERIAL
                      #define STORE_AES_KEY
                      #define USER_AES_KEY
                      
                      #define MY_SOFT_HMAC_KEY 0X2,0X41,0X76,0X28,0XBC,0X15,0X73,0XCC,0X38...
                      #define MY_AES_KEY 0XA7,0X90,0XAD,0X78,0XB2,0XD8...
                      
                      1. Read all value from EPROM (test save):
                      Personalization sketch for MySensors usage.
                      -------------------------------------------
                      EEPROM configuration:
                      SOFT_HMAC_KEY | 02417628BC1573CC380DE0FADF7C87D7D3C77272A783E6E438786A07C3A8C6CF
                      SOFT_SERIAL   | 39BB1370C289643251
                      AES_KEY       | A790AD78B2D8B4DBBB5B2C4B9DD6DAF3
                      --------------------------------
                      Personalization is now complete.
                      
                      1. Send sample sketch to arduino:
                      //!< Enable debug prints to serial monitor
                      #define MY_DEBUG
                      //!< Enable signing related debug prints to serial monitor
                      #define MY_DEBUG_VERBOSE_SIGNING
                      // Enable NRF24L01 radio type
                      #define MY_RADIO_NRF24
                      
                      // Select soft signing
                      #define MY_SIGNING_SOFT
                      
                      // Enable lockdown of node if suspicious activity is detected
                      //-->> #define MY_NODE_LOCK_FEATURE
                      
                      // Enable node whitelisting
                      //#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = GATEWAY_ADDRESS,.serial = {0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01}}}
                      
                      // Enable this if you want destination node to sign all messages sent to this node.
                      #define MY_SIGNING_REQUEST_SIGNATURES
                      
                      // SETTINGS FOR MY_SIGNING_SOFT
                      #define MY_SIGNING_SOFT_RANDOMSEED_PIN 7 //!< Unconnected analog pin for random seed
                      
                      // Add repeater function to this sensor
                      #define MY_REPEATER_FEATURE
                      
                      
                      #include <SPI.h>
                      #include <MySensors.h>
                      #include <Bounce2.h>
                      
                      #define RELAY_PIN  4    // Arduino Digital I/O pin number for relay 
                      #define BUTTON_PIN  3   // Arduino Digital I/O pin number for button 
                      #define CHILD_ID 1      // Id of the sensor child
                      #define RELAY_ON 1
                      #define RELAY_OFF 0
                      
                      Bounce debouncer = Bounce();
                      int oldValue = 0;
                      bool state;
                      
                      MyMessage msg(CHILD_ID, V_LIGHT);
                      
                      void setup()
                      {
                        // Setup the button
                        pinMode(BUTTON_PIN, INPUT);
                        // Activate internal pull-up
                        digitalWrite(BUTTON_PIN, HIGH);
                      
                        // After setting up the button, setup debouncer
                        debouncer.attach(BUTTON_PIN);
                        debouncer.interval(5);
                      
                        // Make sure relays are off when starting up
                        digitalWrite(RELAY_PIN, RELAY_OFF);
                        // Then set relay pins in output mode
                        pinMode(RELAY_PIN, OUTPUT);
                      
                        // Set relay to last known state (using eeprom storage)
                        state = loadState(CHILD_ID);
                        digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);
                      }
                      
                      void presentation()  {
                        // Send the sketch version information to the gateway and Controller
                        sendSketchInfo("Relay & Button", "1.0");
                        
                        // Register all sensors to gw (they will be created as child devices)
                        present(CHILD_ID, S_LIGHT, "Switch Secure Sensor", false);
                      }
                      
                      /*
                         Example on how to asynchronously check for new messages from gw
                      */
                      void loop()
                      {
                        debouncer.update();
                        // Get the update value
                        int value = debouncer.read();
                      //  if (value != oldValue && value == 0) {
                          send(msg.set(state ? false : true), true); // Send new state and request ack back
                      //  }
                      //  oldValue = value;
                        delay(5000);
                      }
                      
                      void receive(const MyMessage &message) {
                        // We only expect one type of message from controller. But we better check anyway.
                        if (message.isAck()) {
                          Serial.println("This is an ack from gateway");
                        }
                      
                        if (message.type == V_LIGHT) {
                          // Change relay state
                          state = message.getBool();
                          digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF);
                          // Store state in eeprom
                          // saveState(CHILD_ID, state);
                      
                          // Write some debug info
                          Serial.print("Incoming change for sensor:");
                          Serial.print(message.sensor);
                          Serial.print(", New status: ");
                          Serial.println(message.getBool());
                        }
                      }
                      

                      And finally in Arduino Serial Monitor I see:

                      0 MCO:BGN:INIT REPEATER,CP=RNNRAS-,VER=2.1.1
                      4 TSM:INIT
                      5 TSF:WUR:MS=0
                      11 TSM:INIT:TSP OK
                      13 TSF:SID:OK,ID=105
                      15 TSM:FPAR
                      16 Will not sign message for destination 255 as it does not require it
                      58 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
                      2065 !TSM:FPAR:NO REPLY
                      2067 TSM:FPAR
                      2068 Will not sign message for destination 255 as it does not require it
                      2110 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
                      4117 !TSM:FPAR:NO REPLY
                      4119 TSM:FPAR
                      4120 Will not sign message for destination 255 as it does not require it
                      4162 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
                      6169 !TSM:FPAR:NO REPLY
                      6171 TSM:FPAR
                      6172 Will not sign message for destination 255 as it does not require it
                      6214 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
                      8221 !TSM:FPAR:FAIL
                      8222 TSM:FAIL:CNT=1
                      8224 TSM:FAIL:PDT
                      

                      and in gateway i see:

                      sudo mysgw -d
                      mysgw: Starting gateway...
                      mysgw: Protocol version - 2.1.1
                      mysgw: MCO:BGN:INIT GW,CP=RNNG-S-,VER=2.1.1
                      mysgw: TSF:LRT:OK
                      mysgw: TSM:INIT
                      mysgw: TSF:WUR:MS=0
                      mysgw: TSM:INIT:TSP OK
                      mysgw: TSM:INIT:GW MODE
                      mysgw: TSM:READY:ID=0,PAR=0,DIS=0
                      mysgw: MCO:REG:NOT NEEDED
                      mysgw: MCO:BGN:STP
                      mysgw: MCO:BGN:INIT OK,TSP=1
                      mysgw: Attempting MQTT connection...
                      mysgw: connected to 127.0.0.1
                      mysgw: MQTT connected
                      mysgw: Sending message on topic: mysensors-out/0/255/0/0/18
                      mysgw: TSF:MSG:READ,171-107-54,s=221,c=2,t=131,pt=4,l=25,sg=0:-1418183441
                      mysgw: !TSF:MSG:PVER,3=2
                      mysgw: TSF:MSG:READ,135-23-172,s=20,c=3,t=200,pt=7,l=25,sg=0:-0.00000178
                      mysgw: !TSF:MSG:PVER,1=2
                      mysgw: TSF:MSG:READ,34-66-89,s=168,c=1,t=9,pt=1,l=25,sg=0:56
                      mysgw: !TSF:MSG:PVER,1=2
                      mysgw: TSF:MSG:READ,223-46-240,s=112,c=5,t=192,pt=5,l=11,sg=1:1407647670
                      mysgw: TSF:MSG:REL MSG
                      mysgw: !TSF:RTE:240 UNKNOWN
                      mysgw: !TSF:MSG:SEND,223-0-240-240,s=112,c=5,t=192,pt=5,l=11,sg=1,ft=0,st=NACK:1407647670
                      mysgw: TSF:MSG:READ,183-139-129,s=37,c=6,t=155,pt=1,l=21,sg=0:48
                      mysgw: !TSF:MSG:PVER,0=2
                      mysgw: TSF:MSG:READ,139-214-233,s=61,c=3,t=193,pt=7,l=0,sg=1:0.00000000
                      mysgw: TSF:MSG:REL MSG
                      mysgw: !TSF:RTE:233 UNKNOWN
                      mysgw: !TSF:MSG:SEND,139-0-233-233,s=61,c=3,t=193,pt=7,l=0,sg=1,ft=0,st=NACK:0.00000000
                      mysgw: TSF:MSG:READ,83-33-7,s=179,c=2,t=27,pt=4,l=25,sg=1:-2057270722
                      mysgw: !TSF:MSG:PVER,3=2
                      mysgw: TSF:MSG:READ,110-148-67,s=113,c=0,t=158,pt=1,l=9,sg=1:251
                      mysgw: !TSF:MSG:PVER,1=2
                      mysgw: TSF:MSG:READ,75-209-102,s=204,c=7,t=25,pt=1,l=11,sg=1:52
                      mysgw: !TSF:MSG:PVER,0=2
                      mysgw: TSF:MSG:READ,184-209-235,s=58,c=1,t=140,pt=6,l=23,sg=1:1DC404A5401119FACF0000000000000000000000000000
                      mysgw: !TSF:MSG:PVER,3=2
                      mysgw: TSF:MSG:READ,172-203-51,s=140,c=2,t=173,pt=0,l=1,sg=1:?
                      mysgw: TSF:MSG:REL MSG
                      mysgw: !TSF:RTE:51 UNKNOWN
                      mysgw: !TSF:MSG:SEND,172-0-51-51,s=140,c=2,t=173,pt=0,l=1,sg=1,ft=0,st=NACK:?
                      

                      Where is problem?

                      pepsonP Offline
                      pepsonP Offline
                      pepson
                      wrote on last edited by
                      #789

                      @macvictor
                      Hi
                      Is any chance to add security & signing for radio RFM69HW ? Please help me how ?

                      AnticimexA 1 Reply Last reply
                      0
                      • pepsonP pepson

                        @macvictor
                        Hi
                        Is any chance to add security & signing for radio RFM69HW ? Please help me how ?

                        AnticimexA Offline
                        AnticimexA Offline
                        Anticimex
                        Contest Winner
                        wrote on last edited by
                        #790

                        @pepson signing is radio agnostic. It has nothing to do with the radio.

                        Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

                        1 Reply Last reply
                        0
                        • AnticimexA Anticimex

                          @wes you can pull. Just as long as you verify that your working directory is clean or only contains changes you intend to have. And you have the appropriate branch or tag checked out.

                          S Offline
                          S Offline
                          sineverba
                          Hardware Contributor
                          wrote on last edited by
                          #791

                          @anticimex @wes Can I please ask how to update? I mean, the right command to type.
                          I have the folder "MySensors" on documents of my user in Pi:

                          /home/sineverba/MySensors

                          Of course I have all installed and perfectly working now (I'm on the 2.2.0 rc2).

                          I need also to relaunch the ./config command?

                          Thank you to both and all!

                          AnticimexA 1 Reply Last reply
                          0
                          • S sineverba

                            @anticimex @wes Can I please ask how to update? I mean, the right command to type.
                            I have the folder "MySensors" on documents of my user in Pi:

                            /home/sineverba/MySensors

                            Of course I have all installed and perfectly working now (I'm on the 2.2.0 rc2).

                            I need also to relaunch the ./config command?

                            Thank you to both and all!

                            AnticimexA Offline
                            AnticimexA Offline
                            Anticimex
                            Contest Winner
                            wrote on last edited by
                            #792

                            @sineverba https://www.mysensors.org/download

                            Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)

                            1 Reply Last reply
                            0
                            • S Offline
                              S Offline
                              Syna
                              wrote on last edited by
                              #793

                              Hello, I configure the raspberry gateway to use MQTT. I set mosquitto as the broker. The problem that I encounter is that when I subscribe to test if the gateway publish on the broker, I have empty message. So my first guess is that there is an issue somewhere which cause that only empty message are sent.

                              Here is my arduino code : https://pastebin.com/YKi4EAad
                              The RasperryPI3 config & logs : https://pastebin.com/Kjn8CC8A
                              The MQTT Client logs : https://pastebin.com/ZP8GrkTj

                              M 1 Reply Last reply
                              0
                              • Sergio RiusS Offline
                                Sergio RiusS Offline
                                Sergio Rius
                                wrote on last edited by
                                #794

                                Regarding the communication issues described in the instructions page with the 2.2 stable version, is that still valid and still recommended to use the development branch?

                                1 Reply Last reply
                                0
                                • gohanG Offline
                                  gohanG Offline
                                  gohan
                                  Mod
                                  wrote on last edited by
                                  #795

                                  Go for stable now, I need to remove that line from the page

                                  Sergio RiusS 1 Reply Last reply
                                  1
                                  • gohanG gohan

                                    Go for stable now, I need to remove that line from the page

                                    Sergio RiusS Offline
                                    Sergio RiusS Offline
                                    Sergio Rius
                                    wrote on last edited by
                                    #796

                                    @gohan Thank you verys muchos. :+1:

                                    1 Reply Last reply
                                    0
                                    • S Syna

                                      Hello, I configure the raspberry gateway to use MQTT. I set mosquitto as the broker. The problem that I encounter is that when I subscribe to test if the gateway publish on the broker, I have empty message. So my first guess is that there is an issue somewhere which cause that only empty message are sent.

                                      Here is my arduino code : https://pastebin.com/YKi4EAad
                                      The RasperryPI3 config & logs : https://pastebin.com/Kjn8CC8A
                                      The MQTT Client logs : https://pastebin.com/ZP8GrkTj

                                      M Offline
                                      M Offline
                                      marceloaqno
                                      Code Contributor
                                      wrote on last edited by marceloaqno
                                      #797

                                      @syna It is empty because it's a message of type I_ID_REQUEST that your node is sending. You need to set up a controller to distribute IDs or you can set it manually by adding this to your node's sketch:

                                      #define MY_NODE_ID X
                                      

                                      where X is a unique number from 1 to 254.

                                      1 Reply Last reply
                                      0
                                      • S Offline
                                        S Offline
                                        sineverba
                                        Hardware Contributor
                                        wrote on last edited by
                                        #798

                                        Hi to all,
                                        tonight I made update from 2.2.0 RC2 to 2.2.0 (stable) on my Raspberry PI3.
                                        It is a live system (my heater control).

                                        By the way the update is very simple.

                                        First of all, backup or better CLONE your PI.

                                        1 - Disable the daemon with

                                        sudo systemctl stop mysgw.service && sudo systemctl disable mysgw.service
                                        

                                        2 - Make a copy of the MySensors folder ( I made a copy with the name of version coming, so...)

                                        cp -r MySensors MySensorsX.X.X(rc2)/
                                        

                                        (the slash at the end means "It's a folder!"

                                        3 - Remove the MySensors folder

                                        sudo rm -r MySensors
                                        

                                        4 - Git the "new" MySensors folder && configure it as usual. Remember to activate the daemon and see on Domoticz (for example) the gateway with new version :)

                                        1 Reply Last reply
                                        2
                                        • O Offline
                                          O Offline
                                          otto001
                                          wrote on last edited by
                                          #799

                                          Hi,

                                          I am running the current version (2.2.0) on a RPi 1.
                                          I noticed that sometimes the cpu usage of the service is increasing dramatically (around 90% and more) - and then the service stops working.
                                          As I am not a C-Pro, I wrote a little python-script, which is called every minute by cron and restarts the service, if it uses more than 50% cpu.
                                          Maybe someone will find it useful:

                                          # -*- coding: utf-8 -*-
                                          import psutil, sys, os, datetime
                                          
                                          PY3 = sys.version_info[0] == 2
                                          LOOKFOR = u"mysgw"
                                          for proc in psutil.process_iter():
                                              if proc.name() == "mysgw":
                                                  dt = str(datetime.datetime.now()).split('.')[0]
                                                  #print(proc)
                                                  cpu = proc.cpu_percent(interval=1)
                                                  #print(cpu)
                                                  #print(proc.cpu_times())
                                                  if cpu > 50:
                                                          print(dt + " high CPU-usage! --> restarting service")
                                                          os.system("/bin/systemctl restart mysgw.service")
                                                  else:
                                                          if datetime.datetime.now().strftime('%M') == "45":
                                                                  print(dt + " everything OK, cpu: " + str(cpu))
                                          

                                          and the crontab-entry (as root):

                                          * * * * * /home/pi/pstest.sh >> /var/log/mysgw-logger.log
                                          

                                          Cheers,
                                          Pula

                                          Nick WillisN 1 Reply Last reply
                                          4
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          1

                                          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
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular