Closed joergs-git closed 7 years ago
HomeKit only allows max 99 devices per bridge, beyond that it acts strange in ways like you describe.
Oh really? Well, I'd expect, that homekit then at least simply ignores devices over 99.
However, apart from Homekit, I am not really sure if that's really my current problem, because homebridge is only initializing 28 devices while other do not even show up in the DEBUG Log. So I assume this is not really a Homekit-Problem itself right now....
`pi@raspberrypi3-jkl1:~ $ DEBUG=zway homebridge WARNING The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi. WARNING Please fix your application to use the native API of Avahi! WARNING For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs WARNING The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. WARNING Please fix your application to use the native API of Avahi! WARNING For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister [2016-12-04 16:26:24] Loaded plugin: homebridge-camera-ffmpeg [2016-12-04 16:26:24] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg' [2016-12-04 16:26:24] --- [2016-12-04 16:26:25] Loaded plugin: homebridge-netatmo [2016-12-04 16:26:25] Registering platform 'homebridge-netatmo.netatmo' [2016-12-04 16:26:25] --- [2016-12-04 16:26:25] Loaded plugin: homebridge-people [2016-12-04 16:26:25] Registering accessory 'homebridge-people.people' [2016-12-04 16:26:25] --- [2016-12-04 16:26:25] Loaded plugin: homebridge-roomba [2016-12-04 16:26:25] Registering accessory 'homebridge-roomba.Roomba' [2016-12-04 16:26:25] --- WARNING The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. WARNING Please fix your application to use the native API of Avahi! WARNING For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister [2016-12-04 16:26:26] Loaded plugin: homebridge-soundtouch [2016-12-04 16:26:26] Registering accessory 'homebridge-soundtouch.SoundTouch' [2016-12-04 16:26:26] --- [2016-12-04 16:26:27] Loaded plugin: homebridge-zway [2016-12-04 16:26:27] Registering accessory 'homebridge-zway.ZWayServer' [2016-12-04 16:26:27] Registering platform 'homebridge-zway.ZWayServer' [2016-12-04 16:26:27] --- [2016-12-04 16:26:27] Loaded config.json with 2 accessories and 2 platforms. [2016-12-04 16:26:27] --- [2016-12-04 16:26:27] Loading 2 platforms... [2016-12-04 16:26:27] Initializing ZWayServer platform... [2016-12-04 16:26:27] Initializing Camera-ffmpeg platform... [2016-12-04 16:26:27] Loading 2 accessories... [2016-12-04 16:26:27] [Roomba] Initializing Roomba accessory... [2016-12-04 16:26:27] [Bewohner] Initializing people accessory... [2016-12-04 16:26:27] Einfahrtkamera is running on port 46233. [2016-12-04 16:26:27] Einfahrtkamera is running on port 34676. [2016-12-04 16:26:28] Initializing platform accessory 'Picoguard-Alarm'... [2016-12-04 16:26:28] Initializing platform accessory 'Hue-Flutlicht'... [2016-12-04 16:26:28] Initializing platform accessory 'SummPieps'... [2016-12-04 16:26:28] Initializing platform accessory 'Bewässerung'... [2016-12-04 16:26:28] Initializing platform accessory 'Küchenbewegung'... [2016-12-04 16:26:28] Initializing platform accessory 'Garagenauge1'... [2016-12-04 16:26:28] Initializing platform accessory 'Bogenleuchte'... [2016-12-04 16:26:28] Initializing platform accessory 'Schrankflursensor1'... [2016-12-04 16:26:28] Initializing platform accessory 'Dielen-Wandleuchten'... [2016-12-04 16:26:28] Initializing platform accessory 'Kleiderschranklicht'... [2016-12-04 16:26:28] Initializing platform accessory 'Hüttenlicht'... [2016-12-04 16:26:28] Initializing platform accessory 'Haustürkontakt'... [2016-12-04 16:26:28] Initializing platform accessory 'Hintertürkontakt'... [2016-12-04 16:26:28] Initializing platform accessory 'Schiebetürsensor'... [2016-12-04 16:26:28] Initializing platform accessory 'Wasseralarm-HW'... [2016-12-04 16:26:28] Initializing platform accessory 'Fensterbank-TV Licht'... [2016-12-04 16:26:28] Initializing platform accessory 'Garagenlichtschalter'... [2016-12-04 16:26:28] Initializing platform accessory 'Wasseralarm-Heizung'... [2016-12-04 16:26:28] Initializing platform accessory 'Wasseralarm-Küche'... [2016-12-04 16:26:28] Initializing platform accessory 'Terassenwand'... [2016-12-04 16:26:28] Initializing platform accessory 'LED Leuchte Lesezimmer'... [2016-12-04 16:26:28] Initializing platform accessory 'Wasseralarm-oben'... [2016-12-04 16:26:28] Initializing platform accessory 'Gästebadschalter'... [2016-12-04 16:26:28] Initializing platform accessory 'Gästebadauge'... [2016-12-04 16:26:28] Initializing platform accessory 'Treppenwanddimmer'... [2016-12-04 16:26:28] Initializing platform accessory 'Terassendecke'... [2016-12-04 16:26:28] Initializing platform accessory 'Fussbodenheizung'... [2016-12-04 16:26:28] Initializing platform accessory 'Hintertür'... Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-151 │
└────────────┘
[2016-12-04 16:26:28] Homebridge is running on port 51826.`
But there should be at least 10-20 more to appear.... really strange. Wouldn't even know where to look/debug any further....
Continued debugging and still kind of unclear/weird to me:
It doesn't seem to be a problem of the number of devices (because I reduced/deactivated lot of them, without seeing any difference)
Certain devices e.g. fibaro wall plug or fibaro door contact/sensor do simply not appear anymore at all. For some of them hombridge-zway doesn't seem to find a suitable devices class.
Also a specific virtual device I created weeks ago doesn't show up during hombridge-zway startup process anymore.
I tried setting specific tags for homebridge in UI, but still no success.
Currently I am wondering if the current Version V2.2.5 of zwave-me with UI 1.5.0. could be the root of the problems and very strange behaviours.....
Would be great to hear something back from someone with an idea/suggestion where to look at.
Okay, went some steps further: It all seems to be related to the tags I suddenly HAD TO set for certain devices. Although I have no clue, why I have to set them and why only for certain ones, while it used to work without them before. Strange. Just found out, that I completely had to remove the line "optin = false" in the config.json.
Now suddenly most devices are shown again - except some Fibaro Door Sensors because no suitable device class is found.
Maybe some hint from @ SphtKr would be great.
Final comment for tonight:
I was only to view the the "Fibaro Door Sensor" in Apple Homekit App, if I define it with tag "Homebridge.IsPrimary", which again doesn't make sense. Because it doesn't work for Homekit that way. But a least it's shown then visually.....not working though.
Door sensor issue is likely #69, FWIW.
Hi, today I noticed that lot's of my around 100 homebridged-zway devices are not being shown/initialized during startup anymore. Only around 24 are being found/initialized.
They are not "hidden" and also not tagged as "Homebridge.Skip".
So I started checking things out with "opt-in" and "Homebridge.Include" some of them step by step.
While doing that I also noticed that e.g. Fibaro DoorSensors or even some virtual-Zwave Devices are not initialized at all anymore. But just yesterday it still worked well (before I added ffmpeg stuff etc.) but that doesn't seem to be the reason. However, no error messages appearing and apart from the reduced set of initialized/found zwaveme-devices homebridge seems to work normally.
Any ideas?