kevkmartin

Thanks for the file. I downloaded it ans was able to successfully run it with the same result. Now I just need to hook up the AD2USB to the NSLU2 and see what I can do with it.

Any chance you can send me the resulting executable?

MrD's excellent tutorials over in the network resources section on using the NSLU2 device in parallel with an ISY-99 to greatly expand / improve its functionality have inspired me. If you haven't read his articles - even if you don't have an NSLU2... you should. They are very informative; much of the info can be extended to apply to any type of server - making it a valuable resource to your ISY-99. After getting an NSLU2 set up and configured with the ISY-99 to do voice announcements, I was driven to action to finally identify and implement a (relatively) cost effective method to transmit and play wireless audio from alarm / home automation systems. I did a lot of on-line research, and never really stumbled across an off the shelf solution. I think what I've come up with it a definite step in the right direction - using off the shelf products; I would appreciate feedback on improvements or alternative products. Equipment: The core of the system is the Rocketfish RF-RBUSB wireless transmitter /receiver http://www.rocketfishproducts.com/products/home-theater/RF-RBUSB.html: This little guy is BOTH a wireless transmitter and receiver (full duplex); up to 8 of these can be linked together to share the same audio. Each one retails for about $65. I also purchased a set of Logitech Speakers Z130. These are pretty standard powered PC speakers; any powered speaker will do. I like these because the pair of speakers can be separated, allowing use of ONLY the single powered speaker. These are ~$17 each. In addition to the transmitter / receiver, and the speaker, I used an Insteon Outlet Linc Relay at each location. This allows me to independently turn on and off specific speaker / transmitter combinations to target WHERE in the house a specific announcement should be made. This part is definitely optional, and may be over-kill for the typical installation. The outlet lincs are $46 from smarthome.com Set-Up: At the location of the audio source (in my network closet, next to the NSLU2, in my case) attach the sound output to the input of as RF-RBUSB. If desired, a powered speaker can also be connected to this unit's output jack - if constant audio output is desired at this location. This RF-RBUSB can NOT be switched, as it will be the "hub" device to which all others are paired. At each additional location, install an additional RF-RBUSB, and attach a powered speaker to its output jack. All of the RF-RBUSBs must be paired to each other. With just this set-up, and at a cost of ~$150, you can have audio in two locations without running wires all over the house. Additional locations can be added for ~$80 per location (1 RF-RBUSB + 1 powered speaker). The system can support up to 8 linked devices. Optional, but COOL Insteon Integration: So now, let's get fancy!!! Assuming that you install multiple wireless locations (zones) throughout your house - independent control may be desired. By installing an Insteon OutletLinc Relay at each location, you can select any combination of audio output locations for any announcement on the fly using ISY-99 programs. Simply plug the RF-RBUSB into the constant power of the Outletlinc, and the Powered speaker into the Insteon switched outlet. With that step done, you can use ISY-99 programs to first turn on the specific speakers you want to announce to, and then broadcast the desired audio. The sky's the limit here! End Vision: With proof of concept now completed, I want to install this as a "polished" product. I plan to identify a location in each room to install a small in-wall box. Inside the box, I will install the Outletlinc, and place the RF-RBUSB and Powered speaker. I will cover each box with a removable speaker grill (painted to match the wall). Using an automatic input selector, both my alarm audio output, and the soundcard output could be connected to the "hub" device (with the alarm prioritized), allowing the alarm system and the home automation system to share a network of speakers. What suggestions / comments do you guys have?

I loaded that package, but I still get command nit found errors for gcc and cc. Did you have to make any path changes?

Thanks. The compilers is what I need help figuring out. Once I get it running, I'll write up a how to for others.

I am trying to get my Ademco Vista 20 panel successfully communicating with my ISY-99. Based on research, it seems the best way to do that is to use an AD2USB device, connected to a hacked NSLU2 to create a "Network Device" that can communicate directly with the Ademco Panel. So far, I have acquired an AD2USB, downloaded the ser2sock.c software, and hacked (uNSULng) the NSLU2. I am having a great deal of difficulty on how to proceed. I believe the next step is to cross-compile ser2sock.c on the NSLU2. Has anyone successfully done this? All help appreciated!

Hoopty... Great that we can build on each others stuff!!! I just implemented your cumulative time code today. I went ahead and set up a monthly reset program that runs at 12:00:01 on the first day of each month and resets the monthly counts.

