zigpy / zha-device-handlers

ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices.
Apache License 2.0
720 stars 669 forks source link

[Device Support Request] Calex Smart Wall Switch #1324

Closed JoryHogeveen closed 1 year ago

JoryHogeveen commented 2 years ago

Describe the solution you'd like It would be nice if the Calex Smart Wall Switch would be supported by ZHA.

Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4509, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=10752, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0810",
      "in_clusters": [
        "0x0000",
        "0x0003"
      ],
      "out_clusters": [
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0019",
        "0x0300",
        "0x1000"
      ]
    }
  },
  "manufacturer": "Calex ",
  "model": "Smart Wall Switch ",
  "class": "zigpy.device.Device"
}

Additional context I've already started on a blueprint automation but that isn't finished. My knowledge on this matter is hitting a wall at the moment. https://community.home-assistant.io/t/calex-smart-wall-switch-blueprint-not-finished-need-help/387748

Z2MQTT claims to support this device already: Calex 421782 control via MQTT | Zigbee2MQTT Also see: Calex Dimmer Switch Colour Control (421782) Zigbee compatibility

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment ๐Ÿ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

JoryHogeveen commented 2 years ago

The issue is partly solved. I've managed to get a blueprint working. However, the battery status still isn't shown.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment ๐Ÿ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

JoryHogeveen commented 1 year ago

It's stale because no one replies :) not because it's inactive.

For context/update, here is a link to my (now finished) blueprint: https://github.com/JoryHogeveen/HomeAssistantConfig/blob/master/blueprints/automation/calex/calex-smart-remote.yaml All the clusters etc. can be found in there.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment ๐Ÿ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.