Michel Kohanim

Hi guy, Unfortunately you cannot for a variety of reasons the most important of which is the total number of PLM links it requires to have both of them synch with one another. If you just want to be notified of the changes on your computer, you can easily use the freely available JSDK which publishes all the changes to your computer instantaneously. With kind regards, Michel

Hi Brian, Would you be kind enough to post the procedure you are using to program this behavior manually? Thanks and with kind regards, Michel

Hi MarkJames, I am so very sorry to hear about the health issues. I hope all is well and everyone is healthy. 4428 tells me that the PLM has gone haywire ... basically, there's no way that the PLM can hold more than 2000 links and thus it's probably restarting at the top every time it reaches the end. What I recommend is for you to unplug your PLM, give it a little rest (maybe a minute or so), plug it back in and do the count again. Restoring KPLs, no matter how many times, should only overwrite the records for which there was a link; i.e. it simply updates the previous links if they exist, adds new ones if they don't, and removes those that no longer exist. Once you are done with the reboot and if your count is still high, I recommend doing a Restore Modem ... but, since I suspect your PLM is defective, I am afraid your PLM may die in the process. So, let's do the count first and then we'll decide what to do next. With kind regards, Michel

Hi MarkJames, Long time no see! For you to see the status of your motion sensor in ISY, there has to be 3 link records in the PLM for each node of the sensor. The first thing I would do is to do a count on PLM links (Tools | Diagnostics | Show PLM Links table). It might be that you have reached the maximum number of links supported by the PLM. If the PLM link count is low, then the next thing is to restore your MS. If that does not work, then I think it would be time for a new MS. All the above assumes that your MS is near an AccessPoint. With kind regards, Michel

Hello nickoonce, Unfortunately not. You can use the Network Module in addition to Global Caché GC100 to effectuate a change in your pool pump but currently we do not have support for bidirectional streams. With kind regards, Michel

Hi Brian, No, the relay does not turn off. Can you please try the same sequence on your 6 button KPL and let me know if it works. If so, please send me the manual steps you followed. I am not sure what this is related to but the memory locations are precisely the same as what ISY sets them. Perhaps there are some variables that are used internally and we do not know about. With kind regards, Michel

HI ryarber, Excellent idea! Thanks so very much and with kind regards, Michel

Hi mitch236, I think you may want to use a range (i.e. time is from 4:00 to 4:30) otherwise at 4:01 (and some grace period) your programs becomes false. With kind regards, Michel

Hi Brian, You are not missing anything and I appreciate your persistence simply because it will make our product better. I did test again with our KPL relay 5 button and it simply does not work even when I do it manually. The memory locations set the same way as ISY and confirm the previous understanding. Do you have 6 button or 8 button KPLs? With kind regards, Michel

Hi Doug, Please contact our tech support team and we'll help you out: http://www.universal-devices.com/contact.htm 818-631-0333 With kind regards, Michel

Hi Brian, The problem is that when you do the manual programming, the KPL does precisely what ISY does: instead of OFF it uses a very low on level. With kind regards, Michel

Hi Illusion, Thanks so very much for the feedback. This is probably another case of firmware idiosyncrasies between devices. Hi Troy, There was indeed a problem with releases starting at 2.7.8 where LED brightness would not work on certain KPLs. This has been fixed in 2.7.15 (which should be our official release). In short, this is how it works: 1. You have Off Level ... i.e the brightness level for when the button is in the Off mode 2. You have On Level ... i.e the brightness level for when the button is in the On mode 3. And, the most important thing to note is that the On Level is a function of the Off Level. So, the lower the Off Level, then the lower the On Level With kind regards, Michel

Hi Nick, Please note that even if a device reports i2 it does NOT mean that the device supports i2 programming for link database. This is why we had to introduce automatic mode since except for motion sensor, triggerlinc, and some function of thermostat, i2 commands were NOT reliable and caused more harm than good. If you can add motion sensors/triggerlincs, and thermostats then I would strongly advise against using the device reported mode since it's basically quite unpredictable. With kind regards, Michel

Hi Dan, There are certain cases that query will help: 1. If you use a lot of dim/brighten locally on your switches, the status might be up to 5% off. This may cause your programs that use specific values (instead of a range) not to work properly 2. If you adjust the on level/ramp rate of a device locally (not through ISY), ISY will not know about it. Query helps rectify this issue With kind regards, Michel

Clarence, Yes, yes, and NO. In short, please do not waste your time trying to figure out why V35s are not behaving reliably. Just have them replaced and you'll have saved 10s of hours of debugging. With kind regards, Michel

Hi Brian, Thanks for the update and I must say that I feel a lot better (even though things do not work anymore) mostly because I cannot stand unpredictable behavior. Consistency is quite important in code development. What you are describing is precisely how all KPLs have worked since they introduced the load control by sub-button in 2A+ firmware. When we read the memory locations for those that were setup manually, we noticed that the on level used was NOT 0 but a very low on level. That's why we put that dialog box in there. In short, there's only two memory locations that decide what the load should do and they are set properly by ISY. You had this setup using non-toggle buttons. Did you change the non-toggle state? With kind regards, Michel

Hi Mark, Looks good. Thanks so very much! With kind regards, Michel

Hi mitch236, Since you are sending one command at a time to your thermostat, and since thermostat modules are a little slower than other modules, what I recommend are: 1. Adding a delay of 3 to 5 seconds between each call OR 2. Make a scene with those settings and activate that scene instead With kind regards, Michel

Hi, Good question as we still haven't found the algorithm which converts one to the other! With kind regards, Michel

Hi Simon, Thanks so very much for the update. Perhaps we should do a constraint check in the code as a workaround. I hate this solution because it does not address the main issue of the thermostat sending the wrong data but it seems that we do not have a choice. With kind regards, Michel

Hi Brian, The main issue is this: You cannot send an On command to a scene and have a KPL sub button turn off (as well as the reverse). This problem is not limited to ISY scenes. Consider adding another KPL button from another KPL as a controller. Now, although you can control all the responders within the scene properly but the status of "other" KPL sub buttons is EQUAL to the command sent. That's the crux of the problem and has been an outstanding issue for over 2.5 years. With kind regards, Michel

Hi Gary, There's another explanation: you had pending device writes and ISY was writing to devices. Did you have any green 0101 icons at any moment in time? With kind regards, Michel

Hi Terry, Thanks so very much for the update and I am so very glad to hear of your progress. The next issue might be related to a firewall software if you have any. If you do, it would be best to put your ISY in the white/trusted list/zone. For a list of firewall issues/resolutions, please checkout this forum: http://forum.universal-devices.com/viewforum.php?f=3 With kind regards, Michel

Hi Brian, Unfortunately I cannot give you any expert advice on the setup. I can only answer your last question: That's precisely what ISY is doing: that's why the KPL has to be in a scene since all those interactions are accomplished via group commands. With kind regards, Michel

Hi, Do you have access to your router? The best thing to do is to see if you see ISY26-HOME-AUTO as one of the clients in the DHCP client table. If not, then in all likelihood your 26 is set with a static IP address which is not in the same subnet as your network. The only way you can reset that is through the shell (hyperterminal): http://www.universal-devices.com/mwiki/ ... _ISY_Shell With kind regards, Michel