I recently purchased a Planet HAC-1000 Z-Wave Home Automation Control Gateway (link).  Rationale here was that I wanted something with great range and that I could mount with more flexibility / coverage as I have a large footprint I'm trying to cover in my home.
This device connects via Ethernet vs. Serial so AFAIK, there isn't a logical driver in CQC that I can leverage.  Any thoughts on how I can integrate this?
Currently you'd have to use the VRC0P. But that's not a problem really. Both of them can be in use. On the footprint, keep in mind that Z-Wave is a mesh network. So as long as you have some reasonable density of wall powered units (which can act as relays), you shouldn't have an issue.
Ok.  I'll look into that this weekend.  The issue I saw with the existing ZWave drivers in CQC was that they all expected the connection to the gateway to be via Serial.  Am I missing something?
Also... I requested the API documentation from the vendor.  I'm attaching it here if anyone is interested.  It actually looks pretty complete.
Actually, I'm not sure if that device acts as a primary controller. So he might still need a primary. Maybe it does. It wasn't obvious from reading that. It looked like more of a small Z-Wave touch screen client widget of some sort perhaps.
(05-11-2017, 09:59 AM)Dean Roddey Wrote: Actually, I'm not sure if that device acts as a primary controller. So he might still need a primary. Maybe it does. It wasn't obvious from reading that. It looked like more of a small Z-Wave touch screen client widget of some sort perhaps.
^^^ Dean is correct.  I was actually on the hunt for a lightweight, powerful Z-Wave gateway with great range and an open API.  I don't want any of the fluff, just a great transport that I can fully control at the API level.
The way I see this is that I would administer the HAC-1000 via TCP-IP over my home network using a driver that spoke to this device via the API.  I would use the HTTP interface on the device (which is actually pretty good) to add and administer my Z-Wave devices.
Is it actually a Z-Wave primary controller? If not, you'll still need a separate primary. So if your goals were to use it as a Z-Wave interface and primary controller, you'd probably be wasting money on both fronts since you'd still need another primary and CQC requires the VRC0P.
If it acts as a primary controller, then it would still be useful to you for that purpose and whatever other features it provides. But CQC couldn't work through it, it would still require the VRC0P.
Any driver for something like Z-Wave is a huge effort and would only be justifiable if a lot of people were using the device already. We've already written three Z-Wave drivers over time now, and probably have put more cumulative time into those than into supporting any other ten devices/systems, which is really sad given that it's one of the worst systems out there.
Thanks for all the advice everyone.  I'm going to buckle in and purchase a VRC0P.  Will report back in a few weeks when I have this all up and running.
