Programs fail to run

[ewind]

I have a series of simple programs and wondering if there's a way to debug them to identify if they are overlapping or timing out or other issue. They run sometimes but not others. I have modified the then and if and created programs to trigger other programs rather than having all steps within a single program. 

[Michel Kohanim]

Hi ewind,

 

Please paste one of the program and that is not working and exactly what's not working.

 

With kind regards,

Michel

[ewind]

Thanks Michel, you're always helpful and if I understand your role it's pretty awesome. Here's one program that has been intermittent. 

 

Driveway Coach Lites Sunset Trigger - [iD 000D][Parent 0007]

 

If

        Status  'Driveway-Opened' is not On

    And From    Sunset 

        To      Sunrise (next day)

 

Then

        Run Program 'Lower Motion Coach Lites' (Then Path)

        Run Program 'Upper Motion Coach Lites' (Then Path)

 

Else

   - No Actions - (To add one, press 'Action')

 

 

The above program calls the following:

 

Lower Motion Coach Lites - [iD 000F][Parent 000B]

 

If

   - No Conditions - (To add one, press 'Schedule' or 'Condition')

 

Then

        Set 'Lower Garage Coach Lite' On

        Set 'Lower Coaches' On

        Wait  1 minute and 7 seconds

        Set 'Lower Garage Coach Lite' Off

        Set 'Lower Coaches' Off

 

Else

        Set 'Lower Garage Coach Lite' Off

        Set 'Lower Coaches' Off

 

and this one

 

Lower Motion Coach Lites - [iD 000F][Parent 000B]

 

If

   - No Conditions - (To add one, press 'Schedule' or 'Condition')

 

Then

        Set 'Lower Garage Coach Lite' On

        Set 'Lower Coaches' On

        Wait  1 minute and 7 seconds

        Set 'Lower Garage Coach Lite' Off

        Set 'Lower Coaches' Off

 

Else

        Set 'Lower Garage Coach Lite' Off

        Set 'Lower Coaches' Off

 

 

 

I also have a similar Insteon motion sensor program that is intermittent. Im using all Insteon devices and have eliminated the Insteon Hub several weeks ago. Trying to go pure ISY.

[ewind]

sorry the 2nd program didn't make it to clipboard, Here it is.

 

Upper Motion Coach Lites Copy - [iD 001C][Parent 000B]

 

If

   - No Conditions - (To add one, press 'Schedule' or 'Condition')

 

Then

        Set 'Front Door Light' On

        Set 'Upper Coach Lites' On

        Wait  9 seconds

        Set 'Sunroom Lamp Dimmer' On

        Wait  1 minute and 4 seconds

        Set 'Sunroom Lamp Dimmer' Off

        Wait  10 seconds

        Set 'Upper Coach Lites' Off

        Wait  7 seconds

        Set 'Front Door Light' Off

 

Else

        Set 'Sunroom Lamp Dimmer' Off

        Set 'Upper Coach Lites' Off

        Set 'Front Door Light' Off

[stusviews]

The "Driveway Coach Lites Sunset Trigger" program will run only if the 'Driveway-Opened' changes from not off to not on. The program won't run if the status doesn't change, regardless of the time constraints.

[ewind]

Yes that's true and by design. I have an Insteon TriggerLinc that once state changes should run both of the programs, but only within the time constaint.

And btw the program just ran successfully. 

Edited December 1, 2017 by ewind

[Michel Kohanim]

Hi ewind,

 

Thank you. When it's intermittent (or it does not run), do you know if any of the following is true (please use Program Summary tab) for all three of your programs

1. It's evaluated properly True/False (Status)

2. What's the Activity (Idle?)

3. Last runtime ... does it coincide with the motion sensor?

4. Which programs calls the Else path on the Upper/Lower Motion Coach Lites?

 

With kind regards,

Michel

[ewind]

Thanks Michel. Your support is much appreciated. I've attached an export of all programs and a screen sot of the programs status page.

Driveway sunset trigger calls both the upper motion and lower motion coach lites programs. each program has a couple steps each. The trigger device is a 2421 open close device hanging off a dakota alert unit. The dakota alert alarms every time without fail.

 

Every now and then I get the cannot communicate with lower garage coach lite or lower coach lites devices. Not sure whats causing that. Does that make the rest of the program error?

In addition the lower motion sensor program and upper motion senor programs do trigger some of the same devices but never at the exact same time, but possibly within the same time window.

Hopefully this all makes sense. It makes logical sense to me but I'm probably not understanding the programmatic steps clearly.

 

My Programs.v4.6.2__Sun 2017.12.03 04.39.50 PM.isy

[ewind]

The driveway sensor did just execute successfully as I had the admin console open the lower garage coach lite had a communication error with red exclamation, but I was able to query status, turn off and back on without issue.

[ewind]

Additional attachment showing the devices status view. Some of the icons are suspect like driveway opened and lower motion sensor, yet as of right now all are working normal.

[Michel Kohanim]

Hi ewind,

 

Thank you. Two things:

1. You see the gray 1011 icon next to Driveway-opened? That has to be cleared. Right mouse click | write updates to device

2. I suspect you have noise/signal issue. Please move the PLM to a different outlet and one which is not shared with other transformers and power supplies

 

With kind regards,

Michel

[ewind]

