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. Hardware
  3. Motion Sensor, flaky behavior

Motion Sensor, flaky behavior

Scheduled Pinned Locked Moved Hardware
22 Posts 7 Posters 7.7k 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.
  • N Offline
    N Offline
    naveen
    wrote on last edited by naveen
    #12

    I'm wondering if there is some way to do this:

    -send tripped command to gw/vera
    -poll gw/vera for the state of the tripped command (this is the step I have no idea how to do)
    -if value of tripped which was sent does not match the value in vera, resend command
    -repeat

    That way you ensure the message is continually sent until it is received (up to some finite number of times to prevent infinite loops)

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

      If you would consider moving your sensor network to 1.4 you can ask for an ack from gateway when you send in your tripped status.

      This mean the gateway will reply back to you sensor and you can pick up this answer (or choose to resend status again after some timeout if ack never reaches your node).

      N 1 Reply Last reply
      0
      • epierreE epierre

        oooppppssss... wiring error.... @hek always told me to double check...

        Here some hysteresis could be added, as commercial grade motion sensor, a value the gateway could send to modify how long the presence sensor will not send the "alarm is over", avoiding thus lots of notifications on server side and lot of redundant messages, here one every 2s ...

        epierreE Offline
        epierreE Offline
        epierre
        Hero Member
        wrote on last edited by
        #14

        @hek is there a way to make an interrupt with time ?

        I mean:

        • if it is tripped and previous status was untripped, send the alarm
        • if it is untripped but below a certain time don't send anything
        • after a while, the timer sends an untrip after the amount of time

        z-wave - Vera -> Domoticz
        rfx - Domoticz <- MyDomoAtHome <- Imperihome
        mysensors -> mysensors-gw -> Domoticz

        hekH 1 Reply Last reply
        0
        • epierreE epierre

          @hek is there a way to make an interrupt with time ?

          I mean:

          • if it is tripped and previous status was untripped, send the alarm
          • if it is untripped but below a certain time don't send anything
          • after a while, the timer sends an untrip after the amount of time
          hekH Offline
          hekH Offline
          hek
          Admin
          wrote on last edited by
          #15

          @epierre

          Yes, all this should be possible.
          Untripped should probably still be handled by the motion sensor (you will get an interrupt when state changes and can use the trimpot to change delay).

          epierreE 1 Reply Last reply
          0
          • hekH hek

            @epierre

            Yes, all this should be possible.
            Untripped should probably still be handled by the motion sensor (you will get an interrupt when state changes and can use the trimpot to change delay).

            epierreE Offline
            epierreE Offline
            epierre
            Hero Member
            wrote on last edited by
            #16

            @hek you mean only the hardware way ?

            Here if under 20s (in arduino time) I get my untrip, I don't send it. If a timer don't occurs, the untrip will never be sent.

            any idea ?

            z-wave - Vera -> Domoticz
            rfx - Domoticz <- MyDomoAtHome <- Imperihome
            mysensors -> mysensors-gw -> Domoticz

            hekH 1 Reply Last reply
            0
            • epierreE epierre

              @hek you mean only the hardware way ?

              Here if under 20s (in arduino time) I get my untrip, I don't send it. If a timer don't occurs, the untrip will never be sent.

              any idea ?

              hekH Offline
              hekH Offline
              hek
              Admin
              wrote on last edited by
              #17

              @epierre

              How do you keep track of time while sleeping your Arduino?

              epierreE 1 Reply Last reply
              0
              • hekH hek

                @epierre

                How do you keep track of time while sleeping your Arduino?

                epierreE Offline
                epierreE Offline
                epierre
                Hero Member
                wrote on last edited by
                #18

                @hek do the millis does it ? else I can add a rtc

                z-wave - Vera -> Domoticz
                rfx - Domoticz <- MyDomoAtHome <- Imperihome
                mysensors -> mysensors-gw -> Domoticz

                1 Reply Last reply
                0
                • hekH hek

                  If you would consider moving your sensor network to 1.4 you can ask for an ack from gateway when you send in your tripped status.

                  This mean the gateway will reply back to you sensor and you can pick up this answer (or choose to resend status again after some timeout if ack never reaches your node).

                  N Offline
                  N Offline
                  naveen
                  wrote on last edited by
                  #19

                  @hek

                  Is there any reason I should avoid 1.4? I wouldn't mind upgrading if it'll make my sensors a bit more robust. I'm waiting for 5V power supplies in case the 12V power supply I have is what is causing my issues

                  hekH 1 Reply Last reply
                  0
                  • N naveen

                    @hek

                    Is there any reason I should avoid 1.4? I wouldn't mind upgrading if it'll make my sensors a bit more robust. I'm waiting for 5V power supplies in case the 12V power supply I have is what is causing my issues

                    hekH Offline
                    hekH Offline
                    hek
                    Admin
                    wrote on last edited by
                    #20

                    @naveen

                    No, not really. Go for it. But things might still change (protocol/api) in 1.4. But that does not mean you have to update every day :smiley:

                    1 Reply Last reply
                    0
                    • YveauxY Yveaux

                      @naveen Did you check the 5v with a multimeter?
                      I have an identical breadboard supply and fried mine with a "12v" adapter. After measuring the output of the adapter it appeared to be around 16v and the onboard voltage converter (ams1117 if I recall right) had it's maximum input set to 15v or so...

                      BulldogLowellB Offline
                      BulldogLowellB Offline
                      BulldogLowell
                      Contest Winner
                      wrote on last edited by
                      #21

                      @Yveaux said:

                      @naveen Did you check the 5v with a multimeter?
                      I have an identical breadboard supply and fried mine with a "12v" adapter. After measuring the output of the adapter it appeared to be around 16v and the onboard voltage converter (ams1117 if I recall right) had it's maximum input set to 15v or so...

                      that happened to me once too.

                      jendrushJ 1 Reply Last reply
                      0
                      • BulldogLowellB BulldogLowell

                        @Yveaux said:

                        @naveen Did you check the 5v with a multimeter?
                        I have an identical breadboard supply and fried mine with a "12v" adapter. After measuring the output of the adapter it appeared to be around 16v and the onboard voltage converter (ams1117 if I recall right) had it's maximum input set to 15v or so...

                        that happened to me once too.

                        jendrushJ Offline
                        jendrushJ Offline
                        jendrush
                        wrote on last edited by
                        #22

                        @BulldogLowell I fried my breadbord power supply by connecting broken power adaptor(it have me about 13-14V instead of up to 12V), this fried AMS1117 5V. I replaced it, and it's working proper again.

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


                        25

                        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