Michel Kohanim

IndyMike, Thanks so very much ... as a matter of fact, I am quite happy that you failed first otherwise we would've never had this wonderful topic. Thanks again and with kind regards, Michel

Hi Frank, Yes, your approach should work without issue unless there's a program that's run in which case a non-operating PLM will cause status errors. And, may I know why you do not have the 3AM Query running? With kind regards, Michel Hello Michel: That's very possible. There may have been one or more programs trying to execute during the time that the PLM was off. Yes, I could have just performed a network query, and if it ever happens again, I will try that. But the problem is that if I had been gone, and the power had gone out, maybe the same problem would have occured. Since I don't use a "3am status query" for the ISY, then my status readbacks would be wrong. That is the reason that I took the ISY off the UPS and put it onto the same outlet as the PLM. At least that way, it should reboot properly. Should this approach work without issues? Thanks

Hello Doug, Please find my answers below. With kind regards, Michel This program is tested/evaluated every time there's a change in the status of that device. If the status of the device never changes then the "Then" clause will never ever again run! No, it only repeats the Actions within it See above

Hello dkaye, Here's what I'd suggest: Create a program such that the condition is 'when' you want your furnace to be on (say, winter nights). Save this program and then go to Program Summary tab, choose this program, then choose Run at Boot, and then click on Apply. This way, your program will run after reboot. With kind regards, Michel

Hi Frank, That is quite interesting and something that should not happen. It's possible that ISY tried some of the programs during the time your PLM was unplugged; that could explain some of the problems. Next time - if there's one - instead of rebooting ISY, may I humbly ask you to simply do Query on the Network node? With kind regards, Michel Hello Michel & Mike: For what it's worth, I found that approach actually caused me a problem. I had my ISY-26 on my UPS, and the PLM plugged directly into the wall. They were both on the same circuit, but the ISY was on the backup. I had to turn that ciruit off to do some work on my home wiring. That meant that the ISY stayed on (due to the UPS), but the PLM went off. The circuit was off for some time (20 minutes?). When the PLM came back on, the communication with the ISY was messed up. If I remember correctly, many of the status readbacks on "My Lighting" were missing. Due to this, some of my programs that depended on devices statuses were not functioning. I had to power cycle the ISY to get it to sync back up with the PLM. It then found the PLM, ran its reboot systemwide query, and everything was good again. Based on that experience, I took the ISY off of the UPS, plugged it directly into the same outlet as the PLM, and the next time I turned that circuit off, the PLM and ISY came up together with no problems. Best wishes,

Charlie911, Yes, it's normal especially if you have the run-at-reboot set on your programs. With kind regards, Michel

