MikeB

Thanks for this code Jeff! I was currently doing my fast on/off triggers with 2 separate programs. Didn't realize I could do it with 1.

Hey Rand - That's what I had thought too, but it's not the case. I run the following code for my front door lights: If From Sunset + 20 minutes To 9:30:00PM (same day) Then Set Scene 'FrontDoor' On Else Set Scene 'FrontDoor' Off I can turn them on any time of the day, and they will stay on. I believe the conditions are evaluated only twice (at the start time, and at the end time) - not continuously.

...or, something like this: If From Sunset + 20 minutes To 9:30:00PM (same day) Then Set Scene 'FrontDoor' On Else Set Scene 'FrontDoor' Off This might be easier if you're using sunset or sunrise as a start/end point, and a fixed time as the other point.

I confirmed that this seems to be correct. I can set it to run, and it will run and stay running (since the THEN statements are continuous). But, if the ISY is rebooted it needs to be started manually. Setting the program to 'run at reboot' causes the ISY to re-start the program when the ISY is rebooted, and it works like I hoped. Thanks for the suggestion Frank! This feels like a 'cleaner' solution than putting a time value under IF since I want the program to always run.

I could certainly be wrong, but my understanding that setting a program to RUN simply tells it to start running now, but doesn't necessarily set it to ALWAYS run.

Hey Frank - Thanks for the suggestion. I think that would work, but then if the ISY were rebooted it would not start - unless I set it to 'run at reboot'. Anyone have any opinions on whether or not this would be a 'cleaner' solution?

I'm beta testing a product which needs to be queried to know it's current state.

There have been reports on Cocoontech of users with the Elk/PLC combo experiencing random lights coming on. You might want to run a search on there. I have never heard of this with the ISY, so I suspect it is somehow Elk-related.

I edited my original post after the fact. I didn't want bad code floating around. Thanks Michel.

Don't take it so literally. You need to find the IP address of your ISY. When you open the admin interface, the web browser with the UDI logo will show you the IP address in the address bar. So, if your ISY's IP address is 192.168.1.102, you would: - click START, then RUN - type in CMD and hit enter - in the black box, type: TELNET 192.168.1.102 126 Good luck!

Correction. This is the code I am testing/using: If From 12:00:00AM To 11:59:59PM (same day) Then Repeat Every 10 minutes Set 'OfficeLight' Query Else - No Actions - (To add one, press 'Action')

What's the best way to query a device every 10 minutes? Would something like this be OK: If From 12:00:00AM To 11:59:59PM (same day) Then Repeat Every 10 minutes Set 'OfficeLight' Query Else - No Actions - (To add one, press 'Action') ..or am I missing something more efficient? Anyone have any sample code they'd like to share? EDIT: CORRECTED CODE

Keep in mind that with the ISY-99, power is supplied through the PLM. I doubt the PLM would behave if plugged into a UPS. So, question is - is there a way with the ISY-99 to NOT use the power supplied by the PLM and use the AC adapter plug instead? That way the PLM could be plugged direct into the wall, and the ISY could stay on a battery backup. Of course, I can't think of a current use for the ISY-99 without a powered PLM anyway. But, I can understand why a user might want to keep it running to avoid a reboot during a small power outage.

I'm heading out too, but you can email me off of www.techav.com . Drop me an email there, and I'll send you my PayPal account info. Thanks!

Hey Jim - I keep trying to send you a PM, but the forums is erroring out. Let me know if you don't get it.

Hey Jim - I'm not aware of any firmware issues with RemoteLincs. All of mine seem to performed equally, and I've never read of any substantial changes. The used one does, however, say rev 0.92. My new one says rev 1.0. Yes, I do have a PayPal account. Feel free to PM me.

Huh.... I read up on it, and confirmed what you wrote - but I could have SWORN when I was using this I had my theater lights on A1 and A2, and my driveway lights on B1 and B2 and I was able to control them through my Harmony remote without flipping the house code on the IR543. If I had time I'd set it up again to verify.... but mine definitely says just IR543 on the bottom.

To be honest, I think a beta ISY-99 would probably be more stable than an X10 solution. Keep in mind that the ISY-99 is pretty much an ISY-26 Part II - pretty much the same firmware, but with the addition of IR support. And IR control for me has been rock solid. Yes, that sounds right. You select the house code via a dial on the unit. The device has built-in hard buttons you can use to send unit codes 1-8. However, the IR port will accept unit codes 1-16. I'm not sure if you can use an IR remote to send house codes other than what's currently selected. So you may be right about the 16 code limit. However, I'm pretty sure I've used it in the past with various house codes on a single remote/IR543. My Harmony 880 has the IR543 in its database. If it's important to you, you may want to look into how bright/dim commands would work. That could be an issue.

Hey Jim - I'm using my Harmony 880 with the ISY-99's IR, and love it. Very responsive, very reliable, very flexible. If you're considering moving up to the ISY-99, you might want to check and see if UDI still has any beta units left for sale. Otherwise, I think the only shipping IR interface would be the X10 IR543. I actually have one up for sale on Cocoontech. If you can get a consistent powerline X10 signal to your PLM/ISY-26, it should work well - but with a second or 2 delay compared with a native Insteon solution.

How about the free Excel viewer: http://www.microsoft.com/downloads/deta ... laylang=EN

After you set the rate through the ISY, go to the switch and physcally soft reset it (pull the airgap for 5 seconds, then softly push it back in - do not hold).

I have no problem using programs to determine the status when I need to. But, if it would not take much effort, and have no downsides, I'm all for having the ISY keep track internally.

I have a 650+ light pre-lit tree (bah humbug) with incandescent mini lights. My Kill-A-Watt says it's using 255 watts. I'm controlling it with an Icon On/Off adapter rated at 480 watts.

Makes sense to me.

I can confirm that this is possible with the beta ISY-99i/IR PRO. The control commands are FADE UP and FADE DOWN.