
enablegroupmanagement), validate, and restart the plugin.After pairing, you should see the devices in DomoticZ, Setup > Devices.
Next, pair the bulb and the MS:
When finished, the red light in the MS switches, the bulb flashes, and the WO makes a clicking sound or its led flashes.
The MS sends its commands to a Zigbee group, created when you paired it with the bulb or WO. To get the motion events in DomoticZ, the coordinator must be a member of that group.
Whenever movement is detected, the MS switches on the bulb or WO. The status of the bulb, the WO and the MS widget change. Depending on the settings of the MS, it switches off after the set time.
The MS can be made standalone by removing the bulb or WO from the group in Management > Group Management, keeping Coordinator (in the group) checked. After validating, the group still exists, with only the coordinator in it. The motion sensor still sends to this group in the background: its status changes can be seen in the MS widget.
Now it is possible to use the MS in a script (Lua, dzVents or Blockly). This way you are not bound to Zigbee products and you can use it with devices running other protocols (Z-Wave, wifi, mqtt or 433MHz).
When using Tradfri devices like the Ikea 5 button round remote or the Ikea motion sensor, the widgets are not active after pairing: they are added to DomoticZ, but the actions can’t be seen in DomoticZ until the coordinator is a member of their group. See Ikea remote control as a pure remote.
With a ZiGate coordinator, the coordinator can only be a member of 5 groups, because of the limited memory of the ZiGate chip. When you add the ZiGate to a group for the sixth time, the membership is not established, and you get this error in the DomoticZ log: We reach the max number of Cycle and didn't succeed in the Group Creation.