I/O Linc status not updating in HKL Siri

(Creating a separate thread). I'm having a lot of trouble creating a functional I/O Linc HomeKitLink device. When I create the HomeKitLink version of an I/O Linc, the status doesn't update in HK. The I/O Linc is connected to a Dakota Motion Sensor for my driveway. It works (triggers) in Indigo, but the HomekitLink version does not seem to register any changes. Am I doing something wrong?

(Creating a separate thread). I'm having a lot of trouble creating a functional I/O Linc HomeKitLink device. When I create the HomeKitLink version of an I/O Linc, the status doesn't update in HK. The I/O Linc is connected to a Dakota Motion Sensor for my driveway. It works (triggers) in Indigo, but the HomekitLink version does not seem to register any changes. Am I doing something wrong?

Hi,

If I recall previous discussion - I suspect that will be because they are not supported - the Garage IO Linc one we attempt to support, and I understand works (although I can’t test)

The more generic one which has multiple inputs and multiple outputs - is more of an issue. Indeed would need a complete new UI to select what Input/Output is being used. I believe previously discussions involved using a virtual device to copy that need IO Linc device and publish the VD.

(I’ll dig up the earlier discussions.)


Sent from my iPad using Tapatalk

The I/O Linc that I have is the one with single input/output similar to the ones used for garage doors. #2450. If there is a way to get it to send status to HKLS I would love to learn about it. Thanks!

Hi

Can you Right click on IO Linc device in Indigo and “Print Device Details to Log”
& copy here

for the Device in question?

Glenn


Sent from my iPad using Tapatalk

analogInputCount : 0
analogInputs : []
batteryLevel : None
binaryInputCount : 1
binaryInputs : [False]
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 : 729543074
globalProps : MetaProps : (dict)
com.GlennNZ.indigoplugin.HomeKitLink-Siri : (dict)
HomeKit_audioSelector : false (bool)
HomeKit_bridgeUniqueID : 683505 (integer)
HomeKit_deviceSensor : binaryInput1.ui (string)
HomeKit_deviceSubtype : MotionSensor (string)
HomeKit_inverseSelector : false (bool)
HomeKit_publishDevice : true (bool)
HomeKit_tempSelector : false (bool)
homekit-name : driveway - motion sensor (string)
id : 1350051905
lastChanged : 2022-12-22 16:21:28
lastSuccessfulComm : 2022-12-22 16:21:28
model : I/O-Linc Controller
name : outdoor - dakota - driveway motion sensor
ownerProps : emptyDict : (dict)
pluginId :
pluginProps : emptyDict : (dict)
protocol : Insteon
remoteDisplay : True
sensorInputCount : 0
sensorInputs : []
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
binaryInput1 : off (on/off bool)
binaryInput1.ui : closed (string)
binaryInputsAll : 0 (string)
binaryOutput1 : off (on/off bool)
binaryOutputsAll : 0 (string)
subModel :
subType :
supportsAllLightsOnOff : False
supportsAllOff : True
supportsStatusRequest : True
version : 54

Ok thanks

What device do you wish it to be in HomeKit?

? Motion Sensor

In which case will try to support on/off (if haven’t already) as True/False and will likely be useful for all.

Glenn


Sent from my iPad using Tapatalk

Ok

Had a few hours prior to Xmas rush, to have a look. Believe this is supported currently.

If want a Motion Sensor - which would seem to be ideal.

Go into appropriate HomeKitLink Bridge edit screen
Select this I/O Linc device
Enable Publish device checkbox
Enter name

ENABLE show all Options (down the bottom)

Select HomeKit Device Type: MotionSensor (or any other true false sensor)

Important one here is the Device State:
This menu shows devicestates available, followed by current setting when dialog opened (just to guide the correct selection)
For this device I would be guessing to select
binaryInput1

Press ** Save Device **

& see if Bridge works without errors and Motion Sensor works

Glenn

Hi Glen!

Thanks for the pointers. I've added two separate I/O Linc Devices. Using BinaryInput1=true and other variations. I don't see any changes in the I/O Linc reflected in the Home device (Motion Sensor). When the sensor triggers (input goes from closed/off to open/on), I see nothing reflected in Home app. I created a notification for any motion on that device and nothing happens when I trigger the motion. Am I doing something wrong?

Hi Glen!

Thanks for the pointers. I've added two separate I/O Linc Devices. Using BinaryInput1=true and other variations. I don't see any changes in the I/O Linc reflected in the Home device (Motion Sensor). When the sensor triggers (input goes from closed/off to open/on), I see nothing reflected in Home app. I created a notification for any motion on that device and nothing happens when I trigger the motion. Am I doing something wrong?

Hi

The state to pick, in this case you have used binaryInput1, will depend on what the right one is for your IO Linc and its setup/connected.

Check to see which state (these states are visible in Indigo in the IO Linc device) changes when motion is detected? Whatever state changes is the one you want to use.


Sent from my iPad using Tapatalk

The I/O Linc has the binary input listed as Closed. In the HKLS device, I've selected "binaryInpu1.ui == 'closed'" I unpublished and then published the device again, watched it update in Home app, but it still doesn't register a motion in Homekit when the sensor sees motion (although it does register in Indigo). Not sure what I'm doing wrong. Thanks for your patience on this! I know I'll get it working soon eventually.

Don’t use the .ui states (Side thought: I should delete them from those lists..). Those are the states that are designed for use in a UI = User interface. Need the raw binaryInput1 true/false, on/off state.

But still - the question will be whether binaryInput1 is the correct number one to use. Will depend on device setup, use etc.

Glenn


Sent from my iPad using Tapatalk