zha-device-handlers icon indicating copy to clipboard operation
zha-device-handlers copied to clipboard

[Device Support Request] EcoLink FFZB1-ECO (Firefighter)

Open hockey6611 opened this issue 3 years ago • 3 comments

Is your feature request related to a problem? Please describe. Device support request for EcoLink FFZB1-ECO (Firefighter), primarily for use with ZHA in Home Assistant

Describe the solution you'd like Support added to zigpy for EcoLink FFZB1-ECO (Firefighter).

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=4130, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=0, maximum_outgoing_transfer_size=82, 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": "0x0402",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0020",
        "0x0402",
        "0x0500",
        "0x0b05"
      ],
      "out_clusters": [
        "0x0019"
      ]
    }
  },
  "manufacturer": "Ecolink",
  "model": "FFZB1-SM-ECO",
  "class": "zigpy.device.Device"
}

Additional context Home assistant community discussion here Manufacturer website Amazon purchase link FCC device listing

The device appears to use the similar (same?) hardware as the ecolink door sensor: EM357 #408, which is supported with zigpy

The device pairs easily with home assistant but usability after pairing is not working. From above linked Home Assistant home assistant forum, there appear to be issues interpretating the battery percentage, but the votage is read. There is also an apparent issue receiving the alert signal, and an apparent missing tamper sensor.

hockey6611 avatar Jan 14 '22 21:01 hockey6611

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.

github-actions[bot] avatar Jul 13 '22 22:07 github-actions[bot]

I do not believe this has been addressed, or added to zigpy. I will be able to test this within 1 day and will report back.

hockey6611 avatar Jul 14 '22 00:07 hockey6611

I do not believe this has been addressed, or added to zigpy. I will be able to test this within 1 day and will report back.

There have been no changes the device remains non-functional.

hockey6611 avatar Jul 15 '22 01:07 hockey6611

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.

github-actions[bot] avatar Jan 11 '23 02:01 github-actions[bot]

There have been no changes the device remains non-functional.

hockey6611 avatar Jan 13 '23 18:01 hockey6611

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.

github-actions[bot] avatar Jul 12 '23 19:07 github-actions[bot]