Hello Frank, Apologies for a tardy reply and thanks so very much for finding yet another bug! Yes, indeed we forgot to put a prompt in the replace function to warn the user when the replaced node is in any scene which also has an RL. This has already been rectified and is part of the next code drop ( http://forum.universal-devices.com/viewtopic.php?p=5399 ). My comments below. Thanks again and with kind regards, Michel Apologies ... this was an oversight on our part which has already been rectified Not normal and definitely and oversight on our part No Yes, absolutely correct!

The 2.6.1 beta release is now available. If interested, please send an email to support@universal-devices.com Fixes - Workaround for KPLs (1.5+) showing as LampLinc BIPHY - Power outage issue: ISY will use a new IP address if one is issued any time after the boot up. Previously, ISY would give up (slow routers) after 3 retries - Java Exception when removing a device the table was not updated correctly - Daylight Saving flag was always set to true when adjusting the time to the computers clock - The slider for a relay in a scene was not being updated back to its original state if the operation was canceled (neither on nor off) - Clicking to the left/right of the slider or using the left/right arrow keys were ignored - Enable Internet Access: null now shows a failure message instead - No replacement menu available for RemoteLincs - 'Program Run/Program Run Else' failed if a program tried to run itself - SocketTimeout exception when loading a large number of programs - Explicit Query no longer clears the status of non-load devices (such as KPL secondary buttons, RL buttons, IRLinc buttons, etc.) Enhancements UDMobile Support - HTTPS Support - HTTP and HTTPS ports can now be changed using the CWP Shell Command - HTTP default port is now 80 - HTTPS default port is now 443 - Simple HTML page both in HTTP/HTTPS which can be used by Mobile devices ... no more Java - Certificate issues remain to be resolved X10 - Added support for sending/testing for X10 unit code separate from X10 command code and vice-versa Programming - Added Fade Up/Down/Stop to programs (both conditions and actions) - Can use a program to set other programs to 'Run/Not Run At Reboot' (for power outage recovery) - Specify from 0-100% for dimmable devices (100% shows as 'On', 0% shows as 'Off') GUI - Changed Reset History to Clear Log - In case of non-Linux clients, one can now selectively decide to save the log (CSV) or view it in Excel - Applied Locally is now on the main view as well - AutoUpdate no longer pops up whenever the Admin Console is started. Rather - and as a compromise - there will be a reminder (in text) at the top right corder of the Status bar - Progress bar when programs are loading General - In the shell, configure default number of insteon command retries - Automatic increase in insteon command retries for long running commands (eg. restore devices) - Automatically reorganize links for KeypadLinc LED backlight (no need to add them to scenes in specific order) INSTEON - Added support for Companion 2 Wire devices (2474S/D) - Added support for KPL Countdown Timers (2484DWH8) - Added support for KPL (v2) sub-buttons controlling the on-level/ramp rate for the local load - Added support for IRLinc - Added programming features for thermostats - Add New INSTEON device now supports providing the type of device to be added SHN - Added support for EZSwitch30 (minimal testing) - Added support for EZIO4O (minimal testing) - Added support for EZIO6I (minimal testing) - Added support for EZSnSRF - Added support for EZX10RF (untested)

Hi aLf, Nothing to worry about ... 50 times: an event is sent for each device/state in your ISY. So, depending on when the connection was dropped, and what you were doing, you might get up to the number of devices in your ISY times 12 (the number of operations which can be done on a device). In short, don't worry about it at all. You can use the filter to look only at the logs With kind regards, Michel

Jeff, We shall try to incorporate IRLinc as soon as we get the programmatic specifications. With kind regards, Michel

Mark, Thanks so very much for this great piece of work ... you deserve all the credit. Charlie911, Since the pages seem to be too wide, you might want to print using the Lanscape option of your printer. With kind regards, Michel

AnthemAVM, Yes, there's a trick which one of our customers figured out. I am going to ask him and reply back. With kind regards, Michel

d_l, You are right on! This is what it means (sorry for the long technical overview): Every time a client logs in and authenticates to ISY, it receives a subscription ID (SID). ISY maintains the subscriptions and makes sure there are no non-responsive clients out there. As such, each client MUST exit normally otherwise you will see -5011 which in short means: 1. ISY found the client not responding (maybe the computer went to standby with ISY's client open or maybe there was a network connection issue) and therefore expired the subscription 2. The client came back on line and issued a request using the previous SID which ISY had already expired aLf, You can do anything you would do locally remotely as well. I haven't seen your log (it was not attached) but what else do you see beyond the -5011? With kind regards, Michel

DEGoodrich, Wow, excellent! Would you be kind enough to post your findings in our EZxx forum (http://forum.universal-devices.com/viewforum.php?f=5)? I would sincerely appreciate it. Thanks so very much and with kind regards, Michel

Hi All, AutoUpdate no longer requires userid/password so you can discard it (nstein, that's why you didn't get the userid/password for 99i). Frank, point well taken ... this shall be implemented as you suggest. With kind regards, Michel

Hello Frank, Unfortunately the answer is no simply because ISY-26 was not designed with 99 in mind. If anything happens to 99, we'll send you a new one! With kind regards, Michel

mohansen, Yes, the first option deletes (logically/22) all the existing links. As far as ELK, this sounds like a bug ... you should never have to reboot ISY. The next time you are going to configure ELK, would you be kind enough to give it at least 30 seconds. Thanks so very much, With kind regards, Michel

Hi Frank, No, you are not doing anything wrong and thanks so very much for the screenshots. This certainly looks like a bug which we'll have to fix. With kind regards, Michel

Hi Frank, Are you aware that you should first add the new RemoteLinc to ISY before attempting a replace? Has anyone else has this problem? With kind regards, Michel Hello Michel: No, I haven't done a KPL replace. In fact, I haven't used the Replace function at all, yet. Which brings up another slightly off-topic question: even though I have ISY 2.6, I still don't see any way to "Replace" a Remotelinc. I have had to replace one already, back when I was using ISY 2.4.15. I looked at that time for a "Replace" function for my Remotelinc after I had added a new one. But there was no such feature to be found, either in a right-click menu, or in the top menu bar. I still don't see that function in 2.6. Am I looking in the wrong place? Thanks

Mark, Wow ... this is wonderful! Thanks so very much. With kind regards, Michel

Hello Frank, Rand and Mark have already answered (correctly) the device properties' utility. Now, let's get back to the question of losing your properties since this might be a bug: In the past, have you replaced any of the KPLs (using the replace method)? With kind regards, Michel

Hello Dave, No. It behaves the same simply because we have not yet added support for the extra features of KPL 1.5+. With kind regards, Michel

upstatemike and JAJ, Apologies for a tardy reply ... as I mentioned before, we can maintain the state of a scene. We just have to make sure we're not doing something to confuse those who do not understand the Unified Scene Theory! As a matter of fact, this thread is added to the list of our enhancements. With kind regards, Michel Not much response... No, though perhaps this particular question has become redundant with the introduction of your unified scene theory . With that in place, the user can have both indications even if ISY maintains only a single scene state. Now the question is, how much of this theory will be implemented, and when is it coming... ?

Hello JAJ, We do have a Trigger 2.0 planned which might include the nested conditions. I still don't understand why you cannot use folders and nest them: If folder 1 is true If folder 2 is true If folder 3 is true If Program is True Run Then Else Run Else Of course this does not give you nested Else but it's a start. With kind regards, Michel

Hello d_l, Yes, they are evaluated every time there's a change in state of any device or time. I have already captured the requirement to rename Run to Run Then and it should be in the next release. With kind regards, Michel