Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Tile Spins Endlessly When Changing Arming Modes in HomeKit App (setup issue with error in log) #25

Open
mkormendy opened this issue Dec 8, 2022 · 1 comment
Assignees
Labels
bug Something isn't working known issue This issue has been reported multiple times

Comments

@mkormendy
Copy link
Owner

After setting up the Konnected device and the Homebridge Konnected configuration, a user may be unable to control the alarm system mode in the HomeKit app, or the tile in HomeKit simply keeps spinning with no change of state.

The homebridge logs show something related to the following:

... characteristic value 0 is not contained in valid values array
@mkormendy mkormendy added bug Something isn't working known issue This issue has been reported multiple times labels Dec 8, 2022
@mkormendy mkormendy self-assigned this Dec 8, 2022
@mkormendy
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working known issue This issue has been reported multiple times
Projects
Development

No branches or pull requests

1 participant