Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 12 2018 05:09
    websrider opened #464
  • Aug 30 2018 18:24

    JakeHartnell on development

    Auto expire events after 1 day Prepare for a new beginning Merge pull request #463 from Co… (compare)

  • Aug 30 2018 18:24
    JakeHartnell closed #463
  • Aug 30 2018 18:24
    JakeHartnell opened #463
  • Aug 30 2018 18:23

    JakeHartnell on new-beginning

    Auto expire events after 1 day Prepare for a new beginning (compare)

  • Jul 11 2018 17:19
    catbarph commented #458
  • Jul 11 2018 17:18
    catbarph commented #459
  • Jul 11 2018 17:18
    catbarph commented #460
  • Jul 11 2018 17:18
    catbarph commented #461
  • Jul 11 2018 17:16
    catbarph commented #462
  • Jul 11 2018 17:16
    catbarph opened #462
  • Jul 11 2018 17:04
    catbarph opened #461
  • Jul 11 2018 17:02
    catbarph opened #460
  • Jul 11 2018 16:46
    catbarph opened #459
  • Jul 11 2018 16:40
    catbarph opened #458
  • Jul 06 2018 22:11

    JakeHartnell on development

    Add splash screens and app icon… v0.5.5 (compare)

  • Jul 04 2018 06:01

    JakeHartnell on development

    Reorganization. Linting. (compare)

  • Jul 04 2018 04:35
    JakeHartnell closed #437
  • Jul 04 2018 04:35
    JakeHartnell commented #437
  • Jul 04 2018 04:34
    JakeHartnell closed #445
JF
@cloudzombie
No timer comes even remotely close to their reliability and accuracy.
If a maker made replacement fails to fire even once in a million cycles, it's worthless comparatively
That timer is bulletproof. I have dumped gallons of nytrient solution over them, still just kicking along.
If you can replace that timer for less than $35 in hardware and have it be that reliable, and still make a profit after logistics etc, hats off.
But I wouldn't use anything not field tested for at least half a million cycles in that particular hardware piece.
Jake Hartnell
@JakeHartnell
But I wouldn't use anything not field tested for at least half a million cycles in that particular hardware piece.
Good feedback. We'll start testing.
Dan Minshew
@newswim
I talked with a guy who does state-funding environmental sensing, including stuff like soil moisture which is notoriously difficult
he said good things about MQTT but they were using an xml messaging protocol
Dan Minshew
@newswim
pretty interesting project, https://www.mesonet.org
state-funded*
Jake Hartnell
@JakeHartnell
Nice, I wonder how much the state paid for that...
Arun Kumar T K
@aruntk
I've moved bower_components to imports/ui in this branch. Initial loading time will be higher than alpha. But after that because of meteor's caching mechanism hot code reload seems to be better.
JF
@cloudzombie
That mesonet is part of the tornado watch probability calculations, early warning there is crucial, I have a bit of land all over there and brother still lives there. http://blog.ametsoc.org/columnists/oklahoma-mesonet-station-stands-tall-in-ef-4-tornado/ so it's
Probably money well spent. Surviving ef4 tornado directly.
Jake Hartnell
@JakeHartnell
I've moved bower_components to imports/ui in this branch
That's cool. Feel free to open a PR.
Jake Hartnell
@JakeHartnell
Happy new year all! Alpha is out, a whole bunch of interesting things are in the works for 2017. Stay tuned!
Arun Kumar T K
@aruntk
Happy new year. :)
Jake Hartnell
@JakeHartnell
Jake Hartnell
@JakeHartnell
CommonGarden/Grow-IoT#323
Dan Minshew
@newswim
Hey everyone, is the hackathon happening today?
Jake Hartnell
@JakeHartnell
@newswim yes! Any ideas for what you'ld like to work on?
Checkout the react branch for starters perhaps: https://github.com/CommonGarden/Grow-IoT/tree/react
I'm going to be playing around with #300 and thing.js.
Jake Hartnell
@JakeHartnell
Jake Hartnell
@JakeHartnell
First growfile:
const Grow = require('Grow.js');

