Garagedoor shows open in Homekit when it is closed...

[7rdr7]

I’ve got the Aetoec controllers and used virtual switches/variables to invert the status, and it works fine.

[juntta]

Ok, virtual devices & variables did the trick and Open/Closed status working now.

However, Opening/Closed states are missing. Is it possible to get those states working with same values that papamac mentions in Virtual Garage Door integration thread:

The Apple HimeKit framework permits 5 door states values (see https://developer.apple.com/documentati ... edoorstate). These are: 0 -> open, 1 -> closed, 2 -> opening, 3 -> closing, and 4 -> stopped.

[papamac]

Although I'm not familiar with the Aeotec device, it seems that it is a z-wave device that maintains an onOffState that is used by HKLS and HomeKit. This state is used both to report the currentState and to set the targetState. The Aeotec device reports that the onOffState is off when the door is closed and on when the door is open. HKLS and HomeKit use an inverse logic. They assume that the onOffState is on when the door is closed and off when it is open. So you have figured a way to invert the logic and the current State reports correctly in HomeKit. So far, so good... but I'm guessing that you still can't command the door to open or close with HomeKit and you don't see the intermediate states (opening/closing) or the obstructed state.

To go to the next level, you need to introduce a new doorState (with the values that you cite) as I did with the VGD plugin. Glenn and I modified HKLS to use the doorState in lieu of the onOffState to set the HKLKS currentState and targetState if it exists in the device's states dictionary. This works fine for VGD and maintains compatibility with other devices that use the onOffState. The obvious solution to your problem is to implement a similar approach in the Aeotec z-wave device driver. If done in the same way as VGD there would be no need for new modifications to HKLS. It is , however, something that would have to be done by the Indigo support team (Jay or Matt). You may want to inquire about this.

It is also possible that my VGD plugin can be modified to accept the Aeotec device with its existing driver. I will look at the device and determine whether or not this is practical within the constraints of the plugin. Please provide the exact model of the Aeotec device and an Indigo device dump showing all properties and states.

Regards,

David (aka papamac)

[juntta]

Thanks David for you reply.

You were right, I wasnt able to control garage door with HKLS directly. I did manage to control it through Indigo actions published to HomeKit.

If I remember right with HomeKit Bridge it did show also those in progress states as well.

Hmm, not sure if I fully follow the next steps you suggested. If I understood correctly with current functionality (either with Indigo/HKLS/VGD) its not possible to publish those middle states to HKLS? Is it possible to expand virtual devices states with some plugin or python scripts in trigger etc?

Here is device dump for the garage door opener:

Code: Select all

 Indigo Z-Wave Version: 2022.2.1
Node ID: 90
Model: Garage Door Controller (ZW062)
Model ID: 0003003E
Manufacturer: Aeon Labs
Manufacturer ID: 0086
Protocol Version: 4.54
Application Version: 1.14
Model Definition Version: 3
Library Type: 3
Class Name: Secure Barrier Add-On
Class Hierarchy: 04 : 40 : 07
Command Class Base: 66
Command Versions: 20v1 85v1 82v1 66v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 5Av1 7Av1 5Ev1 25v1
Encryption Status: Enabled for Commands 82 85 86 59 5A 25 66 70 71 72 73 7A
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming, security
Neighbors: 
Associations: 1:[1] 2:[]
Config Values: 80:2 35:43 37:167905280 38:134416384 39:100927488 40:33883392 252:0



Script                          address : 90
batteryLevel : None
buttonConfiguredCount : 0
buttonGroupCount : 0
configured : True
description : 
deviceTypeId : zwRelayType
displayStateId : onOffState
displayStateImageSel : PowerOff
displayStateValRaw : False
displayStateValUi : off
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState : 
folderId : 305222074
globalProps : MetaProps : (dict)
     com.GlennNZ.indigoplugin.HomeKitLink-Siri : (dict)
          HomeKit_audioSelector :  (string)
          HomeKit_bridgeUniqueID :  (string)
          HomeKit_deviceSensor :  (string)
          HomeKit_deviceSubtype :  (string)
          HomeKit_inverseSelector :  (string)
          HomeKit_tempSelector :  (string)
          homekit-name :  (string)
     com.autologplugin.indigoplugin.zwaveinterpreter : (dict)
          zwave_interpretation : true (bool)
     com.perceptiveautomation.indigoplugin.zwave : (dict)
          SupportsStatusRequest : false (bool)
          address : 90 (integer)
          indigoObjVersion : 10 (integer)
          modelNameAndFirmware : Garage Door Controller (ZW062), firmware 1.14 (string)
          propsPushTickler : 2 (string)
          tempAlwaysFalse : false (bool)
          userConfigVal034 : false (bool)
          userConfigVal035 : 43 (integer)
          userEnergyPollingEnabled : false (bool)
          userPollAfterActivity : true (bool)
          userPollInterval : 0 (integer)
          userPollingEnabled : true (bool)
          userWakeInterval : 60 (integer)
          version : 1.14 (string)
          zwAppVersMajor : 1 (integer)
          zwAppVersMinor : 14 (integer)
          zwAssociationsMap : (dict)
               g1 : (list)
                    Item : 1 (integer)
               g2 : (list)
          zwAssociationsMapStr : 1:[1] 2:[] (string)
          zwClassCmdBase : 102 (integer)
          zwClassCmdMap : (dict)
               c102 : 1 (integer)
               c112 : 1 (integer)
               c113 : 1 (integer)
               c114 : 1 (integer)
               c115 : 1 (integer)
               c122 : 1 (integer)
               c130 : 1 (integer)
               c133 : 1 (integer)
               c134 : 1 (integer)
               c152 : 1 (integer)
               c32 : 1 (integer)
               c37 : 1 (integer)
               c89 : 1 (integer)
               c90 : 1 (integer)
               c94 : 1 (integer)
          zwClassCmdMapStr : 20v1 85v1 82v1 66v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 5Av1 7Av1 5Ev1 25v1 (string)
          zwClassIds : (list)
               Item : 4 (integer)
               Item : 64 (integer)
               Item : 7 (integer)
          zwClassInstanceCountMap : (dict)
          zwClassInstanceCountMapStr : - none - (string)
          zwClassName : Secure Barrier Add-On (string)
          zwConfigVals : (dict)
               p252 : 0 (integer)
               p35 : 43 (integer)
               p37 : 167905280 (integer)
               p38 : 134416384 (integer)
               p39 : 100927488 (integer)
               p40 : 33883392 (integer)
               p80 : 2 (integer)
          zwConfigValsStr : 80:2 35:43 37:167905280 38:134416384 39:100927488 40:33883392 252:0 (string)
          zwDevSubIndex : 0 (integer)
          zwEncryptClassCmdMap : (dict)
               c102 : true (bool)
               c112 : true (bool)
               c113 : true (bool)
               c114 : true (bool)
               c115 : true (bool)
               c122 : true (bool)
               c130 : true (bool)
               c133 : true (bool)
               c134 : true (bool)
               c37 : true (bool)
               c89 : true (bool)
               c90 : true (bool)
          zwEncryptClassCmdMapStr : 82 85 86 59 5A 25 66 70 71 72 73 7A (string)
          zwEncryptionStatusStr : Enabled for Commands 82 85 86 59 5A 25 66 70 71 72 73 7A (string)
          zwEndpointClassMap : (dict)
          zwEndpointClassMapStr : - none - (string)
          zwEndpointDevTypeMap : (dict)
          zwEndpointDevTypeMapStr : - none - (string)
          zwFeatureListStr : routing, beaming, security (string)
          zwLibType : 3 (integer)
          zwManufactureId : 134 (integer)
          zwManufactureName : Aeon Labs (string)
          zwModelDefnVers : 3 (integer)
          zwModelId : 196670 (integer)
          zwModelName : Garage Door Controller (ZW062) (string)
          zwNodeNeighbors : (list)
               Item :
          zwNodeNeighborsStr :  (string)
          zwProtoVersMajor : 4 (integer)
          zwProtoVersMinor : 54 (integer)
          zwShowDumpDevToLog : true (bool)
          zwShowEnergyPollingUI : false (bool)
          zwShowMainUI : true (bool)
          zwShowManualModifyConfigParmUI : false (bool)
          zwShowPollingUI : false (bool)
          zwShowSubmitModelInfoUI : false (bool)
          zwShowWakeIntervalUI : false (bool)
          zwWakeInterval : 0 (integer)
id : 149477386
lastChanged : 2023-04-24 21:27:43
lastSuccessfulComm : 2023-04-24 21:27:43
ledStates : []
model : Garage Door Controller (ZW062)
name : Autotallin nosto-ovi
onState : False
ownerProps : com.perceptiveautomation.indigoplugin.zwave : (dict)
     SupportsStatusRequest : false (bool)
     address : 90 (integer)
     indigoObjVersion : 10 (integer)
     modelNameAndFirmware : Garage Door Controller (ZW062), firmware 1.14 (string)
     propsPushTickler : 2 (string)
     tempAlwaysFalse : false (bool)
     userConfigVal034 : false (bool)
     userConfigVal035 : 43 (integer)
     userEnergyPollingEnabled : false (bool)
     userPollAfterActivity : true (bool)
     userPollInterval : 0 (integer)
     userPollingEnabled : true (bool)
     userWakeInterval : 60 (integer)
     version : 1.14 (string)
     zwAppVersMajor : 1 (integer)
     zwAppVersMinor : 14 (integer)
     zwAssociationsMap : (dict)
          g1 : (list)
               Item : 1 (integer)
          g2 : (list)
     zwAssociationsMapStr : 1:[1] 2:[] (string)
     zwClassCmdBase : 102 (integer)
     zwClassCmdMap : (dict)
          c102 : 1 (integer)
          c112 : 1 (integer)
          c113 : 1 (integer)
          c114 : 1 (integer)
          c115 : 1 (integer)
          c122 : 1 (integer)
          c130 : 1 (integer)
          c133 : 1 (integer)
          c134 : 1 (integer)
          c152 : 1 (integer)
          c32 : 1 (integer)
          c37 : 1 (integer)
          c89 : 1 (integer)
          c90 : 1 (integer)
          c94 : 1 (integer)
     zwClassCmdMapStr : 20v1 85v1 82v1 66v1 86v1 70v1 71v1 72v1 73v1 98v1 59v1 5Av1 7Av1 5Ev1 25v1 (string)
     zwClassIds : (list)
          Item : 4 (integer)
          Item : 64 (integer)
          Item : 7 (integer)
     zwClassInstanceCountMap : (dict)
     zwClassInstanceCountMapStr : - none - (string)
     zwClassName : Secure Barrier Add-On (string)
     zwConfigVals : (dict)
          p252 : 0 (integer)
          p35 : 43 (integer)
          p37 : 167905280 (integer)
          p38 : 134416384 (integer)
          p39 : 100927488 (integer)
          p40 : 33883392 (integer)
          p80 : 2 (integer)
     zwConfigValsStr : 80:2 35:43 37:167905280 38:134416384 39:100927488 40:33883392 252:0 (string)
     zwDevSubIndex : 0 (integer)
     zwEncryptClassCmdMap : (dict)
          c102 : true (bool)
          c112 : true (bool)
          c113 : true (bool)
          c114 : true (bool)
          c115 : true (bool)
          c122 : true (bool)
          c130 : true (bool)
          c133 : true (bool)
          c134 : true (bool)
          c37 : true (bool)
          c89 : true (bool)
          c90 : true (bool)
     zwEncryptClassCmdMapStr : 82 85 86 59 5A 25 66 70 71 72 73 7A (string)
     zwEncryptionStatusStr : Enabled for Commands 82 85 86 59 5A 25 66 70 71 72 73 7A (string)
     zwEndpointClassMap : (dict)
     zwEndpointClassMapStr : - none - (string)
     zwEndpointDevTypeMap : (dict)
     zwEndpointDevTypeMapStr : - none - (string)
     zwFeatureListStr : routing, beaming, security (string)
     zwLibType : 3 (integer)
     zwManufactureId : 134 (integer)
     zwManufactureName : Aeon Labs (string)
     zwModelDefnVers : 3 (integer)
     zwModelId : 196670 (integer)
     zwModelName : Garage Door Controller (ZW062) (string)
     zwNodeNeighbors :
     zwProtoVersMajor : 4 (integer)
     zwProtoVersMinor : 54 (integer)
     zwShowDumpDevToLog : true (bool)
     zwShowEnergyPollingUI : false (bool)
     zwShowMainUI : true (bool)
     zwShowManualModifyConfigParmUI : false (bool)
     zwShowPollingUI : false (bool)
     zwShowSubmitModelInfoUI : false (bool)
     zwShowWakeIntervalUI : false (bool)
     zwWakeInterval : 0 (integer)
pluginId : com.perceptiveautomation.indigoplugin.zwave
pluginProps : emptyDict : (dict)
protocol : ZWave
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
     onOffState : off (on/off bool)
subModel : ui=Garage Controller
subType : 
supportsAllLightsOnOff : False
supportsAllOff : False
supportsOnState : True
supportsStatusRequest : False
version : 1.14

[papamac]

A quick look at this has left me with more questions than answers. I'm interested in understanding how the Aeotec device works within Indigo... forget about HKLS/HomeKit for a while. Let's discuss a few topics:

1. Opening/Closing. The Aeotec device connects to the garage door opener by connecting to the wall button that is used to manually toggle the door open or closed. This implies that the Aeotec device acts as a smart relay that toggles the door without pressing the button. Is this true? Why are there 2 wires to the switch... are these 2 wires for only 1 circuit, or are there 2 switches and 2 doors? Does the Aeotec device respond to the Indigo turnOn/turnOff actions? If you do a turnOn, presumably the onOffState would transition from off to on, the door switch contacts would close, and the door will start opening. Since the same sequence is required to toggle the door closed, the device and the onOffState must have to go off so that they can be turned on again. When/how does this happen?

2. Tilt sensor. The included tilt sensor is mounted on the top segment of the door. If it works like others that I have seen, it is off when the door is vertical (closed) and on when it is horizontal (open). Is this sensor a separate z-wave device in Indigo, or does it report directly to the opener device? Either way, does Indigo have any access to its states?

Some of the answers to my questions may be obvious if could see the Aeotec device/action ConfigUIs. Please send screen shots of the important ones and I will continue to investigate.

It still seems possible that the Aeotec device could integrate with the VGD plugin. VGD uses relay and sensor devices to monitor and control the garage door. Possibly the Aeotec device could serve as a VGD "activation relay" and the tilt sensor could be a VGD "closed sensor". Suggest that you look at the VGD design WIKI at [url]github.com/papamac/VirtualGarageDoor[/url]. See if you think that there might be a match based on your knowledge of the Aeotec device.

I look forward to continuing this discussion.

David

[juntta]

1. Opening/Closing. The Aeotec device connects to the garage door opener by connecting to the wall button that is used to manually toggle the door open or closed. This implies that the Aeotec device acts as a smart relay that toggles the door without pressing the button. Is this true? Why are there 2 wires to the switch... are these 2 wires for only 1 circuit, or are there 2 switches and 2 doors? Does the Aeotec device respond to the Indigo turnOn/turnOff actions? If you do a turnOn, presumably the onOffState would transition from off to on, the door switch contacts would close, and the door will start opening. Since the same sequence is required to toggle the door closed, the device and the onOffState must have to go off so that they can be turned on again. When/how does this happen?

2 wires are connected to one door opener, just one circuit. Indigo turnon action turns Aeotec from off to on as you presumed. And off logic can be used after tilt sensor has reported complete cycle (closed -> opening -> open)

2. Tilt sensor. The included tilt sensor is mounted on the top segment of the door. If it works like others that I have seen, it is off when the door is vertical (closed) and on when it is horizontal (open). Is this sensor a separate z-wave device in Indigo, or does it report directly to the opener device? Either way, does Indigo have any access to its states?

Tilt sensor is reporting directly to opener to my knowledge. States are available through z-wave raw commands that I’ve discovered. So states (open, opening, closed & closing) can be triggered.

Some of the answers to my questions may be obvious if could see the Aeotec device/action ConfigUIs. Please send screen shots of the important ones and I will continue to investigate.

Well, not so much to see here:

It still seems possible that the Aeotec device could integrate with the VGD plugin. VGD uses relay and sensor devices to monitor and control the garage door. Possibly the Aeotec device could serve as a VGD "activation relay" and the tilt sensor could be a VGD "closed sensor". Suggest that you look at the VGD design WIKI at [url]github.com/papamac/VirtualGarageDoor[/url]. See if you think that there might be a match based on your knowledge of the Aeotec device.

I look forward to continuing this discussion.

David

Thanks David, will look into the wiki and let me know if there is something I can help you with.

[papamac]

Let me confirm my understanding of the opening/closing cycles. Based on your comments, here is what I think happens:

Opening: An Indigo turnOn action (or wall button pressed) activates the opener and begins the opening cycle
a. the onOffState presumably transitions from off to on and remains on throughout the opening cycle
b. Indigo turnOff (or additional turnOn) actions have no effect until the tilt sensor indicates that the door is open
c. the opener completes its operation, the onOffState remains on, the tilt sensor indicates open, and the turnOn/turnOff actions are re-enabled

Closing: An Indigo turnOff action (or wall button pressed) activates the opener and begins the closing cycle
a. the onOffState presumably transitions from on to off and remains off throughout the closing cycle
b. Indigo turnOn (or additional turnOff) actions have no effect until the tilt sensor indicates that the door is closed
c. the opener completes its operation, the onOffState remains off, the tilt sensor indicates closed, and the turnOn/turnOff actions are re-enabled

Is this how it works?

[juntta]

Let me confirm my understanding of the opening/closing cycles. Based on your comments, here is what I think happens:

Opening: An Indigo turnOn action (or wall button pressed) activates the opener and begins the opening cycle
a. the onOffState presumably transitions from off to on and remains on throughout the opening cycle
b. Indigo turnOff (or additional turnOn) actions have no effect until the tilt sensor indicates that the door is open
c. the opener completes its operation, the onOffState remains on, the tilt sensor indicates open, and the turnOn/turnOff actions are re-enabled

Closing: An Indigo turnOff action (or wall button pressed) activates the opener and begins the closing cycle
a. the onOffState presumably transitions from on to off and remains off throughout the closing cycle
b. Indigo turnOn (or additional turnOff) actions have no effect until the tilt sensor indicates that the door is closed
c. the opener completes its operation, the onOffState remains off, the tilt sensor indicates closed, and the turnOn/turnOff actions are re-enabled

Is this how it works?

Your assumptions are correct. Although I dont use the wall button on Aeotec so not 100% sure if it will operate same way.

I also have hardwired button to the actual garage door opener which stops door either is opening or closing and then second press changes direction. But thats not relevant here…

[papamac]

I've looked at the code and thought about this, and I think that the Aeotec device might work as an "activation relay". So I think that we should try an experiment. The procedure below will define a VGD device using the Aeotec device as the "activation relay" and then try opening/closing the door using the VGD device. If you can find some time, please follow the following steps:

1. Measure the open/close travel time for your door. It should be in the range of 10-15 sec. Measure the open and close times... they should be equal to within about 0.5 sec. Add 0.5 sec to your consensus measurement and save this number for use in defining the VGD device.
2. Download and install the VGD plugin from the Indigo Plugin Store.
3. From the Indigo Plugins menu, select Virtual Garage Door and then Configure...
4. In the ConfigUi window select the Debug logging level, click Log Door State Tracks, and then click Save
5. Back in the Indigo Home window, click New...
6. In the edit device window, select Type: Virtual Garage Door, and Model: Virtual Garage Door Opener
7. In the ConfigUi window, enter your door's open/close travel time, select your Aeotec device as the activation relay, and click Save
8. Give your VGD device a name and then close the edit device window

Here we go.....

9. Make sure that your garage door is clear to open and close.
10. Select your VGD device in the home window; the device details at the bottom of the window should show closed
11. In the On/Off Controls area, click Turn Off (remember the polarity reversal) to open the door and see what happens.
12. If the door opens, click Turn On to close it and see what happens.
13 Copy the logged messages and paste them into a new post.

Good luck!

[juntta]

I’ll do some timing and perhaps I should post the followup to VGD forum

[papamac]

It occured to me that I read somewhere that the Aeotec device delays opening the door until it flashes lights or sounds an alarm. If true, the open/close travel time that you use for the VGD device should include this delay. The time should be the duration from turning on the Aeotec device until the door motion completes

If the experiment succeeds, I will post on the VGD forum about using the Aeotec device as a VGD activation relay.

David

[juntta]

It occured to me that I read somewhere that the Aeotec device delays opening the door until it flashes lights or sounds an alarm. If true, the open/close travel time that you use for the VGD device should include this delay. The time should be the duration from turning on the Aeotec device until the door motion completes

If the experiment succeeds, I will post on the VGD forum about using the Aeotec device as a VGD activation relay.

David

There is delay but if I remember right this can be changed/removed with configuration parameter.