Brian H Posted April 30, 2015 Posted April 30, 2015 Just saw this while cruising around the Insteon Forums. http://www.insteon.com/insteon-hub-alljoyn http://www.smarthome.com/insteon-2243-223-hub-with-alljoyn.html
Teken Posted April 30, 2015 Posted April 30, 2015 Just saw this while cruising around the Insteon Forums. http://www.insteon.com/insteon-hub-alljoyn http://www.smarthome.com/insteon-2243-223-hub-with-alljoyn.html For more information about alljoyn: http://en.wikipedia.org/wiki/AllJoyn I am still unclear what the intent is with this being made available? Anyone . . .
paulbates Posted April 30, 2015 Posted April 30, 2015 SH/SL is committing and connecting themselves to some of the bigger players. They are opening Insteon up to two larger worlds; Homekit and now Alljoyn. They're making their tough choices and moving forward, and I give them credit for that (which I don't always do ) They are aimed at 2 different markets.. 1) Iphone users, obviously, for Homekit / simplicity. And 2), a more open source-ish, technical crowd with Alljoyn. We need to see what SH/SL's longer term intentions are for the new serial Hub/PLM. The Alljoyn and Homekit versions need a network capability and ET Jack that the new serial Hub/PLM does not currently have. There are unused pads on the main card of the serial Hub/PLM labeled "APP IPC", which (sort of) suggests something network wise could be attached there. Can both pads be used at the same time? Are there plans for a network card and ET jack in addition to serial? No way to know for sure right now. If so, would it be for Homekit or Alljoyn connectivity?? We'll have to see what plays out in the coming months.
stusviews Posted April 30, 2015 Posted April 30, 2015 http://finance.yahoo.com/news/insteon-drives-iot-innovation-microsoft-211500854.html
Teken Posted May 1, 2015 Posted May 1, 2015 That was a good read thanks for the link Stu. How does the ISY Series Controller come into this mix? Apple Home Kit appears to be a proprietary standard vs this alljoyn. Is this something UDI should support given its supposed to be a open platform for all the kids to play in the sandbox? Ideals are peaceful - History is violent
paulbates Posted May 1, 2015 Posted May 1, 2015 Teken, You're right, Alljoyn has possibilities with or without MS. It seems most attractive to me right now vs Homekit. For us with serial PLMs and Hubs, we'll have to wait and see. I don't believe the Alljoyn or Homekit Hubs will have a serial port. And the serial PLM/Hub does not have an Ethernet network connection needed for Alljoyn and Homekit. But we can think about things like Translation Gateways that will provide the connectivity to something like Alljoyn. (Maybe Homekit if Apple permits it.) Instead of using one of these new Insteon hubs, we keep our serial PLMs and use a Translation Gateway to talk to Alljoyn on one side, and UDI rest calls on the other. Its not there today, but its beyond plausible; very similar in concept to what io_guy does with his programs. Paul
Teken Posted May 1, 2015 Posted May 1, 2015 Teken, You're right, Alljoyn has possibilities with or without MS. It seems most attractive to me right now vs Homekit. For us with serial PLMs and Hubs, we'll have to wait and see. I don't believe the Alljoyn or Homekit Hubs will have a serial port. And the serial PLM/Hub does not have an Ethernet network connection needed for Alljoyn and Homekit. But we can think about things like Translation Gateways that will provide the connectivity to something like Alljoyn. (Maybe Homekit if Apple permits it.) Instead of using one of these new Insteon hubs, we keep our serial PLMs and use a Translation Gateway to talk to Alljoyn on one side, and UDI rest calls on the other. Its not there today, but its beyond plausible; very similar in concept to what io_guy does with his programs. Paul Well now 2015 appears to be a very interesting year for HA.
paulbates Posted May 1, 2015 Posted May 1, 2015 Can you think of a small, powerful, lightweight compute platform that might be well suited for a Translation Gateway... hmmm. mmm. it will come to me annnnny moment now
Michel Kohanim Posted May 1, 2015 Posted May 1, 2015 Hello everyone, Quite an interesting topic! Some background: just got a demo of 5.0 on Monday. It's fantastic! The concepts are quite simple: 1. Node servers ... devices that serve nodes, their capabilities, events, etc. to ISY. Automation Shack - if io_guy chooses to implement the interface, is a node server 2. Node clients ... ISY + Networking module is a node client 3. ISY PRO series can be both. i.e. Nodes from an ISY PRO device are immediately accessible to another node client ISY. This means that you can have programs based on any node/event and use programs or regular REST APIs to control nodes on the node server. Status is updated in real time and no polling is necessary. It's just amazing. For node servers, our current thinking is RPi with Python libraries. Now, this is where HomeKit, AllJoyn, Amazon Echo, IPSO, UBI, Threads, etc. come into play. For ISY, nodes from any of these environments are simply nodes with defined capabilities and therefore immediately accessible to programs and everything else ISY does. i.e. transaction gateway/brain is ISY and the rest are just virtual nodes. Since our next step is to enhance Z-Wave, we are running into a little bit of resource constraints. We are considering a kickstarter/indiegogo project but have not decided yet. Quite exciting times ahead of us. With kind regards,Michel With kind regards, Michel
paulbates Posted May 1, 2015 Posted May 1, 2015 Thanks Michel. Not surprised that UDI is ahead of the curve, and looking forward to the brave new world of 5.0! Paul
G W Posted May 2, 2015 Posted May 2, 2015 This is great news Michel. I'm rather excited to get started with Moses nodes as I'm currently laying the ground work for an Android app that will securely connect to the ISY and let you handle almost all functions.While I'm here I have a question. What is the most efficient way to connect and communicate with the ISY?Best regards,Gary
Michel Kohanim Posted May 3, 2015 Posted May 3, 2015 Hi Gary, The best ways to communicate with ISY: 1. Command/Control - REST 2. Variables Command/Control - REST 3. Configuration (variables, system, programs, nodes, etc.) - SOAP 4. Subscriptions - Either Web Sockets or SOAP With kind regards, Michel
G W Posted May 3, 2015 Posted May 3, 2015 Hi Gary, The best ways to communicate with ISY: 1. Command/Control - REST 2. Variables Command/Control - REST 3. Configuration (variables, system, programs, nodes, etc.) - SOAP 4. Subscriptions - Either Web Sockets or SOAP With kind regards, Michel Thank you, Michel.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.