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. Lights on after gateway reboot

Lights on after gateway reboot

Scheduled Pinned Locked Moved Troubleshooting
6 Posts 2 Posters 59 Views 2 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.
  • monteM Offline
    monteM Offline
    monte
    wrote on last edited by monte
    #1

    I have made myself a new standalone mqtt gateway (before I was only using RPi gateways). Now I see strange behavior with 2 of 3 light nodes I have.
    After gateway boots, it sends discovery requests:

    1296965 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
    1296973 TSF:MSG:BC
    1297567 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=0,st=OK:0
    1299177 TSF:MSG:READ,0-0-255,s=43,c=3,t=4,pt=0,l=1,sg=0:1
    1299183 TSF:MSG:BC
    1299316 TSF:MSG:READ,0-0-255,s=63,c=3,t=4,pt=0,l=1,sg=0:2
    1299322 TSF:MSG:BC
    1299456 TSF:MSG:READ,0-0-255,s=16,c=3,t=4,pt=0,l=1,sg=0:3
    1299462 TSF:MSG:BC
    1299595 TSF:MSG:READ,0-0-255,s=30,c=3,t=4,pt=0,l=1,sg=0:4
    1299601 TSF:MSG:BC
    1299736 TSF:MSG:READ,0-0-255,s=239,c=3,t=4,pt=0,l=1,sg=0:5
    1299742 TSF:MSG:BC
    1299877 TSF:MSG:READ,0-0-255,s=192,c=3,t=4,pt=0,l=1,sg=0:6
    1299884 TSF:MSG:BC
    1300019 TSF:MSG:READ,0-0-255,s=145,c=3,t=4,pt=0,l=1,sg=0:7
    1300025 TSF:MSG:BC
    1300301 TSF:MSG:READ,0-0-255,s=112,c=3,t=4,pt=0,l=1,sg=0:9
    1300307 TSF:MSG:BC
    1300441 TSF:MSG:READ,0-0-255,s=18,c=3,t=4,pt=0,l=2,sg=0:10
    1300447 TSF:MSG:BC
    1305182 TSF:MSG:READ,0-0-3,s=255,c=3,t=6,pt=0,l=1,sg=0:M
    1305313 TSF:MSG:READ,0-0-3,s=0,c=1,t=2,pt=0,l=1,sg=0:0
    1305319 TSF:MSG:ECHO REQ
    

    After this my nodes for some reason send current states:

    1305323 TSF:MSG:SEND,3-3-0-0,s=0,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:0
    1305333 TSF:MSG:SEND,3-3-0-0,s=1,c=1,t=3,pt=1,l=1,sg=0,ft=0,st=OK:21
    1305344 TSF:MSG:SEND,3-3-0-0,s=2,c=1,t=3,pt=1,l=1,sg=0,ft=0,st=OK:100
    1305401 TSF:MSG:SEND,3-3-0-0,s=1,c=1,t=2,pt=1,l=1,sg=0,ft=0,st=OK:0
    1305446 !TSF:MSG:SEND,3-3-0-0,s=2,c=1,t=2,pt=1,l=1,sg=0,ft=0,st=NACK:0
    

    And after that they recieve it back from gateway, and act as if it was a command to change their state.

    Gateway is 2.4 alpha, all 3 nodes are 2.3.2, and only two of them acts like this. I guess I am missing something, but can't grasp what exactly.

    Any ideas?

    monteM 1 Reply Last reply
    0
    • monteM monte

      I have made myself a new standalone mqtt gateway (before I was only using RPi gateways). Now I see strange behavior with 2 of 3 light nodes I have.
      After gateway boots, it sends discovery requests:

      1296965 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
      1296973 TSF:MSG:BC
      1297567 TSF:MSG:SEND,3-3-0-0,s=255,c=3,t=21,pt=1,l=1,sg=0,ft=0,st=OK:0
      1299177 TSF:MSG:READ,0-0-255,s=43,c=3,t=4,pt=0,l=1,sg=0:1
      1299183 TSF:MSG:BC
      1299316 TSF:MSG:READ,0-0-255,s=63,c=3,t=4,pt=0,l=1,sg=0:2
      1299322 TSF:MSG:BC
      1299456 TSF:MSG:READ,0-0-255,s=16,c=3,t=4,pt=0,l=1,sg=0:3
      1299462 TSF:MSG:BC
      1299595 TSF:MSG:READ,0-0-255,s=30,c=3,t=4,pt=0,l=1,sg=0:4
      1299601 TSF:MSG:BC
      1299736 TSF:MSG:READ,0-0-255,s=239,c=3,t=4,pt=0,l=1,sg=0:5
      1299742 TSF:MSG:BC
      1299877 TSF:MSG:READ,0-0-255,s=192,c=3,t=4,pt=0,l=1,sg=0:6
      1299884 TSF:MSG:BC
      1300019 TSF:MSG:READ,0-0-255,s=145,c=3,t=4,pt=0,l=1,sg=0:7
      1300025 TSF:MSG:BC
      1300301 TSF:MSG:READ,0-0-255,s=112,c=3,t=4,pt=0,l=1,sg=0:9
      1300307 TSF:MSG:BC
      1300441 TSF:MSG:READ,0-0-255,s=18,c=3,t=4,pt=0,l=2,sg=0:10
      1300447 TSF:MSG:BC
      1305182 TSF:MSG:READ,0-0-3,s=255,c=3,t=6,pt=0,l=1,sg=0:M
      1305313 TSF:MSG:READ,0-0-3,s=0,c=1,t=2,pt=0,l=1,sg=0:0
      1305319 TSF:MSG:ECHO REQ
      

      After this my nodes for some reason send current states:

      1305323 TSF:MSG:SEND,3-3-0-0,s=0,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:0
      1305333 TSF:MSG:SEND,3-3-0-0,s=1,c=1,t=3,pt=1,l=1,sg=0,ft=0,st=OK:21
      1305344 TSF:MSG:SEND,3-3-0-0,s=2,c=1,t=3,pt=1,l=1,sg=0,ft=0,st=OK:100
      1305401 TSF:MSG:SEND,3-3-0-0,s=1,c=1,t=2,pt=1,l=1,sg=0,ft=0,st=OK:0
      1305446 !TSF:MSG:SEND,3-3-0-0,s=2,c=1,t=2,pt=1,l=1,sg=0,ft=0,st=NACK:0
      

      And after that they recieve it back from gateway, and act as if it was a command to change their state.

      Gateway is 2.4 alpha, all 3 nodes are 2.3.2, and only two of them acts like this. I guess I am missing something, but can't grasp what exactly.

      Any ideas?

      monteM Offline
      monteM Offline
      monte
      wrote on last edited by
      #2

      Switching the gateway to 2.3.2 haven't change anything, as expected.

      1 Reply Last reply
      0
      • monteM Offline
        monteM Offline
        monte
        wrote on last edited by
        #3

        I figured this out. After discovery, gateway sends states found in HA (or MQTT I'm not sure). It sends first - state, second - level. My code was turning light state on on every level change greater than 0, so because the state is sent first and the level second, my nodes got confused and turned lights on.
        The question is why this behavior is different from TCP gateway I used before.
        It was pretty dumb problem, but at least there is now this thread for someone who might have same problem in the future :)

        1 Reply Last reply
        0
        • electrikE Offline
          electrikE Offline
          electrik
          wrote on last edited by
          #4

          Could it be the MQTT message is retained? You can use a tool like MQTT explorer to see this

          monteM 1 Reply Last reply
          0
          • electrikE electrik

            Could it be the MQTT message is retained? You can use a tool like MQTT explorer to see this

            monteM Offline
            monteM Offline
            monte
            wrote on last edited by
            #5

            @electrik I am using MQTT explorer, but I don't see where is an option to see if message that was sent is retained. There is only box "retain" for a message to be sent from the program.

            1 Reply Last reply
            0
            • electrikE Offline
              electrikE Offline
              electrik
              wrote on last edited by
              #6

              If the message is retained, it will show up already when you connect MQTT explorer to the broker, without HA sending a message yet

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


              21

              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