Look into a Global Cache iTach IP2IR device (or WiFi2IR) It sits on your network, and will transmit IR signals in response to IP commands. You can use the NETWORK RESOURCES in the ISY to send the IP commands. It takes a bit of work to set up, but it works well.

Would you mind posting up the final code once its confirmed to be working. As I have the same needs and requirements as well. Teken . . . Sure. Here's what I ended up with: Define variables (non-state): $Cool_Cycles_Today $Heat_Cycles_Today Define Custom Notification: Climate_Status Programs: Update_Cool_Cycle_Count If Status 'Thermostat / 14.67.A7 - Main' is Calling for Cool Then $Cool_Cycles_Today +=1 $Cool_Cycles_Today Init To $Cool_Cycles_Today Else No Actions Update_Heat_Cycle_Count If Status 'Thermostat / 14.67.A7 - Main' is Calling For Heat Then $Heat_Cycles_Today +=1 $Heat_Cycles_Today Init To $Heat_Cycles_Today Else No Actions Send_Climate_Status_And_Reset_Variables If Time is 11:59:30PM Then Set 'Thermostat / 14.67.A7 - Main' Query Send Notification to 'kevkmartin e-mails' content 'Climate Status' $Heat_Cycles_Today = 0 $Heat_Cycles_Today Init To 0 $Cool_Cycles_Today = 0 $Cool_Cycles_Today Init To 0 Else No Actions Let me know if you need anything else (or figure out how to get the current set-points and fan condition).

Solved it (at least one part)!!! This certainly wasn't obvious to me, so I hope it helps others. Instead of using the control or status of the Heat or Cool nodes, I noticed that there was an option in the program pull down for the MAIN thermostat node called "Calling For Heat" and "Calling For Cool". When I changed my if statements to look at THOSE... worked like a champ!!! Now... can anyone help figure out how to get the current set points (and possibly even the fan status) into variables so that the can be included in my report?

So... How do I accomplish my objective of counting how many times in a day the heat comes on? The t-stay is running in "auto" mode with a heat and cool set point. I rarely do anything to it "manually".

I can actually look at the variables in the console and see that they are not updating. I can also see that neither program has ever evaluated to TRUE.

Yes. In the program that sends the daily notification, I reset both counts to 0 and to init to 0.

I finally got my Insteon / Venstar 2491Tup and running. It works well in the admin panel, properly reporting and updating. My next project wit it was going to be setting up a simple daily "Climate Control" e-mail notification. I set up a custom notification. The goal was to include the current Heat and Cool Setpoints, as well as the number of cycles of heating / cooling called for that day. I set up two (non-state) variables Heat_Cycles_Today, and Cool_Cycles_Today. I also wrote two simple programs: Update_Cool_Cycle_Count If Status 'Thermostat / 14.67.A7 - Cool Control' is On Then $Cool_Cycles_Today +=1 $Cool_Cycles_Today Init To $Cool_Cycles_Today Else No Actions Update_Heat_Cycle_Count If Status 'Thermostat / 14.67.A7 - Heat Control' is On Then $Heat_Cycles_Today +=1 $Heat_Cycles_Today Init To $Heat_Cycles_Today Else No Actions At midnight, I received my first status e-mail; it reported NO Heat or Cool Cycles. I know the heat came on that day. My first thought was that I needed to query the thermostat to pick up the Heat Status, so I wrote a program (and ran it) that queried the Thermostat once a minute. At midnight, I received my second status e-mail; it still reported NO Heat or Cool Cycles. I* have also found NO way (programmaticly) to retrieve the current heat / cool set points. Any help?

The opener itself is plugged in to the switchlinc controlled outlet. The switchlinc is right beside he mahal operate switch. One must first turn on the switchlinc before using th manual switch.

andyf0, You're fantastic and I thank you for the follow up and testing. I would have done this test straight away but it is currently -36'C in my garage right now so fumbling around with little frozen wires 10 feet in the air wasn't going to be fun. If the results proved unproductive or helpful . . . Much thanks again Sir! Teken . . . I know I've mentioned this in another thread before... But since it's applicable here, I'll repeat. I have the outlet that my garage door opener is plugged in to powered through a switchlinc relay. That adds an extra layer of protection to open / close commands of the garage door. This would have prevented what happened to you, because all off would have left the garage door power OFF preventing the open - regardless of the command to open via "off". I set up programs that execute when I want to open and close the doors. The programs first turn on power to the GDO, wait one second, then perform the open / close, confirm that the expected action completed (via sensor status), then turn OFF power to the GDO again. It works great, and prevents accidental GDO commands very well.

