jgraziano

Hi Michel, well, the implied status was a pretty good indicator as to whether or not it will work in a program based on the control status. Haven't tried restore, but I am absolutely certain that as soon as I created a link to a device, the status started showing up.

Well I don't really understand why a controller only would have a status, but I know when it was showing no status, on or off, it would not work in a program. Although the program was actually using the 'control' condition, not the 'status'. I have a CL that is not linked to anything except the ISY. I did that because I wanted to use each button individually under program control, so that gives me twice the number of buttons (albeit 8 times the amount of code!), since I just use the 'on' button as a toggle for a particular lamp: press on, press off. It's been working fine for several weeks now, no amnesia. We'll see how the RL does.

Hi Michel, I linked the RL to the ISY from the Link Management dropdown. I then manually linked two LL to buttons A and B. Those desplay status, either ON or OFF when I click on them on the tree and the status changes if I press the button. For the buttons I did not link anything to, let's say "C", the status field is blank, no ON, no OFF, just blank, and pressing the buttons does not change that. When I link C to something, it comes to life, displaying ON and OFF properly depending on the C button pressed. Even after I defaulted the LL module I linked to C (I could not get it to unlink properly), the status still worked. So, in short, I have to link each button to something before the ISY will see it. Then I can unlink it. So it really isn't that big a deal after all.

Ok, I unlinked the LL that I linked to get the RL Ch. D working and the status continues to be read by the ISY, even though it is no longer linked to anything.

Hi Michel, thanks for the reply. Happy Thanksgiving! When I originally linked the RL, all of the channels showed up, but the ones that are not linked to anything are not showing anything for status; on or off. And obviously the program did not respond to the status either. When I linked one of those manually to an LL, status started working. You're saying it should not matter whether it's linked or not, the ISY should always read the status? Thx.

It's looking that way. Like MikeB stated, I might just have to use a dummy LL for linking if I want to do it that way.

I have a RemoteLinc that I linked two buttons to two LampLincs. But a couple of the other buttons, I just want to read the status into ISY, to control X10 devices, without linking to anything. But it appears ISY won't even see them unless I link those buttons to something. Is that correct? How can I just read the status? Can I just link those buttons to ISY and nothing else? Thanks.

Totally agree, 100%.

It kind of makes me wonder if SH has been quietly developing a similar product and they want to position it below ISY. Based on my experience with HouseLink, I certainly could not recommend anything they do in that type of product. Or maybe they are coming out with a new version of HL that can actually download to the PLC like they said originally. I bought my ISY from UDI. I didn't want to SH to profit because HL is such a crappy, unstable product. Better for UDI to make the profit. Just my USD$.02

So would this be correct to keep the bedroom lights from turning on Thanksgiving and 'Black Friday'? --------------------------------------------- If From 5:00:00AM on 2007/11/22 To 5:00:00AM on 2007/11/24 Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') ---------------------------------------------- Folder Conditions for 'Events Subject to HOLD' Add conditions to limit when programs in this folder are allowed to run. If Program 'Thanksgiving' is False Then Allow the programs in this folder to run. ------------------------------------------------ The program to turn the lights on is in the 'events subject to hold' folder and normally runs at 5:30 am weekdays only. Thanks! Jim

Thanks Chris. Seems like another way to do it, too, would be to have the capability of program enable or disable by schedule. (I know, 'so many requests, so little time')

It looks like in the old version, you could put a hold on a program on a certain date, ie, Christmas, New Years, Thanksgiving, etc. I don't see that in the new one. It is still possible isn't it? I see the scheduling function, but it appears to be when to run or stop the programs, not 'not' run them. Is the only way to hold a program to put it in a folder with the conditional date? Thanks. Jim

Thanks Guys!

The ISY had an IP of 160, so I just left it and narrowed my pool down to 100-150. Now I have to make the 160 static. Looks pretty straightforward thru the shell, but I was never much of an expert at gateway, mask, dns, etc. settings. Should I just use the same settings that would be displayed for my computer when I do an ipconfig/all. In other words, the IP would be 160, but the other settings I put in the shell for the ISY would be same as those displayed on ipconfig for the computer on the same network? Thanks.

