while looking for a Z-Wave - solution I found out, that Merten offers a product-line called "Connect" for 220V/50Hz(http://www.voltus.de/schalterprogramme/merten/funksystem-connect/)Since this is quite expensive, I started looking for a cheaper system. I found the FS20 - Protokoll, that is allready supported by linux (http://fhz4linux.info/tiki-index.php)There is tons of Hardware available for the FS20 - Protokoll (way more than for the PLCBUS). I would like to have a device-template for FS20 in the next linuxmce-release.

you are totally right! I honestly believe that you are doing a great job, and I thank you for that.But I think that you are not the only one with interest in developing better solutions for lmce.When I look at the "local dealers and custom installers" - list for LinuxMCE on the FIIRE-Website (for example), I allready see companies in many european countries. The solution I suggested (FS20) is allready available in many european countries.Now I am looking for a sponsor to get some cash for that work.

There is tons of Hardware available for the FS20 - Protokoll (way more than for the PLCBUS). I would like to have a device-template for FS20 in the next linuxmce-release.

FS20 is not very reliable and has no status feedback. Friend of mine has a big installation and really does not like it. What does hold you back from adding a device-template? There is even a daemon available that takes telnet commands.

I have contact with a home automation manufacturer in China. Their product is using PLC Technology. What information needed in order to develop an interface compatible with LMCE? Perhaps the Source code for their IR remote controller will help?Please reply, and I will get as much information from this manufacturer.

I have contact with a home automation manufacturer in China. Their product is using PLC Technology. What information needed in order to develop an interface compatible with LMCE? Perhaps the Source code for their IR remote controller will help?Please reply, and I will get as much information from this manufacturer.

If you're referring to PLCBUS, an interface is already in the works.

Logged

The only intuitive interface is the nipple. After that it's all learned.My other computer is your windows box. I'm out of my mind. Back in 5 minutes.Q: What's Red and smells like blue paint?

while looking for a Z-Wave - solution I found out, that Merten offers a product-line called "Connect" for 220V/50Hz(http://www.voltus.de/schalterprogramme/merten/funksystem-connect/)Since this is quite expensive, I started looking for a cheaper system. I found the FS20 - Protokoll, that is allready supported by linux (http://fhz4linux.info/tiki-index.php)There is tons of Hardware available for the FS20 - Protokoll (way more than for the PLCBUS). I would like to have a device-template for FS20 in the next linuxmce-release.

regards Heiermann

Well FS20 is not that well thought of in my experience. But you could give it a try I guess ;-)

However Dan and Hari and others here are working very hard on Insteon (which appears to at last coming to Europe) and on PLCbus. Then of course there is z-wave... that works now with some limitations. Your right about Merten's Connect product line it is z-wave based.

If you look at the activity here on this topic then you will see that Insteon/PLCbus/X10 & Z-wave are peoples focus at the moment... I would start with one of those unless you want to develop the code yourself in which case great!

Hey Dan if you can re-use your Insteon code as a template that wold be great. PLCBUS would pull in a lot of interest outside N. America. Maybe you can code it such that the Insteon & PLCBUS drivers share some common code libaries with all the protocol dependent stuff (ie Insteon & PLCBUS) pulled out into two separate libraries. That way maintaining/supporting/updating the code for both would be easier... just an idea of course! ;-)

Totallymaxed,

I'm in the final stages of a new and improved Obect Oriented design.This new code should give these advantages:

1. Takes care of the threading issue. Handles queuing of all commands and responses.2. Allows a simple 'cut&paste' method for most home automation protocols.3. Each protocol will be implemented as a class. This makes maintaining code MUCH easier.

I'm debugging as I'm writing this..

Of course, I will wiki my results, and instructions on how to create the protocolObnject class.

Regards,

Dan

Logged

The only intuitive interface is the nipple. After that it's all learned.My other computer is your windows box. I'm out of my mind. Back in 5 minutes.Q: What's Red and smells like blue paint?

I'm in the final stages of a new and improved Obect Oriented design.This new code should give these advantages:

1. Takes care of the threading issue. Handles queuing of all commands and responses.2. Allows a simple 'cut&paste' method for most home automation protocols.3. Each protocol will be implemented as a class. This makes maintaining code MUCH easier.

I'm debugging as I'm writing this..

Of course, I will wiki my results, and instructions on how to create the protocolObnject class.

Regards,

Dan

Hi Dan,

I might go the PLCBus route, and if so, I'll make a decision within the next few days. If there's anthing I can do to help, let me know.