[RELEASE] ZConnect Garage Door Controller driver

⚙️ Custom Apps and Drivers
41

I just ran configure on mine. I don't get any errors. The "Null object" error normally occurs when there is a required entry missing, like one of the parameters field is blank.

I haven't had to change parameter 26, so I can't really offer any insight. I might have a go at using the Basic Z wave tool on mine when I get home tonight.
BTW -My contact sensor and switch responses have been almost instantaneous, right out of the box.
Can't understand why your sensor responses are so slow. How far is the unit from your hub?

1 Like
42

it's gone away now, no idea why.

Thanks, I'd appreciate it. I added Sensor 1 & 2 timer reporting values to your driver and the result is the same:

https://www.dropbox.com/s/cotysgk2alw8yjg/ZConnect%20Garage%20Door%20Control%20Parent.groovy?dl=0

It's really bizare as I cant even return it to the default values:

infoConfigurationReport- parameterNumber:31, size:2, value:300

It stays stuck on 8

Yeah I think mine is faulty, Im waiting for support to get back to me.

It's only one Z-wave device hop to the hub.

43

Just tried changing parameter 26 with the Basic Z Wave Tool. Same result as you. Stuck on a value of 8. There's some talk on the Basic tool thread about certain parameters that are hard to/won't change. Something to do with 2 byte hex values, I think.
Luckily my door operation seems unaffected.

1 Like
44

Interesting, cause doing it from my additions to your driver produce the same result. The manual doesn’t say anything about storing the values as hex, only base 10 numbers.

45

Hi all,

dJOS I have the exact same issue as yourself with the second contact sensor input shows up under the child devices but with no status of any sort. Did you manage to work this out?

46

Unfortunately no. Luckily I was able to get a swap (and partial refund) with a Fibaro Smart Implant.

47

For some reason mine has now started working don’t know what changed. Also I modified the code to have debug log switch in the device page as I had to make a rule to run a refresh to update the device and the logs were filling up I couldn’t find other important info

48

Glad to see it’s working for you. I’d like to be able to turn off debug logging too. It does tend to flood the logs. I’ll look into changing my code. I recently modified a virtual garage door device and app to use both of the contact sensors for open and closed, rather than the tilt/accel sensor. I found that wind shaking my door was giving me false indications. With two contact sensors my door position and status is much more accurate.

49

Thanks dazpad,

Here’s the code with the added debug option if anyone wants it.
Thanks @dazpad dazpad for the code to make it all work

50

Thanks Dazpad for sharing and supporting this App. I have had a similar experience to others in that the parent device works correctly but the two child sensors do not (I haven’t tried to use the child relay). CH3 corresponds to S2 and displays correctly ie Current States contact closed or contact opened but it does not update UNLESS Refresh is pressed on the parent.
If there is a change of state ie the contact on S2 or S1 either closes or opens, the change is never notified. However as soon as Refresh is pressed on the parent it updates correctly.
I don’t understand the code enough to try and follow it but hopefully you can?

51

Hi @andrew9. I'm having similar issues with my 2 units. When I first wrote the driver it worked great, pretty much instantly changing state. Over the last six months or so I see that there are many users having issues with contact sensor devices not updating, not just those of us with a Z Connect unit. I think it may be something to do with the firmware updates that have been rolled out for the hub. I'm not a coder by any measure, I "frankensteined" the code together using pieces of other drivers. I will do some research and see if there is anything that can be done. It may come down to hardware incompatibility between the unit and the Hubitat hub, due to changes in the Z Wave system.
In the meantime I've had to use an ESP32 programmed with Hubduino to handle the sensors for my garage. Responses are lightning quick, just like my Z Connect used to be.

52

Thanks Dazpad. Maybe it because it's only a Zwave and not Zwave Plus product?

53

And yet the first identified command cluster is 0x5E which is, according to my research is the device Z wave plus info. I have made some progress with my investigation. My original unit, which I changed parameter 26, do do with sensor reporting intervals, is totally unreliable. Not only that, but the parameter refuses to change back (the default is 300 seconds). As a result it's continually dumping stuff to the logs, choking up the Z Wave bandwidth.
I've since taken a new unit, leaving parameter 26 untouched, and joined it to my hub. It works perfectly. Sensor updates are within a second and it doesn't flood the logs. My next step is to swap out my old unit, put in the new and see how it performs in situ. I'm going to fire up an old Vera hub I have and try and reset the parameters of the old unit with that.
I'll try and post a video of my new unit in my test rig, showing dashboard response times.

54

Thanks for creating this dazpad. There's a typo in the current commit on line 24 (missing quote) which prevents the driver from being loaded.

Not a big deal and easy to fix, however I would like to make other improvements and can't edit the file in Windows. Turns out directories and files ending in a full stop aren't valid Windows filenames. Are you able to rename the folders IStatistica Sensor Device. and ZConnect Garage Control. so they don't end in full stops?

55

Thank you and done! Funny, I don't usually use punctuation in my folder names. Can't explain how they got in.

56

@andrew9, I've put the new unit in. It seems to be working fine. Both sensors are updating properly although I sometimes get a small delay (2-3 seconds) in the dashboard indications. Don't know if this is Z Connect or Hubitat related.

For reference, here is the parameter dump from the working unit. Haven't tried "fixing" the old unit yet.

Z Connect Garage Door Parameter Dump

