Readonly
eventsAccess the behavior's events.
Supported features as a flag object.
Readonly
stateAccess the behavior's state.
Readonly
identifyThis attribute specifies the remaining length of time, in seconds, that the endpoint will continue to identify itself.
If this attribute is set to a value other than 0 then the device shall enter its identification state, in order to indicate to an observer which of several nodes and/or endpoints it is. It is recommended that this state consists of flashing a light with a period of 0.5 seconds. The IdentifyTime attribute shall be decremented every second while in this state.
If this attribute reaches or is set to the value 0 then the device shall terminate its identification state.
Readonly
identifyThis attribute specifies how the identification state is presented to the user.
This field shall contain one of the values defined in IdentifyTypeEnum. The value None shall NOT be used if the device is capable of presenting its identification state using one of the other methods defined in IdentifyTypeEnum.
Release resources. This is the public API for releasing application resources held by behaviors in internal state.
Protected
callbackCreate a generic callback function that has the same properties as a Reactor.
Like a reactor, the callback's "this" will be bound to an active Behavior instance. Because of this: The reactor MUST be a real JS function - arrow functions will not work!
This command starts or stops the receiving device identifying itself.
Behaviors are ephemeral and should not perform initialization in their constructor. They can override this method instead.
This method may be synchronous or asyncronous. If asynchronous, the behavior will not be available for external use until initialization completes.
Optional
_options: {}Protected
reactInstall a Reactor.
Important: The reactor MUST be a real JS function - arrow functions will not work!
This command allows the support of feedback to the user, such as a certain light effect. It is used to allow an implementation to provide visual feedback to the user under certain circumstances such as a color light turning green when it has successfully connected to a network. The use of this command and the effects themselves are entirely up to the implementer to use whenever a visual feedback is useful but it is not the same as and does not replace the identify mechanism used during commissioning.
The implemented cluster.