Re:Jarvis: an Amazon Echo clone in your browser
by zyxley on Thursday April 21, 2016 @01:14PM
(#11543726)
HA does have a REST API, but with the way PageNodes works you'd have to hardcode the HA password right into the PN workflow. Have you considered adding the equivalent of environment variables, which can be set in a PN account and used as placeholders in workflows?
Re:Jarvis: an Amazon Echo clone in your browser
by monteslu on Thursday April 21, 2016 @01:40PM
(#11543916)
That's a good question. Our storage is in local indexeddb. And the site is https, so no one should see your flow if you don't share it.
That said there's nothing stopping you from reaching out to another secure service or plugin before making requests.
Re:Jarvis: an Amazon Echo clone in your browser
by detaro on Thursday April 21, 2016 @01:49PM
(#11544001)
Am I interpreting it right that Pagenodes basically aims to be node-red, but in the browser?
Re:Jarvis: an Amazon Echo clone in your browser
by monteslu on Thursday April 21, 2016 @01:52PM
(#11544026)
The goals are similar.
PageNodes does its best to leverage newer browser capabilites. WebRTC, WebUSB, SeviceWorker, offline support, etc.
Re:Jarvis: an Amazon Echo clone in your browser
by detaro on Thursday April 21, 2016 @02:41PM
(#11544397)
Ok, so less "prototype in the browser, then offload to a server once it works", but more for local "app" type things? Interesting idea, has some limitations but also opens up tons of interactions that are harder for a server-based solution (webcam, ...)
Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.