Michel Kohanim

mdcastle, Absolutely and with pleasure. We are open everyday except Saturdays. I can contact you today after 1:00 PM Pacific Time. If you are interested, please send an email to tech@universal-devices.com . With kind regards, Michel

Hello Frank, You may want to try: Folder Conditions for 'Away' Add conditions to limit when programs in this folder are allowed to run. If X10 'B1/On (3)' is Received And X10 'B1/Off (11))' is not Receieved Then Allow the programs in this folder to run. This way, if you receive B1/Off, the programs within the folder will not run. With kind regards, Michel

sfhutchi, You are 100% correct. It's an annoyance for which we have not yet found a cure. It might involve a redesign which we have been postponing since we wanted to get 2.5 out. Now, not being able to communicate with devices is a problem which we have to address. As far as I remember, this is a problem which you've been experiencing intermittently all along, right? If so, would you please let me know the firmware version of your PLM? I think you should upgrade to 52 and use an AccessPoint (not SignaLinc) on top. Thanks and with kind regards,

C Martin and Mark, thank you! Frank, UDI will take care of you either way. The choice is yours. With kind regards, Michel

Mark and sfhutchi, Thanks so very much ... With kind regards, Michel

sfhutchi, Let's see what we can do ... no promises but I do think this is a valuable feature. With kind regards, Michel

sloop and Mark, Thanks so very much for the feedback. Appreciate it. Frank I am sure you will find ISY to your satisfaction. Here are my comments: You can calculate the number links based on the algorithm that sloop graciously provided. Using that algorithm, if all your devices are KPLs, and if all of them are configured as 8 buttons, then you will surely run out of links immediately: 8 x 30 = 240 buttons 2 links per button = 2 x 240 = 480 ! Otherwise, I don't think you are going to run out of links. Please also take a look at sloop's topology and try to extrapolate. You can use the Beta PLM but you would either have to call them directly and "agree with their Beta program" or I would have to do it for you. In either case, though, if you purchase ISY from SmartHome, it would be very difficult to ask for the Beta PLM. When you are ready, please send me an email (tech@universal-devices.com) and I'll do my best to get it to you. One thing to consider though: this is really a Beta PLM; as sloop can attest to, it might not work! Thank you for the detailed information on your experiences with X10/Essential Timer/PLC. We have not had much experience/exposure to Essential Timer and thus I cannot make any intelligent comments. I leave that for the more knowledgeable users on the forum. Or, if you wish, you can pose your question to our INSTEON Only forum where someone from SmartHome will surely answer your question. Now, as far as sending X10 commands reliably, we do depend on the PLM for communications. We have witnessed as well as corroborated the following scenarios with X10/PLM combination: 1. Sometimes the PLM just gets tired of responding to X10 messages and starts ignoring them ... reboot does not help this situation; you just have to wait it out! 2. Although all our communications to PLM are "timed" perfectly, but it's been known that the PLM might "discard" X10 messages if they are sent within 2 seconds of each other. ISY prevents this from happening (we cover it up) but, ultimately, it's up to the PLM to transfer the command In summary, since there are too many variables to consider when it comes to X10, and since we do offer a 30 day money back guarantee, may I humbly suggest giving ISY a try with your scenarios and make sure it meets your requirements? Thanks and with kind regards, Michel

Hi C Martin, Not a problem. I shall have one sent out to you. Please verify your address (tech@universal-devices.com). With kind regards, Michel

