Windowskel accessories not showing up

[hpetersen]

Hi,

Im trying to get your Windowskel working. It runs fine in homebridge with no warnings or errors, but it never shows up in the Homekit app? Do you have any idea why or what can be wrong?

[mlaanderson]

When working with homebridge, we have several pieces to debug. Starting from the top:

Is the Homekit app paired with the Homebridge? Does the Homebridge configuration file have the WindowSkel accessory defined? Do other Homebridge devices show up in the Homekit app?

What version of homebridge are you using? I haven't tested WindowSkel with versions since 0.2.x.

I don't have debug integrated into WindowSkel yet, but I may have time to get it in there later today. That would let you turn on debug output to look for progress.

[hpetersen]

That would be very cool.

Is the Homekit app paired with the Homebridge? — Yes it is paired.

Does the Homebridge configuration file have the WindowSkel accessory defined? — Yes im using the default you provided in .readme

Do other Homebridge devices show up in the Homekit app? — Yes i have a custom built security alarm showing and working just fine.

Homebridge version is 0.4.27 Maybe the problem is here.

At first install of WindowSkel i got an warning message. I tried to fix the warning because i suspected it to be the reason why it didn’t show up. The warning is regarding Apple removed support for the firmware that you have in your code

[mlaanderson]

Test out the 0.1.2 version (it's only on github for now). Use export DEBUG=homebridge-windowskel to see all the messages.

Also, turn on the debug output from homebridge by starting it with the -D flag. If you can safely attach that output to this issue I can investigate it. Also if you can attach just the window-skel portion of your configuration, or anonymize the entire configuration file I can look at it.

[hpetersen]

Here's the output when running in debug mode

pi@raspberrypi:~ $ /opt/node/bin/homebridge -D
*** WARNING *** The program 'node' 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=node>
*** WARNING *** The program 'node' 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=node&f=DNSServiceRegister>
[2017-8-31 20:36:48] Loaded plugin: homebridge-alarm
[2017-8-31 20:36:48] Registering accessory 'homebridge-alarm.Alarm'
[2017-8-31 20:36:48] ---
[2017-8-31 20:36:48] Loaded plugin: homebridge-server
[2017-8-31 20:36:48] Registering platform 'homebridge-server.Server'
[2017-8-31 20:36:48] ---
[2017-8-31 20:36:48] Loaded plugin: homebridge-windowskel
  homebridge-windowskel Called by homebridge +0ms
[2017-8-31 20:36:49] Registering accessory 'homebridge-windowskel.WindowSkel'
[2017-8-31 20:36:49] ---
[2017-8-31 20:36:49] Loaded config.json with 2 accessories and 1 platforms.
[2017-8-31 20:36:49] ---
[2017-8-31 20:36:49] Loading 1 platforms...
[2017-8-31 20:36:49] [Homebridge Server] Initializing Server platform...
[2017-8-31 20:36:49] Loading 2 accessories...
[2017-8-31 20:36:49] [Alarm] Initializing Alarm accessory...
[2017-8-31 20:36:49] [Window] Initializing WindowSkel accessory...
  homebridge-windowskel Begin constructor +716ms
HAP Warning: Characteristic 00000054-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 0000003E-0000-1000-8000-0026BB765291. Adding anyway.
  homebridge-windowskel End constructor +75ms
  homebridge-windowskel getServices called +3ms
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

    ┌────────────┐     
    │ 000-11-222 │     
    └────────────┘     

[2017-8-31 20:36:50] [Homebridge Server] is listening on: http://10.0.1.40:8765
[2017-8-31 20:36:50] Homebridge is running on port 51826.

Not much info to get here. And the config.json

    "bridge": {
        "name": "Homebridge",
        "username": "CC:33:3D:E3:CE:30",
        "port": 51826,
        "pin": "000-11-222",
        "manufacturer": "hpetersen",
        "model": "Homebridge",
        "serialNumber": "0.4.20"
    },

    "description": "Homebridge for Fælledvej 157C, 2791 Dragør",

    "accessories": [
      {
         "accessory": "Alarm",
         "name": "Alarm",
         "service": "Lock"
      },
      {
         "accessory": "WindowSkel",
         "name": "Window",
         "description": "Skeleton Window"
      }
    ],
    "platforms": [
      {
        "platform": "Server",
        "port"    : 8765,
        "name"    : "Homebridge Server",
        "log"     : "systemd",
        "restart" : "sudo systemctl restart homebridge"
      }
    ]
}

[mlaanderson]

This appears to be the culprit: [2017-8-31 20:36:49] [Window] Initializing WindowSkel accessory... homebridge-windowskel Begin constructor +716ms HAP Warning: Characteristic 00000054-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 0000003E-0000-1000-8000-0026BB765291. Adding anyway. homebridge-windowskel End constructor +75ms homebridge-windowskel getServices called +3ms

I will have to verify the characteristic numbers.

[hpetersen]

That warning is regarding the ‘’Characteristic.FirmwareRevision‘’