bipto

If you install the Admin Console Java application (admin.jnlp), you won't need a browser. Works fine on W10...

I think his intent may be to keep US union labor from fleeing to Canada...

I'm sure others will chime in here, but I was seeing the same symptoms a couple months back and LeeG was kind enough to help me through it. See the following thread: http://forum.universal-devices.com/topic/16137-control-events-not-firing-help/?p=139537 Turned out to be a dying PLM which had "lost" links to the devices in question... Good luck!

Indeed, you're right - thanks Larry!

Ok, so breaking the program in to two conditionals could be done like this... RUN_AWAY_LIGHTING If From Sunset To 2:00:00AM (next day) Or From 5:00:00AM To Sunrise (same day) Then Run Program 'AWAY_LIGHTING' (If) AWAY_LIGHTING If $s.Home.Away is 1 Then Wait 15 seconds Set 'Driveway CFLs Primary' Fast On Set 'Driveway CFLs Secondary' Fast On Set 'Front CFL Floods' Fast On Set 'Landscape Lights' Fast On Wait 15 seconds Set 'Driveway CFLs Primary' Fast On Set 'Driveway CFLs Secondary' Fast On Set 'Front CFL Floods' Fast On Set 'Landscape Lights' Fast On Send Notification to 'My e-mail' content 'Vaca Lights on' Else Wait 15 seconds Set 'Driveway CFLs Primary' Fast Off Set 'Driveway CFLs Primary' Fast Off Set 'Front CFL Floods' Fast Off Set 'Landscape Lights' Fast Off Wait 15 seconds Set 'Driveway CFLs Primary' Fast Off Set 'Driveway CFLs Primary' Fast Off Set 'Front CFL Floods' Fast Off Set 'Landscape Lights' Fast Off Send Notification to 'My e-mail' content 'Vaca Lights off' Note that as shown you would either have to disable the 'AWAY_LIGHTING' program or change 's.Home.Away' variable from a State to an Integer variable to prevent the program from running immediately when you set 's.Home.Away' ... Alternatively you could take the 'AWAY_LIGHTING' as-is and save it under an 'AWAY_DARK_PROGRAMS' folder and use your schedule condition to enable that folder. That would be my preference... --Bill

Sure... I'm on the clock at moment, but if no one chimes in by this evening I'll post them up for you... --Bill

You have two conditions in the IF clause. Whenever either changes, the IF is reevaluated. So whenever your state variable, or the schedule causes the IF to evaluate to false, your ELSE is firing. Your IF clause needs to be broken up, or alternatively you could put a program with just the schedule condition in a folder that enables when your vacation state variable is true...

Ok, so I guess I'm back to my initial befuddlement... If the battery dies in a sensor monitoring a door that is rarely opened / closed, how will we know..?

"Hung" in my software dev world to describe a device, application, process, etc. that has somehow been rendered unresponsive. A "heartbeat" is typically a bit, value, etc., that is changed by such an entity at a specified frequency to indicate a responsive state. I understood Larry's statement to mean that the heartbeat was somehow a static value rather than a single, specified value being "resent" ... I got it now...

Puzzled... How then would one, either visually or programmatically, distinguish a steady-state "heartbeat" value from a "hung" process..?

I don't have any tree / shrub zones (yet). I imagine that their watering requirement would be different than the lawn, and would probably be handled through separate programming. Not sure whether the Irrigation Module would be used for those - I too would be interested in hearing how others handle that scenario. As far my lawn is concerned, my irrigation system is set up to put down an average of 0.18" across all zones in one watering session, so I use the Irrigation Module to fire off the program when the irrigation requirement exceeds that number... --Bill

This is an easy task for (integrated) ELK owners as the panel is typically on its own battery and fires "Power Lost" and "Power Restored" events. Not sure if you could rig something up with other panels...

