Xathros

Hi Teken- I just reviewed the code again and still see no obvious reason for this to happen unless one of the integer variables was defined as a state variable instead. -Xathros

Hi Teken- Sorry for the brief reply yesterday, was out with the family and responding via the small screen. The Runtime variable will be reported by the custom notification as whatever value it has at the time the notification is sent. The first time it is sent, it will be at the 45 min threshold. If the cycle continues long enough that alert is repeated, the value will be higher with each repeat. We are not sending an alert when the cycle ends so unless a cycle ends at the same time that an alert is sent, you won't get a message containing the actual full cycle time. If that is a requirement, I can work in how to do that but it didn't seem from the initial request to be a requirement. If you want to know the amount of time that the cycle exceeded the 45 minute threshold, we will need to define another integer variable and do some math to get that value for you: If $s.FridgeRuntimeCycleMins >= 45 And $s.FridgeNotifySuspend is 0 Then $i.FridgeCycleExtra = $s.FridgeRuntimeCycleMins $i.FridgeCycleExtra -= 45 Send Notification to 'YourCell' content 'FridgeCycleTimeExceeded' $s.FridgeNotifySuspend = 1 Else - No Actions - (To add one, press 'Action') As for the difference between daily and cycle times after midnight, since the cycle time is not time of day dependent, that counter can start before midnight and cross the boundary while the daily gets reset at midnight. Lets say a cycle starts 10 minutes before midnight and runs for 30 minutes. At the end of the cycle, the cycle time should be 30 minutes but the daily will only show 20 since it gets reset at midnight crossing. Make sense? -Xathros

Larry- You may be able to tell by your hops left count. If you get comms from the PLM to "powerline only" items on the opposite phase with 2 hops left, likely the wired coupler is working. Using an RF bridge will cost you one hop. -Xathros

Will reply in full later today. Cycle started before midnight and crossed boundary. Daily reset at midnight. Cycle resets at end of cycle and not at midnight. Variable should work in the notification. Needs to be selected from list or hand entered in the correct format for notifications.

On the variables tab, click the "Refresh Values" button and see if they change. -Xathros

Hi Teken- See: That is certainly a valid statement. The "+= 1" increments the value of the variable by 1. Make sure your focus is in the then or else sections when attempting to select this. Also make sure you are editing a program and not a program folder. We are using the same technique in the runtime monitor program as well. The "IS" operator is used in place of "=" in the ISY. Neither of these are an issue. -Xathros

From your other thread on this subject, disable the Open and Close programs so they don't self trigger. Set up the favorites in ML to "Run IF" on the disabled Open and Close programs. Enjoy. -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