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. smart sleep inconsistent?

smart sleep inconsistent?

Scheduled Pinned Locked Moved Troubleshooting
21 Posts 3 Posters 127 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.
  • CrankyCoderC Offline
    CrankyCoderC Offline
    CrankyCoder
    wrote on last edited by
    #10

    @skywatch said in smart sleep inconsistent?:

    Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....

    battery is only sent when there is a change in the voltage.

    @skywatch said in smart sleep inconsistent?:

    Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....

    Where do you see that? i get 1 and 0 reported as needed based on the state.

    @skywatch said in smart sleep inconsistent?:

    Also you are using sleep but have a receive function - what happens to messages when the node is asleep?

    That is what smartsleep does. It tells my controller (homeassistant) to queue up the messages. Which works fine, as long as the node wakes up.

    @skywatch said in smart sleep inconsistent?:

    Have you modified the pro mini as per the battery page on this site? Have you added capacitors to the radio module?

    Correct, modified for battery use, and capacitors to the radio module.

    @skywatch said in smart sleep inconsistent?:

    directionControl seems like it will always turn off both digital pins regardless of the message as //disable are the last statements to be actioned?

    This is correct, this is a directional H-bridge controller to pulse a latching solenoid valve, so I do not need them on but very briefly.

    Home Automation Tinkerer
    www.CrankyCoder.net

    Controller: HomeAssistant in Kubernetes
    Gateway: MQTTClientGateway
    MySensors: 2.3

    skywatchS 1 Reply Last reply
    0
    • CrankyCoderC Offline
      CrankyCoderC Offline
      CrankyCoder
      wrote on last edited by
      #11

      @skywatch said in smart sleep inconsistent?:

      #define MY_RF24_PA_LEVEL RF24_PA_HIGH

      I have the node and gateway on my desk now for testing, so I am going to reflash with this now! Fingers crossed it helps. :)

      Home Automation Tinkerer
      www.CrankyCoder.net

      Controller: HomeAssistant in Kubernetes
      Gateway: MQTTClientGateway
      MySensors: 2.3

      1 Reply Last reply
      0
      • CrankyCoderC Offline
        CrankyCoderC Offline
        CrankyCoder
        wrote on last edited by
        #12

        Got some more info. Here is some debug log off the gateway. The node in question is node 18

        22:02:47.582 -> 28832653 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
        22:03:51.377 -> 28896448 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
        22:03:51.422 -> 28896512 TSF:MSG:BC
        22:03:51.422 -> 28896533 TSF:MSG:FPAR REQ,ID=18
        22:03:51.468 -> 28896566 TSF:PNG:SEND,TO=0
        22:03:51.513 -> 28896594 TSF:CKU:OK
        22:03:51.513 -> 28896615 TSF:MSG:GWL OK
        22:03:51.967 -> 28897026 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
        22:05:01.405 -> 28966464 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
        22:05:01.497 -> 28966569 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
        22:07:04.200 -> 29089296 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
        22:07:04.246 -> 29089359 TSF:MSG:BC
        22:07:04.292 -> 29089380 TSF:MSG:FPAR REQ,ID=18
        22:07:04.337 -> 29089414 TSF:PNG:SEND,TO=0
        22:07:04.337 -> 29089442 TSF:CKU:OK
        22:07:04.382 -> 29089463 TSF:MSG:GWL OK
        22:07:05.152 -> 29090214 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
        22:10:01.430 -> 29266499 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
        22:10:01.521 -> 29266604 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
        22:10:59.660 -> 29324730 TSF:MSG:READ,38-38-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
        22:10:59.706 -> 29324794 TSF:MSG:BC
        22:10:59.706 -> 29324815 TSF:MSG:FPAR REQ,ID=38
        22:10:59.751 -> 29324848 TSF:PNG:SEND,TO=0
        22:10:59.797 -> 29324877 TSF:CKU:OK
        22:10:59.797 -> 29324897 TSF:MSG:GWL OK
        22:11:00.523 -> 29325594 !TSF:MSG:SEND,0-0-38-38,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
        

        Running it through the log parser it would appear the gateway is responding to the find parent request.

        BUT. The node it self seems to be failing to find parent periodically. Like it's not getting the message back from the gateway.

        22:12:10.465 -> Going to sleep
        22:12:10.465 -> 44562 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
        22:12:10.465 -> 44572 !MCO:SLP:TNR
        22:12:20.399 -> 54491 TSM:FAIL:RE-INIT
        22:12:20.399 -> 54493 TSM:INIT
        22:12:20.399 -> 54499 !TSM:INIT:TSP FAIL
        22:12:20.444 -> 54501 TSM:FAIL:CNT=5
        22:12:20.444 -> 54503 TSM:FAIL:DIS
        22:12:20.444 -> 54505 TSF:TDI:TSL
        22:12:20.489 -> 54575 MCO:SLP:MS=19999
        22:12:20.489 -> 54577 !TSF:SND:TNR
        22:12:21.035 -> 55080 TSF:TDI:TSL
        22:12:42.255 -> 55083 MCO:SLP:WUP=-1
        22:12:42.301 -> 55085 TSF:TRI:TSB
        22:12:42.301 -> 55091 !TSF:SND:TNR
        22:12:42.301 -> Awake Now
        22:12:42.301 -> 1010
        22:12:42.301 -> 3.29
        22:12:42.301 -> Battery Voltage: 7.98 V
        22:12:42.301 -> Battery percent: 94 %
        22:12:42.301 -> sensorValue:1010
        22:12:42.301 -> Going to sleep
        22:12:42.301 -> 55099 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
        22:12:42.301 -> 55109 !MCO:SLP:TNR
        22:12:51.744 -> 64509 TSM:FAIL:RE-INIT
        22:12:51.744 -> 64512 TSM:INIT
        22:12:51.744 -> 64518 !TSM:INIT:TSP FAIL
        22:12:51.744 -> 64520 TSM:FAIL:CNT=6
        22:12:51.744 -> 64522 TSM:FAIL:DIS
        22:12:51.744 -> 64524 TSF:TDI:TSL
        22:12:52.330 -> 65112 MCO:SLP:MS=19999
        22:12:52.330 -> 65114 !TSF:SND:TNR
        22:12:52.829 -> 65617 TSF:TDI:TSL
        

        Home Automation Tinkerer
        www.CrankyCoder.net

        Controller: HomeAssistant in Kubernetes
        Gateway: MQTTClientGateway
        MySensors: 2.3

        mfalkviddM 1 Reply Last reply
        1
        • CrankyCoderC CrankyCoder

          Got some more info. Here is some debug log off the gateway. The node in question is node 18

          22:02:47.582 -> 28832653 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
          22:03:51.377 -> 28896448 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
          22:03:51.422 -> 28896512 TSF:MSG:BC
          22:03:51.422 -> 28896533 TSF:MSG:FPAR REQ,ID=18
          22:03:51.468 -> 28896566 TSF:PNG:SEND,TO=0
          22:03:51.513 -> 28896594 TSF:CKU:OK
          22:03:51.513 -> 28896615 TSF:MSG:GWL OK
          22:03:51.967 -> 28897026 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
          22:05:01.405 -> 28966464 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
          22:05:01.497 -> 28966569 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
          22:07:04.200 -> 29089296 TSF:MSG:READ,18-18-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
          22:07:04.246 -> 29089359 TSF:MSG:BC
          22:07:04.292 -> 29089380 TSF:MSG:FPAR REQ,ID=18
          22:07:04.337 -> 29089414 TSF:PNG:SEND,TO=0
          22:07:04.337 -> 29089442 TSF:CKU:OK
          22:07:04.382 -> 29089463 TSF:MSG:GWL OK
          22:07:05.152 -> 29090214 TSF:MSG:SEND,0-0-18-18,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
          22:10:01.430 -> 29266499 GWT:IMQ:TOPIC=mygateway1-in/10/1/1/0/40, MSG RECEIVED
          22:10:01.521 -> 29266604 !TSF:MSG:SEND,0-0-53-10,s=1,c=1,t=40,pt=0,l=6,sg=0,ft=0,st=NACK:FFFFFF
          22:10:59.660 -> 29324730 TSF:MSG:READ,38-38-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
          22:10:59.706 -> 29324794 TSF:MSG:BC
          22:10:59.706 -> 29324815 TSF:MSG:FPAR REQ,ID=38
          22:10:59.751 -> 29324848 TSF:PNG:SEND,TO=0
          22:10:59.797 -> 29324877 TSF:CKU:OK
          22:10:59.797 -> 29324897 TSF:MSG:GWL OK
          22:11:00.523 -> 29325594 !TSF:MSG:SEND,0-0-38-38,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
          

          Running it through the log parser it would appear the gateway is responding to the find parent request.

          BUT. The node it self seems to be failing to find parent periodically. Like it's not getting the message back from the gateway.

          22:12:10.465 -> Going to sleep
          22:12:10.465 -> 44562 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
          22:12:10.465 -> 44572 !MCO:SLP:TNR
          22:12:20.399 -> 54491 TSM:FAIL:RE-INIT
          22:12:20.399 -> 54493 TSM:INIT
          22:12:20.399 -> 54499 !TSM:INIT:TSP FAIL
          22:12:20.444 -> 54501 TSM:FAIL:CNT=5
          22:12:20.444 -> 54503 TSM:FAIL:DIS
          22:12:20.444 -> 54505 TSF:TDI:TSL
          22:12:20.489 -> 54575 MCO:SLP:MS=19999
          22:12:20.489 -> 54577 !TSF:SND:TNR
          22:12:21.035 -> 55080 TSF:TDI:TSL
          22:12:42.255 -> 55083 MCO:SLP:WUP=-1
          22:12:42.301 -> 55085 TSF:TRI:TSB
          22:12:42.301 -> 55091 !TSF:SND:TNR
          22:12:42.301 -> Awake Now
          22:12:42.301 -> 1010
          22:12:42.301 -> 3.29
          22:12:42.301 -> Battery Voltage: 7.98 V
          22:12:42.301 -> Battery percent: 94 %
          22:12:42.301 -> sensorValue:1010
          22:12:42.301 -> Going to sleep
          22:12:42.301 -> 55099 MCO:SLP:MS=30000,SMS=1,I1=255,M1=255,I2=255,M2=255
          22:12:42.301 -> 55109 !MCO:SLP:TNR
          22:12:51.744 -> 64509 TSM:FAIL:RE-INIT
          22:12:51.744 -> 64512 TSM:INIT
          22:12:51.744 -> 64518 !TSM:INIT:TSP FAIL
          22:12:51.744 -> 64520 TSM:FAIL:CNT=6
          22:12:51.744 -> 64522 TSM:FAIL:DIS
          22:12:51.744 -> 64524 TSF:TDI:TSL
          22:12:52.330 -> 65112 MCO:SLP:MS=19999
          22:12:52.330 -> 65114 !TSF:SND:TNR
          22:12:52.829 -> 65617 TSF:TDI:TSL
          
          mfalkviddM Offline
          mfalkviddM Offline
          mfalkvidd
          Mod
          wrote on last edited by mfalkvidd
          #13

          !TSM:INIT:TSP FAIL indicates that the radio chip is not responding to the arduino's commands.

          The most common cause is unreliable wiring. But it could be something else. Define MY_DEBUG_VERBOSE_RF24 to get more details.

          CrankyCoderC 1 Reply Last reply
          0
          • mfalkviddM Offline
            mfalkviddM Offline
            mfalkvidd
            Mod
            wrote on last edited by
            #14

            Btw, are you using MySensors 2.3 on the node and the gateway?

            CrankyCoderC 1 Reply Last reply
            0
            • CrankyCoderC CrankyCoder

              @skywatch said in smart sleep inconsistent?:

              Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....

              battery is only sent when there is a change in the voltage.

              @skywatch said in smart sleep inconsistent?:

              Looking at the code, send_status_message only ever sends 1 - is this what you want? It seems to never send anything else (like 0)....

              Where do you see that? i get 1 and 0 reported as needed based on the state.

              @skywatch said in smart sleep inconsistent?:

              Also you are using sleep but have a receive function - what happens to messages when the node is asleep?

              That is what smartsleep does. It tells my controller (homeassistant) to queue up the messages. Which works fine, as long as the node wakes up.

              @skywatch said in smart sleep inconsistent?:

              Have you modified the pro mini as per the battery page on this site? Have you added capacitors to the radio module?

              Correct, modified for battery use, and capacitors to the radio module.

              @skywatch said in smart sleep inconsistent?:

              directionControl seems like it will always turn off both digital pins regardless of the message as //disable are the last statements to be actioned?

              This is correct, this is a directional H-bridge controller to pulse a latching solenoid valve, so I do not need them on but very briefly.

              skywatchS Offline
              skywatchS Offline
              skywatch
              wrote on last edited by
              #15

              @CrankyCoder Do the data drop outs have any correlation to the solenoid valve operating and does the valave use the same power supply as the node MCU?

              CrankyCoderC 1 Reply Last reply
              0
              • mfalkviddM mfalkvidd

                !TSM:INIT:TSP FAIL indicates that the radio chip is not responding to the arduino's commands.

                The most common cause is unreliable wiring. But it could be something else. Define MY_DEBUG_VERBOSE_RF24 to get more details.

                CrankyCoderC Offline
                CrankyCoderC Offline
                CrankyCoder
                wrote on last edited by
                #16

                @mfalkvidd Will add this now.

                Home Automation Tinkerer
                www.CrankyCoder.net

                Controller: HomeAssistant in Kubernetes
                Gateway: MQTTClientGateway
                MySensors: 2.3

                1 Reply Last reply
                0
                • mfalkviddM mfalkvidd

                  Btw, are you using MySensors 2.3 on the node and the gateway?

                  CrankyCoderC Offline
                  CrankyCoderC Offline
                  CrankyCoder
                  wrote on last edited by
                  #17

                  @mfalkvidd said in smart sleep inconsistent?:

                  Btw, are you using MySensors 2.3 on the node and the gateway?

                  Correct 2.3 on node and gateway.

                  Home Automation Tinkerer
                  www.CrankyCoder.net

                  Controller: HomeAssistant in Kubernetes
                  Gateway: MQTTClientGateway
                  MySensors: 2.3

                  1 Reply Last reply
                  0
                  • skywatchS skywatch

                    @CrankyCoder Do the data drop outs have any correlation to the solenoid valve operating and does the valave use the same power supply as the node MCU?

                    CrankyCoderC Offline
                    CrankyCoderC Offline
                    CrankyCoder
                    wrote on last edited by
                    #18

                    @skywatch unfortunately no. This is for a sprinkler valve that I haven't set up any automations for yet since the questionable reliability at the moment would flood my yard lol

                    Home Automation Tinkerer
                    www.CrankyCoder.net

                    Controller: HomeAssistant in Kubernetes
                    Gateway: MQTTClientGateway
                    MySensors: 2.3

                    1 Reply Last reply
                    0
                    • CrankyCoderC Offline
                      CrankyCoderC Offline
                      CrankyCoder
                      wrote on last edited by
                      #19

                      Not sure if this helps or if anything jumps out, but here is the node and gateway side by side. Node does find parent request, gateway sees it, responds with 0. But node never gets it.

                      5b95b0ce-3b3b-44c8-ad45-f1bb1ed7af22-image.png

                      Home Automation Tinkerer
                      www.CrankyCoder.net

                      Controller: HomeAssistant in Kubernetes
                      Gateway: MQTTClientGateway
                      MySensors: 2.3

                      mfalkviddM skywatchS 2 Replies Last reply
                      1
                      • CrankyCoderC CrankyCoder

                        Not sure if this helps or if anything jumps out, but here is the node and gateway side by side. Node does find parent request, gateway sees it, responds with 0. But node never gets it.

                        5b95b0ce-3b3b-44c8-ad45-f1bb1ed7af22-image.png

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

                        @CrankyCoder I am not sure but to me it looks like it takes a bit more than 1 second for the gateway to send the response? And by then, the node has already gone to sleep so it can't receive the message.

                        1 Reply Last reply
                        0
                        • CrankyCoderC CrankyCoder

                          Not sure if this helps or if anything jumps out, but here is the node and gateway side by side. Node does find parent request, gateway sees it, responds with 0. But node never gets it.

                          5b95b0ce-3b3b-44c8-ad45-f1bb1ed7af22-image.png

                          skywatchS Offline
                          skywatchS Offline
                          skywatch
                          wrote on last edited by
                          #21

                          @CrankyCoder How far apart are the node and gateway? What is between them? Can you post any photos of of each with the wiring?

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


                          16

                          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