CoRE and Piston Rules Engine, first design steps

SmartApps & Automations webCoRE
2619

Added the isPhysical as “Interaction” modifier for certain attributes.

I assumed switch, lock and door… any other attributes that can be physical?

You can now filter by Interaction: any, physical or programmatic

2620

Hope I didn’t break anything with that “physical” stuff…

v0.0.065.20160603 - Alpha test version - Introducing trigger interaction method (any, physical, programmatic) for some attributes (door, lock, switch). Various other fixes.

2621

I am still having a problem getting the “Mode” “changes away from” trigger to work.
This trigger will not fire.

720×1280 67.6 KB

But this one works great.

720×1280 65.9 KB

2622

Any logs please? Latest version? V0.0.065

2623

I just updated but not getting any logs, however I am not sure of how to do that?
I am looking at live logging in the IDE, do I need to turn on debugging or something?

2624

Each piston has its own debug settings all the way down that need enabled.

And since u updated, is it working now? The ,] in the description suggests you were on an old version that had mode issues…

2625

OK think i got it.
I see logs now when I use the working trigger.
but there are no logs when the trigger is not working.

2626

No its still not working

2627

Go to the piston and edit the condition, make sure it is correctly setup - tap on the list and choose the mode to go away from again, then Done, Done, Done all the way out. THEN try again :wink: it will work. The list was saved as a string instead of a list some versions back. Bad robot :wink:

2628

I’m thinking if CoRE can get its own sub forum to properly organize sub topics. I feel this thread is getting too long and complicated with many different sub topics. Searching for something “I thought I’ve seen last week” is getting difficult by the day.

2629

Logs

	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:57 PM:
trace
╔═══ Task processing took 34ms


	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:57 PM:
trace
║░░░ Removing any existing ST safety nets


	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:57 PM:
trace
║░░░ Rescheduling time triggers


	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:57 PM:
trace
╚═══ Processing tasks (v0.0.065.20160603)


	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:57 PM:
trace
╔═══ Event processing took 114ms


	9204714a-00a1-40f7-b371-07b58152f7d5

5:58:56 PM:
trace
╚═══ Processing event mode, value Night, generated on Fri Jun 03 23:58:56 UTC 2016, about 68ms ago (v0.0.065.20160603)
2630

Wouldn’t be a bad idea to start spinning off new threads when particular issues arise that are different than previous posts. Like CoRe dashboard testing, for example.

2631

Why does the light not go off. It shows in the log it is closed

2632

sorry I get logs now but it is still not working

2633

Nevermind…hub was offline for the third time and did not know it…duhhhhh I feel stupid

2634

log for “changes from”

	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
╔═══ Task processing took 24ms


	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
║░░░ Removing any existing ST safety nets


	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
║░░░ Rescheduling time triggers


	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
╚═══ Processing tasks (v0.0.065.20160603)


	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
╔═══ Event processing took 101ms


	9204714a-00a1-40f7-b371-07b58152f7d5

6:24:58 PM:
trace
╚═══ Processing event mode, value Night, generated on Sat Jun 04 00:24:58 UTC 2016, about 59ms ago (v0.0.065.20160603)

Logs for “changes” this one works!!!

	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
╔═══ Task processing took 146ms


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
║░░░ Removing any existing ST safety nets


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
info
║░░░ Executing virtual command sendSMSNotification (21ms)


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
║░░░ Installing ST safety net


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
║░░░ Rescheduling time triggers


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
╚═══ Processing tasks (v0.0.065.20160603)


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
╔═══ Event processing took 136ms


	9204714a-00a1-40f7-b371-07b58152f7d5

6:28:42 PM:
trace
╚═══ Processing event mode, value Night, generated on Sat Jun 04 00:28:42 UTC 2016, about 63ms ago (v0.0.065.20160603)
2635

Piston Restrictions?

2636

I created the piston below at 8:45 PM and I made sure that all logging options were enabled and the piston was running and then I cleared Live Logging.

As of 8:57 PM, nothing had been written to Live Logging for that piston and the action wasn’t performed.

I figured it must not like “is between” so I changed it to “happens at” 9:01 PM. It was 8:59 PM when I saved, and the action ran immediately and then ran again at 9:01 PM.

Around 9:02 PM, I changed it to “happens at” 9:05 PM and it ran when it was supposed to at 9:05 PM.

Do you have any idea why the piston shown below didn’t work or why when I changed it to “happens at”, it ran the action immediately after saving?

Screenshot_2016-06-03-20-50-50.png1080×1920 66.6 KB

2637

Missed: Suggestion to add IsPhysical for physical switch…

… gah, nevermind. Note to self: read entire thread before commenting. :confused:

2638

So tonight, I had a few snafus with pistons that worked yesterday. I’m on the latest version.

My late night routine where my cabinet leds would dim over time didnt fire

My hello didnt disarm when my wife got home, which triggered shm alarm.

My good night piston did everything BUT turn off my cabinet lights.

Anyone else seeing similar or odd things tonight?