jwddsinc

I wasnt able to get the plugin to discover the sonos netowork but after some playing around i was able to add nodes via custom parameters. I can see them now in my admin panel and when i click on a node it correctly displays its state such as "status" "volume" etc. I can set the volume base and treble as well as mute and unmute, however none of the other buttons are working like play pause stop previous next or party mode. Only mute and unmute work. There is no error message when i click them. Any ideas on what i am doing wrong? Thanks

There is an electricity module, I am not sure how it works but that may have the variables you are looking for. If you have a device that is always on, you could write a program that starts a timer variable ( you create a variable for secs min etc) that increments until the device turns back on. If the device doesnt turn back on automatically with the power then you will have to add a query statement to your else / then clause to try to turn it back on. As that is failing you increment your timer variable. When it finally turns back on you could get notified with the timer variable which would give you the number of seconds minutes etc. IF you lose power to the isy you could check the log to see when you stopped getting events and when it turned back on again. hope that helps,

Thats a great tip about the mms. Thanks!

This is a poor man's approach, but given the programming limitations it will suffice as a workaround. The approach is very straight forward and can be adapted to getting other information from the elk that isnt yet available though the ISY interface. This technique involves using outputs from the elk system to trigger events in the ISY. So for this example to determine which user disarmed the system try the following: Create or modify an existing rule in the elk system: WHENEVER yoursystem (Area #) ARM STATE BECOMES DISARMED AND LAST USER WAS employee (User #) THEN TURN Output # ON FOR 10 SECS, RESTART TIMER IF RUNNING Output # is whatever you want to assign to that employee I started at output 100 and used 101 for employee 1 etc. Next step is to create a notification and program in the ISY to catch the output trigger in the elk, like this: Custom Notification: Subject: hard code your employee's name here, Body: employee's name disarmed the system, status:${elk.area.1.alarmState} ${elk.area.1.armedState} ${sys.date} ${sys.time12} ____________________________________________________________________ ISY PROGRAM IF Elk Area 'your system' 'Armed State' is Disarmed And Elk Output 'Output # you used for that employee' is On Then Send Notification to 'you' content 'custom message for that employee' _____________________________________________________________________ using this approach you can capture almost any data in the elk not yet visible in the ISY though it could be a bit laborious if you have a lot of employees. If you are limited by the number of outputs available consider using more than one output to define an employee for example with only 5 outputs available you could control 2 to the 5th power or 32 employees, then just change your rules and program's to reflect the additional outputs. I also receive a text message from the isy instead of an email by using this format for the email: 310#######@txt.att.net you can check with your own service provider on their format for converting emails to text messages. Good luck

Ok so usually when you post something and no one replies there is an obvious answer and guilty as charged: The variables work fine but you have to substitute the # for the actual number. Obvious but I didnt catch that as I am new to this system. I am reposting this useful link I saw in a related topic: http://wiki.universal-devices.com/index ... _Variables

Typically you use them both in conjunction with one another. The program has conditions that will execute your scene. If you just want to use it as an on off switch then a scene is fine. A program is used when you want to automate calling the scene under certain conditions. For example if you had a party every friday night then you could use a program that would set that condition for you every friday night at a certain time. Also if you have to coordinate scenes programs are useful for that too.

I installed the elk module and i have it integrated with the isy994i. I can see alll my data under the elk tab. However when i send a custom message using any of the elk variables the variables do not display in the notification email. I have tested this with the weather module variables and they work great. It seems to be problematic only to the elk variables. I am using 4.24 beta firmware and insteon. For example I want to know what the temp of a zone is or the keypad temp ?

I currently have an ISY994i and an Elk M1. I have had the Elk for several years, but recently added the ISY to better manage the insteon appliances. While I dont have the Elk integration module, I have integrated the ISY with the Elk so that the Elk can perform on off Insteon commands through the ISY994i . I am now wondering if it is possible to create a program in the ISY994i which is triggered by the Elk alarm being activated or deactivated? Does that require the elk integration module or is there a way to do that without it?