Michel Kohanim

My pleasure. Very much looking forward to resolving this issue. With kind regards, Michel

GPG, Hello and I am so sorry to hear that you are having trouble with ISY. I don't think what you did has anything to do with double solid lights. But, before you do factory reset, please reboot ISY and look at your hyperterminal for any startup failures. Would you please let me know what you see. Thanks and with sincere apologies, Regards,

Mark, Yes but with the pre-condition that you cannot use KPL buttons to do an All On/All Off if the KPL load itself for those buttons is going to be part of that scene. So, if you want an All on/All off scene using your KPL buttons, you have to use the KPL load button as the controller for that scene. If you want to control only the load for that KPL, then simply do a Synchronized Group between the KPL load button and another button which is going to control only the load; i.e between KPL button A and KPL button 1/load. The effect is that from now on every time you click on the load button, the whole scene turns on/off. When you click A, only the load for the KPL turns on/off. I hope this makes sense. With kind regards, Michel

HAS, You are right! I think sloop has already tried this so he might be better able to help you with the gizmos and scary things! As far as the port, you don't have to assign a port to ISY. ISY already has its own port: a. Right mouse click on My lighting b. Click on Properties c. Look at the Device Address you will see something like: http://192.168.0.105:16872/0/p.html In the example above 16872 is ISY's port for my device. I hope this helps a little. With kind regards, Michel

Mark, We are trying to figure out what we can do to alleviate these scenarios. As of right now, there are a couple of "ugly" workarounds that we are considering! I shall keep you all updated with the progress. With regards, Michel

Hi Sloop, Long time no see! EI in the shell is equal to File->Enable Internet Access. If I may, I would like to explain the sequence of events at ISY start up: a. Start Network Services (make sure we are on the network and an IP has been assigned) b. Initialize Filesystem (make sure we can get access to the file system on our SD card) c. Initialize Device/Nodes (make sure we can communicate with all the devices configured in ISY) d. Start Logger/UPnP/HTTP/D2D ... (low level services) e. Look for an Internet Gateway: i. This issues a UPnP Search Request for all the UPnP Gateway devices on the network ii. If one is found, and if Enable Internet Access has been issued at some time before ISY startup, then try to communicate with the router and get the necessary information to create a port forwarding rule in the router. This may fail if the router does not want to give out that information in which case the status of Internet Access becomes Disabled iii. If one is not found (i.e. the router never responded to the UPnP search request), then the status of Internet Access becomes Disabled When you get "null", it means that the router did not want to supply "port forwarding" information in step ei. Now, I have to emphasize that not being able to enable/disable internet access has no bearing whatsoever on the operations of ISY. As far as your router not being able to assing an DHCP address, that's quite strange because that function has nohting to do with UPnP. If your other devices on the network can be assigned a DHCP address, then we surely have to get one of these ActionTec routers and figure out why that is the case. With regards, Michel

