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. Development
  3. Anybody else seeing - unstable nodes - Need restart every ~24-48 hours?

Anybody else seeing - unstable nodes - Need restart every ~24-48 hours?

Scheduled Pinned Locked Moved Development
13 Posts 7 Posters 4.2k Views 1 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.
  • A Offline
    A Offline
    andriej
    wrote on last edited by
    #3

    Running out of memory - that's the problem for most of programs/nodes.
    I have this problem in one too, so I made a code to restart node every x hours.

    :-)

    1 Reply Last reply
    0
    • korttomaK korttoma

      I had a node with similar behavior. In my case I found that the radio got to high voltage so the radio caused the hole node to freeze.
      Most problems are usually related to power supply so I would start the investigation there.

      J Offline
      J Offline
      Joey Edelstein
      wrote on last edited by
      #4

      I have this on a number of nodes using different power supplies. I have measured the voltage in to the radio arduino. I also have have a decoupling capacitor of 4.7uF across the radio's 3.3V and GND.
      While it could be a mem leak if that is the case it in the mysensor lib as my sketch is pretty basic and should be using constant memory .

      RJ_MakeR 1 Reply Last reply
      0
      • hekH Offline
        hekH Offline
        hek
        Admin
        wrote on last edited by
        #5

        The library does not use any dynamic allocation. So I doubt it it a memory leak situation.

        1 Reply Last reply
        0
        • J Joey Edelstein

          I have this on a number of nodes using different power supplies. I have measured the voltage in to the radio arduino. I also have have a decoupling capacitor of 4.7uF across the radio's 3.3V and GND.
          While it could be a mem leak if that is the case it in the mysensor lib as my sketch is pretty basic and should be using constant memory .

          RJ_MakeR Offline
          RJ_MakeR Offline
          RJ_Make
          Hero Member
          wrote on last edited by
          #6

          @Joey-Edelstein said:

          I have this on a number of nodes using different power supplies. I have measured the voltage in to the radio arduino. I also have have a decoupling capacitor of 4.7uF across the radio's 3.3V and GND.
          While it could be a mem leak if that is the case it in the mysensor lib as my sketch is pretty basic and should be using constant memory .

          Try a large cap, try 47uf

          RJ_Make

          1 Reply Last reply
          0
          • J Joey Edelstein

            Hi,
            I built a small home automation setup based on ago controller on a Raspberry pi with a serial gateway.
            I have 3 nodes and they all work fine after being plugged in and continue for a while but after 24-48 they stop working.
            If I unplug and plug back in they come back to life. I haven't been able to debug as the restart that comes with trying makes them work fine.
            At first I though the issue was with the build quality (I solder like a butcher) but I added a temp/humidity sensor on a bread board with good Arduino and am seeing the same issues.
            Anybody seeing something like this?
            Any ideas how to debug?
            Thanks
            Joey

            A Offline
            A Offline
            andriej
            wrote on last edited by
            #7

            @Joey-Edelstein try posting a code here so we can look better, maybe it's one of libraries?
            or interrupt? or something...

            :-)

            1 Reply Last reply
            0
            • J Offline
              J Offline
              Joey Edelstein
              wrote on last edited by
              #8

              This is the simplest sketch I'm using that is demonstrating the behavior I described:
              https://codebender.cc/sketch:103465

              1 Reply Last reply
              0
              • H Offline
                H Offline
                HarryDutch
                wrote on last edited by
                #9

                @Joey-Edelstein

                Have a look here. Remove all Serial.print(...) and Serial.println(...) and try again. Or use Serial.print(F(....)).

                J 1 Reply Last reply
                0
                • H HarryDutch

                  @Joey-Edelstein

                  Have a look here. Remove all Serial.print(...) and Serial.println(...) and try again. Or use Serial.print(F(....)).

                  J Offline
                  J Offline
                  Joey Edelstein
                  wrote on last edited by
                  #10

                  @HarryDutch said:

                  Serial.println(...) and try again. Or use Serial.print(F(....)).

                  interesting. I will give it a try. Thanks!

                  1 Reply Last reply
                  0
                  • J Offline
                    J Offline
                    Joey Edelstein
                    wrote on last edited by
                    #11

                    Just a thought here but if Serial.print("This string that gets allocated every time this is called") and basically is a memory leak shouldn't samples be updated to use Serial.print(F(....)) so the unwashed masses (like me) don't make stupid mistakes?

                    In the meantime I have updated my most accessible node and will see if this solves my issues.

                    1 Reply Last reply
                    0
                    • hekH Offline
                      hekH Offline
                      hek
                      Admin
                      wrote on last edited by
                      #12

                      The normal Serial.println() using char-array does not leak memory. The F()-version just uses less of the precious RAM by keeping the strings in flash.

                      So the F() is really good to use, especially if you're sketch is big.

                      1 Reply Last reply
                      0
                      • G Offline
                        G Offline
                        GaryStofer
                        wrote on last edited by
                        #13

                        Maybe you can setup a RF sniffer as seen here http://forum.mysensors.org/topic/242/wireless-nrf24l01-sniffer-for-mysensors and observe what traffic you see when the system or node fails to give you some clues as to what is going on ?

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


                        18

                        Online

                        11.7k

                        Users

                        11.2k

                        Topics

                        113.0k

                        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