Describes options passed to the RecordingManagement.
List of supported media MediaContainerConfigurations (or a single one).
EventTriggerOptions are derived automatically as follows:
The size of the prebuffer in milliseconds. It must be at least 4000 ms. A sensible value for this property is in the interval [4000, 8000].
In order to provide some context to recording event, it is a good user experience
to also have the recording of a few seconds before the event occurs.
This exactly is the prebuffer. A camera will constantly store the last
x seconds (the
prebufferLength) to provide more context to a given event.
There are predefined types DefaultControllerType for all controller implementations provided by hap-nodejs. You can define custom ControllerTypes if you wish to, but be careful that it does not collide with any known definitions.
Defines a pincode for the HAP accessory. Must have a format like "XXX-XX-XXX".
Defines a mac address. Must have a format like 'XX:XX:XX:XX:XX:XX' with XX being a valid hexadecimal string
Any value set to this optional property will overwrite the automatically determined local address, which is sent as RTP endpoint to the iOS device.
UUID string uniquely identifying every HAP connection.
An optional ResourceRequestReason. The client decides if it wants to send this value. It is typically
only sent in the context of HomeKit Secure Video Cameras.
This value might be used by a
CameraStreamingDelegate for informational purposes.
handleSnapshotRequest is called, it is already checked if the respective reason is allowed in the current camera configuration.
This method can be used to retrieve the current running library version of the HAP-NodeJS framework.
The SemVer version string.
A simple clone function that also allows you to pass an "extend" object whose properties will be added to the cloned copy of the original object passed.
This method is the legacy way of decoding tlv data. It will not properly decode multiple list of the same id. Should the decoder encounter multiple instances of the same id, it will just concatenate the buffer data.
Loads all accessories from the given folder. Handles object-literal-style accessories, "accessory factories", and new-API style modules.
Accepts object-literal JSON structures from previous versions of HAP-NodeJS and parses them into newer-style structures of Accessory/Service/Characteristic objects.