This plugin generated a warning from the characteristic 'Security System Target State': characteristic value 0 is not contained in valid values array.

[mkormendy]

HomeKit shows a constantly spinning "Disarming" alarm system accessory tile.

Every time Home.app is opened, the following warning/error gets thrown/printed in the logs:

[6/22/2022, 2:39:01 PM] [homebridge-konnected] This plugin generated a warning from the characteristic 'Security System Target State': characteristic value 0 is not contained in valid values array. See https://homebridge.io/w/JtMGR for more info.
[6/22/2022, 2:39:01 PM] [homebridge-konnected] Error:
at SecuritySystemTargetState.Characteristic.characteristicWarning (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
at SecuritySystemTargetState.Characteristic.validateUserInput (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/src/lib/Characteristic.ts:2054:14)
at SecuritySystemTargetState. (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/src/lib/Characteristic.ts:1582:21)
at step (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:144:27)
at Object.next (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:125:57)
at /var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:118:75
at new Promise ()
at __awaiter (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:114:16)
at SecuritySystemTargetState.Characteristic.handleGetRequest (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/dist/lib/Characteristic.js:689:38)
at SecuritySystemTargetState. (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/src/lib/Characteristic.ts:2207:22)
at step (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:144:27)
at Object.next (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:125:57)
at /var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:118:75
at new Promise ()
at __awaiter (/var/lib/homebridge/node_modules/.pnpm/tslib@2.4.0/node_modules/tslib/tslib.js:114:16)
at SecuritySystemTargetState.Characteristic.toHAP (/var/lib/homebridge/node_modules/.pnpm/hap-nodejs@0.10.2/node_modules/hap-nodejs/dist/lib/Characteristic.js:1328:38)

[mkormendy]

This is a known issue and has to deal with sensor zones not assigned a triggerable mode. I have created this ticket here to track the bugfix progress for this in the next release.

In the meantime, there is a workaround to get the Homebridge Konnected plugin past this issue.

Using Homebridge Config UI X interface or HOOBS visual configuration user interface:

1. scroll down and edit the first zone that is a contact sensor
2. expand the binary sensor settings and scroll down further slightly
3. enable Home/Stay, Night, and Away
4. save your configuration
5. now reboot homebridge twice

Editing the Homebridge config.json file directly:

See below, making note of the of the triggerableModes property array under the binarySensorSettings property class for a zone:

...
      "zones": [
        {
          "enabled": true,
          "zoneNumber": "2",
          "zoneType": "contact",
          "zoneLocation": "Front Entrance",
          "binarySensorSettings": {
            "invert": false,
            "audibleBeep": true,
            "triggerableModes": [
              "0",
              "1",
              "2"
            ]
          }
        }
      ]
...

This should fix this issue, and you can then change the triggerable modes to whatever setup you require.