Hey @deepakmurthy, here's an SQS data collector that @AdamMagaluk put together: https://github.com/zettajs/zetta-device-data-sqs
Hi. I am setting up a basic pc-pi-led setup, using the zetta server on the pc to toggle the led attached to pi. I'm wondering if I am configuring the app wrongly because i get an exception after the LED switches on when i make the call using led.call('turn-on') inside server.observe. backtrace traces to line 99 in virtual_device.js and it seems err isn't initialized...
@kevinswiber really apologize for the delayed response. haven't found time to properly respond to you. I have uploaded some necessary info here: http://dumptext.com/VEVU4FZA.
I think that should get rid of the error. Let me know if that works, and we'll try to get an issue filed.
@mingsheng88 There are a few larger deployments in the conception/planning phase. We use the same open source Zetta as the runtime for Apigee Link (http://apigee.com/about/products/apigee-link) in the cloud.
Thank you!
This link from Sep 2014 mentions Zetta integrating with Z-Wave devices, but I don't see any driver or documentation mentioning it anymore, was the support removed for some reason?
Hi, @suhas95. There are several ways to contribute. The most common way is through the module ecosystem. For examples, you can see the list here: http://www.zettajs.org/modules/. You can learn more about building device drivers here: https://github.com/zettajs/zetta/wiki.
For the Zetta core, there's a list of issues here: https://github.com/zettajs/zetta/issues
Let us know if you have any questions!
We'd be happy to review any Pull Requests. :)
This link from Sep 2014 mentions Zetta integrating with Z-Wave devices, but I don't see any driver or documentation mentioning it anymore, was the support removed for some reason?
@mingsheng88 I'm not sure I know of any drivers currently using Z-Wave. It would be possible to build a Zetta device driver for a Z-Wave device using something like this to handle the communication: https://github.com/jperkin/node-openzwave
@t1tcrucible I took a break from putting the tutorials together, but will be trying to setup something in the near future. Anything in particular you'd be interested in me going over?
@mdobson It would be interesting explaining the query possibilities on the interface, as how a device can be registered, unregistered, blocked,… A second part where I’m interested at, more information about coupling Zetta hubs to eachother, how to manage, and some more info about how the websocket ‘inter-communication’ works.
Hey, I just started experimenting with zettajs and try to follow the HelloWorld tutorial http://www.zettajs.org/projects/2014/10/13/Hello-World.html. In "Blink the LED from the PC" it requests to open http://browser.zettajs.io/#/overview?url=http://127.0.0.1:1337, but this cannot work due to CORS. Any recommendations what to do anyone?
@NicolasDuran The project is alive and well. It forms the core of Apigee’s IoT offering, and it has become relatively stable. (Reference: https://apigee.com/api-management/#/products?jump=slider_group_section7&sub=2)
Hey, I am unable to create the relations in my loopback project, any one can plz help.
http://stackoverflow.com/questions/41637593/unhandledpromiserejectionwarning-unhandled-promise-rejection-rejection-id-2
http://stackoverflow.com/questions/41637593/unhandledpromiserejectionwarning-unhandled-promise-rejection-rejection-id-2
Apps are just passed an instance of the runtime when they’re instantiated.
You could bootstrap additional apps from a single app instance.
zetta()
.use(runtime => {
appsEmitter.on(‘ready’, app => {
app.call(null, runtime);
});
})
.listen(process.env.PORT || 1337);
@AdamMagaluk I think you’re the new Benevolent Dictator of Zetta. Any thoughts on @gcornetta’s question?
Hi all, I've played a little with Zetta and connected our Arduino-based line camera - there's a live plot: http://lab.voxel.at/zetta/zb/#/overview?url=http:%2F%2Flab.voxel.at:3338%2F
I have two data streams, one raw data, one with detection results. I'd like to update the detection result stream only if something interesting happens, but this freezes the output. I have no clue yet where this happens - should I look in the browser code or somewhere deeper?
I have two data streams, one raw data, one with detection results. I'd like to update the detection result stream only if something interesting happens, but this freezes the output. I have no clue yet where this happens - should I look in the browser code or somewhere deeper?
@kevinswiber good question :) will try a few things and report…
The extensions per se are not too terrific, I just added a basic plot functionality to zb (https://github.com/voxel-dot-at/zetta-browser) , the device is also quite basic, reading from serial and forwarding what it gets (plus some basic computations; https://github.com/voxel-dot-at/zetta-liner if you want to peek )
The extensions per se are not too terrific, I just added a basic plot functionality to zb (https://github.com/voxel-dot-at/zetta-browser) , the device is also quite basic, reading from serial and forwarding what it gets (plus some basic computations; https://github.com/voxel-dot-at/zetta-liner if you want to peek )
But I don’t recall.
still, seems to be some garbage collector issue or so
cross-browser stuff has been fun for >15years now ;)