Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - hari

Pages: 1 [2] 3 4 ... 162
Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: May 08, 2013, 01:31:00 pm »
some progress on the ago control side. We've settled onto a MVC approach via ember js and jquery. It also supports templates and other nice things. Gumby is used for the appearance. Communication is done viai JSON-RPC. Getting the inventory (aka device list and stuff™), sending commands and receiving live status updates works fine so far. Still a lot of work to do but hey this is brand new, very hot, and will receive a lot love over the next weeks and months.

Users / Re: ZCS101 RS232 Interface Dead?
« on: April 20, 2013, 01:40:58 pm »
No you can't. It uses a binary protocol. When you don't send a valid frame, don't expect reply

Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: March 28, 2013, 09:56:03 am »
there is a simulator available, it will provide some fake devices. Ping me on IRC when you're going to have a look, I'll be more than happy to assist. Just be warned that the current resolver component was rewritten in c++ and still has some issues. There is a python one, too, which is quite stable already.

Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: March 28, 2013, 12:48:30 am »
yes, there are other methods besides "message". Regarding the inventory, that is only fetched at the first load. You'll get notifications for changes when you subscribe to them on ago control. When listening to the proper events you can keep it up to date without needing a "reload". With standard I mean this:
Adhering to it allows clients from multiple languages to talk to the service without much hassle. You can e.g. batch requests and have a defined set of result codes. Anyway..

Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: March 27, 2013, 04:51:37 pm »
it is fairly simple to do JSON-RPC via jquery, e.g. setting a dimmer level does look like this in ago control:
Code: [Select]
function setlevel(uuid, level) {
  var request = {};
  request.method = "message";
  request.params = {};
  request.params.command = "setlevel";
  request.params.uuid = uuid;
  request.params.level = level; = 1;
  request.jsonrpc = "2.0";

  $.post(url, JSON.stringify(request), myCallback, "json");

So JSON-RPC barely adds overhad/code but provides a standardised way to talk to it. And that snippet isn't much more complex than concatenating specific URI strings. Coming up with dozens of /what/ever/it/might/be RESTful URLs ain't gonna make it easier in the long run. Specific URIs to fetch e.g. a list of lights are too specialised. A simple inventory request that delivers structured data with all rooms, scenarios, devices and states provides all that data in a single request. Plus it provides the schema. So the GUI knows what kind of actions the devices support. That allows for a generic widget approach (on, off, level, …). My two cents.

br Hari

Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: March 27, 2013, 11:11:33 am »
The reason why I chose JSON-RPC is that you can talk to it from a lot of languages in a standardised way. Media is on the list. We already have a lot of drivers in that area. What lacks is the logic that glues the things together and provides the user with a media browser.

Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: March 26, 2013, 06:42:43 pm »
maybe we can join efforts with ago control and come up with an abstraction layer that hides the innards of DCE/ago control and talk the same JSON-RPC protocol. I've added JSON-RPC to ago control recently, this page describes the current protocol:

It should be straightforward to add similar methods to the DCE RPC plugin. I'd volunteer to implement this.

as possy said you should be able to detect apple devices via bonjour. That is saner than matching mac ranges..

Developers / Re: LightwaveRF Wifi Link
« on: March 12, 2013, 11:48:42 pm »
I assume at least one of these bulbs for 220V? And a interface? Or do they talk real Wifi (in a 802.11a/b/g sense)?

I had a lot of issues with vbox and z-wave stick pass-through

Users / Re: Future of (AV) device control
« on: February 22, 2013, 11:17:03 am »
Onkyo AMPs also work great. The new network receivers TX-NR 414, 515, and 616 all support full remote control.

Regarding price.. if you want home automation you can't just buy the cheapest parts from best buy. Do your homework.

Users / Re: Future of (AV) device control
« on: February 19, 2013, 07:34:31 pm »
you can use a raspberry pi and write a DCE wrapper for libcec. That would be the first standalone DCE device built for LMCE :-)

Users / Re: 1-Wire Temperature Sensors
« on: February 16, 2013, 11:58:32 pm »
the OneWire DCE device uses the OWFS client API. If you can see the devices in OWFS, they will appear in LinuxMCE.

Installation issues / Re: Fibaro Dimmer Module - FGD-211 - Dianemo
« on: February 15, 2013, 10:43:35 pm »
meet me on irc.

Users / Re: Completely Portable Wireless System(PXE, etc)
« on: February 15, 2013, 10:42:38 pm »
hey what do you expect :-) You're talking about limited device support because your two gadget proposals for brand new stuff are not implemented yet? Heck you were pointed to existing stuff that works well. Z-Wave is mature and there are a lot of other options like KNX and others. Home automation does not stop right after the bulb. You got a lot of valuable information in this thread. Still you tell us everything was insulting?

Stop trolling :-)

Pages: 1 [2] 3 4 ... 162