Michel Kohanim

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!

Sloop, Currently, it only works through wi-fi ... we are really at cross-roads trying to either add more functionality into this "super-fast" and "non-memory-hog" implementation or spend more time on a new platform (as suggested before). I welcome all your suggestions and feedback. With kind regards, Michel

Wow ... I think we have beaten the world record for responsiveness! You can ignore the spinning thing (it's a bug); can you use the menu and navigate to Scenes? Thanks so very much, Regards, Michel

Sloop, No. You don't need to enable internet access. Can you browse the internet using your PPC? If so, then you are all set and the issue lies with UDMobile. If you could tell me the exact error you are experiencing, I might be in a better position to help you. If you have already installed it in the flash, please wait a few moments (it might take a long time if you have a lot of devices). As Rand suggested, I think we might be reaching the limit on the memory on your PPC. When you run UDMobile, do you know how much memory you are left with? Thanks so very much, With regards, Michel

Sloop, Have you tried a simple unzip of: http://universal-devices.com/downloads/UDMobile-SD.zip to your /Storage Card? And then, use file explorer to navigate to and click: /Storage Card/UDClient/UDMStorage Please let me know. P.S. Don't worry about the warning ... Microsoft wants all PPC applications to have a certificate ($30.00 or more per unit) but we don't believe in having to pay so much just for a license. With kind regards, Michel

Sloop, This should work but only in Wifi (local intranet) mode. Would you please let me know the name of your SD Card directory; it's normally one of the following /SD Card /Stroage Card Thanks and with kind regards, Michel

Rand, You are 100% correct. UDMobile should find ISY on its own (UPnP) without knowing a predefined IP address. Sloop, May I ask what brand PocketPC you are using? Thanks and with kind regards, Michel

Rand, Excellent topic. Thanks so very much for suggesting it. Thanks so very much for the encouragement. Just for my edification, were you trying to install UDMobile on your SDCard? If so, that will not work. Please review the previous thread for instructions and let me know if you still have any problems. You are absolutely correct. J9VM in general and our implementation in particular have been known to eat up a lot of memory. For a fact, UDMobile will not function if you have more than 60 nodes (no more memory will be available). We have practically stopped all development on UDMobile because it no longer makes sense to keep on waiting for IBM to figure out what they want to do with their licensing nor is it to our benefit to wait for Sun to come up with a J2ME runtime implementation. As such, we are working on two other solutions: a. A simple web browser accessible interface which would not require any Java. The problem with this scenario is security b. A .Net implementation which requires neither a license nor does it eat up all the memory Yes, I agree! While designing/implementing the other solutions, you should not be left with an annoying problem like what you mentioned. I can't give you a date but please take my word that we shall work on resolving it. Thanks so very much for your feedback and insight, With regards,

Hello All, UDMobile client is based on J2ME (IBM Websphere Micro Environment Runtime = WEME). The only reason that we do not actively advertise our UDMobile client is that we have had a hard time figuring out where our clients can buy the license for WEME. The price for the license is $5.99 and we were told that users can buy it directly from Handango but it is not listed. If you, or anyone else for that matter, is willing to take the responsibility for acquiring a license for WEME, you can download our UDMobile client using one of the following methods: 1. http://universal-devices.com/downloads/ ... e-Full.zip -- use this download if you want to use ActiveSynch and install UDMobile in the Pocket PC's regular filesystem (flash) --->Download and unzip into a directory, and run setup.bat; this will install the app using ActiveSynch. Make sure you install to the device and not the SD Card. 2. http://universal-devices.com/downloads/UDMobile-SD.zip -- use this download if you want to simply copy the files into and run UDMobile from your SDCard --->Copy the contents of the zip file into an SD card --->Insert the SD card into your Pocket PC --->Use File Explorer and go to your /SD Card/UDClient or /Storage Card/UDClient directory depending on the name given to your SD Card file system by your Pocket PC --->If your SD directory is called SD Card, then click on UDMSD --->If your SD directory is called Storage Card, then click on UDMStorage For the most part, all development has stopped on UDMobile in the favor of a .Net to alleviate licensing issues. Thanks and with kind regards,

Hello all, We have decided to release version 2.3 by no later than 07.09.2007 and dedicate version 2.4 solely for triggers/scheduler. Version 2.3 is packed with some bug fixes but many functional and cosmetic enhancements: Bug Fixes: XML Parse Error with certain firewall software Fixed Lat/Long for Alberta, Canada ISY hang after DHCP renew Dynamic-DNS addresses 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 ... a workaround to link KPL to itself 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 Thanks so very much for all your support and help, With regards, Michel

Sloop, Welcome back. After thoroughly going through your dissertation, here are my comments: a. No, you are not doing too much. You can safely ignore the out of memory for block size 140 error unless you have more than 255 devices/scenes combination. In the worst case scenario all you need to do is to reboot. 140 byte is used to notify the clients (such as computers, PDAs, etc.) of the status of the system b. It seems that the button grouping you've discussed would address all your concerns/design requirements: i.e. all you need is to have KPL load backlight to also come on when any of the other buttons are pressed on the same KPL c. We are investigating the KPL button grouping as we speak. May I humbly ask you to hold off on that piece till our next release? Other than the above, and based on your thorough analysis of the situation, triggers, scene management you've gotten everything under control. Thanks so very much and with kind regards, Michel

dougos2, Unfortunately, we haven't had time to add support for EZSnsRF. As of now, we have no plans to support it but I added your request to our queue which we review every week. Thanks so very much for the feedback, With regards, Michel

Mark, Yes, you are right. We should lock 2.4 for triggers/schedules with no other new functionality. But, I am still not sure if this requires a vote. Do you? With regards, Michel