And I care for you too, LOL … if you really care, you’d ship some cold weather out our way in the southwest part of the U.S., hehe
Here you go:
Door Locks Status, kn6p
Door Status, w4d7
Notify To Open/Close Sliding Door, g56b
The Door Locks Status and Door Status pistons are the same — only the devices and attributes (and piston titles) were changed to protect the innocent … the last piston not so much, LOL. The keys to the last piston are the variable defines and the piston state statement at the very bottom. I did it this way so I could change the order of the variable output if needed/wanted.
What is missing from webCoRE (that CoRE has), other than the FOLLOWED BY?
Someone already mentioned Piston Recovery … but I’ll mention it again
A slow UI, but Core can keep that!!
You should be able to get the daily high and low using WC’s built-in JSON parsing. (See ady’s example here).
Use the expression
$weather.forecast.forecast.simpleforecast.forecastday.high.fahrenheit for high and
$weather.forecast.forecast.simpleforecast.forecastday.low.fahrenheit for low.
You added the orientation feature right before I’m leaving for the weekend, so I can’t test it out right away! I’ll be able to test it out on Sunday if someone else have beaten be to it by then.
This was the last feature I was still using core for. Thanks!!
I’ll try give it a go after work today and provide feedback. Thanks for adding the capability @ady624!
Thx a bunch.
Expanded the door status a bit my selv, did you look into finding the last time valu pr. device, using $time gives the same value on each row.
thinking something like $device:motion.lastactive.$time
You seem clever at this
Webcore and Core does not handle unlocked by user actions in the same way
Core runs an action if the selected code is used on the lock to unlcok the door.
Webcore also do this but it also runs the actions selected for user #1 if the lock is unlocked by the app or by manually unlocking it from the inside.
This webcore piston gives me a notification no matter how the lock us unlocked (except for usercode 2 or higher)
This Core piston only gives me a notification if code #1 is actually used to unlock the door
Not yet … I created this rather quickly (between wifey chores, LOL) this past weekend. Also, I almost never have more than one device opened/unlocked at a time, so a simple time-stamp was satisfactory — for now. I’ll probably do something for time-value-per-device eventually
@ady624 Is there any way to get
\n to work in notifications?
NVM… I just realized that creating an expression and pressing enter will move the text to the new line and that’s mirrored in the notifications
Now, we need a way to collapse it
To get the data when it last changed status you can use the following:
time( addSeconds( $now, ( (-1) * age([$device:contact]) / 1000) ) )
$now - age([$device:contact])
Using time( value ) will strip off the date and keep the time only.
I suggested the function time because the original script was using the $time, and in my case the time is sufice, no need to have the full date.
But, now that you mention the time function, is there a way to return the time in a 24h format?
Working as expected now.
I am loving this
Did we get “Interaction” (Any, Physical, Programmatic) for switches in WebCore yet? I am using the variable “currentEventPhysicalDevice”. Having the interaction type in the main condition would make my piston’s simpler.
Yup, as of:
06/16/2017 >>> v0.2.0c2.20170616 - BETA M2 - Added support for lock codes, physical interaction