Michel Kohanim

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

Hello Mark, Thanks so very much for the offer but I think that we don't have enough time to collect enough votes. In all likelihood, we will have a 2.3 release before the triggers release. Thanks so very much, Regards, Michel

Hello Mark, In short, at the moment, we are running a little late on the new triggers/scheduling functionality mostly due to our desire to add as many new requested functions (almost on a daily basis) as possible before the release. At the same time, release 2.3 has a lot to offer including expanded support for Linksys and Buffalo routers, multi-select drag/drop, many firmware enhancements and bug fixes, etc. As such, I think we'll be releasing 2.3 without the new triggers/scheduling by the end of the week. Thanks and with kind regards, Michel

sfhutchi, Yes, that would work but then again, how would that notify the other devices of the status? i.e. they all have to master so that the status is synched up between all of them. With regards, Michel

Backlight will be supported in either 2.3 or 2.4 release. I have added your request (schedule/trigger) to our list of requirements to discuss in our weekly meeting. Thanks for the feedback, Regards,

No, I have no idea how to fix it. Triggers would be counter-productive. I think a work-around would be to create a new Scene by copying the Responders from another scene. (Copy of ...) Then one could select a new Controller (different button) and set new levels for the Responders. It would be more convenient, if not quicker, than doing it manually. Thank you, Rand Rand, I do understand and agree. Thanks so very much for your continued support, Regards, Michel

Hello Rand, Yes, unfortunately we still haven't figured out a way to allow more than one button from the same KPL to be in the same scene. Apparently KPL cannot send a group command to itself! Do you have any ideas on how to fix it? As far as release 2.3: yes are up to our noses and have not yet fully tested everything. We are hoping to have it fully tested and published soon. Thank you all for your patience, With regards, Michel

Pioneer, For more technical information, please refer to http://forum.universal-devices.com/viewtopic.php?t=21 . You got it right! All you have to do is to make a scene where A, B, C, and D are all controllers. As far as which settings control what: If you click on the Scene icon on the Nav Pane (to your left), to your right, at the bottom, you are given the option of setting on level/ramp rate for all the members of that scene. Please note that these setting are only applicable if you turn on/off that scene through ISY. Now, for each controller with in a scene, you have the option of having different on level/ramp rates for all the other members of the scene. To do so, within a scene icon, click on the controller icon you'd like to adjust. To your bottom right you will see all the permissible on level/ramp rates that you can adjust for all the other members of the scene. I hope I've been able to answer your questions, With kind regards, Michel

John, we've experienced a lot of communications errors in the presence of malfunctioning X10 devices (they start bombarding the network with noise). Do you always have the problem? Do you remember the name of the person you spoke with at SmartHome? Based on Insteon spec, this does not sound logical at all. I'd like to hear more from the person who gave you this information. I suspect timer switch malfucntion. I am more of the opinion that you have a malfunctioning/intermittent X10 device on the network. -John

No. ISY acts as a liason if and only if you want to use ISY triggers/scheduling/access on the web. Yes, absolutely correct. Partly 100% correct Unfortunately, although the firmware supports it but we had to remove it from the applet as it made everything more confusing; i.e. for each device, go through the linked devices, if there's a controller in the linked devices, do the same, continue till you find all the linked controllers. When done, check each controllers linked responders and figure out which set of responders are the same for each controller and then make a group. In most cases, we ended up with disjoint sets and thus created spurious groups which had to be removed/merged. Yes, there's a much easier way: make A, B, and C all controllers in one scene. In this case, then, all switches will follow the status of one another If I understood your question correctly, what I suggested in the previous step should fix your problems. With kind regards, Michel

John, First of all, I have to address your concern: ISY is in the loop if and only if 1.You are programming (creating scenes, adjusting ramp rates, etc.) 2.You want to use ISY's scheduling/trigger functions In short, when you are done programming switches/buttons/scenes you can simply unplug ISY and all your buttons/scenes should work as programmed. The reason that you cannot see the the state of your KPL button, is that for KPLs, only the load button is associated with a status (on/off/level). The rest of the buttons (A, B, C, D, ...) do not have any states unless they are part of a scene/group. In this respect, then it seems to me that you are trying to use your existing links (between the timer and the KPL) which means that ISY's PLM is not part of the scene and thus ISY shall never be notified of any changes on the KPL buttons (except for the load). If I've been able to allay your concerns vis-a-vis a third item in the loop, may I humbly ask you to: a. Create a scene b. Drop your timer as a controller into the scene c. Drop you KPL button as a controller into the scene d. Right mouse click on the KPL button and choose Restore Device e. Right mouse click on the timer and choose Restore Device In this scenario, everything will work as you suggest + ISY (if plugged in) shall be notified of the changes either on the KPL button or the switch. With kind regards, Michel

John, Thanks so very much for the feedback. I would like to caution that using multiple timer modules in combination with ISY scheduling/triggers might have unpredictable results unless one can make sure that none of the timers and ISY schedules/triggers are overlapping/conflicting; this could become quite a daunting task. ISY in and of itself, tries to minimize overlaps/conflicting schedules. Now, I am very concerned with your statement: It is of utmost import for us to make sure ISY functions properly. Would you be kind enough to elaborate a little on your issues with ISY communications? I would sincerely appreciate it. With regards, Michel

sfhutchi, Yes, you got it ... the time element shall be incorporated into the triggers in our release 2.3. With regards, Michel

Mark, Not that my opinion matters for I am biased! But, why wouldn't you want to try ISY scheduler first and see whether or not it meets your expectations before spending money on a TimerLinc? With regards, Michel