1 device stopt working

[flipmoo]

Hi There,

For a while now my KaKu plugin worked really wel.
But now i cant get 1 of the items to work, the problem is with the subwoofer.
(wich i turn on and of trough homebridge with Kaku)
I see the item in homekit but it mentions that this accessoire is not suitable for the home app (when for an examples the commode item does work!

this is what i have in my config:

{
"platform": "KlikAanKlikUit",
"driver": {
"type": "rpi",
"pin": 11
},
"accessories": [{
"name": "Warmtedeken",
"type": "Switch",
"address": "B",
"device": "1"
}, {
"name": "Keuken",
"type": "Lightbulb",
"dimmable": true,
"address": 12345,
"device": "1"
}, {
"name": "Commode",
"type": "Switch",
"address": "A",
"device": "1"
}, {
"name": "Subwoofer",
"type": "Switch",
"address": "C",
"device": "1"
}]
}],

[robertklep]

Very strange, especially since you're getting a message about the accessory not being suitable.

You should probably consider resetting Homebridge.

[flipmoo]

That was not the answer i hoped for :)

[robertklep]

I understand, but I don't see an obvious reason why a device would suddenly stop working, and with the error that you're getting, which all points to an issue between HomeKit and HomeBridge, and not necessarily this plugin.

You could start and try to remove the directories ~/.homebridge/persist/ and ~/.homebridge/accessories (or move them to somewhere else), which (if I remember correctly) is similar to a "soft" reset that doesn't require having to add the bridge to Home again.

FWIW, my personal experience is that third-party HAS implementations like Homebridge tend to be relatively unstable. I've used Homebridge myself for a few years, and although it has been functioning properly for a good while now, initially I had similar issues like you have: accessories that would disappear or become unresponsive, especially after adding/changing the Homebridge configuration.

Right now I'm working on a HomeKit-related project for another device, also using a third-party HAS implementation (has-node), and I'm running into those same issues for that project as well. Those issues typically disappear when I do a "hard" reset (changing the equivalent of the username in the Homebridge config, and changing the TCP port on which the server listens).