Family - All nodes of the device

[NielsK 0]

Hi everyone,

I'm not new with the Fibaro product and using those as my home domotics.

But I never understood the Famile of nodes.

Looking to the Double Switch 2, the family tree is like below picture.

20.1 and 20.2 are the switches on the device, that's clear.

But all the others I don't get what these are and how to use.

Did internet searches quite some times and never found Fibaro related explanation on the family tree of below picture.

 

Maybe some forum members might tell what it is and how to use.

Or perhaps a link to a site where below Fibaro family is explained.

 

Thank you in advance.

Niels

 

Please login or register to see this image.

/monthly_2025_02/image.png.e3508b260300b724156553d7e58e4eaf.png" />

[Fabir 73]

@NielsK

 

In Z-Wave smart home systems, the concept of "Parent" and "Child" devices plays a central role in managing and controlling the network structure:

Parent Devices:

• Definition: A Parent device, often referred to as a "Primary Controller" or simply "Controller," is the main device that manages a Z-Wave network. This could be a Z-Wave hub or a central control unit that coordinates all other devices in the network.
• Functions:
  • Network Management: The Parent is responsible for initializing, configuring, and monitoring the entire Z-Wave network. This includes including (inclusion) and removing (exclusion) devices from the network.
  • Communication: It sends commands to Child devices and receives status updates or data back from them.
  • Security: Some functions like managing security keys or encryption methods are handled by the Parent device.

Child Devices:

• Definition: Child devices are all the devices in the network controlled by the Parent device. These can be lights, switches, sensors, door locks, thermostats, and many other smart home gadgets.
• Functions:
  • Actuators and Sensors: Child devices act as endpoints in the network. They can perform actions (like turning lights on or off) or collect data (like temperature or motion).
  • Repeater: In a Z-Wave mesh network, many Child devices can also serve as repeaters by relaying messages between other devices to extend the network's range. However, only Child devices with a permanent power supply (not battery-powered) can act as repeaters.
  • Communication: They receive commands from the Parent device and send feedback or messages. In a well-constructed Z-Wave network, Child devices often have multiple communication paths to other devices, enhancing reliability.

Example of Parent-Child Relationship:

• A Z-Wave Hub (Parent) is connected to a smart home system and manages a network consisting of several light switches, motion sensors, and a smart thermostat (Child devices). The hub sends commands to the switches to control the lights based on data it receives from the motion sensors. The thermostat can send its data to the hub, which then regulates room temperature or informs users of changes.

Key Points:

• Inclusion: Child devices are included into the network by being "included" by the Parent device. This is usually initiated through a special sequence, often by pressing a button on the device or through an action in the control interface.
• Role Change: In some cases, a Secondary Controller (a special type of Child device) can act as a Parent if the primary controller is not available or is replaced, offering some flexibility in network management.

The Parent-Child relationship in Z-Wave systems ensures that all devices work in a coordinated and efficient manner while creating a robust network structure.

[NielsK 0]

@Fabir

 

Thank you for the explanation.

 

Looking to below picture "20" is the Parent device and the others are the Child devices,?

"20.1" and "20.2" are physical connections on the device for e.g. input by light switch and output to e.g. a lamp.

 

Why is it that "20.0" is split up by "20.0.1" and "20.0.2"?  

And what are those, where/how to use these?

 

Thanks again!

 

 

Please login or register to see this image.

/monthly_2025_02/image.png.e3508b260300b724156553d7e58e4eaf.png" />