| layout | title |
|---|---|
documentation |
FT100 - ZWave |
{% include base.html %}
This describes the Z-Wave device FT100, manufactured by Fantem with the thing type UID of oomi_ft100_00_000.
The device is in the category of Sensor, defining Device used to measure something.
The FT100 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is unable to participate in the routing of data from other devices.
The FT100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. Refer to the Wakeup Information section below for further information.
Oomi by Fantem’ MultiSensor looks like nothing that has come before. It’s a motion sensor and it’s also so much more. Installing this 1 piece of Z-Wave®technology is the same as installing 6 pieces of Z-Wave technology. Your home control network will immediately understand motion, temperature, humidity,light, Ultraviolet and Vibration readings wherever MultiSensor is installed. Those intelligent readings will equate to intelligent automation. And intelligent automation will give you the perfect smart home.
MultiSensor can be powered by battery or by USB with an appropriate adaptor.
Technical Specifications:
-
Power Input: 5V 1A
-
Battery Type: 2x CR123A (not included)
-
Temperature Sensor Range: 32 ºF-104 ºF (0 ºC-40 ºC) / V1.3: 14 °F-122 °F (-10 °C-50 °C)
-
Motion Sensor Field of View: 100º
-
Motion Sensor Range: 16 feet
-
Humidity Sensor Range: 20-80% RH
-
Light Sensor Range: 0-30000 Lux
-
UV Sensor Range: 0-11 Index level
-
Dimensions: 1.8 x 1.8 x 1.5 inches
- Set your Z-Wave gateway to accept new products.
- Press the Action Button on your MultiSensor.
- Test that your sensor has been successfully added your Z-Wave gateway by pressing its Action Button. If you press the button and its LED is solid green for a few seconds, then inclusion has been successful. If the LED blinks green when the button is pressed, the inclusion has been unsuccessful and you should repeat the above steps.
Your MultiSensor can be removed from your Z-Wave network at any time.You’ll need to use your Z-Wave network’s main controller to do this and the following instructions tell you how to do this using Aeotec by Aeon Labs’ Z-Stick and Minimote controllers. If you are using other products as your main Z-Wave controller, please refer to the part of their respective manuals that tells you how remove devices from your network.
If you’re using a Z-Stick:
- If your Z-Stick is plugged into a gateway or a computer, unplug it.
- Take your Z-Stick to your MultiSensor.
- Press and hold the Action Button on your Z-Stick for 3 seconds and then release.
- Press the Action Button on your MultiSensor.
- If your MultiSensor has been successfully removed from your network, the RGB LED will be active with a colourful gradient for 3 seconds. When you press the Action Button on the MultiSensor, its green LED will blink. If the removal was unsuccessful, the green LED will stay solid for a few seconds when you press the Action Button. Press the Action Button on the Z-Stick to take it out of removal mode.
If you’re using a Minimote:
- Take your Minimote to your MultiSensor.
- Press the Remove Button on your Minimote.
- Press the Action Button on your MultiSensor.
- If your MultiSensor has been successfully removed from your network, the RGB LED will be active with a colourful gradient for 3 seconds. When you press the Action Button on the MultiSensor, its green LED will blink. If the removal was unsuccessful, the green LED will stay solid for a few seconds when you press the Action Button.
- Press any button on your Minimote to take it out of removal mode.
The FT100 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
If your MultiSensor is battery powered, you will need to ensure that it is active when configuring it. To do this, press the Action Button once, which will trigger to send out a wake up notification command.
If you want it to wake up for 10 minutes, to do this, press and hold its Action Button for 3 seconds and then release it. Your MultiSensor’s orange LED will fast blink for 10 minutes to indicate that it is active.
When you are done configuring or communicating with your MultiSensor, you can put it back into sleep mode to conserve battery power. To do this, press and hold its Action button for 3 seconds and then release it. Your MultiSensor’s LED should now be off to indicate that it is asleep.
Resetting your MultiSensor:
At some stage or your primary controller is missing or inoperable, you may also wish to reset all of your MultiSensor’s settings to their factory defaults. To do this, press and hold the Action Button for 20 seconds and then release it. Your MultiSensor will now be reset to its original settings, and the green LED will be solid for 2 seconds and then be colourful gradient to confirm a success.
The following table summarises the channels available for the FT100 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|---|---|---|---|---|
| Sensor (temperature) | sensor_temperature | sensor_temperature | Temperature | Number:Temperature |
| Sensor (ultraviolet) | sensor_ultraviolet | sensor_ultraviolet | Number | |
| Sensor (luminance) | sensor_luminance | sensor_luminance | Number | |
| Sensor (relative humidity) | sensor_relhumidity | sensor_relhumidity | Humidity | Number |
| Motion alarm | alarm_motion | alarm_motion | Motion | Switch |
| Tamper alarm | alarm_tamper | alarm_tamper | Switch | |
| Battery Level | battery-level | system.battery_level | Battery | Number |
Indicates the current temperature.
The sensor_temperature channel is of type sensor_temperature and supports the Number:Temperature item and is in the Temperature category.
Indicates the current ultraviolet level.
The sensor_ultraviolet channel is of type sensor_ultraviolet and supports the Number item. This is a read only channel so will only be updated following state changes from the device.
Indicates the current light reading.
The sensor_luminance channel is of type sensor_luminance and supports the Number item. This is a read only channel so will only be updated following state changes from the device.
Indicates the current relative humidity.
The sensor_relhumidity channel is of type sensor_relhumidity and supports the Number item and is in the Humidity category. This is a read only channel so will only be updated following state changes from the device.
Indicates if a motion alarm is triggered.
The alarm_motion channel is of type alarm_motion and supports the Switch item and is in the Motion category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
Indicates if the tamper alarm is triggered.
The alarm_tamper channel is of type alarm_tamper and supports the Switch item. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the Switch item type -:
| Value | Label |
|---|---|
| OFF | OK |
| ON | Alarm |
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
The system.battery-level channel is of type system.battery-level and supports the Number item and is in the Battery category.
This channel provides the battery level as a percentage and also reflects the low battery warning state. If the battery state is in low battery warning state, this will read 0%.
The following table provides a summary of the 12 configuration parameters available in the FT100. Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|---|---|---|
| 2 | Stay Awake in Battery Mode | Stay awake for 10 minutes at power on |
| 3 | Default PIR time | The default PIR time |
| 4 | Motion sensor sensitivity | Sensitivity level of PIR sensor (1=minimum, 5=maximum) |
| 5 | Motion sensor command when triggered | |
| 39 | Low battery value | |
| 40 | Selective Reporting | Select to report on thresholds |
| 101 | Setting automatic report flags - Association Group 1 | |
| 102 | Setting automatic report flags - Association Group 2 | |
| 103 | Setting automatic report flags - Association Group 3 | |
| 111 | Setting an automatic report interval - Association Group 1 | |
| 112 | Setting an automatic report interval - Association Group 2 | |
| 113 | Setting an automatic report interval - Association Group 3 | |
| Wakeup Interval | Sets the interval at which the device will accept commands from the controller | |
| Wakeup Node | Sets the node ID of the device to receive the wakeup notifications |
Stay awake for 10 minutes at power on Enable/Disable waking up for 10 minutes when re-power on (battery mode) the Multi Sensor, value=0=disable, value=1=enable The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | disable |
| 1 | enable |
The manufacturer defined default value is 0 (disable).
This parameter has the configuration ID config_2_1 and is of type INTEGER.
The default PIR time The default PIR time is 4 minutes. The Multisensor will send BASIC SET CC (0x00) to the associated nodes if no motion is triggered again in 4 minutes.
Range: 10 - 3600
Note:
The time unit is second if the value range is in 10 to 255. If the value range is in 256 to 3600, the time unit will be minute and its value should follow the below rules:
a) Interval time = Value/60, if the interval time can be divided by 60 and withoud remainder.
b) Interval time = (Value/60)+1, if the interval time can be divided by 60 and has remainder.
Other values will be ignored.
Values in the range 10 to 3600 may be set.
The manufacturer defined default value is 240.
This parameter has the configuration ID config_3_2 and is of type INTEGER.
Sensitivity level of PIR sensor (1=minimum, 5=maximum) Enable/disable the function of motion sensor.
Value = 0, disable
Value = 1, enable, sensitivity level = 1 (minimum level)
Value = 2, enable, sensitivity level = 2
Value = 3, enable, sensitivity level = 3
Value = 4, enable, sensitivity level = 4
Value = 5, enable, sensitivity level = 5 (maximum level)
The following option values may be configured, in addition to values in the range 0 to 5 -:
| Value | Description |
|---|---|
| 0 | disable |
| 1 | sensitivity level 1 |
| 2 | sensitivity level 2 |
| 3 | sensitivity level 3 |
| 4 | sensitivity level 4 |
| 5 | sensitivity level 5 |
The manufacturer defined default value is 5 (sensitivity level 5).
This parameter has the configuration ID config_4_1 and is of type INTEGER.
The following option values may be configured -:
| Value | Description |
|---|---|
| 1 | Basic Set CC |
| 2 | Sensor Binary Report CC |
The manufacturer defined default value is 1 (Basic Set CC).
This parameter has the configuration ID config_5_1 and is of type INTEGER.
Values in the range 10 to 50 may be set.
The manufacturer defined default value is 20.
This parameter has the configuration ID config_39_1 and is of type INTEGER.
Select to report on thresholds Enable/disable the selective reporting only when measurements reach a certain threshold or percentage set in 41-44 below. This is used to reduce network traffic. The following option values may be configured -:
| Value | Description |
|---|---|
| 0 | disable |
| 1 | enable |
The manufacturer defined default value is 0 (disable).
This parameter has the configuration ID config_40_1 and is of type INTEGER.
Parameter 101-103 [4 byte dec] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
128 - Light Sensor
64 - Humidity Sensor
32 - Temperature Sensor
16 - Ultraviolet Sensor
1 - Battery Sensor
The table above shows a decimal representation of all flags that can be set on parameter 101-103 to report specific data.
For example, if you want to report only the temperature and light sensor you would add 32 + 64 and set the sum (96) to parameter 101, 102, or 103.
As another example, if you want to report only the light sensor and battery, you would add 1 + 128, then set the sum (129) to parameter 101, 102, or 103.
And if you want to report all of the sensors, you would add the whole table together and set the sum (241) to parameter 101, 102, or 103. Values in the range 0 to 255 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_101_4 and is of type INTEGER.
Parameter 101-103 [4 byte dec] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
128 - Light Sensor
64 - Humidity Sensor
32 - Temperature Sensor
16 - Ultraviolet Sensor
1 - Battery Sensor
The table above shows a decimal representation of all flags that can be set on parameter 101-103 to report specific data.
For example, if you want to report only the temperature and light sensor you would add 32 + 64 and set the sum (96) to parameter 101, 102, or 103.
As another example, if you want to report only the light sensor and battery, you would add 1 + 128, then set the sum (129) to parameter 101, 102, or 103.
And if you want to report all of the sensors, you would add the whole table together and set the sum (241) to parameter 101, 102, or 103. Values in the range 0 to 255 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_102_4 and is of type INTEGER.
Parameter 101-103 [4 byte dec] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
128 - Light Sensor
64 - Humidity Sensor
32 - Temperature Sensor
16 - Ultraviolet Sensor
1 - Battery Sensor
The table above shows a decimal representation of all flags that can be set on parameter 101-103 to report specific data.
For example, if you want to report only the temperature and light sensor you would add 32 + 64 and set the sum (96) to parameter 101, 102, or 103.
As another example, if you want to report only the light sensor and battery, you would add 1 + 128, then set the sum (129) to parameter 101, 102, or 103.
And if you want to report all of the sensors, you would add the whole table together and set the sum (241) to parameter 101, 102, or 103. Values in the range 0 to 255 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_103_4 and is of type INTEGER.
Parameter 111-113 [4 byte decimal] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
Parameter 111 will set the interval for Group 1 (parameter 101), parameter 112 will set the interval for Group 2 (parameter 102), and parameter 113 will set the interval for Group 3 (parameter 103).
As an example, you have set parameter 101 to 241 which will report all of the sensors, and you want to report it every 1800 seconds. Set parameter 111 to 1800 to accomplish this. Values in the range 0 to 0 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_111_4 and is of type INTEGER.
Parameter 111-113 [4 byte decimal] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
Parameter 111 will set the interval for Group 1 (parameter 101), parameter 112 will set the interval for Group 2 (parameter 102), and parameter 113 will set the interval for Group 3 (parameter 103).
As an example, you have set parameter 101 to 241 which will report all of the sensors, and you want to report it every 1800 seconds. Set parameter 111 to 1800 to accomplish this. Values in the range 0 to 0 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_112_4 and is of type INTEGER.
Parameter 111-113 [4 byte decimal] can be configured through your gateway in case the default settings of your MultiSensor are not what you desire.
Parameter 111 will set the interval for Group 1 (parameter 101), parameter 112 will set the interval for Group 2 (parameter 102), and parameter 113 will set the interval for Group 3 (parameter 103).
As an example, you have set parameter 101 to 241 which will report all of the sensors, and you want to report it every 1800 seconds. Set parameter 111 to 1800 to accomplish this. Values in the range 0 to 0 may be set.
The manufacturer defined default value is 0.
This parameter has the configuration ID config_113_4 and is of type INTEGER.
The wakeup interval sets the period at which the device will listen for messages from the controller. This is required for battery devices that sleep most of the time in order to conserve battery life. The device will wake up at this interval and send a message to the controller to tell it that it can accept messages - after a few seconds, it will go back to sleep if there is no further communications.
This setting is defined in seconds. It is advisable not to set this interval too short or it could impact battery life. A period of 1 hour (3600 seconds) is suitable in most instances.
Note that this setting does not affect the devices ability to send sensor data, or notification events.
This parameter has the configuration ID wakeup_interval and is of type INTEGER.
When sleeping devices wake up, they send a notification to a listening device. Normally, this device is the network controller, and normally the controller will set this automatically to its own address. In the event that the network contains multiple controllers, it may be necessary to configure this to a node that is not the main controller. This is an advanced setting and should not be changed without a full understanding of the impact.
This parameter has the configuration ID wakeup_node and is of type INTEGER.
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The FT100 supports 3 association groups.
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation. Group 1 is assigned to the Lifeline association group and every device has 5 nodes to associate.The Motion sensor, Humidity sensor, thermometer, light sensor and Ultraviolet sensor reports will be sent to the associated nodes in Group 1.
Association group 1 supports 5 nodes.
Association group 2 supports 5 nodes.
Association group 3 supports 5 nodes.
| Command Class | Comment |
|---|---|
| COMMAND_CLASS_NO_OPERATION_V1 | |
| COMMAND_CLASS_BASIC_V1 | |
| COMMAND_CLASS_SENSOR_MULTILEVEL_V1 | |
| COMMAND_CLASS_CONFIGURATION_V1 | |
| COMMAND_CLASS_ALARM_V1 | |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1 | |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1 | |
| COMMAND_CLASS_BATTERY_V1 | |
| COMMAND_CLASS_WAKE_UP_V1 | |
| COMMAND_CLASS_ASSOCIATION_V1 |
Did you spot an error in the above definition or want to improve the content? You can contribute to the database here.