Hi carranoelectric Yes, you can use one ISY to configure each and everyone of your jobs. Here's the procedure (assuming that you are starting fresh): A. Configuration Step 1. Configure your client's lighting using ISY 2. File->Backup ISY ... save it using your customer's name. This is your customers configuration 3. File->Remove Modem if and only if you want to take the PLM with you. I recommend leaving the PLM with the customer mostly because of the time it takes to "Restore" it in case you'd have to go back B. Clean Up When you are done with the job: 1. If you are going to take the PLM with you, then do a Factory Reset on the PLM 2. Do a Factory Reset on ISY (please consult the Advanced Configuration Guide: http://www.universal-devices.com/resources.htm C. Next Job If you have already done step B (clean up), then simply start with step A. Otherwise, make sure you do a clean up before proceeding with step A. D. Modifications to an Existing Job 1. Make sure you have already done step B 2. Find the customers backup file which you saved in Step A2 3. File->Restore ISY 4. If you have left the PLM with your customer, then no other action is necessary. Otherwise, File->Restore Modem (PLM). This may take between 2 minutes to 30 minutes. That's why I do recommand leaving the PLM with the customer 5. After you've done your modifications, make sure to do another File->Backup ISY so that you have the latest configuration for the customer 6. If you want to Remove the PLM, then issue File->Remove Modem That's about it. Yes, there is but I really don't think it's worth your time. Anyway, here are the steps: 1. Configure your computer with a static IP address 2. Configure ISY with a static IP address (please consult Advanced Configuration Guide http://www.universal-devices.com/resources.htm). Make sure both the computer and ISY are on the same subnet and IP range (usually 192.168.1.xx and subnet 255.255.255.0) 3. Connect your ISY to your Computer using a Cross-Over Ethernet Cable Please note: If your computer was using DHCP before, then you would have to revert back to DHCP or might run the risk of not being able to access any network resources (internet/network printers/etc.) after Step 1. With kind regards, Michel

Rand, I agree with you 100%. sfhutchi, I do agree with your premise as well as the fact that something should be done about it. Again, the problem is not the coding; the problem is how to avoid delays/network traffic/unexplained behaviors when ISY is trying to set all those devices back to their previous state. Any ideas? Thanks and with kind regards, Michel

sceaton, Precisely ... that's the major obstacle. Mark, I agree with your suggestion (turning back on the scenes) which is equal to what Rand was suggesting. With kind regards,

sceaton, Just for clarification purposes: Not entirely true. ISY calulates/predicts what the value should be regardless of what you do and from where (the physical device itself or ISY) including brighten/dim. Infact, you can test this scneario and you'll note that ISY is usually within +/- 5% accuracy of the actual state. Therefore, ISY does keep tab of the state of devices without having to query them after each command. If you want 100% accuracy, then you can activate the Query schedule which currently runs at 3:00 AM (or whatever time you might have readjusted it to). With kind regards,

Mark, I like the idea of making the slider's label red for the controller. It shall be done for the next drop. Thanks so very much. With kind regards, Michel

mdcastle, I am a little relieved now that you are back up and running. Please do be kind enough to request for a new PLM from SmartHome; if they give you a hard time, let us know and we'll send you one. As far as final 2.5, may I humbly suggest trying our beta; you will not regret it. In an attempt to make sure our customers our satisfied, Mr. Steve Lee from SmartHomePro has graciously accepted to have an INSTEON only forum within our forums @ http://forum.universal-devices.com/viewforum.php?f=15 . Please do copy and paste your INSTEON only questions to that forum and he will surely reply to them. Please do not hesitate to contact us with your questions/comments/suggestions. With kind regards, Michel

Hi Mark, I am still thinking about them mostly because: a. I am still confused as to what ISY/Scene Local/Responder mean b. We are expecting users to "remember" 5 different colors for concepts that are not even clear to us. In short, the person/document who's going to describe the colors can simply describe the situation instead Personally, I think it makes much more sense to have a pop if and only If changing a slider within a scene changes the LOCAL on level/ramp rate for that device Beyond this, I really don't think there should be any changes. Of course, we are always open to suggestions especially when backed by requests from a number of clients. Thanks so very much, With kind regards, Michel

My pleasure! With kind regards, Michel

Hello C Martin, Any updates on your testing? Actually, we have experienced some "intermittent" behavior with the PLM deciding to ignore X10 messages for "while". If you do not yet have PLM v.52, please do call SmartHome for an upgrade which is a little better in handling X10 messages. If they give you any trouble, please do let me know. With kind regards, Michel

Just Another Joe, Ok, yes. It must have been. Would you be kind enough to notify us in case you find any problems with 1.6.03? Thanks in advance, With kind regards, Michel Hi Michel. I had JRE 1.6.0_02 until about a week ago, when it notified me of an available update, and I updated to JRE 1.6.0_03-b05. So, I guess the problem must have been a. cached version of applet. Though recycling the ISY didn't help, the problem disappeared after turning the computer off for the night, then back on today. So far, it appears to be working correctly.

mdcastle, I apologize for the troubles you've been experiencing. If you get a lot of "Request Failed" messages, then it could be one of the following three things: 1. Signal issue; Please do be kind enough to plug an AccessPoint or a SignaLinc right on top of your PLM 2. You linked devices and "brought existing links" ... if your existing links have a conflict with what you are trying to do with ISY, then the device simply rejects the request. This happens very often with devices that have been linked using HouseLinc (half links/orphaned links) 3. As sloop suggested, your PLM is "tired" ... believe it or not, that's precisely what happens when the PLM is confronted with a lot of operations We can certainly walk you through all the issues and setup problems regardless of the cause. If you need further assistance, please do not hesitate to contact us directly by phone or email. With kind regards, Michel

sfhutchi, Mike B, Rand, and Mark: Thank you so very much for the feedback and the brainstorming. I must admit that on this point I am more in tune with Rand. This said, however, I do understand that switches/lights would never stay at their preset levels especially if you have kids. The technical difficulty is not about coding; it's about managing the resources while being the least obtrusive. Let me elucidate: Let's assume you have 40 devices and a trigger that turns on a scene with 20 of your devices. Let's assume that these devices each were at different levels prior to the trigger. Now, let's say you want to store the state of each and every device. This means that ISY has to send 20 commands to 20 devices which should take approximately 15 to 20 seconds if you have a flawless INSTEON network. If you don't, then add 4 seconds for each "misbehaving device". Now, during these 20-25 seconds: a. All the schedules are delayed 20-25 seconds (have to wait for the queue to finish) b. Any communications from Admin Console to INSTEON will be queued and thus delayed 20-25 seconds (you won't even be able to do it since the System will be busy!) So, the more devices you have, the more the delay, the more the likelihood of communications errors, etc. If you add more of these triggers, then there's nothing to prevent this scenario to completely hog the network/ISY resources and stop all other activities. And, this is precisely why group commands/scenes are so wonderful: they only take one operation. Similar ideas which are less obtrusive could be: 1. Capture and apply the current state of the devices within scenes. So, for instance, your kids adjust the levels for your dining room scene to a level that makes the most sense. You simply go to the controller for that scene and apply the current state of each device to that controller 2. Some type of pattern recognition based on ISY's log entries With kind regards, Michel