dev:19022021-02-09 11:21:40.334 infoConfigurationReport- parameterNumber:50, size:1, value:0
dev:19022021-02-09 11:21:39.189 infoConfigurationReport- parameterNumber:43, size:1, value:0
dev:19022021-02-09 11:21:38.723 infoConfigurationReport- parameterNumber:42, size:1, value:0
dev:19022021-02-09 11:21:38.621 infoConfigurationReport- parameterNumber:41, size:2, value:300
dev:19022021-02-09 11:21:38.501 infoConfigurationReport- parameterNumber:40, size:2, value:1
dev:19022021-02-09 11:21:38.108 infoConfigurationReport- parameterNumber:37, size:2, value:0
dev:19022021-02-09 11:21:38.010 infoConfigurationReport- parameterNumber:39, size:1, value:0
dev:19022021-02-09 11:21:37.871 infoConfigurationReport- parameterNumber:38, size:2, value:0
dev:19022021-02-09 11:21:37.630 infoConfigurationReport- parameterNumber:36, size:2, value:300
dev:19022021-02-09 11:21:37.525 infoConfigurationReport- parameterNumber:35, size:2, value:1
dev:19022021-02-09 11:21:37.171 infoConfigurationReport- parameterNumber:32, size:2, value:0
dev:19022021-02-09 11:21:37.060 infoConfigurationReport- parameterNumber:34, size:1, value:0
dev:19022021-02-09 11:21:36.905 infoConfigurationReport- parameterNumber:33, size:2, value:0
dev:19022021-02-09 11:21:36.639 infoConfigurationReport- parameterNumber:31, size:2, value:300
dev:19022021-02-09 11:21:36.463 infoConfigurationReport- parameterNumber:29, size:1, value:0
dev:19022021-02-09 11:21:18.607 infoConfigurationReport- parameterNumber:26, size:2, value:300
dev:19022021-02-09 11:21:17.130 infoConfigurationReport- parameterNumber:26, size:2, value:300
dev:19022021-02-09 11:21:14.824 infoConfigurationReport- parameterNumber:24, size:1, value:0
dev:19022021-02-09 11:21:14.514 infoConfigurationReport- parameterNumber:23, size:1, value:0
dev:19022021-02-09 11:21:13.984 infoConfigurationReport- parameterNumber:21, size:1, value:0
dev:19022021-02-09 11:21:13.864 infoConfigurationReport- parameterNumber:22, size:1, value:0
dev:19022021-02-09 11:21:13.756 infoConfigurationReport- parameterNumber:20, size:1, value:0
dev:19022021-02-09 11:21:13.183 infoConfigurationReport- parameterNumber:16, size:1, value:0
dev:19022021-02-09 11:21:12.719 infoConfigurationReport- parameterNumber:15, size:1, value:0
dev:19022021-02-09 11:21:12.626 infoConfigurationReport- parameterNumber:12, size:2, value:5
dev:19022021-02-09 11:21:12.502 infoConfigurationReport- parameterNumber:14, size:1, value:0
dev:19022021-02-09 11:21:12.421 infoConfigurationReport- parameterNumber:13, size:2, value:0
dev:19022021-02-09 11:21:12.106 infoConfigurationReport- parameterNumber:11, size:2, value:5
dev:19022021-02-09 11:21:11.758 infoConfigurationReport- parameterNumber:10, size:1, value:0
dev:19022021-02-09 11:21:11.680 infoConfigurationReport- parameterNumber:9, size:1, value:0
dev:19022021-02-09 11:21:11.556 infoConfigurationReport- parameterNumber:8, size:1, value:0
dev:19022021-02-09 11:21:11.392 infoConfigurationReport- parameterNumber:6, size:2, value:0
dev:19022021-02-09 11:21:11.285 infoConfigurationReport- parameterNumber:7, size:1, value:0
dev:19022021-02-09 11:21:11.116 infoConfigurationReport- parameterNumber:5, size:2, value:0
dev:19022021-02-09 11:21:10.746 infoConfigurationReport- parameterNumber:2, size:2, value:10
dev:19022021-02-09 11:21:09.698 infoConfigurationReport- parameterNumber:3, size:2, value:10
dev:19022021-02-09 11:21:09.490 infoConfigurationReport- parameterNumber:1, size:1, value:0

57

Thanks Dazpad
I have compared it to my parameters and they are identical except for 1 which I changed from zero to 1. I have now added a second magnetic contact to monitor door fully open. I have also added a notification rule to report if the status of door down sensor changes and it all works EXCEPT that it requires a manual refresh of the parent device first. It takes about 3-5 seconds to update the dashboard from the time of the manual refresh.

58

@dazpad,

I've submitted a pull request with some changes. These are mostly to do with the way settings are displayed, cleaning up the interface a little.

We can now do this:

image
image886×859 33.3 KB

Let me know if you approve or would like to suggest any changes. My next bit of work will be to fix up child device handling and give the driver GarageDoorControl capability.

59

Thanks mate, looks great. I said at the time I first released the driver that I had very limited (read "none") programming experience. This is exactly the sort of input I was hoping for.
Cheers.

60

No problems @dazpad, happy to help. And I've noticed you've already seen to the latest PR I sent. Thanks for merging it in.

Everyone, the previous release had an issue with the wrong value being sent from the drop down selectors in preferences to the zConnect device. Anyone that used that version of the driver and saved preferences while either relay or sensor preferences were visible will have incorrect (or unintended) values for some settings.

Recommend downloading the latest version of the driver which corrects this. Load the preferences and and save them without making any changes to get the correct settings back. I know it's a bit hard to keep track of versions at the moment, I'll be adding a version number to the next merge.

Apologies for any problems this might have caused.

@dazpad, for the next release I'm interested in submitting this driver for inclusion in Hubitat Package Manger. Do you have any issues with this?