GPG, Apologies for tardy reply. Mr. Sanctuary tried automatic configuration with BEFSR81. Have you tried Enable Internet Access with the new release of ISY (2.3). If so, are you still having issues? You are 100% correct vis-a-vis remote access 101. In short, you would have to create a Port Forwarding rule in your router. This said, however, if your ISY is being assigned DHCP addresses by your router, then you might run into an issue where ISY is assigned a different IP address (at some point) and thus your port forwarding will no longer work. So, here are the instructions: a. Make ISY use a static IP address: i. In the Run dialog, type: telnet your.isy.ip 126 ii. type CT (configure TCP/IP) iii. enter the desired IP address for ISY iv. enter the mask (usually 255.255.255.0) v. enter the gateway IP (usually the IP address of your router; i.e. 192.168.1.1) vi. enter your DNS IP (you have to look at your router's configuration page for this address) vii. you are done; wait for the system to reboot b1. For Linksys, open up the router's adminstrative page i. Go to Applications and Gaming ii. Go to Port Forwarding (sometimes, it's under UPnP) iii. Create a rule such that all TCP (not UDP) traffic directed to ISY's port is handled by ISY's static IP address b2. For DLink i. Go to Firewall tab (under Advanced) ii. Follow steps ii and iii in b1 (above) Please let me know if you run into any issues. With regards, Michel

HAS, Excellent question! The best option would be for us to get one of these routers and figure out what it takes for us to do it automatically. As far as I remember, the router is an Actiontec (MI424-WR). Do you know where we can buy one since the last time I checked it was a discontinued model and we couldn't buy it. To enable internet access manually, you have to do Port Forwarding. Unfortunately, in the case of sloop, ActionTec did not allow Port Forwarding for devices which were not issued an IP address by the ActionTec (DHCP). Have you tried port forwarding? In short, what you have to do is: a. Have your ISY use a static IP (if it's DHCP, then since ISY is not taking care of the forwarding, then when ISY gets a new IP, your port forwarding will not work) b. Go to the firewall configuration page in your router c. Forward all the TCP traffic directed to ISY's port, to ISY's IP address This should do it. I would sincerely appreciate receiving your feedback and experiences in this regards. Thanks and with kind regards, Michel

HAS, It makes perfect sense and quite elegant. Thanks so very much for the feedback. With regards, Michel Thanks for the understanding. My suggestion (i guess in a round about way) is to NOT put the bath fan (exhaust fan aka **** fan) on any sort of automation. Just replace the standard wall switch with a wall switch timer, llike the Intermatic I mentioned. As fun as automation is...some things don't need to be automated.

HAS, Not only you are not stepping on any toes but also we consider all suggestions and feedback invaluable. Here are some minor issues with the configuration as you suggest it: a. If your timer cuts power to your Insteon device, then you will receive "Device Communication Error" in ISY especially if there are some other functions (schedules/triggers) which need to communicate with that device b. There's probably not an easy way for ISY to figure out whether or not that device is on/off. You may decide to create a schedule to query the device every n minutes, but even that will fail if the timer cuts power to your device (see "a" above) So, in all likelihood, ISY's state will be out of synch with the actual state of the device being controlled by the timer. In short, you have an excellent suggestion if: a. You are not concerned with ISY being in synch with the actual state of your device b. You don't have any schedules/scenes/triggers which reference that device c. You have an extra space for a timer next to your device Thanks and with kind regards, Michel

Greetings HAS, Thanks so very much for your willingness to try this suggestion. Yes, you are 100% correct; there's collision and we should add a "wait" between the requests. We are working hard to release our trigger/scheduler functionality very soon so that we can get the scenario also resolved. Thanks again for the feedback and your support, With kind regards, Michel Greetings, I tried the above, and it kinda/sorta worked. It seems as if the signals are crashing into themselves, only allowing this "work around" to work intermittently. I worked on this "ALL OFF" scenario for many hours now, using various triggers and the conclusion is always the same; will not work 100% of the time. I think some 'delay' options need to be added before we (at least in this case) can control KPL button lights, with buttons on the same KPL, to eliminate the collision.

HAS, Would you be kind enough to try the following: a. Create a scene called whole house b. Drop in all your devices in there as responders c. Drop in D as the controller Next: a. Create a scene called KPL All Off Scene b. Drop in all the KPL buttons in there as responders c. Create a trigger such that when D is off, KPL All Off Scene is turned off With regards, Michel Works! Yippie! OK, how to make the A,B and C KPL lights go off when D (all off) is pressed?

Scott, I wouldn't say it's 100% useless; it's mainly used to have one of the buttons control the load since you cannot link them in the conventional way (controller/responder). With regards, Michel

Scott, You are right: there's no information in the manual since maintaining the PDF in each release takes 25% more time. We have chosen to update the documentation after major releases only. In the mean time, we are working on a Wiki site with all the information. Now, to do synchronized buttons, all you have to do is to drag and drop those buttons that you want to be synchronized into a group (say Synchronized Buttons 1). After the programming is complete, all the buttons in the same group follow each other: turning one off, turns all the others off as well and vice versa. With kind regards, Michel

HAS, Is D controller for a scene? If so, drop in A, B, and C as "responders" in the same scene. This is by far the best and cleanest solution. Otherwise, you will have to use Synchronized Buttons feature which I do not recommend since it only impacts local LEDs AND if you put all of A, B, C, D in one group then they all either turn on or off together which defeats the purpose. Let me know please, Regards, Michel Works! Yippie! OK, how to make the A,B and C KPL lights go off when D (all off) is pressed?

Rand, You are, as always, 100% correct. Of course, by linking I hope we all understand that this not "real" linking; it's just linking the KPL backlights. Sfhutchi, Yes, we can do the same. Or, in the mean time, while trying to do synchronized buttons, you can always choose the KPL last (drop it in last); this would have the same exact effect. With regards, Michel

HAS, Choose a KPL and make the button you wish to do all off a non-toggle button. When you click on the KPL button, on your right bottom you will see a button called "Toggle Mode". When you make that button Non-Toggle in "off" position, then every time you click on that button it sends out an Off command. With regards, Michel

Mark, Very good question. Synchronized buttons means that two ore more buttons in the same Synchronized groups follow each other: if you turn one on, all others will turn on as well and same for off. Unfotunately, you cannot use this function with combination of toggle-mode because when the synchronization turns an LED on then the state does not change regardless of the toggle mode. Of course, you already know first of all, you cannot "link" (put them in the same scene) two buttons of the same KPL with one trying to be a controller for the next one. So, I think what you would want to do is combine A/B into All On/Off and create a scene for that. Then you can use Synchronized buttons to turn on the load (since you cannot put them in the same scene). I hope this answers your question, With regards,

Mark, Yes. Thanks so very much for the information. It turns out that 2.3 resets the main configuration which includes: userid/pwd Latitude/Logitude/TMZ Offset email settings I am so very sorry for the inconvenience. With regards, Michel

Excellent ... would you be kind enough to update the list of our supported routers with yours? I'd sincerely appreciate it. With kind regards, Michel

John, Our pleasure. Unfortunately, triggers (in the current incarnation) do not work with non-toggle buttons since they are "trigger" based and non-toggle buttons never change their state= they are always off! I hope you can bear with us a little more till we get our enhanced trigger/scheduling functionality out. With kind regards, Michel

Hello all, Although we had promised to include enhanced trigger functionality in release 2.3, however due to the implementation of an overwhelming number of features and enhancements, we decided to release 2.3 without the triggers/scheduling. Please note that your userid/password/location settings/email settings may be reset after this upgrade (admin/admin). Please do make sure to check your Configurations by clicking on the Configurations icon after the upgrade is complete. Sincere apologies for the inconvenience As usual, please make sure you have a current backup of your configuration before upgrading to a new release. Here are the highlights of version 2.3: Bug Fixes: XML Parse Error with certain firewall software Fixed Lat/Long for Alberta, Canada ISY hang after DHCP renew Using a dynamic-DNS address would not get resolved when accessing ISY remotely Extra html tags on the AutoUpdate dialog Functional Enhancements: Multi selection of devices to be moved into a scene Support for KPL Toggle Mode Support for KPL Synchronized Buttons Support for one or more buttons from the same KPL as responders in the same scene Support for Linksys Routers WRT54GS and DLink DIR-655 Performance improvements in system startup Performance improvements in adding devices Cosmetic Enhancements: Changed the color to RED for a controller within a scene; everything else is blue Left Nav bar widened to support long names Changed the "Cancel" label to "Done" in certain dialogs Added UDI Forum menu option to the Help menu Progress bar: - No longer Always on Top - More accurate when clearing configuration before a Restore ISY - More accurate after linking/adding/removing devices and scenes If you have AutoUpdate credentials, simply logon to ISY and wait for the notification of the update. Otherwise, you may download version 2.3 here. Please don't hesitate to contact us with your questions/issues/suggestions. With kind regards,

Sloop, Yes, it's IBM's WEME (Websphere Everyplace Micro Edition) runtime. No since most phones/PPCs are supported. Yes, if you can, PLEASE have someone from IBM contact me. I sure appreciate it. With kind regards, Michel

Rand, I am quite disappointed with J9VM as it's simply not scalable and keeps eating memory not to mention that the last time I asked IBM about their licensing, they sent me a brochure for their blade servers (and that's when we decided that it's simply hopeless). We have no choice but to completely get rid of it. Sloop, You don't give yourself due credit. The answer to your question: You can have 5 simultaneous client sessions to ISY be it UDMobile, ISY Applet, MCE client, etc. and all will be updated whenever you change any settings on any of the clients or if you click on a physical button. With regards, Michel

Thank you Sloop!