One additional thing I did for security, was to put the outlet powering the GDO on a switchlinc relay. When I "lock down" for the night or vacation, the garage door opener is actually powered OFF once the garage door is verified closed. Even if someone broke into a car and got to the open button, they aren't getting in. It's easy with the ISY / mobilinc to programmatically turn on the GDO power as needed and /or on a schedule. I also have programs set up that send me a text message confirming every time the door opens or closes. If I drive away and am not sure of the status, I can check the text log to see at a glance.

It is my understanding that iRule does not work at all outside of the local network.

@Aaron, it would certainly be AWESOME if there was a utility that could be run on a user's network to auto-generate all the commands and make an importable "device" for iRule. @Michael, please do. This (and other) forums have been a huge help; I'm more than willing give back!

OK.... I FOUGHT MY WAY THROUGH THIS!!! So here's how it's done... Assume: ISY-99 fixed IP: 192.168.1.200 Port: 443 User name: User Password: password In the iRule Builder, you will need to define a new device. I called mine Insteon. You will also need information from your ISY-99 REST interface to do this. In a browser, navigate to https://192.168.1.200:443/rest/nodes If prompted, log in using User and password. The XML returned will contain data - a node - for each device and scene set up in your ISY-99. A device node will look something like: 0A BB CC 1 Hallway Cans (M) - Living Room . . . A scene node will look something like: 12345 Hallway Lights . . A BB CC 1 A BB DD 1 Note that in the scenes, any LEADING zeros are dropped from each device hex pair, so device 0A 0B CC will show up as A B CC Whether setting up a command for an individual device, or a scene, you will need to note the value of the node. For my example, I will be creating on and off commands for the Hallway Lights scene - address is 12345. So, under the Insteon device created in the builder, you will create commands for your Insteon devices / scenes. I initialy created "Hall Cans On" and "Hall Cans Off" The data field for the commands should be: name: Hall Cans On data: rest/nodes/12345/cmd/DON/255 name: Hall Cans Off data: rest/nodes/12345/cmd/DOF Note that if you are using a device vs. a scene, the command would be: name: Hallway Cans (M) - LR On data: rest/nodes/A%20B%20CC%201/cmd/DON/255 name: Hallway Cans (M) - LR Off data: rest/nodes/A%20B%20CC%201/cmd/DOF These would turn on and off the SINGLE SWITCH with Insteon ID 0A 0B CC Remember that leading zeros are dropped from EACH hex pair in th Insteon ID, and the spaces MUST be replaced with %20 in the data field. Once you have created the On and Off commands in the iRule builder, assign them to buttons on your panel(s). Don't forget to SAVE your iRule setup after adding the Insteon device and commands. On your device (iPad), start iRule Select Sync, and tap your device (iPad) to download th changes you just made in the builder to your iPad. Next, you will need to set up the ISY as a gateway in iRule. Select gateways, and then edit. Under HTTP gateway, select add gateway with properties: Name: ISY-99 Address: https://User:password@192.168.1.200:443 Save you new gateway. Select back to sync, and tap Backup gateways to save your new gateway. You should now be able to navigate through panels to th panel(s) with you Insteon device buttons. Hopefully, you will find success!!!

Would you have a tutorial on how you got the ISY-99I synced with iRule? Trying to do the same thing. Is it a network or http gateway that I need to create? Thank you! Did anyone ever get a tutorial put together on this? I've been trying to get iRule to work with my ISY-99 to no avail. I assume I need to set up an Http gateway in the rule software, but I can't figure out the embedded authentication. I tried setting up the gateway as: Name: ISY-99 Address: https://user:password@192.168.1.200 Port: 443 For the commands, I was making a simple 2 button panel with one "on" button and one "off" button. Command data was: On: rest/nodes/[insteon id]/cmd/DON/255 Off: rest/nodes/[insteon Id]/cmd/DOF THe rule software says is connects to the gateway, but the buttons have no response... I assume an authentication issue of some sort. Any help appreciated!

Is your working list of requirements (enhancements) available for review?

Hello! I'm new to the Network Resources aspect of the ISY. I currently have a program set up (and working successfully) that will notify me via MMS when a trigger event occurs. I would like to have the notification MMS include a snapshot from an IP camera that I have set up. I can retrieve a snapshot from the camera using the following url: 192.168.xx.xxx:5679/snapshot.cgi?user=username&pwd=password How do I set up the ISY to get a snapshot from the camera and insert it into the body of the notification?