Andreas Bauer

Have we verified that this issue only occurs on 1.7.0? Cause looking at the version diff there weren’t any major changes in that release that could cause any issues like...

For this case https://github.com/homebridge/homebridge/issues/3536#issuecomment-2012078868, can we get the full log with the actual crash in it? Not just the terminating message. Additionally, the list of configured plugins would also be...

On thing to note, Code 143 is usually SIGTERM on Linux. So this is not a crash that is happening from within homebridge, but an external system killing homebridge process...

As shown in the linked commit, and option `--hostname` was added to the CLI to specify a custom hostname. This acts as a workaround for this issue.

@Sroose you current "inherit" your AbstractItem from PlatformAccessory. Your using a so called "StaticPlatformPlugin" (exposing a method `accessories`, which returns a array of AccessoryPlugin objects). Your `accessories` returns an array...

@keuninkske if you really want to rollback. You probably need to rollback to some 0.4.x version.

This plugin needs an update. As already explained. Homebridge can’t really fix this.

duplicates https://github.com/Sroose/homebridge-loxone-ws/issues/51

Hey Miguel, this behavior is likely caused by the legacy (but still default) mDNS advertiser `hap-bonjour`. HAP-NodeJS supports a range of different mDNS advertiser. Next to our re-written and typescript...

> Hi @Supereg thank you for the clarification. > > the thing is that I’m limited to NRCHKB implementation since I’m using that package to expose my accessories. I think...