Unlock door and turn on lights

#1

1) Give a description of the problem
The piston is not working. The trace shows canceling statement (4 for example)

2) What is the expected behavior?
Turn on the kitchen and pantry lights when the door is unlocked between 5:30pm and 4am

3) What is happening/not happening?
I unlock the door and nothing happens

4) Post a Green Snapshot of the pistonimage

image
image.png1178×581 27.3 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
</|+2ms|╔Received event [Garage Entry Door 2].lock = unlocked with a delay of 110ms|
|—|---|
|+241ms|║RunTime Analysis CS > 18ms > PS > 200ms > PE > 24ms > CE|
|+243ms|║Runtime (37956 bytes) successfully initialized in 200ms (v0.3.108.20180906) (241ms)|
|+245ms|║╔Execution stage started|
|+263ms|║║Comparison (time) 75571145 is_between (time) 63000000 … (time) 14400000 = true (10ms)|
|+265ms|║║Time restriction check passed|
|+267ms|║║Condition #6 evaluated true (16ms)|
|+272ms|║║Comparison (enum) unlocked changes_to (string) unlocked = true (1ms)|
|+274ms|║║Cancelling condition #7’s schedules…|
|+275ms|║║Condition #7 evaluated true (7ms)|
|+276ms|║║Cancelling condition #1’s schedules…|
|+277ms|║║Condition group #1 evaluated true (state changed) (27ms)|
|+280ms|║║Cancelling statement #4’s schedules…|
|+290ms|║╚Execution stage complete. (46ms)|
|+292ms|╚Event processed successfully (292ms)|>

#2

The problem is that you have {Door} set to a contact sensor. That doesn’t support “unlocked”. You need to set it to be your door lock or change the event handler to be “{Door}'s contact changes to open”. Either one would work.

#3

I don’t know why it’s appearing as a contact sensor. I never added a contact sensor, only an electronic lock. I verified that I added it as an electronic lock. I deleted webcore from my app. Added it back in along with the devices but the lock is still showing up as a contact sensor. Is there a bug i’m missing. It’s a Schlage Connect BE469NX.

#4

Hmmmm, what DTH are you using in ST? Is it custom or the built-in one? Also, in your webCoRE setup (SmartApps -> webCoRE->Settings->Available Devices->Available Devices->on the ST side, can you remove the lock from Actuators and add it in the “Which electronic locks” section?

It could be that webCoRE is getting confused because of the DTH from ST.

#5

I originally had the device in the electronic locks section. I moved it to continue testing. I’m using a custom DTH by Rboy. I didn’t have this problem with the older core app. If the DTH is the issue is the only recourse to not use the custom DTH?

#6

Perhaps. For all my locks, I moved away from custom DTHs and just went with the built-in DTHs. They don’t have all the bells and whistles of RBoy’s DTHs and apps, but I use webCoRE to replicate a lot of that.

#7

I pinged Rboy. If they can’t find an issue then I will have to move to the ST DTH.

#8

I use RBOy DTH with my Schlage lock and it works to turn on lights so I don’t think it is an RBoy issue. When I take a green screenshot of one of my pistons the lock shows as contact sensor but it shows as a lock and works fine in the actual piston.

Is the issue your turn in command? It shows turn all on, maybe just try Turn On. And in the With make sure the Lights are set to All Of.