HomeKit with s132 2.0.0-7.alpha

[Mike Voytovich]

Hi,

I'm attempting to use Version 2.1.0 of the HomeKit SDK on an nRF52. We're using the s132 SoftDevice 2.0.0-7.alpha (the SoftDevice in the latest nRF5 SDK v11.0.0).

However, I see that this version of the HomeKit SDK requires version 1.0.0-3.alpha of the s132 SoftDevice, which I believe is causing an error when we run it with version 2.0.0-7.alpha.

In particular, the gattdb_init() routine in libnrf52hkble.a is generating an error when attempt to initialize our HomeKit services.

I realize that there are some API changes between 1.0.0-3.alpha and 2.0.0-7.alpha. Would you expect that those API changes are what is causing gattdb_init() to fail?

Any ETA on an update of the HomeKit SDK to work with the latest s132 SoftDevice?

Thanks!

[RK]

I wouldn't expect gattdb_init() to fail, all that does is zero out the structure and init app_timer. I would however expect lots of other things to fail dismally with S132v2.

[run_ar]

The current version (2.1.0) of our SDK for homekit is not tested with the latest alpha softdevice releases. So I don't know if this will work, however the big increase in the softdevice version number from 1 to 2 means there is api changes so I don't think the hap library would works just like that.

A new sdk for homekit version will be released some time after the first production version of the softdevice and SDK is released.

Note that Homekit is under the MFI program and thus support request should be issued in our private support system, mypage.

[Mike Voytovich]

Ah, maybe that's the problem - if it's using a timer, with the older SoftDevice API could simply declare a static variable of app_timer_id_t and then call app_timer_create() to create the timer; the newer API requires you to use APP_TIMER_DEF() macro to declare the timer first before creating it.

[Mike Voytovich]

OK thanks for the reply - I'll file a support request for all further questions.

[RK]

I don't know - one of the things I now have to do now I'm using homekit is use app_timers instead of my own library, which is a bit of a nuisance. But if there's an app_timer difference it's in the SDK, nothing to do with the softdevice API at all.