Premise Aeon Labs Z-Stick

Motorola Premise

yackimoff

New Member
Have been searching the forum but found no answer.

Can't get my Aeon Labs Z-Stick Series 2 to work with Premise. It works perfectly with HomeSeer. I have downloaded Leviton dll, VISARF xdos, but nothing helps. DiscoverDevices fails every time.

Any tips would be appreciated.
 
The Z-Wave module was made for the Leviton RZC0P or VRC0P controller; it's an RS232 secondary zwave controller. Unlike the Aeon stick, it does not support the new security codes for locks. It's rumored that Leviton will add this to a newer version of the VRC0P, but I have no idea when or if this is true. Currently, the VRC0P supports everything else including the two way feedback of the vizia RF and RF+ lines.

I would use the Aeon stick as a primary controller via a thiird party program and consider adding the VRC0P as a secondary controller that will allow Premise to controll Z-Wave lights. Or you could always build a driver for the Aeon stick. Does the Aeon stick show up as a virtual com port?
 
I would use the Aeon stick as a primary controller via a thiird party program and consider adding the VRC0P as a secondary controller that will allow Premise to controll Z-Wave lights. Or you could always build a driver for the Aeon stick. Does the Aeon stick show up as a virtual com port?

Yes, it shows up as a COM port. But all jobs sent to it fail.

Is there any SDK for Premise drivers?
 
If I remember correctly all computer connected zwave controllers are serial based whether or not they are physically USB or rs232 type connection.
 
If the Aeon stick shows up as a COM port, I would think Premise would see it as a serial port. If this is the case you could just use builder's IDE to code a module using a vbscript derivative (much simpler than using the SDK). Here's a zwave driver written in this manner: http://www.cocoontech.com/forums/index.php...0&start=150
You could import this module and create a copy of it (in this way the GUI ID will be different, this is very important if you intend to share your work as any GUI ID conflicts will crash SYS).

If you're a programmer (I'm not), the SDK maybe just as easy for you. The SDK is attractive since it will allow your module to run in it's own thread, but this has never been an issue for me.

If I remember correctly all computer connected zwave controllers are serial based whether or not they are physically USB or rs232 type connection.
 
Back
Top