Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. chaeron
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by chaeron

    • chaeron

      Upgraded my home sensor network to 2.1.1...
      General Discussion • • chaeron  

      1
      1
      Votes
      1
      Posts
      492
      Views

      No one has replied

    • chaeron

      Presentation of 3rd sensor for a node fails....
      Troubleshooting • • chaeron  

      10
      0
      Votes
      10
      Posts
      2167
      Views

      Efflon

      @robosensor I have tried the bool in the present() function but it doesn't help setting it to true...
    • chaeron

      Glass break sensor?
      Hardware • • chaeron  

      18
      0
      Votes
      18
      Posts
      7917
      Views

      Rod MacPherson

      Yes, regardless of the source, always check the spec sheet and even take some measurements your self when you get it to be sure. You can use resistors as voltage dividers, or use optocouplers/relays, or even burn it off with a step down voltage regulator like an LM7805. You will need to supply ~12V to the sensor too, as that is what it is designed for in a burglar alarm system, so take that into account. This one says it will operate off 9V, but don't count on powering it long off a 9V square battery.
    • chaeron

      Gateway questions....
      General Discussion • • chaeron  

      4
      0
      Votes
      4
      Posts
      1067
      Views

      chaeron

      Thanks for the explanation of inclusion mode. Much appreciated. I thought some of the gateway sketches did allocate node id's....but that for some reason the MQTT Client gateway didn't. No big deal....I don't want to use a 3rd party controller, so will just hard code the id's for now.
    • chaeron

      Sensor to Gateway protocol documentation?
      Controllers • • chaeron  

      9
      0
      Votes
      9
      Posts
      4298
      Views

      chaeron

      True enough on using MS a bit differently than most. But, IMO, that does not excuse the lack of documentation on the actual on the wire messages and protocols (message sequences from sender to recipient). The most important thing is not always the implementation (sketches, pre-done code, examples), but documentation of the underlying protocols, so that you can integrate other capabilities and approaches. 'nuff said on that. Check out the thermostat project that I built with a Raspberry Pi 2 and the new 7" touchscreen....this is what has gotten me interested in IoT, and the sensor world: https://github.com/chaeron/thermostat The code could be better (what code couldn't), but given it's a personal project and time was limited, I think the docs and the code is pretty decent and easy to figure out if you have the right background (Python, Kivy UI framework, etc.). Been running flawlessly for about a month now. Even emits detailed logging info over MQTT....and accepts a few commands over MQTT. Once I get my home sensor network built and running, based on MS and arduinos, I'm gonna use the secondary Pi to reformat the sensor MQTT messages to something a bit more semantically useful (room designators instead of numbers for temperature sensors around the house), and maybe implement some sort of weighted averaging for HVAC control of house temperatures. All fun stuff!