Xathros

rw86347-Just Disable both programs so that they don't self trigger. You can then call the programs manually from another program, Mobilinc, or the Admin console. Or, as Stu said above, add a "and Control 'XXX' is switched On" or "and Control 'XXX' is switched Off"condition to the programs using whatever device you wish to trigger the door activity (Like a KPL button for example.) -Xathros

It does not. The internal clock is only used for display and for any programs set within the Stat. Most of us never program anything in the stat and use the ISY instead. I can't remember the last time I even looked at the clock on my Venstar. -Xathros

I haven't experienced any issues with the window size, which is why I haven't spoken up in this thread till now. My results are identical to Andy's above. I also wish the settings would survive an OS reboot. I need to re-add all of my URL's to the finder after a reboot or cache clear. Most annoying. I've given up switching themes as well. I prefer the desert theme but I have to reset after every OS reboot and then restart the console after switching the theme. Not worth the hassle. In any case, it seems way too easy to make the Java app forget it's settings on my Macs. Maybe try a different user account on your mac and see if you get different results. If you don't have another account, it's easy enough to create one for testing then delete it after. Unlike Windows, that won't end up costing you a bunch of disk and registry bloat. -Xathros

You can periodically query the plug in module and use Status Is Not Responding in a program to send an alert if the module becomes unreachable. If Status 'Garage Freezer APL' is Not Responding or Status 'Garage Freezer APL' is Not On Then Send Notification to 'Your Cell' Content 'Freezer_lost_power' Else -Xathros

Anytime. Always happy to help. -Xathros

Yes. If the Firmware in the ISY was at 4.2.8 then any UI pulled from the ISY would also be 4.2.8. This sounds more and more like network problems to me. -Xathros

Create a scene containing the lights that you want to control and turn the scene on/off instead of the devices directly. -Xathros

@Teken- Wow! Sounds like quite an ordeal. It's possible that I'm just misunderstanding your terminology but a few things jumped out at me. First, restoring an ISY backup from an older firmware will not change the current firmware or UI versions as the firmware is not contained in the backup. UI version is dependent on what UI you download from either your ISY or the UDI website and what version may already be in your java cache up until you clear the cache. When plulling a new UI from the ISY, the UI will always equal the firmware version. The backup contains only your settings, devices, scenes, programs, variables, network resources, custom notifications etc. To go back to an older firmware you would have to "Manually Upgrade" and select an older firmware image. To go back to an older UI, clear your java cache and pull the UI from the UDI website using a URL specifying the version. Another thing to note is that often the error messages displayed during a backup / restore are unrelated to the backup/restore process and are instead related to other devices attempting to connect to the ISY over the network. I get the impression that the ISY gets too busy to respond to some network traffic when doing backup/restore operations and connections may timeout. I often see socket timeouts during a backup. Just acknowledge them continue on. The backup is still happening behind the messages. If the message says "Upgrade failed", "Backup Failed", "Restore Failed", then thats another story. All in all it sounds like a rough few days. I'm glad to hear you have got it back under control now. -Xathros

@Teken- Any updates? Have you worked out whats going wrong yet? -Xathros

@teken I found an error in my code that is responsible for this. I'm so sorry that i have put you through so much grief trying to track this down. I will post revisions shortly that will resolve the loop. The problem is in calculating the AlertDelta. The first step in the calculation is triggering the override. I feel horrible that I have caused you so much grief. -Xathros EDIT: Nevermind. After another review, the problem I thought I saw is a non issue. i.AlertDelta is an integer variable and does not cause a trigger. Also, these programs are fine on my test system. Only difference is that I don't have an Autelis updating the SecureRoom variable, I do that manually. -Xathros

@smokegrub- Sounds like you may have a signal sucker on the circuit. Unplug any power strips that are on that circuit and test again. -Xathros

I don't think so. Values would obviously be different but math is math and best as I can tell, your values are 10X actual to account for the inability of the ISY to do floating point. If they were 100X then the values would make no sense though as I recall, you are up north in Canada so maybe it really is that cold... -Xathros