Thanks Michel. I will try to locate another circuit for the PLM. I have written updates to device driveway-opened, no errors, icon stays the same.My upper and lower motion sensor devices also stay in that same icon state.

Also I wonder if my upper and lower motion programs, which are triggered by the motion sensors, and call the same coach lites, are in conflcit with the driveway sunset trigger program. The two motion sensors do not reliably execute either and I have not found a pattern. Is there any logs I'm not aware of?

[ScottAvery]

The motion sensors need to be awake to be programmed.   Somewhere around here are instructions for a program to watch for activity on battery operated devices and then force updates, so they can be written the next time they naturally are activated, versus running around to wake them up and running back to write.

 

What is the device "driveway-opened"?  You have a heartbeat so I assume it is something battery operated like a wireless window sensor?  If so, same thing applies as the motion sensors - must be awake to write.

[ewind]

Ah thanks for that, I'll look for those instructions. I did not glean that detail about battery powered devices needing to be awake to write to them. That may be my entire problem. driveway-opened is a 2421 triggerlonc open close sensor and is battery powered. It is activated by a dakota dcr2500 and works great. The issue has been the ISY reliably taking that signal and executing the programs. The other 2 motion sensors have exhibited similar reliability issues which may be explained by outdated program steps being written to them??

[ewind]

Odd that it appears the feature "Automatic Writes to battery powered devices" is enabled for isy 99i but not 994i ?? Is see a program I can create for the 994i but Im not sure where to find the action or function "write updates" in this following example code....

 

 

Write Updates - [ID 00DB][Parent 00BE]

If
'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' is switched On

Then
Wait 2 seconds
Set 'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' Write Device Updates

Else
- No Actions - (To add one, press 'Action')

[Brian H]

Sounds like the ISY99i is a Pro model and the ISY994i is not a Pro model.

Did you exchange the ISY99i with an Upgrade to ISY994i?

If it was an upgrade. You may want to see if UDI has any options to move the Pro from the ISY99i to the ISY994i.

 

Try clicking on the module and wake it up. Then see if there is a Write Updates choice shown.

Edited December 5, 2017 by Brian H

[ewind]

Thanks, I bought the 994i new with PLM "ISY994i Home Automation Controller with Dual-Band PLM", I wasnt aware of a pro model. Is it a software update or different hardware entirely? Searching now.

[Brian H]

You can purchase it directly from the Administrative Console.

Help Tab Manage. Modules Choice.

It tells you what options are installed and what you can purchase.

It is a update you purchase and then UDI enables it directly.

Some like the IR addition also send you a small IR board you have to install yourself.

Edited December 5, 2017 by Brian H

[ewind]

Dangit!! Thanks. I had no idea that module was there.

[Brian H]

It is a firmware change UDI does remotely.

Also adds a larger number of scenes the nodes you can have. Over the standard model.

In addition to the Automatic writes On or Off. For both AC powered modules and Battery devices.

 

Gave an incorrect choice.

It is Purchase Modules not Manage Modules. To see what you have and what can be added.

Manage Modules see if the installed ones are up to date.

Edited December 5, 2017 by Brian H

[ScottAvery]

Pro definitely gives delayed write option for wired devices but I thought toggling for battery operated devices was standard.  The delay on wired devices is invaluable as your device pool gets larger.

 

The issue here isn't about options in the admin console, anyway.  The battery operated devices have to be woken up manually by pushing the set button or triggering their input.

[ScottAvery]

Odd that it appears the feature "Automatic Writes to battery powered devices" is enabled for isy 99i but not 994i ?? Is see a program I can create for the 994i but Im not sure where to find the action or function "write updates" in this following example code....

 

 

Write Updates - [ID 00DB][Parent 00BE]

 

If

'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' is switched On

 

Then

Wait 2 seconds

Set 'Door Sensors / Upstairs Bathroom / Upstairs BR - Door Sensor' Write Device Updates

 

Else

- No Actions - (To add one, press 'Action')

 

I'm not looking at the console now, but this reads as though it is on the Set Device menu in the program interface.  First choose set.  then select the device, then choose Write.

 

Note that this is what you want to do for long term sanity, but to get you through today's exercise, you can just go manually trigger them and run back to write while the icons are active.

 

This is not likely the source of your main issue, by the way, so just get the updates written so you can move on to pinpointing whether or not there are any real communications problems.

Edited December 5, 2017 by ScottAvery

[stusviews]

ewind, I have a program for each and every battery powered device like the one you posted (post #15) except that I do not have the 2 second wait and, most importantly, all those programs are disabled. I enable them as needed and then disable them again. Otherwise, you'll use up the battery faster.

 

That's because sending an on or off takes only an instant, but updating takes time and the battery is being used during the entire update writing process.

Edited December 5, 2017 by stusviews

[larryllix]

ewind, I have a program for each and every battery powered device like the one you posted (post #15) except that I do not have the 2 second wait and, most importantly, all those programs are disabled. I enable them as needed and then disable them again. Otherwise, you'll use up the battery faster.

 

That's because sending an on or off takes only an instant, but updating takes time and the battery is being used during the entire update writing process.

I discovered another problem with leaving them run. It was missing some signal into ISY, but I cannot remember what it was exactly.  I also  had to disable the programs  and just re-enable when needed.