prefixkit Ask an engineerAsk Support RU

Zigbee devices Switches and relays

Schneider Electric CCTFR6000

Wiser underfloor heating controller. Works with Zigbee2MQTT with no vendor hub or cloud: it pairs with a Zigbee stick and shows up in Home Assistant.

Vendor
Schneider Electric
Model
CCTFR6000
Type
Switches and relays
Power
mains: usually a router that extends the mesh
Firmware updates (OTA)
yes, through Zigbee2MQTT
Also sold as
Schneider Electric CCTFR6600, Schneider Electric CCTFR6610

Find it in shops: AliExpress

Links open a search in the shop; some are affiliate links: buying through them costs you nothing extra and supports this site. We do not sell devices or get them from manufacturers.

What it exposes

FeaturePropertyValuesControl
On / off (1)state_1—settable
On / off (2)state_2—settable
On / off (3)state_3—settable
On / off (4)state_4—settable
On / off (5)state_5—settable
On / off (6)state_6—settable
On / off (7)state_7—settable
On / off (8)state_8—settable
Demand percentage (1)demand_percentage_1% · 0…100settable
Demand percentage (2)demand_percentage_2% · 0…100settable
Demand percentage (3)demand_percentage_3% · 0…100settable
Demand percentage (4)demand_percentage_4% · 0…100settable
Demand percentage (5)demand_percentage_5% · 0…100settable
Demand percentage (6)demand_percentage_6% · 0…100settable
Demand percentage (7)demand_percentage_7% · 0…100settable
Demand percentage (8)demand_percentage_8% · 0…100settable
Cycle time (1)cycle_time_1s · 300…3200settable
Cycle time (2)cycle_time_2s · 300…3200settable
Cycle time (3)cycle_time_3s · 300…3200settable
Cycle time (4)cycle_time_4s · 300…3200settable
Cycle time (5)cycle_time_5s · 300…3200settable
Cycle time (6)cycle_time_6s · 300…3200settable
Cycle time (7)cycle_time_7s · 300…3200settable
Cycle time (8)cycle_time_8s · 300…3200settable

MQTT: state and commands

Zigbee2MQTT publishes the device state to zigbee2mqtt/my_device (my_device is the name you give the device). An example message:

{
  "state_1": "ON",
  "state_2": "ON",
  "state_3": "ON",
  "state_4": "ON",
  "state_5": "ON",
  "state_6": "ON",
  "state_7": "ON",
  "state_8": "ON",
  "demand_percentage_1": 50,
  "demand_percentage_2": 50,
  "demand_percentage_3": 50,
  "demand_percentage_4": 50,
  "demand_percentage_5": 50,
  "demand_percentage_6": 50,
  "linkquality": 120
}

Send commands to zigbee2mqtt/my_device/set:

mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_1":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_2":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_3":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_4":"TOGGLE"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"state_5":"TOGGLE"}'

Watch the topics live from the browser: MQTT client.

Home Assistant automation example

Zigbee2MQTT creates Home Assistant entities from the device name. If it is called my_device, an automation in automations.yaml can look like this:

- alias: "Off at night"
  mode: single
  triggers:
    - trigger: time
      at: "23:30:00"
  actions:
    - action: switch.turn_off
      target:
        entity_id: switch.my_device_1

Check the YAML: YAML checker.

How to pair it

  1. In Zigbee2MQTT click Permit join.
  2. Put the device in pairing mode: usually a long press of the reset button (5–10 s) until the LED blinks; bulbs: switch the power off and on 5–6 times.
  3. Keep the device close to the coordinator or a router while pairing.
  4. Give it a clear name: MQTT topics and Home Assistant entities are built from it.

Exact procedure and model notes: the device page in the Zigbee2MQTT docs. No coordinator yet: coordinator picker.

Similar devices

Idea?