MikeB

I hope to do one within the next 30-45 days. Please keep an eye on this thread.

Hi John - Unfortunately not. We tried recording a previous session, but the quality wasn't there. I may try recording the next session, but we're also working on some short how-to videos that we'll have posted up.

Great, glad to hear!

Try changing the ANDs to ORs.

Yes. Unfortunately, in order to control a KPL secondary button you need to create a scene containing it and control the scene instead.

Make sure your program turns off a scene containing ONLY the KPL button that you want to turn off (not the scene containing all your lights). "Is Load" is purely cosmetic. Some users use this to indicate that an installed switch carries a load.

Check out this thread: http://forum.universal-devices.com/viewtopic.php?t=2280

Correct. The Motion Sensor is not a responder. Consider this scenario if it worked like you suggest - you walk into a room, the Motion Sensor kicks in and turns your scene on, you walk to the light switch and turn the switch off, which turns the scene off and let's say it turns the Motion Sensor off like you desire. What happens when you move again in that room? The second you take a step, the Motion Sensor would trip again - and your scene would turn back on!

Have you tried disabling the momentary option and simply creating an ISY Program that will turn off the relay any time it is turned on? There would be some delay involved, but I bet it would quicker than 2 seconds.

Until the 30 second no-motion timeout period is finished, correct? If so, that is a limitation of the Motion Sensor itself - whether or not it is included in a scene. You can't force the completion of that timeout period on the Motion Sensor. The Motion Sensor does not receive commands (to preserve battery life) unless it is in programming mode.

Other than a slight delay in activation, what drawback would there be to using ISY Programs to accomplish what you want? Isn't this scenario the same even if the Motion Sensor is in a scene?

Even if you were able to remove the Motion Sensor from the scene - how would that fix the timeout issue you are describing? I may be missing something, but the problem seems to be that the Motion Sensor will not send another ON command until its timeout period of no motion (minimum 30 seconds I believe) has expired. This limitation exists whether you are using the Motion Sensor in a scene or via ISY Programs. What would the solution be? If I am in a room and the Motion Sensor activates and turns on a light, if I decide to manually turn the light off I wouldn't want the Motion Sensor to immediately pop back on. What am I missing?

You must use a 2412S.

You will need the 2412S.

Then, a day or two later, I return to the console and the program is no longer set to Run at Startup and the program is no longer running. Not sure why it's no longer set to 'Run At Startup'. What firmware version are you running? Also - I believe you will need to put an IF condition in if you want it to start at reboot. Such as: If From 12:00:00AM For 24 hours

Just a reminder that our online demo is today at 8pm EST. Hope to see you there!

Wow, what a pain. Thanks for reporting back, I'm glad you got it resolved. First time I've seen that issue on a router. Thanks

Our second online training and demo has been scheduled for Saturday 10/10 at 8pm Eastern, 5pm Pacific. Target audience is the same as the last meeting - people considering purchasing the ISY and new users looking to get familiar with the ISY. There will be a dial-in # available for audio (long distance charges apply). Date: Saturday October 10, 2009 Time: 8pm Eastern / 5pm Pacific Meeting URL: https://webmeeting.dimdim.com/portal/Jo ... al_devices Optional Dial-In: 702-473-3463 Dial-In Code: 1234 Hope to see you there!

Smarthome offers various sensors bundled with their IOLinc. For example: http://www.smarthome.com/24950A8/I-O-Li ... Kit/p.aspx They seem to have pulled their water/leak sensor kit (or I can't find it on the site anyway). I know some users were reporting issues with the sensor not reliably triggering the IOLinc.

Please let us know how you make out!

The DHCP table is probably showing you the IP address it last assigned to the ISY, before you set the static address. I'm sorry to say, but I can't think of a good reason for your issue. I'm sure that your problem running the Admin Console from your notebook's wifi connection is the same as your inability to ping reliaby from the same, but I can't imagine why you'd be able to ping the router and other network devices reliably but not the ISY. Especially when it pings fine from a hardwired connection. If I were you I would probably try the following: - move the ISY to a different port on your router - set the ISY to a different static IP address - change to a different router (probably Linksys)

Does seem very strange. What happens if you ping another device on your network, besides the ISY or router?

Sounds like your notebook does not have a good wireless connection to your router, but I'm assuming if that were the case the problem would be more obvious to you. Can you ping your router reliably from the notebook's wireless connection? Run a PING -T for a continuous ping instead of re-typing the command several time. Is the ISY plugged directly into the Belkin? General tips for wireless connection issues: - update router firmware - update wireless adapter driver - ensure you are in good range - change the wireless channel on your router (try 11)

Maybe I'm misunderstanding. So, you have an ALL OFF scene containing all your lights as responders to the scene, with a KPL button H as the controller (in non-toggle OFF mode). One of your lights is also controlled (on/off) by a KPL button B. If you turn the light on with KPL button B, the LED is illuminated and the light turns on. If you then hit the KPL button H all your lights turn off, but the KPL button B stays on. Correct? If so, this is normal. If the KPL button B is not a responder to your ALL OFF scene, it will not automatically turn off. You must add KPL button B to your ALL OFF scene as a responder, otherwise how would the button ever get turned off?

Have you added the B button to the ALL OFF scene as well?