Here are mine: 779 = 77.9F = Outside Temp 185 = 18.5F = Failed Sensor that I haven't had a chance to replace yet. 1234 = 123.4F = Output side of hot water tank -Xathros

I believe that the Autelis data is temp x 10 so your 20 is actually 2 deg and 50 should be 5 deg. 5 would be .5 deg. My concern in the other thread is the frequency with which the Autelis updates the ISY state variables. I would expect updates to be at 1 per second or less frequent. -Xathros

Good. That rules out a loop caused by that at least. I'd be interested to see some of the other flickering programs to see if there is a common element. -Xathros

Check the Variables tab and see if i.NotifySuspend is on the State or Integer sub tab. and of my vars that start with "i." should be defined on the Integer tab and any beginning with "s." should be on the State tab. -Xathros

@Teken- Is i.NotificationSuspend possibly defined as a state variable instead of an Integer? If so, There's your cause! -Xathros

@Teken- How frequent are updates from the Autelis unit? I have to agree with Larry that it looks like these programs are stuck in a loop. Can you shut down the Autelis for a few minutes when this happens and see if it stops? I'm going to review the programs and see if I missed something that might cause this. -Xathros

smokegrub- I have to say the the outletlinc has been my most problematic device in my install. I many times needed to reset and restore the device to get it working again and it seems to have a very weak PLM inside. I have several switchlincs on the same circuit that are all flawless yet the outletlinc in the middle of the circuit often fails to communicate. The load I'm controlling with it is just a small doorway fan to move heat from my pellet stove into the next room. It's possible that a spike from cutting power to the fan motor is whats upseting the OL and forcing me to restore but that doesn't account for the poor comms issue and adjacent devices on that circuit have not had any issues with spikes. At some point before the heating season begins again, I will replace this with a ZWave outlet and be done with the problem once and for all. -Xathros

Custom notifications. Same as the example I provided just in HTML rather than text and a lot of HTML tags between the variables. The image is hosted on my website and referenced by it's URL. -Xathros

Hi Teken- Yes, you should. In my testing I was able to watch both the cycle and daily mvars increment once per minute. Of course, I don't have a GEM and was using a state variable as my trigger instead. Does the ISY see changes in the GEM values in real time and trigger status events when the values change? -Xathros

Sure. Here you go: -Xathros

The 994 will come with a power adapter - no need to buy a separate one. You can upgrade to Pro at anytime after purchase. Simply purchase the Pro (or any other module) and UDI will activate that feature in your 994. You will want to purchase the ZWave version for your lockset and I do recommend the external antenna for better ZWave range. Note: ZWave, IR and Zigbee modules also have a hardware component so when upgrading to one of those modules after purchase will require a part to be shipped and installed inside the ISY's case. Not difficult but not as instant as upgrading to a software only module like Pro, Network, Weather, Irrigation etc. Buy your 994 with the ZWave option already installed and you won't need to worry. The Pro module allows for a larger number of programs and scenes as well as improved SSL support for interfacing with other devices. That would likely require the network module as well. These are easy after purchase addons if needed. Zigbee and Zwave options are mutually exclusive. You can only have one or the other unless you want multiple ISYs. Another thing to note is the level of support offered by UDI and this community is second to none. No other controller out there comes close. Hope this helps. -Xathros

There are a few on this forum that run both together. I believe in most cases, the ISY is the primary controller handling the logic and HomeSeer is a secondary device used to interface with personal weather data or in another case is being used for Multi Channel ZWave devices that the ISY does not yet support. I highly suspect most on this forum (including those two) would recommend the ISY over most any other controller. In addition, I believe in the two cases I mentioned above, those users are migrating their systems to the 994 from Homeseer. -Xathros

I have only the ISY-994 and have not found it to be limiting in anyway what I can accomplish. My system is comprised of a large insteon install and a young but growing ZWave mesh. I access all of my devices easily with my iPhone using Mobilinc. I see no need for Homeseer though I have never used Homeser and may be missing something. -Xathros