Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle optional characteristics? #31

Closed
Bouke opened this issue Oct 29, 2017 · 1 comment
Closed

How to handle optional characteristics? #31

Bouke opened this issue Oct 29, 2017 · 1 comment

Comments

@Bouke
Copy link
Owner

Bouke commented Oct 29, 2017

Take for example the Info service, described in 9.1 of the HAP specifications:

9.1 Accessory Information
Every accessory must expose a single instance of the Accessory Information service with the following definition. The values of Manufacturer, Model, Name and Serial Number must be persistent through the lifetime of the accessory.
Any other Apple-defined characteristics added to this service must only contain one or more of the following permissions: Paired Read or Notify. Custom characteristics added to this service must only contain one or more of the following permissions: Paired Read, Notify, or Broadcast. All other permissions are not permitted.

Currently it's not worked out how to add custom characteristics. Off course one could create a custom Service, but we need to test that this actually works and is documented.

@gbrooker
Copy link
Contributor

gbrooker commented Apr 1, 2019

Can be closed with PR #73

@Bouke Bouke closed this as completed Apr 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants