Skip to content
  • 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. General Discussion
  3. Sensor connectivity and reliability
  • Getting Started
  • Controller
  • Build
  • Hardware
  • Download/API
  • Forum
  • Store

Sensor connectivity and reliability

Scheduled Pinned Locked Moved General Discussion
6 Posts 3 Posters 2.1k 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.
  • S Offline
    S Offline
    samppa
    wrote on last edited by
    #1

    Is there a way to know when the sensor was last reporting a measurement?

    I am planning to make a kind of supervision system with multiple sensors that monitor each other so that a faulty reading or failing sensor would not cause any dramatic consequences in the logic. So the reliability of each sensor could be calculated and e.g. fire alarm would be given only if the conclusion can be drawn from multiple verified sensor readings. So the sensors in house would have primary function ans several secondary functions to verify other sensors (whenever possible). E.g. a camera could be used to double check if a light was actually lit or not although the primary function would be surveillance (or just recording the last month).

    hekH 1 Reply Last reply
    0
    • S samppa

      Is there a way to know when the sensor was last reporting a measurement?

      I am planning to make a kind of supervision system with multiple sensors that monitor each other so that a faulty reading or failing sensor would not cause any dramatic consequences in the logic. So the reliability of each sensor could be calculated and e.g. fire alarm would be given only if the conclusion can be drawn from multiple verified sensor readings. So the sensors in house would have primary function ans several secondary functions to verify other sensors (whenever possible). E.g. a camera could be used to double check if a light was actually lit or not although the primary function would be surveillance (or just recording the last month).

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

      @samppa

      If you are running Vera as a controller, the plugin keeps track of last updated value for each sensor.

      The scenario you're describing is quite advanced and requires logic on the controller side.

      S 1 Reply Last reply
      0
      • hekH hek

        @samppa

        If you are running Vera as a controller, the plugin keeps track of last updated value for each sensor.

        The scenario you're describing is quite advanced and requires logic on the controller side.

        S Offline
        S Offline
        samppa
        wrote on last edited by
        #3

        @hek
        Is that the last sensor reading time shown somewhere in Vera UI5?
        Sorry for the stupid question, but is the luup code the correct way to implement logic on the controller side?

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

          Yes, you can see the time for the last reported value for each arduino-node on Vera.

          1 Reply Last reply
          0
          • S Offline
            S Offline
            samppa
            wrote on last edited by
            #5

            The first step I am planning is to track in the sensor node if measurement of a sensor value (e.g. DHT or Dallas) fails for some reason (loose wire) and then report this fact as another reliability sensor value. On the controller side it would be then easy to raise an alarm.

            The question is what sensor type should I use to report an array of success/fail values. It would clutter the UI if each is a separate "light".

            BulldogLowellB 1 Reply Last reply
            0
            • S samppa

              The first step I am planning is to track in the sensor node if measurement of a sensor value (e.g. DHT or Dallas) fails for some reason (loose wire) and then report this fact as another reliability sensor value. On the controller side it would be then easy to raise an alarm.

              The question is what sensor type should I use to report an array of success/fail values. It would clutter the UI if each is a separate "light".

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

              @samppa

              An option would be to create a sensor sensor node. Nodes can transmit messages to one another.

              • Set up the sensor sensor as a motion sensor.

              • Transmit messages from each sensor to the sensor sensor.

              • If a message does not get received within established parameters... signal motion.

              Or, just (as Hek pointed out) do it server side.

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


              4

              Online

              11.7k

              Users

              11.2k

              Topics

              113.0k

              Posts


              Copyright 2019 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
              • OpenHardware.io
              • Categories
              • Recent
              • Tags
              • Popular