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] 5 6 ... 162
Installation issues / Re: Changing Parameters on Fibaro z-wave dimmer
« on: January 20, 2013, 09:48:39 pm »
yes, it is.

Installation issues / Re: Z-Wave - Aeon, HA07 and SUC/SIS
« on: January 07, 2013, 10:20:19 pm »
you should reset every device with a controller before including it again.

Users / Re: Welcome
« on: December 21, 2012, 02:40:30 pm »

Developers / Re: Elk Rs232 Protocol PDF links
« on: December 20, 2012, 08:09:27 pm »
come on.. scribd?? To download this document you must become a Premium Reader..

Installation issues / Re: Z-Wave - Aeon, HA07 and SUC/SIS
« on: December 17, 2012, 11:47:31 pm »
I don't like using the built in button in bigger networks as SIS mode makes things much easier and you get a flawless routing table.

Installation issues / Re: Z-Wave - Aeon, HA07 and SUC/SIS
« on: December 17, 2012, 12:00:28 pm »
 you should not add the devices with the aeon stick button but with an inclusion controller. I'm not sure if the HA07/09 can do this but all recently made portable controllers support inclusion controller mode. Use the "Add node" in the web admin to add the controller. You need to consult your controllers manual to identify the key press/sequence needed on the HA07/09 to get it included as inclusion controller. Then add your devices with the HA07/09.

br Hari

Users / Re: FreePbx
« on: December 10, 2012, 11:40:07 pm »
use ago control, you have to configure Asterisk yourself :-)

Users / Re: 64-bit support
« on: December 08, 2012, 12:20:34 pm »
if you want to unleash the power of 64bit, you can use ago control ( It provides 64bit packages. Not that 64bits are better than 32 for home automation, but you were asking for it :-)

Users / Re: LMCE right for me?
« on: November 24, 2012, 08:37:32 pm »
What do you mean with data storage?

ago control ( might also fit your needs.

Users / Re: LMCE & security
« on: November 24, 2012, 08:35:16 pm »
You can always put another firewall in front of LMCE. Please be aware that the system is quite open to attacks from the inside, too. The underlying communication protocol DCE has no security at all. No authentication and no encryption. If you control sensitive things like door locks, garage door openers and such via LinuxMCE, make sure that you don't have a patched CAT5 wire in your garden :-) (I'd recommend to use 802.1x anyway). Rebooting the core via a DCE command would also disable the security system for a while..

Users / Re: AW: Funding Drive: ZWave Door Locks
« on: November 19, 2012, 09:05:46 pm »
All current dongles should work

Users / Re: Funding Drive: ZWave Door Locks
« on: November 19, 2012, 10:58:29 am »
I'm working on a new Z-Wave DCE device together with Sambuca that uses the OpenZWave library. OZW was inspired by our work and got in a pretty decent shape already. The current code in LMCE is not well structured and would need a massive overhaul. It lacks too many things to support encryption. Initially it was just a proof of concept. It just worked quite well so it went into production :-)
While OZW does not yet support encryption in the main branch, there is some work done already. When the new DCE device works well with OZW, we're looking at the encryption bits.

br Hari

Users / Re: Taps talk
« on: November 11, 2012, 09:10:57 pm »
installation done, should work now (it does on my phone)

Users / Re: Welcome
« on: November 10, 2012, 08:25:45 pm »
it is just another networked device. For multimedia it will control existing players like XBMC, WD TV Live and other UPnP players and probably squeezeboxes. For TV the plan is to support the VDR remote control protocol and set top boxes running enigma (Dreambox, ..). More devices might come in the future but we have to start somewhere :-)

Users / Re: Welcome
« on: November 10, 2012, 11:04:59 am »
ago control is written from scratch, so it currently lacks a lot of the features offered by LinuxMCE. This is the major drawback right now. On the win side, there is the following from a "core" perspective:

- much easier to understand code base with modern architecture
- does not use DCE/DCERouter for messaging but the AMQP protocol via the apache qpid daemon. This provides enterprise class messaging with things like authentication, fail over (high availability), encryption, very easy integration into many languages like c++, python, Java and more. Messages use english language like 'message["command"] = "on"'. So you don't need to know that command id 192 means on like in DCE. Do you know the parameter number for set level? In ago control it is 'message["level"] = ..'
- loose coupling between components, so no central database with ugly things like sqlCVS or sql2cpp. If you restart a single component, you don't have to restart everything (like when quick reloading the DCERouter in LinuxMCE). Device schema is held in a yaml structure so user interfaces know easily what controls to provide to the user. No hard dependencies on components and easy replacement of them. No need for "plugins" that share the DCERouter memory space, everything is just another daemon. You don't have to rely on services like the "resolver", it is just helpful to map device UUID to name and such.
- very leightweight, runs on many embedded systems like the raspberry or a plug computer
- cloud features, you can log in to the ago control cloud and control your devices even when you're not at home. Without any complex VPN configuration

In my dreams this will become LinuxMCE 3.0. It has the potential. Of course there is a huge amount of work to do to get feature parity with the current LMCE 2.0. Currently there is no such thing as an orbiter, the user interface options are:

1) Web admin
2) access via cloud
3) simple android app, much work needs to be done in this area, but it allows on/off control of devices and scenarios
4) meloware iphone app

On the home automation side there is a scenario handler and an event handler. So you can make "command groups" via scenarios, and also add delay in between commands. You can respond to events like sunset, device level change or do timed events. They can be edited via the web admin. Needs some polishing but basic functionality is there. Next step will be enrichment of event criteria, like states of other devices and "global" state like day/night.

On the device support side the things are improving daily. Z-Wave support via OpenZWave (much cleaner design than the LinuxMCE driver, better support for enhanced protocol features), KNX support will be ready in a few days (via eibd, so running in parallel with lmce works fine), EnOcean is under construction, about 50% done. 1wire works fine for temp, humidity, brigthness and I/O sensors. Chromoflex USP3 is also supported. Onkyo EISCP just needs a few more lines of code to implement more than on/off.

There also exists a bridge from LinuxMCE to agocontrol. It still needs some work to automatically announce devices to LinuxMCE and support more commands than on/off/setlevel. This will allow you to run LinuxMCE and agocontrol in concert. You might ask yourself "why?" - e.g. you could use ago control for basic automation and only power on your LinuxMCE system when you need media. This will save a lot of energy when you're running ago control on a low power ARM computer.

So much for a short overview. Volunteers for coding, testing, and using? ;=)

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