dgage said:
Nice work! So how much do you use the Elk for automation vs CQC? Maybe you could list some of the drivers/equipment leveraged by each as I'd really be interested in that info. Thanks.
I own a CQC license, but I've actually never installed it... literally never installed CQC (including a trail). So, I'm doing everything via the Elk right now.
EDIT: I guess I could have elaborated more. Right now I've just got the XEP for remote access (via eKeypad); the XSLZW for interfacing with my Zwave network; and the XSP, which I'm currently trying to integrate with my LG TV(s).
I don't have a LOT of Zwave rules setup right now. I've got ones for our Christmas tree lights; on at sunset, and off at 9:30pm. I've got another for our son's (5mo old) nightlight; on at 7:30pm, off at ~6:00am. I use eKeypad to remotely control the main deadbolt when needed.
The issue that I found with automating the lights (at least for me) is that I don't have enough sensors to trigger events (e.g. occupancy sensors). So everything I've really done is time based. Unfortunately, we're not well scheduled from day-to-day, so there aren't many things that we need on 'timers'.
Last week I added an Elk-930 (doorbell detector). With the XSP, I'm planning to be able to know the status of my TV (on/off); if on what input (HDMI1/AV1). If the doorbell is rung and the TV is on, and on HDMI1, it will auto switch to AV1, displaying my CCTV system.
Something else that I want to add, but haven't spent the time to determine the logic and program, is to write a "Sleep" task, which checks if doors are closed, doors are locked, garage door is closed, locks deadbolts that aren't locked (but door is closed), and turns all of the lights off. The
logic isn't all that complex, but it's a LOT of checking this, and if this, do this task, else do something else. Doing it from the Elk alone is possible, but a lot of lines of code, probably many counters or phantom outputs, and I just haven't spent the time to do it.