You're very welcome. If you have any questions or see any opportunities to improve upon it, please share! Gotta hand it to you Paul, you find the coolest toys... That rain sensor looks like quite an improvement over the Rain Bird mechanical cork / contact model that I currently have attached via an IOLinc. It's the legacy sensor that I was using with my old irrigation controller, and though it's adequate as a downfall detector, allowing me to cancel irrigation just before or during a session, something that allowed actual measurement would be better suited here... I may consider one of these. What mode do you yours in..? I've been running this program with minimal supervision since mid-summer last year. Predictably it's weakest link has been HAM weather drop-outs and inaccuracies, this is why I use wide margins on the "Total Rainfall / Forecast Rainfall" data, but thankfully HAM reliability seems to have improved / stabilized considerably since I wrote the program, so I may be able to tighten those up a bit. Since I turned the system on a month ago it just works... zerop, I second Paul's request - I'd love to see your programs... --Bill

My approach is a bit different, but may be of some use to you as if uses both climate and forecast data to determine when watering is needed. Note that rather than temperature, I use the Irrigation Requirement parameter from the Irrigation module to determine watering requirements. It's quite simple - the following 4 programs "check" twice per day at optimal watering times whether to launch a watering session... Irrig_Sched_All_SMTWTFS - [ID 0033][Parent 007E] If ( Time is 5:00:00AM Or Time is 4:00:00PM ) And Program 'Irrig_Required' is True And Program 'Irrig_Available' is True And Program 'Irrig_Permitted' is True Then $i.IRRIG.bScheduledRun = 1 Run Program 'Irrig_Zone_All' (Then Path) Else - No Actions - (To add one, press 'Action') Irrig_Required - [ID 004E][Parent 007C] If Module 'Climate' Irrigation Requirement >= 0.18 inches Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Irrig_Permitted - [ID 004D][Parent 007C] If Module 'Climate' Low Temperature > 40 °F And Module 'Climate' 24h Low Temperature > 40 °F And Module 'Climate' Wind Speed < 20 mph And Module 'Climate' Gust Wind Speed < 20 mph And Module 'Climate' Total Rain Today <= 0.09 " And Module 'Climate' 24h Rain < 0.36 " And Program 'Irrig_Event_Rain_Sensor_Wet' is False Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Irrig_Available - [ID 00C1][Parent 007C] If Status 'Irrigation / Zone1' is Off And Status 'Irrigation / Zone2' is Off And Status 'Irrigation / Zone3' is Off And Status 'Irrigation / Zone4' is Off And Status 'Irrigation / Zone5' is Off And Status 'Irrigation / Zone6' is Off And Status 'Irrigation / Zone7' is Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Gotta love the bit about "What's on the 2015 firmware Roadmap" though! Gave me goosebumps...

Indeed, as suggested this behavior disappeared when I switched back to http access. Thank you both!

Hi Michel! Given that this behavior seems to be a direct result of my switching to https client access, I'm thinking your bandwidth suggestion may be right on the money, but I'll go back on http tonight and try it a couple of times just to be sure. Thanks! --Bill

Both are true, thanks.

So several days ago I finally got around to self-signing the certificates and switching from http to https client access. All seemed fine until, during the course of an ISY backup, I saw the following error... It doesn't halt the backup, in fact it seems as if the backup goes on to complete successfully (though I am hesitant to attempt a restore to find out for sure). Stranger still is that subsequent backup attempt showed that these errors seem to occur at arbitrary times during the backup, sometimes multiple times... Anybody else seeing this..? I'm running 4.2.30 with https configured to TLS 1.2 Low for both client and server...

Unfortunately, no - Mobilinc has us all over a barrel at this point. Not so bad if you're an iPhone user I understand, but there is little love for Mobilinc among the Android users in this community. Android versions of the product are feature-starved in comparison to iOS versions, and by consensus seem to be lacking in stability. There is definitely opportunity for improvement in ISY mobile integration...

Ah, got it, thanks! Cool stuff...

SEG..?

IdeaScale is a great idea (pun intended), glad to see UDI putting it to good use! Now we all need to convince Wes (Mobilinc) to use it...

Well that's a fine bit of news, sounds like 5.0 is moving right along... Thanks Michel!

Ah, yeah... Mine too...