Recent Posts

Pages: 1 ... 7 8 [9] 10
Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by golgoj4 on October 27, 2016, 06:55:22 pm »
High Level observations after working with google, smartthings

*Does every lmce box now support https connections?
*We cannot do this for only one service. We must develop a linuxmce web api. period! The upside is all these cloud connected services can utilize this one api, so we only have to do it the one time. Until they invent the next thing besides json...

My showstopper: user credentials. If you think about it for a second, we would basically be storing very sensitive account information for multiple services for a multi-tude of people. That makes users a very juicy target, plus we need to respect privacy between users. Im sure people know how to do this, I dont have much experience there but im confident as a group we could figure it out. kids shouldn't be able to sneak into the parents google account via linuxmce db diving, etc.

Ive settled on using cakephp in addition to webadmin. I know most people would think that this is something that would be rolled into the webadmin, but frankly the webadmin is big, ugly and it doesn't make sense from my standpoint to tack on a massive feature like this. cakephp would be able to  integrate into our existing database with some work but it provides a nice clean framework to provide a gui frontend if we choose, but a json api next to it from the same codebase.

I should also add that a c++ adapter would be in the mix purely for passing event into the linuxmce system (unless something better already exists) for sending events / anything else not directly connected to web api.

Kudos to you guys for also attacking this!

Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by phenigma on October 27, 2016, 02:23:02 pm »
Golgo has already made a lot of additions to enable the secure login/connection.  Likely an addition needs to be made for the Amazon login/authentication vs. google/etc.

There was a JSON device created, it's quite limited iirc.  As for an lmce interface, my opinion is that it should be a proper plug-in to the dcerouter so that the interface has access to lmce information and data.  This will require a c++ plug-in to be written.  My opinion is that it would be counter productive to move forward any other way, except for initial testing.  Others may have different opinions.

How do we access the skill you have created?  i.e. is it available for use/testing?

Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by garagevibes on October 27, 2016, 11:19:48 am »
Im still playing around with this, from a lot of reading up on the amazon developer site i think I've now created a basic skill that I can enable and send and receive requests from but the responses are NULL as I haven't actually done any linking to linuxmce yet thats the next step.

Did i see once on this forum that someone had created a JSON dcedevice before? I don't seem to be able to find it or any documentation on the api for it, just thought it might be an easy way to plug in.

Otherwise ill probably need to create my own scripts, but unfortunately my only coding skills are in php, javascript and html so id probably write an interface in php using a connection to the mysql db to get the details of controllable devices and there device ids etc and then use the same script to fire off exec commands to send the required dcemessages as they are received from amazon.

Obviously i need to add in a secure connection between the core and the amazon web service as well.

Does this seem the right approach or at last a workable approach?
Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by phenigma on October 24, 2016, 04:40:09 pm »
I currently have Alexa running on an RPi and I am also interested in connecting with LMCE.  Any existing info people have would be great to share here.  I'm still trying to figure out how we would interface with it.  As far as I can tell once we have a secure authentication that happens automatically I think we simply need to create a 'skill' for Alexa to interface to LMCE, and then an associated LMCE device/plugin to handle interaction.

Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by garagevibes on October 24, 2016, 10:58:58 am »
Hey sorry for the delay had a few family issues, my echo arrived yesterday though so really keen to have a go at setting this up, my skill set is in web design really so I'm sure i could help at least with the http interface and designing of the api. my main struggle would probably be with the actual connecting up to the dcerouter, how to announce available devices ect.

You mentioned you found some nice code from google that would handle this don't suppose you could send a link  and ill see if I can get this intergraded as a starting point maybe?

Users / Re: autotagger
« Last post by golgoj4 on October 24, 2016, 01:17:19 am »
Did you mark the files as TV shows (as a subtype)

thanks for point this out.
Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by golgoj4 on October 14, 2016, 11:19:21 pm »
Hi all,

The amazon echo has final made it way to the UK and I'm excited to get my hands on one, just wondering if anyone had looked in to adding a Linuxmce skill to control basic home automation like lights and heating ect, it seems like someone has created a skill for our slightly common sister vera but it annoyingly connects via there in house web interface so even though the code has familiar terminology like Device Ids ect it just wont simply port over.

the amazon alexa system looks simple enough at creating a skill using node.js the issue i have is just trying to think of the best way of implementing a secure external api type interface so that the external amazon alexa voice service can send and receive commands to our internal DCErouter.

Just thought id put it out there and see if anyone had looked into this or had any ideas of the best way of implementing a solution.


Whats your development skillset?
I was looking into creating some interfaces for this, but it needs to be a 2 part system.
  • Simple http interface for doing the initial security handshake. google has some nice code for doing this, i did it successfully in my tests. It would need to be handled per cloud service: Alexa, Smartthings, google, iftt, etc
  • A proper http api exposing proper endpoints for these things to communicate.

i have been working on work and an xbmc device so ive been busy. but if you are serious, we can attack this problem and get something basic like light control going.

I'm aware of that but the rumors agree already flying of potential consumer devices built the same.  Time will tell.  ;)

Sent from my Nexus 5 using Tapatalk

Feature requests & roadmap / Re: New displays coming with RPi Compute Module 3 built in.
« Last post by posde on October 14, 2016, 09:42:43 pm »

I saw that today as well. Those are public displays. Build to last. Priced to be out-of-range ;)
Feature requests & roadmap / Re: Alexa and amazon echo skill
« Last post by posde on October 14, 2016, 09:41:41 pm »
golgoj4 has been looking into it. Maybe he can chime in.
Pages: 1 ... 7 8 [9] 10