Xathros

Hi Teken- Sorry for the delay, I'm just getting back from vacation. Are you still having issues with this or did you get the timing worked out? -Xathros

Yes, scenes add links. Delete unnecessary scenes. Combine other scenes if possible. Then, You can do a restore PLM to compress out deleted links.

Correct. In addition, you could buy a basic non IR 994, xfer all of your modules including the IR. Then take the IR board out of your 99 and install it on your new 994.

The IR has a hardware component. If you wish to keep that then purchase the 994/IR.

Buy the base 994 and xfer all but the IR module.

I have been working with Teken over the last week or two to develop and test some programs for monitoring household temperatures and generating notifications if values go out of range. Teken is using a network of OneWire temperature probes tied to an Autelis OneWire Bridge. The Autelis bridge periodically updated state variables in the ISY with the probe temperatures with .1 degree resolution. Since the ISY only supports whole numbers at the moment, the Autelis multiplies the value by 10 before posting to the ISY. I am posting these at Teken's request. The programs and variables below are used to monitor the kitchen temp probe and provide for the following requirements: Send an alert once every 30 minutes if/while the Kitchen temperature exceeds 23 Deg C (230 Autelis Units) If the kitchen temperature continues to rise by 2 or more Deg C (20 Autelis Units) - Alert Again without waiting for the 30 minute delay and do so each time the last alerted temperature is exceeded by 2 or more Deg C. Reset once kitchen temperature drops below 23Deg C threshold. Support up to 32 temperature sensors. This set of programs and variables serves as a model for the remaining 31 programs and variable sets. Variables: s.Autelis_Kitchen_Temp - State variable - Set by Autelis bridge (or other sensor input source) i.Autelis_Kitchen_Suspend - Integer Variable - Used to throttle notifications - 1= Suspended, 0=Normal i.Autelis_Kitchen_Alert_Temp - Integer Variable- To record the temp at last alert send. i.Autelis_Kitchen_Delta - Integer Variable- Used to calculate the change in temp since last alert sent. Kitchen_Temp_Monitor If $s.Autelis_Kitchen_Temp > 230 And $i.Autelis_Kitchen_Suspend is 0 Then Wait 0 secon ds Send Notification to 'GMX' content 'Autelis - Kitchen Temp Alert' Wait 3 seconds $i.Autelis_Kitchen_Suspend = 1 $i.Autelis_Kitchen_Alert_Temp = $s.Autelis_Kitchen_Temp Run Program 'Kitchen_Notification_Suspend' (Then Path) Else Wait 0 seconds $i.Autelis_Kitchen_Delta = $s.Autelis_Kitchen_Temp $i.Autelis_Kitchen_Delta -= $i.Autelis_Kitchen_Alert_Temp Wait 6 seconds Run Program 'Kitchen Override Suspend' (If) Send a notification if the Autelis probe reads higher than the threshold defined in line 1. Threshold is set in Autelis units which equal 10 units per 1 Deg C. We record the temp at notification so that we can monitor and alert again if temp continues to rise. NOTE: If you need to change the threshold, you also need to set the same value in Kitchen_Temp_Reset line 1 The First Wait in the Then and Else sections are to insert a delay for multiples of these programs to offset the runs and reduce ISY load when the Autelis updates all temp values at once. Stagger groups of these programs by 1 second. Kitchen_Notification_Suspend If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 30 minutes $i.Autelis_Kitchen_Suspend = 0 Else - No Actions - (To add one, press 'Action') Notify every 30 minutes while the temperature remains above the threshold set in the Kitchen_Temp_Monitor program. Kitchen_Override_Suspend If $i.Autelis_Kitchen_Delta >= 20 And $i.Autelis_Kitchen_Suspend is 1 Then Run Program 'Kitchen Temp Monitor' (Then Path) Else - No Actions - (To add one, press 'Action') The delta setting in the IF section controls the override if the temp continues to rise beyond this value since last notification was sent. This value is in Autelis units of 1 deg = 10 units. ie 20 = 2Deg C Kitchen_Temp_Reset If $s.Autelis_Kitchen_Temp < 230 And $i.Autelis_Kitchen_Suspend is 1 Then Wait 10 seconds $i.Autelis_Kitchen_Suspend = 0 Stop program 'Kitchen Notification Suspend' Else - No Actions - (To add one, press 'Action') Reset the override and stop the override timer when the temp drops below the threshold. NOTE: If you need to change the threshold, you also need to set the same value in Kitchen_Temp_Monitor line 1 In the coming weks, I plan on reworking this model to work for both high and low temperature limits. I will follow up with the updates once completed and throughly tested. -Xathros

The problem is the SSL settings in the ISSY dashboard. Thanks to MWareman, we know that setting the SSL Server settings to SSL3, ALL, Verify unchecked will allow the UBI connections to succeed. I have been using my UBI as the voice and ears for my ISY for a few months now. It kinda works, as long as the TV isn't on, nobody else is talking and UBI is in a good mood. I find it more useful as an output device to let me know about critical events in the home rather than an input device for issuing commands. -Xathros

Teken- I have reviewed the code and see no reason for the counts to differ with the exception of a run crossing the reset boundary. I suggest crafing a notification that reports both values and schedule that for right before the reset and again right after so that we can track and compare results. -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