Just Another Joe, Yes, absolutely acceptable. The only problem arises if a) you are using DHCP and your ISY's DHCP lease expires in which case, your link will no longer work. To alleviate this, you can make ISY use a static IP address. Please consult Advanced Configuration Guide (http://www.universal-devices.com/resources.htm) to configure ISY with static IP. With kind regards, Michel

Mark, Thanks so very much for your help. Just Another Joe, In all likelihood, the problems are/were: a. Cached version of the applet (Control Panel->Java->Settings->Delete Files) b. You must have an older JRE. Please try JRE 1.6.02 ... you can download it directly from our website @ http://www.universal-devices.com/resources.htm Please let us know how it goes. Thanks and with kind regards Michel

siegeld, What type of conditions? Are these conditions the same as those used by our programs or others? Right now, if you implement onTriggerStatus, and if in the shell you turn on DBG 1, you will be notified of all button presses and state changes. Are you interested in any other specific events? With kind regards, Michel

MikeB, Aha! That makes sense but a little difficult to implement mostly due to limited resources on the box. We shall investigate since I think this would be a great feature. Thanks and with kind regards, Michel

Hi sfhutchi, Interesting but why would you want to change the settings? If you do an All On (My Lighting->On), then all devices will turn on, ISY is updated with their status, and when you turn them off, ISY is updated yet again with the correct status. Would you be kind enough to elaborate a bit? With kind regards, Michel