FIBARO FIB_FGSS-101 Manuel de démarrage rapide - Page 8

Parcourez en ligne ou téléchargez le pdf Manuel de démarrage rapide pour {nom_de_la_catégorie} FIBARO FIB_FGSS-101. FIBARO FIB_FGSS-101 15 pages. Smoke detector

Imprimer la page

This device is battery operated and turned into deep sleep state most of the time to save battery

life time. Communication with the device is limited. In order to communicate with the device, a static

controller C is needed in the network. This controller will maintain a mailbox for the battery operated devices

and store commands that can not be received during deep sleep state. Without such a controller,

communication may become impossible and/or the battery life time is significantly decreased.

This device will wakeup regularly and announce the wakeup state by sending out a so called Wakeup

Notification. The controller can then empty the mailbox. Therefore, the device needs to be configured with

the desired wakeup interval and the node ID of the controller. If the device was included by a static

controller this controller will usually perform all necessary configurations. The wakeup interval is a tradeoff

between maximal battery life time and the desired responses of the device.

When in battery mode tripple click on the B-button to wake up the device.

It is possible to set the node ID to 255 to send wakeup notifications as broadcast. In this mode device takes more time to

go to sleep and drains battery faster, but can notify all it's direct neighbors about a wakeup.

Node Information Frame

The Node Information Frame is the business card of a Z-Wave device. It contains information

about the device type and the technical capabilities. The inclusion and exclusion of the device is confirmed

by sending out a Node Information Frame. Beside this it may be needed for certain network operations to

send out a Node Information Frame.

Hitting the B-button three times will send out a Node Information Frame.

Associations

Z-Wave devices control other Z-Wave devices. The relationship between one device controlling

another device is called association. In order to control a different device, the controlling device needs to

maintain a list of devices that will receive controlling commands. These lists are called association groups

and they are always related to certain events (e.g. button pressed, sensor triggers, ...). In case the event

happens all devices stored in the respective association group will receive a common wireless command.

Association Groups: