tpolito

That's what I am going to end up doing.

Thanks, that was it. I tried the program on one of my v37 switches and it worked fine. For the v27 it required a power cycle. Thanks for all the help.

First of all, thanks to everyone for the help. I tried making the recommended change, choosing the switch instead of the scene. It still does not work. Here are a few other things I have tried. If I change the On-Level [Applied Locally] for the switch itself through the Admin console, the switch turns on to that on-level, but if I turn the switch off (at the switch) and turn it back on, it goes back to 10% on, instead of the new value. It is a V.27, so it is an older one. If I manually set the on level at the switch, it works. No power cycle needed. Could it still be that I would need to cycle power if the change is initated from the ISY instead of locally?

I have been following this thread (and other similar ones), and I guess I only half-way understand what the issue is. In terms of a program that I am currently using: If Control 'Kid's Bathroom Light' is switched Off And Status 'Kid's Bathroom Vent' is On Then Wait 10 minutes Set 'Kid's Bathroom Vent' Off Else - No Actions - (To add one, press 'Action') I assume what currently happens is when I turn off the kid's bathroom light, the program evaluates whether or not the vent is on. If it is, then in 10 minutes it will be turned off. What I am not sure of is what happens if I go back into the bathroom and turn on the light again, and then turn it off within the original 10 minute "wait". Will a new 10 minute period start, or will the light turn off after the original 10 minutes? Is this along the same lines y'all are discussing, or am I way off?

I am still at a loss. Yes, it the switch is the one actually controlling the load. In my "Then" statement, I chose Adjust Scene. Then in the "In Scene" drop down, I chose "Son's Room Lights" scene, and under the "Set" drop down, I selected the actual switch (not the scene). If I pull up the switch itself in the admin console, it shows that the local on level should be 30%, but that is not getting written to the device. I have the Automatically Write Changes to Device set, so I thought it should write those changes. Am I still missing something?

I am trying to program my kids' lights so that between 8:30pm and sunrise, when we press "on" on their switch, the lights only come on at 30%. During the day I want them to come on at 100%, when we turn them on locally. I cannot get it to work. Can anyone tell me what I am doing wrong? Here is my program... If From 8:30:00PM To Sunrise + 30 minutes (next day) Then In Scene 'Son's Room Lights' Set 'Son's Room Lights' 30% (On Level) Else In Scene 'Son's Room Lights' Set 'Son's Room Lights' 100% (On Level)

So far, so good (knock on wood). I have only had it up and running for a couple of weeks, but it has been reliable so far. It requires a few more steps for programming to interface the two systems, but not too bad. It still would be ideal to only have one system, but since neither does everything I am looking for, it will do.

No v35 Switchlincs, just v27 and v37. I have two access points (the first generation). Other than that, the only dual-band device I have is the PLM. The scene test results are not consistent. Sometimes a scene fails, and then I run the test immediately again, and it passes. Then it fails again if I run the test later.

I have a couple of scene tests that repeatedly fail. All of my programs are disabled. What is my next step? Does this indicate that I may have noise on the powerline somewhere?

Just thought I would post an update of how my setup is going. I set-up my ISY, and I am also still using HAL 2000 with a USB PLC. HAL still receives Insteon commands, and controls my Ocelot and Omni panel, but the ISY handles the Insteon control. For example, at night, I press a button on my keypad. HAL sees that and adjusts my thermostats, and sets the alarm, but I used the ISY to create a scene which is controlled by that same keypad button to turn off all of my lights. I have only had the ISY for a couple of days, but this seems to be working fine. When I want to control Insteon devices based on events from the Ocelot, or Omni, I have HAL send an X10 command to the ISY, and the ISY controls the devices accordingly. I have my dual-band PLM plugged into the pass-thru plug on my PLC, so I expect the X10 to be pretty reliable. Time will tell how reliable this ends up being, but limited testing so far seems to indicate that it should work well. I loved the ease and flexibility of HAL2000, and was pleasantly surprised that the ISY was equally easy to get started with. I have only begun to tap the potential of it, and look forward to doing so. Thanks to Michel and LeeG for helping me out with ideas on how to make these systems work together! I still would love to figure out a way to get away from the X10 signals between HAL and the ISY, but for now, I think it will do.

