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. Advice needed

Advice needed

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 2 Posters 57 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.
  • T Offline
    T Offline
    Tommy Petersen
    wrote on last edited by
    #1

    Hello All

    I am in need of some advice, for a expansion of my setup.

    My current setup is as follows.

    Temp/Moist node--RPI Gateway--Node Red--InfluxDB--Grafana Dashboard.

    Now what I want to do is, when temp on node 1 is higher than XX and the time is between this and that.
    Activate relay on node 2 for x amount of time.

    My questions is how would I go about to setup this up.
    Can it be done within the MySensor network or should I do it in node-red?

    Any advice is welcome

    1 Reply Last reply
    0
    • skywatchS Online
      skywatchS Online
      skywatch
      wrote on last edited by
      #2

      There are 2 ways of doing this.

      First is to have a 'dumb' node that sends data to the controller. Then the controller decides if the relay has to be on or off and sends a signal to make it happen. This is how many systems work.

      The down side to this is that if the gateway becomes unavailable or the controller crashes, the relay state will not change.

      Personally I prefer to make the node as smart as possible, collecting data, doing calaculations and performing actions while sending the results to the controller for display. The controller can still send commands to the node but if the gateway or controller fail the realy will still operate as expected.

      You could even have the nodes request/send data to each other to confirm the status of the realy or anything else for that matter. That's really a third option ;)

      So I would approch it by haing node 1 get temp, send to controller and node 2. Have node 2 decide on realys status, switch relay and inform node 1 and controller of the status change. I am sure you can think of variations on this as well because you know best how you want things to work.

      T 1 Reply Last reply
      3
      • skywatchS skywatch

        There are 2 ways of doing this.

        First is to have a 'dumb' node that sends data to the controller. Then the controller decides if the relay has to be on or off and sends a signal to make it happen. This is how many systems work.

        The down side to this is that if the gateway becomes unavailable or the controller crashes, the relay state will not change.

        Personally I prefer to make the node as smart as possible, collecting data, doing calaculations and performing actions while sending the results to the controller for display. The controller can still send commands to the node but if the gateway or controller fail the realy will still operate as expected.

        You could even have the nodes request/send data to each other to confirm the status of the realy or anything else for that matter. That's really a third option ;)

        So I would approch it by haing node 1 get temp, send to controller and node 2. Have node 2 decide on realys status, switch relay and inform node 1 and controller of the status change. I am sure you can think of variations on this as well because you know best how you want things to work.

        T Offline
        T Offline
        Tommy Petersen
        wrote on last edited by
        #3

        @skywatch Thanks for the advice.
        I think I will go for the option of sending the data from node to node.

        Funny thing though, this feature of node to node is the first time I am hearing of it, but after some forum search, I can see it's been about for a while, this open up a whole new level of complexity for my sensor network :)

        1 Reply Last reply
        0
        • skywatchS Online
          skywatchS Online
          skywatch
          wrote on last edited by
          #4

          Yes the node to node is very handy sometimes. Make sure to send any data and changes to the controller too so that everything is in sync. Good luck!

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


          18

          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