Well I'll tell you, that's not the only thing it got. I lost a bunch of icons from the system tray. One of them my UPS monitor icon. I can't figure out how to get it back either. The UPS works fine and shuts down the computer when I lose power, but now the only way I can get to it is from the Start menu. I'm not even sure what else was there that isn't any longer.

Thanks Frank yes, that's exactly what I want to do. To me it makes more sense, and I can just put it in my favorites network folder along with my router, WAP, etc. Or I could just try all of the IP addresses in my pool, one by one. Definitely want to put it outside the DHCP pool in case it doesn't grab an IP first. Not sure where to set it, though. Didn't see anything in the Configuration tab, unless it is the one that looks like it is a config. setting for Elk? Does have IP and Port. MikeB I did try the hide/unhide several times! Thanks! Jim

Uncle Bill updated my computer last night and now I no longer have the My Lighting icon. I've tried everything, toggling the Hide/Unhide while the ISY is on and off, cycling the PLM although the ISY is executing everything perfectly, so I didn't think it was that. Windows Firewall is OFF. Any ideas? Thanks. Update: I remembered that I had it set up on my laptop, so I tried it, no problem. I looked at the ip address then went back to my desktop and pinged that address, and it responded, still do not have the icon on the desktop. I then went to Explorer on my desktop machine and went to the full address manually and it logged onto the ISY. Still no icon.

Ok, that is simpler, I didn't realize the 'repeat' function is used that way. Thanks.

Is there an elegant way to get a particular device to flash for testing? I got it to work with a 2-program 'flip-flop', but it's a bit cumbersome. Thanks. Jim

Thanks!

Yep, that's it exactly. In addition, though, it would be very useful to be able to send X10 codes manually from the GUI. There is no way to do that outside of program control. Maybe the manual control could be on that tab also. Sure, it would be nice if you could set up X10 devices so they could be in the tree, used in scenes, etc., but I understand that a cost/benefit check on that probably wouldn't come out so good! Thanks. Jim

For the cost, I would definitely at least try the X10 route. I don't believe the delay is avoidable but I think in most cases 1-2 seconds is not critical. I have one activating a floodlight, however, it is to an X10 wall switch module, so that does not address Insteon compatibility. I have another in a hallway which does send a signal to ISY to turn on room lights, and so far that has worked reliably. With X10, it's all about the phases. I have some other X10 applications that do not work very well, hoping the new PLM will help.

I think a variation of this is what I'm looking for. I am trying to program a 'one-shot', the program should run and then not be allowed to run again until I re-enable it, either manually or on a schedule. Scenario: A motion sensor detects when somebody walks into a room and it turns on the lights one time, ie, in the morning. It will not turn them on again via the motion sensor until after 4 am on the following day. So throughout the day, if the lights are turned off manually, they won't be turned on again every time someone walks by the motion sensor. It resets at 4 am. What would be the best way to do that? Thanks. Update: Ok, I think I figured out a way to do it. In folder conditions, I allow the program to run if 4 am rolls around and one of the lamps in the room is off. When the motion detector detects motion it turns that lamp (and others) on, thus disabling the folder. It will re-enable again at 4 am the following day as long as that lamp is off. Seems to work well in testing, am I missing a possible gotcha here? Thanks.

I would also like to see some additional X10 support in ISY, but not to the detriment of other future capabilities. As bad as HouseLinc is, they did do a very good job of integrating X10. Of course SH has more of a vested interest in that than UD! At a minimum, I would just like to see the tab as mentioned where you can have an X10 translation table and a manual on/off right there on the table. That would fill 80-90% of my needs. Right now, as others have done, I keep a spreadsheet with the X10 addresses and names. Sometimes for quick reference, I will copy and paste that into the 'comments' section of the program. For direct control, which is mostly for testing. I dug up an old 4-channel controller and set it to a house code I never use. Then I did a program for each button with just the 'if' statement for that address. I put in the X10 'then' as needed and use that controller for the manual control. It's a workaround, but it does work. Sure would like to see that X10 tab, though!

When I try and run a log it returns a compile error in Excel and highlights "TrailingMinusNumbers:" in the code debugger. This is a pretty old version of Excel, 2000. On my laptop it works fine with Excel 2003. Should 2000 work? Thanks.