I guess there isn't a way for the ISY to periodically query switches for their device status? In other words, if my home automation software turned on a light, I understand that the ISY may not recognize that. Could I have the ISY poll all devices at a given time interval to sync back up with the device status?

Thanks again for the responses. I am not very familiar with netwwork sockets or http requests, so I don't really know the answer to those questions. I am going to go ahead and get one anyway and give it a shot. Worst case, I will just use X10 commands to communicate between the ISY and my other devices. Or very worse case, I will just use the ISY as an expensive way of managing the links on my Insteon devices instead of the tap method 100 different times to set up all the scenes I want. From what I understand, I could use it to set up the scenes, and then even if I disconnect the ISY, the scenes would still work.

Thanks Lee, that is what I was originally trying to ask, but you wordrd it a lot better than I did. If I understand you correctly, and IF the PLC is supported, then that would take care of actions like setting my alarm based on a keypad button press. But it wouldn't take care of turning on Insteon devices based on a change in the status of my alarm, correct? I may still have to use X10 for that?

Thanks for the response, I figured there would be some issues with it. I can't say for absolute sure, but I am almost positive I can send and receive X10 commands from my software, the alarm panel, and the Ocelot, so I do think it would work that way. My only hesitation is that in my current system, all of those devices are connected serially, and I feel like that is a much more reliable connection than changing to X10 would be. I never had any X10 devices, so I don't really know that for sure. But I would hate to take all of those things that are working very well now, and change them over to X10 and start having problems. I am not up to speed on the Network module and REST interface. Is there any way I could use those (or just a serial interface to my PC) to communicate with my software, so that if an Insteon button is pressed, the ISY could tell my software over the network module, and if my alarm was activated, the software could tell the ISY to run a scene via the REST interface? I'm sure this depends on the capabilities of my software. What features would it need in order to make this work, if it is even possible? Thanks for all of your help. Tom

I posted this over on Smarthome’s forum , and got a little bit of help, but I thought I may get a little more information on this forum. I currently have about 40 Insteon devices installed in my house, as well as an HAI Omni alarm panel, a Rain8 serial sprinkler controller, and an Ocelot. I currently use a software program (that many here may be familiar with) to control and interface all of those devices. It is a very powerful program, but is very lacking in it’s support of Insteon. I understand they are working diligently to fix these issues, but with no estimate for when they will be complete, I am getting a little impatient. I have been reading a lot about the ISY, and think I am ready to try it for a couple of reasons. One, all of the scenes and groups are stored in the software, not the switches, so if my PC is off for some reason, they do not work. And two, I am tired of having spent all of this money, only to have some of it not work consistently. What I am hoping I can do is leave my software (and USB PowerLinc Controller) in place, AND install an ISY with a Powerline modem. My thinking is that the ISY can keep most, if not all, of the Insteon control, while my software still handles the interface to the Omni and Ocelot. What problems will this cause? I was thinking I could handle it the following way: • Still allow Insteon signals to initiate the software to be able to control my alarm, Ocelot, etc. For example, I have a “Goodnight†scene that turns of my lights, sets my alarm, and adjusts my thermostats. Currently, I press a Keypadlinc button, and my software recognizes that the button was pressed and then turns off a “Goodnight†group of Insteon devices and also sends a signal to my Omni to set the alarm and adjust the thermostats. I am thinking I could create the scene “Goodnight†in the ISY to link all of the devices to that Keypadlinc, and remove that step from the software, but still allow the software to recognize the Keypadlinc was pressed and adjust the alarm and thermostats. • The next thing I need to do is turn on/off lights based on arming/disarming my alarm. Or turn on my garage light based on the garage door opening (which is connected through my Ocelot). I guess this is where I could either use an X10 output from the alarm panel (or Ocelot), or possibly use the REST interface, although I will have to get more familiar with that. My software can output serial commands if there is a way to have the ISY receive them. Does this sound reasonable? What are the pitfalls? Thanks, Tom