I have App Code to support the Zooz Zen17 as a Garage Door Opener (GDO). The first time I created the App, it showed up in the Devices page. That's what I expected.
I had issues with sensors not working, and discovered a more current driver to use. I removed the GDOs created, Removed the App code and the Device code. I also excluded the Zen17. In other words, I tried to start over, and I think I basically succeeded.
I installed a much newer driver and re-included the Zen17. All the basics seemed to work reliably.
I added the App code for the Zooz GDO Opener child and the Zooz GDO Opener App. I created a new GDO App. It didn't show up in Devices. I tried removing, adding it back, rebooting, etc.
I'm using the instructions here and specifically focused on step 3 of this Zooz support page . I make it through "click done". The next instruction is to go to the Devices page to see the new GDO. Nope, not there.
Devices created by apps can but apps dont. My guess is there is an error in your app config and the device is not being created. Maybe turn on debugging in the app resave and check the logs.
Once configured, the Zooz GDO app should create a garage door device, so that part is true.
Aside from starting over again with a fresh app install (first ensuring any existing installation is fully removed), I don't have any troubleshooting advice for OP, but they aren't wrong that a corresponding device should be showing up on their Devices page.
Before attempting the app re-install, I would fist triple-check that the Z17 relay & sensor are working tip-top WRT raw control of the opener/door. Once certain that part is fully OK, then I'd work on setting the app up.
Alright, these replies say I am not crazy. I can imagine the case that, when I thought I'd purged all traces of my original install and thought I was starting over, perhaps was not as clean as I'd hoped.
Turning on debug, ok. I'll give that a shot.
The hardware device and the base integration with Hubitat are working robustly. I've been using it quite a bit in the last 24 hours. Sensors and Relay behaviors are as expected. I don't recall ever seeing one instance where they were not as expected. (The exception is my first attempt that used an old driver, and caused me my initial angst.)
That brings me back to debugging and possible "leftover" crumbs from my first install that is fouling things up.
I'll post back later. Right now ... the lawn is calling for a good mowing.
The terminology used in shorthand phrases is often confusing to new members.
Code has to be available ON the hub to be used. Hubitat themselves have a big advantage in the fact they can include their own Apps and Drivers with zero extra steps. The Community has to get the code onto the hub first. That's where HPM (Hubitat Package Manager) thrives. It makes it so much easier to get code onto the Hub, and over time, remain up to date.
Unfortunately the Zooz set of code you're using is not in HPM. (I sent a message to Zooz trying to correct that.. but their answer will be too late to benefit you.) Having added the Code the next step is the same for Hubitat code or for Community code. Either way, you have to "install" the App. (Community Driver Code just need to be added to the hub to put them on the same footing as Hubitat's own drivers.... automatically available.)
The advice above is, I think, to roll back to the point after adding the Code and before "installing" the App. The App discussed here is a Parent/Child app and the installed app will detect it's child and, once you select devices IN THE APP, it will create matching child Devices as well.
You need to confirm that you've added the 3 bits of Code to the hub... two Apps, one Driver. The App will bark if it can't find the child (app or driver). I believe the advice is to go into the App and then click the Remove all Garage Doors button. Once you complete that step, go back to the Apps page and do another Add User App to start over.
Well, this got interesting. I sought to create a new instance of a GDO, "GDO-New". This caused the following three lines in the log:
app:1842025-04-26 05:18:28.579 PMerrorUnable to create the Garage Door. You must install the Zooz Garage Door Driver in order to use this App.
app:1842025-04-26 05:18:28.550 PMdebugCreating GDO-New
app:1842025-04-26 05:18:25.489 PMwarninstalled()...
That would seem to mean that the "tried-&-true" app is expecting the older driver, not the more recent that Jeff (jtp10181) is maintaining.
Now I wonder how others are able to use the older "tried-&-true" Zooz app with this newer driver.
Thoughts?
EDIT: Now I wonder if there is a differnt Zooz GDO out there. I keep reliably finding the one I have, but I could simply be in a cup de sac with my search terms.
Over in your other topic, you were given this advice:
with it's link to the Zooz page defining the 3 bits of code to add to the hub. Only you know if you did that or not.
As to the "Jeff's Z17driver" that's for the physical device. Nothing about the Zooz Garage Door has to do with that. just in case you didn't have enough confusion.
Let me back up a bit and say that the Zooz Garage Door package assumes you have the 3 physical devices working. You need a switch (the Z17) that will make the garage door motor move, and a Contact Sensor that can indicate the door is open or closed. They each need to be working in Hubitat BEFORE the Zooz Garage Door package is installed. The Zooz package will as you to identify them AND will then create another virtual Garage Door device "that sits between" the app and the various physical devices.
Ok, now light bulbs are going off. My first attempt had the three code packages as called out in the Zooz support page. I had an issue with the sensors not responding. That's when I searched around and found Jeff's driver. I uninstalled everything and then assumed the driver could be swapped out. There's the issue. The three-part package in the Zooz page is self-consistent, then.
From this I assume that:
I need to go back to the original 3 package install to get a basic opener working. I need to solve my sensor issue (if it is still there) with that set of files.
Jeff's advanced driver is if I need to do something beyond what the basic "tried-&-true" GDO does. If I want that driver, I am on my own to work through my own app to satisfy my requirements that are beyond the basic GDO function.
And now everything works. Reliably. Using the original code that for some reason didn't work (the sensors) the first time.
Thank you for your patience. This back and forth with everyone has been useful.
Now ... to find a way to disable the "are you sure?" prompts. And, before you say anything, I have seen several threads on this arguing pros and cons of providing that option; it's not there as of now. Do I delve back into programming and take this up? I have other more pressing priorities.
just in case you didn't have enough confusion.
