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. mysgw MQTT Issues

mysgw MQTT Issues

Scheduled Pinned Locked Moved Troubleshooting
22 Posts 3 Posters 2.3k 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.
  • gohanG Offline
    gohanG Offline
    gohan
    Mod
    wrote on last edited by
    #11

    move node closer. You could also try swapping the 2 radio modules to see if the problem changes.

    1 Reply Last reply
    0
    • X Offline
      X Offline
      xefil
      wrote on last edited by
      #12

      @gohan said in mysgw MQTT Issues:

      move node closer. You could also try swapping the 2 radio modules to see if the problem changes.

      Strange is, the same radios had worked well until I've switched to RPi GW.
      From the logs, correct me if I'm wrong, the issue seems to be on the gateway, not able to send the return/ack message:

      !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
      

      The node is sending well!

      TSF:MSG:SEND,27-27-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      

      Or not??

      I've added capacitors 100uf to both and, as well, added a copper coli antenna 868Mhz.
      Now the GW is 10meters far away from the node. There is only one wall between.
      I was testing to switch to RF69 radios which should be better if compared to nRF24L01+ in terms of range and walls.
      This is not what expected...

      I'll try to replace the radio on the GW side.

      Any other suggestion is well appreciated!

      Thanks, Simon

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

        I forgot you had rfm69, so capacitor is not that important. Try to look at my rfm69 signal scanner and look for the code to print on debug the rssi of signal and output power and try to move around to see if you get any value change. I had problems with rpi3 gw using the alpha version, but on stable it works. You could also try to compile it as an ethernet gateway just to see if you get any changes. Can you also post the configure parameters you user?

        X 1 Reply Last reply
        0
        • gohanG gohan

          I forgot you had rfm69, so capacitor is not that important. Try to look at my rfm69 signal scanner and look for the code to print on debug the rssi of signal and output power and try to move around to see if you get any value change. I had problems with rpi3 gw using the alpha version, but on stable it works. You could also try to compile it as an ethernet gateway just to see if you get any changes. Can you also post the configure parameters you user?

          X Offline
          X Offline
          xefil
          wrote on last edited by
          #14

          @gohan said in mysgw MQTT Issues:

          I forgot you had rfm69, so capacitor is not that important. Try to look at my rfm69 signal scanner and look for the code to print on debug the rssi of signal and output power and try to move around to see if you get any value change. I had problems with rpi3 gw using the alpha version, but on stable it works. You could also try to compile it as an ethernet gateway just to see if you get any changes. Can you also post the configure parameters you user?

          Hello!
          Which parameters?
          compiling parameters of the GW?
          I've configured it with:

          ./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-gateway=mqtt --my-controller-ip-address=192.168.1.50 --my-mqtt-publish-topic-prefix=mygateway1-out --my-mqtt-subscribe-topic-prefix=mygateway1-in --my-mqtt-client-id=raspberryRFM69
          

          About the rfm69 signal scanner, should it run on the node or on the RPi?
          (where to find it?)

          Thanks @gohan :-)

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

            https://forum.mysensors.org/topic/7822/portable-rfm69-signal-scanner/6

            X 1 Reply Last reply
            0
            • gohanG gohan

              https://forum.mysensors.org/topic/7822/portable-rfm69-signal-scanner/6

              X Offline
              X Offline
              xefil
              wrote on last edited by
              #16

              @gohan said in mysgw MQTT Issues:

              https://forum.mysensors.org/topic/7822/portable-rfm69-signal-scanner/6

              Ok, then I need to upload it on the node (which is on a little wooden bird house) and go around with my laptop connected on it :-) Not a problem.
              But would that report issues on the GW RPi as well? How?

              Meanwhile I can try to compile the ethernet version to give it a try.

              Thanks, Simon

              1 Reply Last reply
              0
              • X Offline
                X Offline
                xefil
                wrote on last edited by
                #17

                Hello @gohan
                Installed ethernet version:

                ./configure --my-gateway=ethernet --my-port=5003
                

                And it's even worst:

                # ./mysgw -d
                mysgw: Starting gateway...
                mysgw: Protocol version - 2.2.0
                mysgw: MCO:BGN:INIT GW,CP=RNNGL---,VER=2.2.0
                mysgw: TSF:LRT:OK
                mysgw: TSM:INIT
                mysgw: TSF:WUR:MS=0
                mysgw: !TSM:INIT:TSP FAIL
                mysgw: TSM:FAIL:CNT=1
                mysgw: TSM:FAIL:DIS
                mysgw: TSF:TDI:TSL
                mysgw: TSM:FAIL:RE-INIT
                mysgw: TSM:INIT
                mysgw: !TSM:INIT:TSP FAIL
                mysgw: TSM:FAIL:CNT=2
                mysgw: TSM:FAIL:DIS
                mysgw: TSF:TDI:TSL
                mysgw: TSM:FAIL:RE-INIT
                mysgw: TSM:INIT
                mysgw: !TSM:INIT:TSP FAIL
                mysgw: TSM:FAIL:CNT=3
                mysgw: TSM:FAIL:DIS
                mysgw: TSF:TDI:TSL
                mysgw: TSM:FAIL:RE-INIT
                mysgw: TSM:INIT
                mysgw: !TSM:INIT:TSP FAIL
                

                Using the mqtt version at least the init gets completed.
                Ideas?

                Simon

                1 Reply Last reply
                0
                • MasMatM Offline
                  MasMatM Offline
                  MasMat
                  wrote on last edited by
                  #18

                  Just a quick idea: are you powering the RFM69 from the Rpi?
                  I use a Rpi Zero W and when I powered my radio NRF24 from that it doesnt get enough juice even with caps.
                  I now use a bigger USB-wall wart and use AMS1117-3.3 to power the radio (PA-version) and added caps.

                  My two cents

                  X 1 Reply Last reply
                  1
                  • MasMatM MasMat

                    Just a quick idea: are you powering the RFM69 from the Rpi?
                    I use a Rpi Zero W and when I powered my radio NRF24 from that it doesnt get enough juice even with caps.
                    I now use a bigger USB-wall wart and use AMS1117-3.3 to power the radio (PA-version) and added caps.

                    My two cents

                    X Offline
                    X Offline
                    xefil
                    wrote on last edited by xefil
                    #19

                    @masmat said in mysgw MQTT Issues:

                    Just a quick idea: are you powering the RFM69 from the Rpi?
                    I use a Rpi Zero W and when I powered my radio NRF24 from that it doesnt get enough juice even with caps.
                    I now use a bigger USB-wall wart and use AMS1117-3.3 to power the radio (PA-version) and added caps.

                    My two cents

                    Hello,

                    I've tried to get 3.3V from external source, but same situation:

                    Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSF:LRT:OK
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSF:WUR:MS=0
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT:TSP OK
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSM:INIT:GW MODE
                    Apr 16 23:27:02 mysensors-gateway mysgw: TSM:READY:ID=0,PAR=0,DIS=0
                    Apr 16 23:27:02 mysensors-gateway mysgw: MCO:REG:NOT NEEDED
                    Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:STP
                    Apr 16 23:27:02 mysensors-gateway mysgw: MCO:BGN:INIT OK,TSP=1
                    Apr 16 23:27:02 mysensors-gateway mysgw: GWT:RMQ:MQTT RECONNECT
                    Apr 16 23:27:02 mysensors-gateway mysgw: connected to 192.168.1.50
                    Apr 16 23:27:02 mysensors-gateway mysgw: GWT:RMQ:MQTT CONNECTED
                    Apr 16 23:27:02 mysensors-gateway mysgw: GWT:TPS:TOPIC=mygateway1-out/0/255/0/0/18,MSG SENT
                    Apr 16 23:27:42 mysensors-gateway mysgw: TSF:MSG:READ,1-27-177,s=48,c=0,t=32,pt=7,l=23,sg=1: 0
                    Apr 16 23:27:42 mysensors-gateway mysgw: !TSF:MSG:LEN,7!=32
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:BC
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:PNG:SEND,TO=0
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:CKU:OK
                    Apr 16 23:27:45 mysensors-gateway mysgw: TSF:MSG:GWL OK
                    Apr 16 23:27:47 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
                    Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
                    Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:BC
                    Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:FPAR REQ,ID=27
                    Apr 16 23:27:51 mysensors-gateway mysgw: TSF:CKU:OK,FCTRL
                    Apr 16 23:27:51 mysensors-gateway mysgw: TSF:MSG:GWL OK
                    Apr 16 23:27:53 mysensors-gateway mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
                    

                    Possible the problem is only sending and not receiving?
                    I've not tested the signal scanner right now.
                    I was hoping it's a power issue :'(

                    Simon

                    1 Reply Last reply
                    0
                    • X Offline
                      X Offline
                      xefil
                      wrote on last edited by
                      #20

                      Hello @gohan ,

                      I was able to compile correctly the network IP mode. I had compiled it with the wrong transport.
                      BTW, now it initialized correctly, BUT same problems.
                      I've replaced the radio as well (only on the gateway).
                      Here the logs:

                      mysgw: Starting gateway...
                      mysgw: Protocol version - 2.2.0
                      mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0
                      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: Listening for connections on 0.0.0.0:5003
                      mysgw: MCO:BGN:STP
                      mysgw: MCO:BGN:INIT OK,TSP=1
                      mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
                      mysgw: TSF:MSG:BC
                      mysgw: TSF:MSG:FPAR REQ,ID=27
                      mysgw: TSF:PNG:SEND,TO=0
                      mysgw: TSF:CKU:OK
                      mysgw: TSF:MSG:GWL OK
                      mysgw: !TSF:MSG:SEND,0-0-27-27,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
                      mysgw: TSF:MSG:READ,27-27-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
                      mysgw: TSF:MSG:BC
                      mysgw: TSF:MSG:FPAR REQ,ID=27
                      mysgw: TSF:CKU:OK,FCTRL
                      mysgw: TSF:MSG:GWL OK
                      

                      As you can see the SEND message fails.
                      I'll try now to move the node closer and then try the scanner.

                      Hope it helps :-(

                      Simon

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

                        You have to check both gw and node at same time in order to understand if message is delivered but ack fails or else.

                        X 1 Reply Last reply
                        0
                        • gohanG gohan

                          You have to check both gw and node at same time in order to understand if message is delivered but ack fails or else.

                          X Offline
                          X Offline
                          xefil
                          wrote on last edited by
                          #22

                          @gohan said in mysgw MQTT Issues:

                          You have to check both gw and node at same time in order to understand if message is delivered but ack fails or else.

                          Of course. I'll provide details this evening ;-)

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


                          19

                          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