Author
Topic: Zwave or Insteon (Read 7616 times)

the rzcop only helps a bit as you also have to understand the command class structure. We have some work ongoing to reverse engineer the pieces. There is a wiki page (http://wiki.linuxmce.org/index.php/ZWave_API) and a forum thread (http://forum.linuxmce.org/index.php?topic=3987.0) where we try to collect information from free sources. We also have serial sniffs from homeseer and the old linuxmce driver. The old zwave driver was available as source in the past. Thats pretty good information for basic set and get commands and device initialization.

Karl, from the link below is running it off of freebsd and has a good command of the functionality. maybe you could approach him. he is very knowledgable on the rzcop and is more than friendly. not stuck up at all. garylm has been experimenting also and i see him on multiple zwave boards trying to figure this out too.

i have most of the modules on the market if anyone needs to test a specific type. i just don't currently have a linux box but have a box laying around that might work for basic testing. i would need someone to work with me patiently as i don't know much about linux.

also, you can download the mcontrol windows software and monitor the zwave adapter for device classes as well. for instance, the DBMZ motor, which is referenced on the wiki but not defined shows up as a multilevel motor. it may be inherited from multilevel switch since it's properties are very similar. mcontrol also has a log which may assist with some info.

controlthink's thinkessentials pro has some functionality like the ztool also. also, they have a sdk for their dll. would this not help hari?

this is another longshot too but recently hawkingtech.com/homeremote just updated their firmware to regulate control via a remote website. you could just use something like ethereal to sniff the traffic back and forth to your local network to see what comes up in the payload.

i had a bad taste on this board from another user on here but am willing to take a chance with other people since i doubt everyone is as negative. hopefully, even with this user, it is just a misunderstanding. we'll see.

There is an improved ZWave driver almost ready for LMCE that should fix a lot of the issues with the current driver. It will probably be closed source etc. because of Zen-sys restrictions. The Leviton people and Controlthink have both confirmed that the serial codes for the Leviton module are different from the actual ZWave commands. (The ZWave chips take rs232 commands directly.) This means that code for the Leviton module won't necessarily work with other ZWave devices. ControlThink doesn't support the Leviton module yet.The 2-way communications between light switches and the controller is covered by a Lutron patent and they have sued Leviton (and I think Cooper) over infringement. Leviton worked out a settlement but I don't know about Cooper. I know that Intermatic and the others are legally on thin ice with active 2-way communications.

Syner- If you need assistance getting an LMCE box up I can help. PM me if you want to discuss it. I have lots of hard won experience.

There is an improved ZWave driver almost ready for LMCE that should fix a lot of the issues with the current driver. It will probably be closed source etc. because of Zen-sys restrictions.

That's all nice and such but on the long term it does not help. Hey, it's not like we are controlling mars rover landings with Z-Wave(tm). We are talking about switching lights, reading some sensor values and triggering some relays/whatever. The protocol is not even sophisticated enough to do routing stuff on its own. The user has to assign routes and whatnot. Yeah, a few devices enumerations for dimmers, pet feeders an remote controls. Look at the Insteon specs if you can't come up with a complete list. Wow, a sensor can not only send on/off but also multi values. That really qualifies for NDA.

When we now rely on closed source drivers for basic controlling of HA we could even go hack homeseer on windows. There is a SDK with a Z-Wave(tm) DLL.

I really don't understand Zensys about that. An open spec would give more implementations and allow them to sell more devices.

IMO the closed source decision is a strategic one based on financial variables. 1. there has been vc money coming in for some time now. i doubt these companies would embrace an open standard if they want a return on their investment. people tend to put more value on something that costs them. not that it is really better, just psychologically it may be. 2. they think they have something special that can be commercialized. so far they have over 100 device manufacturers onboard so they must be on to something. 3. they look at zigbee and a. want to differentiate themselves from it, b. don't want to get bogged down by seemingly neverending meetings on agreement of standards. same thing is happening with 802.111n. the technology is being marketed ahead of finalization and people become disillusioned when things don't happen sooner rather than later.

they were able to sign on most manufacturers early on so i don't think they felt the pressure to have an open spec to sell more devices.

just another rant, i have yet to find a decent physical light switch in the US. i think the rocker style on leviton is annoying. i wake up at night to use the b-room and find myself automatically hitting the top of the switch in the dark to turn it on. i wind up having to hit the switch twice to turn it on. the cooper wiring is annoying too. it is a top/bottom rocker but on the right side. in other words you have to hit the top right or bottom right corner of the switch to toggle it. also, it is a toggle switch, meaning 1 click on, next click off. so you could hit the bottom to turn on and top to turn off, bottom to turn on, bottom to turn off, etc. this could be cool for different programming options but there is no decent labelling system physically on the device to note how you programmed it so anyone who is not familiar with it will be lost. the intouch line has a somewhat european style with the finger imprint however the 15amp clicks so loud you can hear it 2 rooms away at night. finally, the homesettings and act line have a decent style however i don't like the dimmer built into the switch. i prefer the side toggle like leviton/cooper. the timing can be hard to get used to in order to dim/brighten from the switch itself. of course you can program these setttings but i still prefer the side toggle.

Insteon is probably the best you are going to get (at a cost of course). They are reliable, very fast and perform very well. They are also very well supported in LMCE. They are the most expensive, however, and I'm not crazy about their selection of devices.

ZWave is kind of a middle guy here. They are pretty fast, fairly reliable, and still pretty expensive. They have had a lot of integration issues in the past in LMCE. Their selection of devices is decent though. I havn'e messed with them much, but it appears that you need separate interfaces for their lighting vs. their climate devices (can anyone confirm this?)

X10 is also an option. Though they are slower (about 1 second latencies, sometimes a few seconds if a lot of brightening/dimming events are being sent), less reliable (though I swear that in about 4 years, I've never had a signal fail to go through. But then again, I do have my 2 phases coupled properly, which a lot of people don't do. They are dirt cheap (about $5-$7 each on ebay for switches and outlets, much cheaper if you buy a used lot). This is still my favorite as it has a nice "bang-for-your-buck" effect. I also like their selection of devices (Simple On/Off switches that work with Compact Flourescent bulbs, dimming switches, motion detectors, wall outlets, plug-in light and appliance modules, etc..). I have well over 100 x10 devices in my home - i cringe at thinking how much that could have cost with the more expensive solutions... (Though I readily admit that Insteon and Zwave are much nicer than x10 - But - I can have all of the features in my home as people that make much more money than I do)

So you do have some options.I would say that if you have the money, go with the best. If you only want to add a few switches, etc, go with the best. If you want a lot of devices and you don't have a large income to support it, i would definitely recommend the x10 - they aren't nearly as bad as some make them out to be)

Either way, you'll have fun. Home automation is addicting!

Actually, a Lamp module straight from ZWave is like 40 dollars US, and a lamp module for Insteon is 34.99 dollars US. I would say that they are both roughly the same cost. They both have an interface unit that needs to be purchased in order to operate the units. With that being said I would lean towards Insteon. It utilizes a meshed Wired and Wireless network and is inter-operatable with X10, if you wanted to use that as well.

Sorry for the major post chopping, but this is my understanding as well. IMHO, and what I plan to do, buy an Insteon controller, and buy devices that make sense. x10 for some, Insteon for others. This way you can get all the cheap bang for your buck items that you might not be willing to pay the Insteon premium for, ie x10 kitchen lights, but still be able to buy Insteon stuff for when you need the better and more reliable items such as HVAC or Security systems.