Skip to content

Latest commit

 

History

History
85 lines (68 loc) · 2.9 KB

K4003C_L4003C_N4003C_NT4003C.md

File metadata and controls

85 lines (68 loc) · 2.9 KB
title description
BTicino K4003C/L4003C/N4003C/NT4003C control via MQTT
Integrate your BTicino K4003C/L4003C/N4003C/NT4003C via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendors bridge or gateway.

To contribute to this page, edit the following file

BTicino K4003C/L4003C/N4003C/NT4003C

| Model | K4003C/L4003C/N4003C/NT4003C | | Vendor | BTicino | | Description | Light switch with neutral | | Supports | on/off, led color | | Picture | BTicino K4003C/L4003C/N4003C/NT4003C |

Notes

Device type specific configuration

How to use device type specific configuration

  • transition: Controls the transition time (in seconds) of on/off, brightness, color temperature (if applicable) and color (if applicable) changes. Defaults to 0 (no transition). Note that this value is overridden if a transition value is present in the MQTT command payload.

  • hue_correction: (optional) Corrects hue values based on a correction map for matching color rendition to other lights. Provide a minimum of 2 data sets in the correction map. To build a map:

    • choose one of your other lights to be the color reference
    • send a sample color to both lights (reference and non-reference)
    • modify hue value for non-reference light until it color matches the reference light
    • take note of the in and out values, where
      • in is the hue value you sent to your reference light
      • out is the hue value you had to dial your non-reference light to
    • repeat with a few other sample colors (4-5 should suffice)

    Example correction map:

    hue_correction:
        - in: 28
            out: 45
        - in: 89
            out: 109
        - in: 184
            out: 203
        - in: 334
            out: 318

Manual Home Assistant configuration

Although Home Assistant integration through MQTT discovery is preferred, manual integration is possible with the following configuration:

{% raw %}

switch:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    payload_off: "OFF"
    payload_on: "ON"
    value_template: "{{ value_json.state }}"
    command_topic: "zigbee2mqtt/<FRIENDLY_NAME>/set"

sensor:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    value_template: "{{ value_json.action }}"
    icon: "mdi:gesture-double-tap"

sensor:
  - platform: "mqtt"
    state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
    availability_topic: "zigbee2mqtt/bridge/state"
    unit_of_measurement: "lqi"
    value_template: "{{ value_json.linkquality }}"
    icon: "mdi:signal"

{% endraw %}