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. [SOLVED] 8MHz Gateway : node not receiving any data

[SOLVED] 8MHz Gateway : node not receiving any data

Scheduled Pinned Locked Moved Troubleshooting
14 Posts 6 Posters 7.8k 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.
  • fetsF Offline
    fetsF Offline
    fets
    wrote on last edited by
    #5

    @rene_2k2 what sketch do you use on your node ?
    I'm now able to read incoming messages, I had to change mysensor.sleep(xxx) call in loop function by mysensor.wait(xxx).
    I hope it helps.

    1 Reply Last reply
    0
    • fetsF fets

      @rene_2k2 from what I read, the id resquest is manage by the controller not by the serial gateway and I think that MYSController doesn't support this feature. So you have to use a static id (this is what I do).
      I experience the same issue with my rfm69 (tested yesteray night for the first time) so I planed to take a closer look this evening but as I see that I'm not alone, may be i'll try to check what nagelc said or take a closer look to the forum.
      The suprise is that my gateway receive succesfully message from node but not the other way :(

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

      @fets said:

      @rene_2k2 from what I read, the id resquest is manage by the controller not by the serial gateway and I think that MYSController doesn't support this feature. So you have to use a static id (this is what I do).

      nope, ID requests are handled by MYSController. If the power supply is stable and ID assignments fail, you may try clearing the routing tables (clear gw eeprom)

      1 Reply Last reply
      0
      • R Offline
        R Offline
        rene_2k2
        wrote on last edited by
        #7

        Hi,

        Sorry for late reply, big storm, falling trees, internet/phone cables on the ground...

        @fets The sketches I used on my node is MockMySensors from the examples of MySensors V1.5 (adapted for RFM69), this sketch allows me to test sending and receiving messages. I've also tried others such as TimeAwareSensor, but with the same results...
        @tekka I've tried clearing eeprom of node and gateway, but does not seems better.

        I now have 2 physical nodes like the ones described by @Francois (Arduino Pro Mini & RFM69W connected by jumper wires, see his post ). The strange thing is that when using LowPowerLab node & gw sketches, it looks like no frame is lost (gw receiving each frame sent by node and all ACK responds OK) [even without caps and antennas when nodes are not far away]. whereas when using MySensors (gw & node or even 2 PingPong), they have difficulties to catch each others data.
        When using gw & node, gw seems to get node data but node does not get gw data : for TimeAwakeNode, it often needs to send at least 6 time requests before catching the gw response... This behaviour remains unchanged when swapping hardware. Do you know how I can first determine if this is the node not catching data or the gateway not sending data correctly (in MYSController's debug tab, I see the lines of data which are normally sent by the gateway but can I check that this data is really transmitted) ?

        @Francois : you have played with RFM69, don't you have any problems of nodes which do not receive reliably data from the gateway ? (I'm using V1.5)

        Any idea ?

        1 Reply Last reply
        0
        • FrancoisF Offline
          FrancoisF Offline
          Francois
          wrote on last edited by
          #8

          @rene_2k2 I don't have any issue with any of my nodes that is using the rfm69 radios. I also upgrade all my nodes to ver 1.5. I am using a series gateway and my controller is Domoticz

          1 Reply Last reply
          0
          • R Offline
            R Offline
            rene_2k2
            wrote on last edited by
            #9

            @Francois : Thanks for the answer.
            I'll keep investigating then...

            1 Reply Last reply
            0
            • E Offline
              E Offline
              etrombly
              wrote on last edited by etrombly
              #10

              I just switched over to mysensors, and am having the same issue. Using RFM69's with arduino pro mini's and openhab. The sensor registers with the serial gateway, and receives acks, but the gateway does not send any other messages to the node. I'll try to dig more into it, but since I'm new to mysensors I'm getting familiar with how everything works. Here's the debug info from the gateway:

              2015-09-12 19:17:24 - Arduino state updated to 0;0;3;0;9;read: 100-100-0 s=255,c=3,t=11,pt=0,l=5,sg=0:Relay
              100;255;3;0;11;Relay
              0;0;3;0;9;read: 100-100-0 s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
              100;255;3;0;12;1.0
              0;0;3;0;9;read: 100-100-0 s=1,c=0,t=3,pt=0,l=0,sg=0:
              100;1;0;0;3;
              
              2015-09-12 19:17:43 - KitchenPower received command ON
              2015-09-12 19:17:44 - Arduino received command 100;1;1;0;2;1
              
              2015-09-12 19:17:45 - KitchenPower state updated to ON
              

              and the relay node:

              send: 100-100-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
              sensor started, id=100, parent=0, distance=1
              send: 100-100-0-0 s=255,c=3,t=11,pt=0,l=5,sg=0,st=ok:Relay
              send: 100-100-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.0
              send: 100-100-0-0 s=1,c=0,t=3,pt=0,l=0,sg=0,st=ok:
              
              1 Reply Last reply
              0
              • E Offline
                E Offline
                etrombly
                wrote on last edited by
                #11

                Got it figured out. If anyone has this trouble in the future. If you are using a pro mini at 3.3V and 8mhz it isn't compatible with 115200 baud for serial communications. Switch BAUD_RATE to 57600 in MyConfig.h and it will fix the problem. You'll also need to change the baud to match in your demo.items, or whatever your site is called. (for openhab)

                1 Reply Last reply
                1
                • R Offline
                  R Offline
                  rene_2k2
                  wrote on last edited by rene_2k2
                  #12

                  @etrombly : thank you so much ! Setting baudrate to 57600 on my gateway seems to resolve the issue.

                  I had just realized there was a problem with gateway not sending packets thanks to the "WITH_LEDS_BLINKING" option but did not realized that my ProMini did not understand serial input at 115200... The tricky part is that it had no problem with serial output at 115200 and it sometimes even parse and process correctly serial 155200bauds input. However setting lower baudrate seems to work always now !

                  1 Reply Last reply
                  0
                  • E Offline
                    E Offline
                    etrombly
                    wrote on last edited by
                    #13

                    @rene_2k2 no problem, it was a really frustrating issue to troubleshoot. I ended up adding some debug prints to serialEvent() in the serialGateway code. Noticed that the first character on a send was fine, then the rest was garbled. A little googling showed what the problem was.

                    1 Reply Last reply
                    0
                    • R Offline
                      R Offline
                      rene_2k2
                      wrote on last edited by
                      #14

                      Just updated the subject so that people with the same issue find it easily.

                      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.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