// A rough GrowFile example... first draft, it's crude.
// Feel free to make suggestions though.
module.exports = new Grow({
  name: 'It goes by many names...',
  version: '0.0.1', // Not grower tested, any recommendations?
  phases: {
    vegetative: {
      global: {
        ph: {
          min: 6.0,
          ideal: 6.15,
          max: 6.3,
        },
        ec: {
          min: 1400,
          ideal: 1500,
          max: 1700,
        },
        humidity: {
          min: 51,
          max: 61
        },
      },
      cycles: {
        day: {
          // Note: you may want to run the lights a little longer, adjust accordingly.
          start: 'after 6:00am',
          targets: {
            temperature: 24,
            // Protip: C02 emitter should be timed in relation to exhaust fan so that C02 is not sucked out of room.
            co2: {
              min: 900,
              max: 1600
            }
          }
        },
        night: {
          start: 'after 9:00pm',
          targets: {
            temperature: 20,
            co2: {
              min: 400,
              max: 1000
            },
          }
        }
      }
    },

    bloom: {
      global: {
        ph: {
          min: 6.0,
          ideal: 6.15,
          max: 6.3,
        },
        ec: {
          min: 1400,
          ideal: 1500,
          max: 1700,
        },
        humidity: {
          min: 51,
          max: 59
        },
      },
      cycles: {
        day: {
          start: 'after 7:00am',
          targets: {
            temperature: 24,
          }
        },
        night: {
          start: 'after 7:00pm',
          targets: {
            temperature: 20,
            co2: 400,
          },
        }
      }
    }
  }
});
Jake Hartnell
@JakeHartnell
Added comments:
```

const Grow = require('Grow.js');

// A rough GrowFile example... first draft, it's crude.
// Feel free to make suggestions though.
module.exports = new Grow({
name: 'It goes by many names...',
version: '0.0.1', // Not grower tested, any recommendations?
phases: {
vegetative: {
// Global targets durning this phase.
// min / max set alerts
// ideal is the target for the phase or cycle
global: {
ph: {
min: 6.0,
ideal: 6.15,
max: 6.3,
},
ec: {
min: 1400,
ideal: 1500,
max: 1700,
},
humidity: {
min: 51,
max: 61
},
},
// You can have more cycles than just day or night.
cycles: {
water: {
// Cycles have a start property which I will probably rename to schedule, because that's what it is.
// Grow.js calls the corresponding function according to the schedule.
start: 'every 2 hours'
},
day: {
// Note: you may want to run the lights a little longer, adjust accordingly.
start: 'after 6:00am',
// You can also specify a targets property, these will be updated before the function runs. ; )
targets: {
temperature: 24,
// Protip: C02 emitter should be timed in relation to exhaust fan so that C02 is not sucked out of room.
co2: {
min: 900,
max: 1600
}
}
},
night: {
start: 'after 9:00pm',
targets: {
temperature: 20,
co2: {
min: 400,
max: 1000
},
}
}
}
},

bloom: {
  global: {
    ph: {
      min: 6.0,
      ideal: 6.15,
      max: 6.3,
    },
    ec: {
      min: 1400,
      ideal: 1500,
      max: 1700,
    },
    humidity: {
      min: 51,
      max: 59
    },
  },
  cycles: {
    day: {
      start: 'after 7:00am',
      targets: {
        temperature: 24,
      }
    },
    night: {
      start: 'after 7:00pm',
      targets: {
        temperature: 20,
        co2: 400,
      },
    }
  }
}

}
});

const Grow = require('Grow.js');

// A rough GrowFile example... first draft, it's crude.
// Feel free to make suggestions though.
module.exports = new Grow({
  name: 'It goes by many names...',
  version: '0.0.1', // Not grower tested, any recommendations?
  phases: {
    vegetative: {
      // Global targets durning this phase.
      // min / max set alerts
      // ideal is the target for the phase or cycle
      global: {
        ph: {
          min: 6.0,
          ideal: 6.15,
          max: 6.3,
        },
        ec: {
          min: 1400,
          ideal: 1500,
          max: 1700,
        },
        humidity: {
          min: 51,
          max: 61
        },
      },
      // You can have more cycles than just day or night.
      cycles: {
        water: {
          // Cycles have a start property which I will probably rename to schedule, because that's what it is.
          // Grow.js calls the corresponding function according to the schedule.
          start: 'every 2 hours'
        },
        day: {
          // Note: you may want to run the lights a little longer, adjust accordingly.
          start: 'after 6:00am',
          // You can also specify a targets property, these will be updated before the function runs. ; )
          targets: {
            temperature: 24,
            // Protip: C02 emitter should be timed in relation to exhaust fan so that C02 is not sucked out of room.
            co2: {
              min: 900,
              max: 1600
            }
          }
        },
        night: {
          start: 'after 9:00pm',
          targets: {
            temperature: 20,
            co2: {
              min: 400,
              max: 1000
            },
          }
        }
      }
    },

    bloom: {
      global: {
        ph: {
          min: 6.0,
          ideal: 6.15,
          max: 6.3,
        },
        ec: {
          min: 1400,
          ideal: 1500,
          max: 1700,
        },
        humidity: {
          min: 51,
          max: 59
        },
      },
      cycles: {
        day: {
          start: 'after 7:00am',
          targets: {
            temperature: 24,
          }
        },
        night: {
          start: 'after 7:00pm',
          targets: {
            temperature: 20,
            co2: 400,
          },
        }
      }
    }
  }
});
Jake Hartnell
@JakeHartnell
Updated current UI: CommonGarden/Grow-IoT#339
Also going to add instructions for running over a local network soon!
Jake Hartnell
@JakeHartnell
CommonGarden/Grow-IoT#352
CommonGarden/Grow-IoT#353
CommonGarden/Grow-IoT#354
Myles McNamara
@tripflex
hey guys, i'm trying to get a better understanding of the possibilities with grow-iot and custom hardware devices ... but can't seem to find anything online regarding tutorials for grow-iot or creating custom hardware to work with grow-iot, can anybody explain it a little bit further for me or answer some questions?
like for instance, if I had this breakout board connected to an arduino or node mcu ... how would I go about connecting it to grow-iot? https://github.com/CommonGarden/Grow-IoT/wiki/Luminosity-Lux-Light-Sensor
i already have some custom arduino code running for some temp sensors and such, and wanted to try out grow-iot by connecting it ... but can
can't seem to figure out how i would even go about that through arduino
Jake Hartnell
@JakeHartnell
The easiest way through arduino is to use something like johnny-five or firmata: http://johnny-five.io/
I'm sorry for the poor state of documentation, I'm happy to answer any questions.
The documentation there might make more sense.
Thing.js and it's cousin Grow.js (https://github.com/CommonGarden/Grow.js) have examples for connecting arduinos and more!
Let me know if you have any questions!
Jake Hartnell
@JakeHartnell
Will have examples for nodemcu soon.
Myles McNamara
@tripflex
awesome, thank you will check it out!