Best Way to map IOLink for Garage Door Opening #121

jjschwarz · 2018-10-28T17:20:58Z

I have an I/O-Linc Controller setup in Indigo 7.2 which acts as both a garage door opener on output 1 and a garage door status detector on the binary input. I added it as a "garage door opener" homekit type object in HomeKit Bridge, however that seems to have no effect on anything.

Is there a better way I should map this object that would allow for open/close and sensor functionality?

dscottbuch · 2018-10-28T17:36:46Z

Jason,

I have 3 of these set up as Garage doors and all work well. My goodnight scene makes sure they're closed. While there might be an easier way this is was worked for me. For EACH door I had to set up 2 devices, 1 variable and 3 actions. Below are screen shots of the setup. When I was running Homebridge myself the sense of the variables was reversed, i.e. false was closed and true was open but with HomeKit-Bridge I had to reverse the sense. Not sure why but this is but it works this way. I add the Virtual Device, Truck Garage, to HomeKit-Bridge as a garage door opener.

jjschwarz · 2018-10-28T17:46:02Z

OK, our setups seem very different and I really don't want to change what is working in every other place to make homekit work.

I have the input sensor and legacy sensor settings opposite of your settings.

I assume you did all of the virtual device setup just to get HomeKit working with these devices? I ask because I haven't needed that with just regular Indigo, so I wanted to make sure you were using them just for integration purposes. My understanding was you created an action group and virtual device just to map these, but they seem to maintain state based on the action not on the sensor, is that correct?

I really want to make sure on that, because I want to only maintain the open/close state based on the input sensor because we have had issues with the door closed being interrupted before.

jjschwarz · 2018-10-28T17:48:08Z

When I mention maintained state above, I meant it appears the variable contains the state, but I do not see anything linking the variable to the door sensor.

Colorado4Wheeler · 2018-10-28T17:49:30Z

That I/O sensor works natively with HomeKit Bridge, it is what I use and didn’t need any variables or custom scripts. I’ll have to look at your settings and logs to know why it may not be working. When you opened the ticket and it asked you for all of this information did you just not want to bother?

jjschwarz · 2018-10-28T18:04:03Z

I collected all of the logs, but I put them on the other door ticket. I will update them on this one too.

jjschwarz · 2018-10-28T18:10:20Z

Versions

Plugin: v1.0.2

Configuration

"platforms": [
        {
                "protocol": "http", 
                "name": "HomeKit Bridge Server", 
                "listenPort": "8445", 
                "platform": "Indigo2", 
                "host": "127.0.0.1", 
                "debug": false, 
                "serverId": REMOVED, 
                "port": "8558"
        }
], 
"bridge": {
        "username": "REMOVED", 
        "name": "HomeBridge", 
        "pin": "XXX-YY-ZZZ", 
        "port": "51826"
}, 
"accessories": [], 
"description": "HomeKit configuration generated by HomeKit Bridge on 2018-10-28 13:21:08.655000 for device HomeBridge"

Homebridge Log / Command Output

[2018-10-28 13:21:09] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[2018-10-28 13:21:09] ---
[2018-10-28 13:21:09] Loaded plugin: homebridge-indigo2
[2018-10-28 13:21:09] Registering platform 'homebridge-indigo2.Indigo2'
[2018-10-28 13:21:09] ---
[2018-10-28 13:21:09] Loaded config.json with 0 accessories and 1 platforms.
[2018-10-28 13:21:09] ---
[2018-10-28 13:21:09] Loading 1 platforms...
[2018-10-28 13:21:09] [HomeKit Bridge Server] Initializing Indigo2 platform...
[2018-10-28 13:21:09] [HomeKit Bridge Server] HomeKit Bridge base URL is http://127.0.0.1:8558
[2018-10-28 13:21:09] [HomeKit Bridge Server] HomeKit Bridge serverId is REMOVED
[2018-10-28 13:21:09] Loading 0 accessories...
Load homebridge-camera-ffmpeg.Camera-ffmpeg
[2018-10-28 13:21:09] [HomeKit Bridge Server] Listening on port 8445
[2018-10-28 13:21:09] [HomeKit Bridge Server] HomeKit Bridge request: http://127.0.0.1:8558/HomeKit?cmd=deviceList&serverId=REMOVED
[2018-10-28 13:21:09] [HomeKit Bridge Server] Discovered Device GarageDoorOpener (ID cf7bc734d2bf3726aaf6a6d4d45f22933198fd1d7b4c2b2248a1dcf0673f020a): Garage Door
[2018-10-28 13:21:09] [HomeKit Bridge Server] Initializing platform accessory 'Garage Door'...

