Door Locks and User Codes


#15

Thanks, I really appreciate the research. Definitely a bit above where I’m at right now, but I believe I understand what’s going on. Is this looking like it’s not going to work? With this DTH?

I see output for ST App, Piston are the same
I see Output for manually with Key or with deadbolt are the same
I’m not sure I see the output from the keypad on outside. Was it this?

A:lock^ D:Front Door Lock^ DI:1^ DP:false^ U:^ V:locked^ S:^

If so, then it looks to be the same as manual with or without key, right?

Again, appreciate the effort


#16

yeah looks like that.

could you please post a screenshot of this in piston edit mode with the physical device lock selected:

as an example:


#17

Sure, thanks! Here’s two different one just to be safe


#18

thanks. i think everything that is needed is there.

if you can do a log to console and use this expression at the top of the piston

'autolock:' [Back Door (Lock) : autolock] '^beeper:' [Back Door (Lock) : beeper] '^codeChanged:' [Back Door (Lock) : codeChanged] ...

… and so on for all those attributes and trigger the same piston and check the values there. if you do update that from log please mask any secret info like lock code before posting here. :slight_smile:

the expression value is typed freehand so you may need to correct the syntax if i missed something.


#19

I’m sure its me. I am getting errors in the log output

║Error executing virtual command [].log: (3ms) groovy.lang.MissingMethodException: No signature of method: physicalgraph.sandbox.TruncatingLoggingListener.autolock:disabled^beeper:enabled^codechanged:7^codechanged:7() is applicable for argument types: (org.codehaus.groovy.runtime.GStringImpl, null) values: [║ null, null]

Here is my piston. I broke it up into multiple log outputs just in case, but receive the same error for each log output.


#20

if you remove the empty “” at the end of each log statement, does that make a difference? did you put those in the value field or the expression? it should be expression not value.


#21

try this one:


#22

Another way to go is you could disable One touch lock (aka lock and leave) during Workers Hours. Just have them punch in there 4 digit access code to lock the door. Then later reenable “lock and Leave” during non working hours. The added benefit to this would be knowing exactly who Locked the door.

disable one touch


#23

Hmm, that’s not a bad idea, other than the worry that they might forget to lock the door since it would be a change to how its been being done for a while.


#24

you are a lifesaver @bangali, i wish i saw this before using variables to for fuelstream names and data,


#25

one life every 4 months … dont seem to be saving many lives :wink:

not sure how i helped … but I will take it … every life is worth it :smile:


#26

the frustration you saved me is priceless. im not good at programming, i can do plc’s and logic but simplifying lines into understandable code has been a struggle. i seem to learn everything by trial and error :slight_smile: this saves me alot of error time. im an electrician by day, not a programmer :smiley:

i see your name alot around here, if you dont mind taking a look at my first operational piston, ill tag you in it so i dont hijack this thread (found it from google)


#27

any programmer who tells you they learnt without trial and error is fibbing :wink: so dont shortchange yourself :slight_smile:

tag me


#28

i did tag ya, posted about 46 min ago.

im not short changing myself on pupose. im more suprised/embarrassed by the amount of time ive spent with webcore in the last 3 weeks. ill have the control house for a new substation me and a helper are building before im done with moving all the automation rules to webcore.


#29

we all did the same when we were also getting started :smile:

check the other thread.


#30

The thing I don’t like about inputting a code - or even having to press the Schlage button - to lock the door is that it increases the opportunity for error… and if that error occurs, your home is left vulnerable.

If the goal is to re-engage SHM after everyone leaves, perhaps motion and contact sensors are the key?
If no motion/contact change within X minutes of front door lock, turn on SHM…


#31

Great thread!

I am looking to do the same thing:

  • if door locked from keypad, do X.

But I can’t manage to get this condition. How can I get webcore to trigger on “door locked from keypad” ?


#32

Using RBoy’s dth: and webcore


Piston not firing Echo Speaks after wait
#33

Love this site! Exactly what I needed.


#34

Hello there I’m new to this hole webcore. I’m hoping someone can help me out understanding better the usercode for a lock.

I own a August Smart lock Pro, all i want to do is turn on a certain LED on a switch that I own when door in unlocked and turn it off when it’s Locked.

I Do know how to control the LED’s of the switch, thats fines for me. But I can’t seems to understand the “user code” section when selecting my lock. I tried different combinations and both if’s return False.
Can Anyone help me out here.
Thanks!