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 ... 163
16
Developers / Re: linuxmce.org re-design
« on: May 16, 2013, 09:31:33 pm »
very cool! Keep up the good work!!

17
there is no issue with making money through LinuxMCE per se. There were just a few cases in the past were people sold their customers solutions, could not support them because of lacking skill, and left the burden of fixing the mess to the community. So profit itself does not lead to uneasiness, but if you want to run a business, you need to make sure to be a "good citizen" in the LMCE ecosystem. The first task is to learn the system in and out, so that you know what you can promise to your customers.

19
Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: May 08, 2013, 09:59:09 pm »
maybe you can provide a more detailed bug report, e.g. what exactly you're doing. Are there any messages in syslog? Adding devices to rooms works fine (we've no other reports that indicate otherwise). But for the records, this is the old web admin written in cherrypy. The new interface is served via agorpc on port 8008. Just make sure to install the latest package.

20
Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: May 08, 2013, 06:44:21 pm »
afaict yes

21
Users / Re: Z-wave plugin module - security light issue
« on: May 08, 2013, 01:36:34 pm »
I have a motion security light which plugs in to a standard wall socket, to which I have now added a z-wave plugin module.

However the light doesn't turn off! Is LMCE and/or the Z-wave controller doing something to the plug-in module that prevents the light from turning off?

Cheers,
Matt.
what plugin module is that?

Did you check the logs for any errors?

22
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.

23
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

24
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.

25
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: http://www.jsonrpc.org/specification
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..

26
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;
  request.id = 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

27
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.

28
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: http://wiki.agocontrol.com/index.php/RPC

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

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

30
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)?

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