Live data from Hacker News

Jarvis: an Amazon Echo clone in your browser

iceddev.com

11–20 of 79 posts

Re: Jarvis: an Amazon Echo clone in your browser

#11
post #3

Yeah it's a clone of the trivial parts of the Echo, but not the difficult parts that are necessary to make it great, specifically: * Beamforming microphone array (this is a real clone: http://www.xmos.com/products/microphones ) * Wake-word / hot-word detection ("Ok Google", "Alexa", etc.) * Intent recognition / NLU

Even if true, not sure why you wrote such a snarky comment. This obviously is a side project of the author and just serves as an inspiration, it's not like he is asking money for it or anything.

Re: Jarvis: an Amazon Echo clone in your browser

#12
post #6

I'm curious, anybody know if there's a simple way to wire this up to Home Assistant ( https://home-assistant.io )? My first thought was MQTT, but for some reason PageNodes doesn't have any MQTT output support, which is kind of odd for something claiming to be an IoT connectivity platform.

You could use Octoblu Meshblu node in PageNode to connect Jarvis to an MQTT platform.

Octoblu confuses me. I can't find anything about their pricing scheme (if any), while all their professional partners listed make me think there definitely has to be one hidden in there somewhere.

Re: Jarvis: an Amazon Echo clone in your browser

#13
Unfortunately, I think my first chatbot that I wrote about a year ago, and named Jarvis (based on Hubot by Github) will be cloned by a million of these projects...

I admit, it's not the most creative name; I just thought it would be cool a year ago to feel like Iron Man as I asked Jarvis to deploy my application to production...

Re: Jarvis: an Amazon Echo clone in your browser

#14
post #9
post #8

Earlier quoted context omitted.

Pure MQTT is done over TCP which browsers don't support without an extension. I'm trying to keep this purely web based as long as I can :) Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.

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?

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

#15
post #7

Hey, it's monteslu! If you are unaware, OP runs the best coworking meetup(s) in Phoenix. If you're a Phoenix dev and not coming to coffee and code, then you're missing out! Louis/Alyson (since Jarvis was her project, I think): welcome to the #1 on HN club ;-) /me snark

I have to agree, it's nice that Phoenix has a pretty active node community... though it feels like everyone is too busy working to hit a lot of the meetings... I'd love to catch a coffee and code meetup, but I work too far away, and am in the office for morning standups etc, around that time.

Just the same, always get ideas from the Phoenix/AZ node user group meetings... it's also nice to see when someone demos an idea you had... such as routing redux at the server via websockets.

Re: Jarvis: an Amazon Echo clone in your browser

#16
post #12

Earlier quoted context omitted.

You could use Octoblu Meshblu node in PageNode to connect Jarvis to an MQTT platform.

Octoblu confuses me. I can't find anything about their pricing scheme (if any), while all their professional partners listed make me think there definitely has to be one hidden in there somewhere.

I don't believe there is any pricing scheme at all as of yet. It's a great opportunity really, check it out!

Re: Jarvis: an Amazon Echo clone in your browser

#17
post #7

Hey, it's monteslu! If you are unaware, OP runs the best coworking meetup(s) in Phoenix. If you're a Phoenix dev and not coming to coffee and code, then you're missing out! Louis/Alyson (since Jarvis was her project, I think): welcome to the #1 on HN club ;-) /me snark

I have to agree, it's nice that Phoenix has a pretty active node community... though it feels like everyone is too busy working to hit a lot of the meetings... I'd love to catch a coffee and code meetup, but I work too far away, and am in the office for morning standups etc, around that time. Just the same, always get ideas from the Phoenix/AZ node user group meetings... it's also nice to see when someone demos an id…

You should try and make it out at least once. I loved it when I used to live there and definitely regret not going more since moving.

Re: Jarvis: an Amazon Echo clone in your browser

#18
post #8
post #6

I'm curious, anybody know if there's a simple way to wire this up to Home Assistant ( https://home-assistant.io )? My first thought was MQTT, but for some reason PageNodes doesn't have any MQTT output support, which is kind of odd for something claiming to be an IoT connectivity platform.

Pure MQTT is done over TCP which browsers don't support without an extension. I'm trying to keep this purely web based as long as I can :) Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.

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

#19
post #18
post #8

Earlier quoted context omitted.

Pure MQTT is done over TCP which browsers don't support without an extension. I'm trying to keep this purely web based as long as I can :) Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.

Am I interpreting it right that Pagenodes basically aims to be node-red, but in the browser?

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

#20
post #18
post #8

Earlier quoted context omitted.

Pure MQTT is done over TCP which browsers don't support without an extension. I'm trying to keep this purely web based as long as I can :) Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.

Am I interpreting it right that Pagenodes basically aims to be node-red, but in the browser?

[deleted]
Post reply on HN