[2018-10-28 13:21:10] Homebridge is running on port 51826.
[2018-10-28 13:21:12] [HomeKit Bridge Server] Garage Door: get(TargetDoorState) => 1
[2018-10-28 13:21:12] [HomeKit Bridge Server] Garage Door: get(CurrentDoorState) => 1
[2018-10-28 13:21:12] [HomeKit Bridge Server] Garage Door: get(ObstructionDetected) => false
[2018-10-28 13:21:55] [HomeKit Bridge Server] Garage Door: set(TargetDoorState) 1 -> 0
[2018-10-28 13:21:55] [HomeKit Bridge Server] HomeKit Bridge request: http://127.0.0.1:8558/HomeKit?objId=905523190&serverId=35246918&jkey=cf7bc734d2bf3726aaf6a6d4d45f22933198fd1d7b4c2b2248a1dcf0673f020a&cmd=setCharacteristic&TargetDoorState=0
[2018-10-28 13:21:55] [HomeKit Bridge Server] Garage Door: updateCharacteristicValue(TargetDoorState): 0 -> 1
[2018-10-28 13:48:18] [HomeKit Bridge Server] Garage Door: get(ObstructionDetected) => false
[2018-10-28 13:48:18] [HomeKit Bridge Server] Garage Door: get(CurrentDoorState) => 1
[2018-10-28 13:48:18] [HomeKit Bridge Server] Garage Door: get(TargetDoorState) => 1
[2018-10-28 13:56:15] [HomeKit Bridge Server] Garage Door: get(TargetDoorState) => 1
[2018-10-28 13:56:15] [HomeKit Bridge Server] Garage Door: get(CurrentDoorState) => 1
[2018-10-28 13:56:15] [HomeKit Bridge Server] Garage Door: get(ObstructionDetected) => false

Device Simulation Report

[code]
##### DEVICE DATA DUMP #####

address : 15.19.E2
analogInputCount : 0
analogInputs : []
batteryLevel : None
binaryInputCount : 1
binaryInputs : [True]
binaryOutputCount : 1
binaryOutputs : [False]
buttonGroupCount : 1
configured : True
description : 
deviceTypeId : 
displayStateId : binaryOutputsAll
displayStateImageSel : PowerOff
displayStateValRaw : 0
displayStateValUi : 0
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState : 
folderId : 1666810870
globalProps : MetaProps : (dict)
id : 905523190
lastChanged : 2018-10-27 20:49:33
lastSuccessfulComm : 2018-10-27 20:49:33
model : I/O-Linc Controller
name : Garage Door
ownerProps : emptyDict : (dict)
pluginId : 
pluginProps : com.eps.indigoplugin.homekit-bridge : (dict)
protocol : Insteon
remoteDisplay : True
sensorInputCount : 0
sensorInputs : []
states : States : (dict)
     analogInputsAll : no analog input values (string)
     binaryInput1 : on (on/off bool)
     binaryInput1.ui : closed (string)
     binaryInputsAll : 1 (string)
     binaryOutput1 : off (on/off bool)
     binaryOutputsAll : 0 (string)
     sensorInputsAll : no sensor input values (string)
subModel : 
supportsAllLightsOnOff : False
supportsAllOff : False
supportsStatusRequest : True
version : 54

##### DEVICE SIMULATION DATA #####

