"Dumb" switch not opening garage


#1

1) Give a description of the problem
I have a GoControl/Linear GD00Z-4 Z-Wave Garage Door Opener that works just fine opening my garage when “open” is pressed in the App… In my house I have a WT00Z-1 “dummy” switch. When you turn the switch on, the garage door should open (as if you’d pressed “open” in the SmartThings app).

2) What is the expected behaviour?
The garage door opens!

3) What is happening/not happening?
The garage door does not open, but the switch LED does go out and reports “on”.

**4) Post a Green Snapshot of the piston!

Thoughts?


#2

Have you tried just switch changes to on and take the “physically” part out of it?


#3

Just did (and updated above snapshot). No good.


#4

Just because I am not familiar with the GoControl units, that is the “Contact Sensor 6” that’s showing in this piston? Its odd to me that that device would be listed as a contact sensor?

Also next would be to put the piston in trace and hit the switch and post the logs fyi.


#5

… with Log Level set to Full


#6

is this Contact Sensor 6 is WT00Z switch?


#7

Yes it is!

I’m sorry for the delay - I had a few projects come due! I’ll upload the log tomorrow.


#8

Sooo… Huh. I have logging at full now. I clicked “trace”. I went and pressed the switch. I came back to my PC and… Nothing? No log entry. “The log is empty.”

Clearly, I have greater issues…


#9

Try actually doing the action of pressing that switch thats the trigger


#10

I’m not sure what you mean. What switch that’s the trigger? We’re talking one switch here -the dumb switch that I want to use to control the garage door zwave controller. That controller doesn’t have a physical switch.


#11

Your switch that you are using to try and open the garage, the WT00z-1 unit. Essentially we are wanting to go through the motions of how this would function in real life as opposed to hitting test on the piston.


#12

Well, yes, in that previous post I said I went and pressed the switch after I set logging to full and clicked trace…


#13

Huh, that was odd - the logging didn’t show up until I closed the tab and then opened a new one.
ANYWAY - here’s the logging:

12/17/2019, 9:12:51 AM +219ms
+0ms ╔Received event [ZZLeft Garage Door].switch = on with a delay of 199ms
+54ms ║RunTime Analysis CS > 19ms > PS > 28ms > PE > 7ms > CE
+56ms ║Runtime (36398 bytes) successfully initialized in 28ms (v0.3.110.20191009) (55ms)
+57ms ║╔Execution stage started
+64ms ║║Comparison (enum) on changes_to (string) on = true (1ms)
+65ms ║║Cancelling condition #2’s schedules…
+66ms ║║Condition #2 evaluated true (5ms)
+67ms ║║Cancelling condition #1’s schedules…
+68ms ║║Condition group #1 evaluated true (state changed) (7ms)
+70ms ║║Cancelling statement #3’s schedules…
+152ms ║║Executed physical command [Left Garage Door].open() (79ms)
+154ms ║║Executed [Left Garage Door].open (81ms)
+156ms ║╚Execution stage complete. (99ms)
+157ms ╚Event processed successfully (157ms)

Clear

Full


#14

Glad at least the logging is working, can you also post the green snapshot with trace enabled so that it can be compared to this log please?


#15

Of course! (I’ve never USED trace before!)


#16

It appears that the piston sent the open command but you did not see it actually open? All of the rest of the log looks fine with the piston as well.

So its back to some basic questions I feel. In your WITH on line 21 you are using a device called Contact Sensor 6. Just want to verify that unlike its name implies, this is actually a device capable of performing a task to open? None of my contact sensors actually open or close something, they just report open or closed. In my mind this line 21 device should be whatever you have named your GoControl/Linear GD00Z-4 Z-Wave Garage Door Opener.


#17

The garage door did not open, no. So you’re saying that, from how it appears, the piston is working properly and the door should have opened?

Contact Sensor 6, when I edit and look at it, is definitely the label I have for the zwave garage door opener - the GD00Z-4. I’m not sure why it’s called a Contact Sensor (although the GD00Z-4 physically consists of two parts, the main part that receives the zwave signal and acts as a switch to tell the garage door to open or close, and a tilt sensor that tells the main part whether the actual door is opened (tilted) or not.


#18

Yes, WebCore Piston did in fact send the command to open as its written in the piston.

I suspect your issue to be here. It could be that we are talking to the wrong portion of this device but I have no experience with this particular unit. In your SmartThings device list does it populate as two different devices by any chance? Also what device handler are you using with this unit?


#19

So - maybe possibly there’s an issue with the garage door opener itself. When the storm stops I can check it out (snow!)

Nope, just one device, and the handler is called (under “type”) quite simply: Z-wave Garage Door Opener


#20

I am in Florida so dont have that issue today :slight_smile:

Once you are able to again I would be curious to see if you go into SmartThings and open the door to see if it does work. Might not be a bad idea to then check the events list/log for that device in SmartThings IDE to get a better idea of what it actually did.