dano

Hello Michel, It's been a while since anyone has followed-up on this topic. Is there any current or near term solutions as it pertains to: ISY994 Z Series (zigbee) communication with zigbee Kwikset locks. Two ISY994 (one zigbee and one z-wave) bridged using version 5 firmware. This would involve changing the zigbee module on the kwickset to a z-wave module and using the second bridged ISY for communication. As Teken stated, this would be a expansive solution over supporting Zigbee locks. However, this would provide two widely used standards to expand one network system for future growth. Best regards, Dan

Good afternoon Michel, Any word on this subject?

Good evening Michel, I'm very interested in seeing if Kwikset zigbee interface is even possible. Have you heard back regarding obtaining their API? With great anticipation, Dano

Chris with UD also provided the folllowing suggestion that sounds like it would be a solution: "It may be possible to control the lock by having ISY set an Elk output (e.g. 1 - Unlock, 2 - Lock, 3 - Query) and then having Elk rules send the appropriate text message. To set the status for ISY, another Elk rule could read the text messages from Z-Wave and set a different Elk output indicating whether the door is locked or unlocked." I also found out that Kwikset makes a Smartkey signature series deadbolts with either z-wave or zigbee. Michel informed me the support for zigbee locks is not available at this time but UD could add it to the ISY if there's enough demand.

Teken, Not sure you understand completely. I'm communicating to the Elk using the ISY Elk module which uses standard network TCP/IP communication. The Elk itself has an add-on board call the z-wave serial expander. The Elk would be controlling the z-wave door locks directly through this z-wave serial expander. The method it uses to conduct two-way communication with the door locks is via simple text commands. These simple text strings is how the z-wave locks communicate. I need to know if the ISY's Elk Module has the current capability to send and receive those text commands. The path looks like this: ISY w/ Elk Module --------> Elk M1--------> Elk z-wave serial expander ----------> Kwikset z-wave door lock The reverse path would occur for door lock status. It should be possible as long as the ISY Elk Module has the ability to select the "port" on the Elk which the text string is sent to or received from.

If that's the case, I could use add the z-wave serial expander for my Elk M1. Since the door locks in the Elk are controlled via text commands through the z-wave serial expander serial port, does the ISY Elk Module have the ability to send text strings to a designated port (i.e. the serial expander port)? I know the ISY Elk module can send text (custom message) to the keypad port but wasn't sure if you can designate the port for the text message.

Good morning Michel, I'm trying to add door locks to my ISY994i Z/IR PRO. I'm currently using the zigbee radio feature for both energy management and thermostat control. I assume the ISY can only be zigbee OR z-wave (not both). What are my options to add door locks to my system?

Hi Michel, understand. Is there current (or planned) method to import/export the Variables?

What exactly does "program import/export" provide in a stored file? How does it handle things when the program references a variable or device that hasn't been entered or configured in the ISY? This might be the way to go to save key entry time. Is there any way to import/export all the variables? Programs and Variable appear to be the two areas that would take time to manually type for each ISY system.

I understand your point. Since I spent a good amount of time creating the master program, It still should save me a lot of time using this process on the initial setup of the second and third system. Once these are relinked/reconfigured, I could then make a system specific backup of each system. I would think this would be much faster than manually typing all the programming and variables. Do you agreed? Can you also answer my initial question regarding the extent of data saved in the backup process?

Can you provide what type of data is handled in the backup/restore process? (i.e. program, variables, config, notifications, all module settings, etc.). My situation is the following: I have more than one location that I'm installing the ISY systems (two homes and a condo). I have been working on a "master" configuration for the ISY that includes all programs that will be needed from any of the three locations. My intent was to create this master program that can be backed up and restored to each of the ISY, relink the same devices with new addresses, disable any programs or devices that won't be needed and make any other minor changes. I'm hoping this can be accomplished in an easy manner in an effort to maintain one master backup (archive) with all features and functions. I would make any necessary program changes to the master and only need to maintain this one backup for all systems. Can you confirm the necessary steps that would be required for this approach when restoring a system using a "master" backup?

I understand the ISY network module is only capable of invoking commands via HTTP. Is it possible to have the ISY (via network module) send a command to a FTP sight (like www.drivehq) for it to start a download (send) a specific file to a UPnP storage device on my local LAN? The ISY would not be storing any files, just initiating the commands to transfer the file from a cloud location to a local storage location. Or is there any other method to accomplish this?