Service : 
	alias : Garage Door
	model : 
	subModel : 
	indigoType : indigo.MultiIODevice
	pluginType : Built-In
	type : GarageDoorOpener
	desc : Garage Door Opener
	objId : 905523190
	serverId : 35246918
	invertOnState : False
	convertFahrenheit : False
	required : (List)
		ObstructionDetected : False
		TargetDoorState : 1
		CurrentDoorState : 1
	optional : (List)
		LockTargetState
		Name
		LockCurrentState
	native : True
	requiresPlugin : (List)
	actions : (List)
		Action : (HomeKitAction)
			Characteristic : TargetDoorState
			When : equal
			Value : 0 (int)
			Value2 : 0 (int)
			Command : iodevice.setBinaryOutput
			Arguments : [905523190, 0, True]
			monitors : {905523190: 'state_binaryInput1'}
		Action : (HomeKitAction)
			Characteristic : TargetDoorState
			When : equal
			Value : 1 (int)
			Value2 : 0 (int)
			Command : iodevice.setBinaryOutput
			Arguments : [905523190, 0, True]
			monitors : {905523190: 'state_binaryInput1'}
		Action : (HomeKitAction)
			Characteristic : CurrentDoorState
			When : equal
			Value : STUB (str)
			Value2 : 0 (str)
			Command : STUB
			Arguments : [905523190, 0]
			monitors : {905523190: 'state_binaryInput1'}
	loadOptional : False
	characterDict : (Dict)
		ObstructionDetected : False
		TargetDoorState : 1
		CurrentDoorState : 1


[/code]

dscottbuch · 2018-10-28T19:05:09Z

I did this for HomeKit integration. I have a magnetic sensor for open/closed. Attached to the Io linc sensor input. I have the sensor mounted at the closed position. This works perfectly whether the door is interrupted or not. Of course there is no information that it was interrupted as that’s not available. I have never used Indigo or Insteon for remote activation, just for scheduling. I’ve been using Indigo for probably close to 15 years. I understand about the settings and not sure why HomeKit-Bridge is reverse of the CLI version but I just wanted something that worked:). I can say this setup is working extremely well. I get notifications when open/closed. Siri works great to open/close either one or all. And the scenes make sure I don’t forget and leave one open.

…

Sent from my iPhone

On Oct 28, 2018, at 10:46 AM, Jason John Schwarz ***@***.***> wrote: OK, our setups seem very different and I really don't want to change what is working in every other place to make homekit work. I have the input sensor and legacy sensor settings opposite of your settings. I assume you did all of the virtual device setup just to get HomeKit working with these devices? I ask because I haven't needed that with just regular Indigo, so I wanted to make sure you were using them just for integration purposes. My understanding was you created an action group and virtual device just to map these, but they seem to maintain state based on the action not on the sensor, is that correct? I really want to make sure on that, because I want to only maintain the open/close state based on the input sensor because we have had issues with the door closed being interrupted before. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

dscottbuch · 2018-10-28T19:07:35Z

Regarding the state I forgot the triggers. Here they are.

dscottbuch · 2018-10-28T19:10:10Z

Again, this is what I needed for homebridge and homebridge-indigo. I did not try to change it with HomeKit-Bridge

dscottbuch · 2018-10-28T19:37:44Z

So, I apologize but I didn't realize I could just use the IO linc as a garage control in HomeKit-Bridge. I just reconfigured them a bit and they work great, as is. I did have to use the Invert State checkbox and also change my configuration of the Link for the sense of the 'Input Sensor' On/Off to Off. but it work just great now with only the IO linc device.

jjschwarz · 2018-10-31T10:20:50Z

dscottbuch: Sounds like you and I have the same settings now, but I am still having no luck with my setup actually working. I think this might be related to another case, which is I found none of my doors are actually updating in HomeKit since I upgraded from the NPM module to the integrated software. I hope Colorado4Wheeler can assist me in tracking down the issue.

Ghawken mentioned this issue May 6, 2022

Garage Door Opener opening… Ghawken/HomeKitLink-Siri#4

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Best Way to map IOLink for Garage Door Opening #121

Best Way to map IOLink for Garage Door Opening #121

jjschwarz commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

Colorado4Wheeler commented Oct 28, 2018 via email

jjschwarz commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

dscottbuch commented Oct 28, 2018 via email

dscottbuch commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

jjschwarz commented Oct 31, 2018

Best Way to map IOLink for Garage Door Opening #121

Best Way to map IOLink for Garage Door Opening #121

Comments

jjschwarz commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

Colorado4Wheeler commented Oct 28, 2018 via email

jjschwarz commented Oct 28, 2018

jjschwarz commented Oct 28, 2018

Versions

Configuration

Homebridge Log / Command Output

Device Simulation Report

dscottbuch commented Oct 28, 2018 via email

dscottbuch commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

dscottbuch commented Oct 28, 2018

jjschwarz commented Oct 31, 2018