Run Grow-IoT instance on Raspberry pi

[JakeHartnell]

While it's nice to be able to connect multiple pi's to a Grow-IoT instance, it would be nicer still if Grow-IoT could be hosted on the device itself.

Currently, this isn't working though. Hopefully Meteor will support ARM architectures soon... or #365 happens. : )

pi@rpitbr3w:~/Grow-IoT $ $HOME/meteor/meteor && sudo node ../Grow.js/examples/rasp-pi/bioreactor.js 
=> Running Meteor from a checkout -- overrides project version (Meteor 1.5.1)
[[[[[ ~/Grow-IoT ]]]]]                        

=> Started proxy.                             
=> Started MongoDB.                           
=> Errors prevented startup:                  
   
   While selecting package versions:
   error: No version of meteor-base satisfies all constraints: @1.1.0, @=1.0.4
   Constraints on package "meteor-base":
   * [email protected] <- top level
   * meteor-base@=1.0.4 <- top level
   
   No version of mongo satisfies all constraints: @1.1.19, @=1.1.9_1
   Constraints on package "mongo":
   * [email protected] <- top level
   * mongo@=1.1.9_1 <- top level
   
   No version of session satisfies all constraints: @1.1.7, @=1.1.6
   Constraints on package "session":
   * [email protected] <- top level
   * session@=1.1.6 <- top level
   
   No version of tracker satisfies all constraints: @1.1.3, @=1.0.14
   Constraints on package "tracker":
   * [email protected] <- top level
   * tracker@=1.0.14 <- top level
   * [email protected] <- ground:db 2.0.0-rc.7
   * [email protected] <- react-meteor-data 0.2.6-beta.16
   * [email protected] <- ostrio:files 1.3.14
   
   No version of es5-shim satisfies all constraints: @4.6.15, @=4.5.12_1
   Constraints on package "es5-shim":
   * [email protected] <- top level
   * es5-shim@=4.5.12_1 <- top level
   
   No version of ecmascript satisfies all constraints: @0.8.1, @=0.4.6_1
   Constraints on package "ecmascript":
   * [email protected] <- top level
   * ecmascript@=0.4.6_1 <- top level
   * [email protected] <- shell-server 0.2.4
   * [email protected] <- ground:db 2.0.0-rc.7
   * [email protected] <- react-meteor-data 0.2.6-beta.16
   * [email protected] <- dynamic-import 0.1.1
   
   No version of accounts-base satisfies all constraints: @1.3.1, @=1.2.8
   Constraints on package "accounts-base":
   * [email protected] <- top level
   * accounts-base@=1.2.8 <- top level
   
   No version of accounts-password satisfies all constraints: @1.4.0, @=1.1.11
   Constraints on package "accounts-password":
   * [email protected] <- top level
   * accounts-password@=1.1.11 <- top level
   
   No version of http satisfies all constraints: @1.2.12, @=1.1.7
   Constraints on package "http":
   * [email protected] <- top level
   * http@=1.1.7 <- top level
   * [email protected] <- ostrio:cookies 2.0.1 <- ostrio:files 1.3.14
   
   No version of force-ssl satisfies all constraints: @1.0.14, @=1.0.12
   Constraints on package "force-ssl":
   * [email protected] <- top level
   * force-ssl@=1.0.12 <- top level
   
   No version of npm-bcrypt satisfies all constraints: @0.9.3, @=0.8.6_1
   Constraints on package "npm-bcrypt":
   * [email protected] <- top level
   * npm-bcrypt@=0.8.6_1 <- top level
   
   No version of check satisfies all constraints: @1.2.5, @=1.2.3
   Constraints on package "check":
   * [email protected] <- top level
   * check@=1.2.3 <- top level
   * [email protected] <- ostrio:files 1.3.14
   * [email protected] <- dynamic-import 0.1.1
   
   No version of reactive-var satisfies all constraints: @1.0.11, @=1.0.10
   Constraints on package "reactive-var":
   * [email protected] <- top level
   * reactive-var@=1.0.10 <- top level
   * [email protected] <- useful:connectivity 2.0.0
   * [email protected] <- ground:db 2.0.0-rc.7
   * [email protected] <- ostrio:files 1.3.14
   
=> Your application has errors. Waiting for file change.

[aruntk]

There is this fork for meteor on ARM devices https://github.com/4commerce-technologies-AG/meteor. But it is outdated. stuck at v1.3. Lead developer said that they'll be releasing v1.5 4commerce-technologies-AG/meteor#65

[JakeHartnell]

Lead developer said that they'll be releasing v1.5 4commerce-technologies-AG/meteor#65

Cool, we shall wait on that then.

[JakeHartnell]

#365 and #417 are relevant to this.

[dowliang]

I ran into this exact problem as well. I am wondering whether there is any alternative to this. We have a project that we would like to use grow IoT for it.

[JakeHartnell]

@dowliang, you can use Grow.js to create a device driver for Raspberry Pi. Here's an example: https://github.com/CommonGarden/Grow-Hub

More Raspberry Pi examples are located in the .examples directory: https://github.com/CommonGarden/Grow-IoT/tree/development/.examples/rasp-pi

Grow-IoT can run in the Cloud (such as AWS or Meteor Galaxy) or on a local x86 based computer. We run an instance on https://grow.commongarden.org

For development purposes you can run Grow-IoT server on your computer and connect the Raspberry pi to it. In summary:

• Use Grow.js or Thing.js for creating device drivers
• Run a Grow-IoT instance on your computer

You can create a custom UI component for your device by:

1. Make a new CustomComponent.jsx file in imports/things/ or yarn add package-name
2. Open imports/things/index.js in a text editor of your choice and import your new component. Example: import CustomComponent from './CustomComponent'
3. Lastly, add the CustomComponent to the exported components object.

Feel free to ask follow up questions.

[JakeHartnell]

@dowliang, here's a simpler example I made with better instructions for Raspberry pi setup: https://github.com/CommonGarden/BasicRaspberryPiExample

Pull requests or suggestions for improving documentation are welcome.

[dowliang]

Thanks, Jake. This is very helpful. Tony

…

On Fri, Nov 17, 2017 at 9:03 PM, Jake Hartnell ***@***.***> wrote: @dowliang <https://github.com/dowliang>, here's a simpler example I made with better instructions for Raspberry pi setup: https://github.com/ CommonGarden/BasicRaspberryPiExample Pull requests or suggestions for improving documentation are welcome. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#387 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQXuEcHbEZuiG0f36ybjTEZcisuAZogAks5s3kj2gaJpZM4O8KOO> .