Mimolite garage door device driver

🛎️ Get Help
26

Tried the stock Hubitat mimolite device handler and just didn't like how it had to be setup.

So I updated the original mimolite DH to be backwards compatible with the stock Hubitat DH and also added door timing and s/w lock.
(thanks to @JasonJoel and @mike.maxwell for helping)

This way is much easier to display and control on your dashboard as well.

the s/w lock ensures that hubitat can not open the door when locked.
Think of it like the manual lock option on the garage door panel on your garage door wall.
not really a mimolite issue but saw when the Hubitat hub started slowing down and was doing a nightly backup that if the hub was running slow it could cause an arrival device to go departed then back arrive again which could accidentally fire rules. Adding more conditions to rules also helps prevent this but adding a s/w lock option will help a lot as well.
Just add lock the garage door to a secure house rule.
To be clear

  • the s/w lock function does not physically disable the lock if you were to put "unlock" and "open door" when you arrived in a rule it would open the door.
    You probably would not use it that way.
    Use the lock function as a separate rule to secure the door unless your car is like mine and only powers the arrival sensor when the car is running (so a slow hub would not affect it).
  • The lock function only s/w locks the garage door when it is closed not open
  • If you manually open the garage door the garage door will automatically go to unlocked.
    - If you use the "push" command in your rules it will bypass both the lock and door timing you need to use the "open/close" or "on" command.
  • added lock and door timing to push command
1 Like
27

Updated the mimolite DH above
added logic and cleaned up the code
So the DH should never get out of sequence with the garage door and the garage door can not be activated unless open or closed for a set time (default is 20 seconds).
The momentary switch has been set to default 3 seconds on if you want it disabled then set to 0 in the device settings.

28

Updated the device handler, and now I have no door function? Any ideas? I changed back to old DH and it works.. Thank you.

29

@jesse.fetterman strange I just copied and pasted from the github back to my hub just to make sure I didn't fat finger anything and it still works fine.
If you enable debug logging and try and open the door do you get any errors?
nothing happens if you try all commands?

30

Just tried new DH again and got the same results. Tried all commands and only refresh works, not sure why. The log says, no open command sent door is already open. However in the device, the current state is closed and the door is physically closed.

image
image1125×2436 476 KB

31

try and use the basic Zwave tool DH
you do not have to input anything just select the top 4 get report buttons at the top of the page then look at your logs page.
one of your parameters is different than mine I would be curious to which one.
My DH only reads parameter 8,9,and 11 and pushing config on my DH will only write those 3 parameters to match mine and sets groupingIdentifier 2 and 3 .
and your jumper is off of P5 prior to installing I assume?

Parameter list

I see from your logs your parameter 9 is set to 3 and mine set at 5 but that just tells device to send multivalue sensor updates every (1 = 10 seconds) x seconds.
here are the rest of my parameters:

VersionReport- applicationVersion:1.17

VersionReport- zWaveProtocolVersion:3.42

VersionReport- zWaveLibraryType:Routing Slave

ConfigurationReport- parameterNumber:11, size:1, value:30

ConfigurationReport- parameterNumber:9, size:1, value:5

ConfigurationReport- parameterNumber:8, size:1, value:3

ConfigurationReport- parameterNumber:7, size:1, value:-2

ConfigurationReport- parameterNumber:6, size:1, value:-1

ConfigurationReport- parameterNumber:5, size:1, value:-85

ConfigurationReport- parameterNumber:4, size:1, value:-69

ConfigurationReport- parameterNumber:3, size:1, value:0

ConfigurationReport- parameterNumber:2, size:1, value:0

CommandClassReport- class:0x25, version:1

CommandClassReport- class:0x85, version:1

CommandClassReport- class:0x70, version:1

CommandClassReport- class:0x35, version:1

CommandClassReport- class:0x31, version:1

CommandClassReport- class:0x30, version:1

CommandClassReport- class:0x71, version:1

CommandClassReport- class:0x86, version:1

CommandClassReport- class:0x72, version:1

AssociationReport- groupingIdentifier:5, maxNodesSupported:2, nodes:[]

AssociationReport- groupingIdentifier:4, maxNodesSupported:2, nodes:[]

AssociationReport- groupingIdentifier:3, maxNodesSupported:2, nodes:[1]

AssociationReport- groupingIdentifier:2, maxNodesSupported:2, nodes:[1]

AssociationReport- groupingIdentifier:1, maxNodesSupported:2, nodes:[1]

32

image
image1125×2436 499 KB
image
image1125×2436 499 KB
image
image1125×2436 542 KB
image
image1125×2436 505 KB

33

my config cmd on my DH also sets
groupingIdentifier 2 and 3 which
// enable alarms to be sent to hub
// enable multivalue sensor updates to be sent to hub

34

Where do I set that?

35

just use my mimolite DH and select configure in the device page,
I cleaned up my parameter results in my post above to make them easier to read

36

Maybe I’m missing something? when I hit configure, nothing happens. Do I need to make these changes in the basic zwave tool?

37

no that is correct mine writes theses settings
what parameter results did you get when you use the basic Zwave tool DH?

38

you may have to match a parameter using the Zwave tool DH

39

I posted pictures above of the results

40

I do not see Parameters 2,3,4,5,6 and idendtifier 2 and 5 in your pictures
looks like groupingIdentifier:3 is not set
mine reads
groupingIdentifier:3, maxNodesSupported:2, nodes:[1]
yours reads
groupingIdentifier:3, maxNodesSupported:2, nodes:[]

41

Also what are your versionReports ?
mine:

VersionReport- applicationVersion:1.17

VersionReport- zWaveProtocolVersion:3.42

VersionReport- zWaveLibraryType:Routing Slave

42

I would try with basic Zwave tool DH to set
parameter 9 size 1 value 5
parameter 11 size 1 value 30

just to see if they are taking writes and changing
and your jumper is off P5 on your mimolite circuit board correct?

43

to be clear using my mimolite DH
When you select configure the logs will just say:

momentary switch state enabled 3 sec
Configuring defaults

Then
selecting refresh afterwards the logs will say:

ConfigurationReport- parameterNumber:11, size:1, value:30
ConfigurationReport- parameterNumber:9, size:1, value:5
ConfigurationReport- parameterNumber:8, size:1, value:3
Refreshing

44

Ok, I changed the perimeters manually and then tried the new DH again. Nothing. Yes, my jumper is removed. I have Mimolites on 12 overhead doors and none work with new DH. I don’t get it.

image
image2958×1536 1.32 MB

45

When I revert back to your last device handler, dated 9/24/19 everything works.