-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] Heiman CO_CTPG Carbon Monoxide sensor #1995
Comments
There is a proposed quirk: HeimanSmokCO_CTPGclass HeimanSmokCO_CTPG(CustomDevice):
"""CO_CTPG quirk."""
signature = {
MODELS_INFO: [(HEIMAN, "CO_CTPG")],
ENDPOINTS: {
1: {
# "profile_id": 260,
# "device_type": "0x0402",
# "in_clusters": ["0x0000","0x0001","0x0003","0x0009","0x0500"]
# "out_clusters": ["0x0019"]
PROFILE_ID: zigpy.profiles.zha.PROFILE_ID,
DEVICE_TYPE: zigpy.profiles.zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
PowerConfiguration.cluster_id,
Identify.cluster_id,
Alarms.cluster_id,
IasZone.cluster_id,
],
OUTPUT_CLUSTERS: [
Ota.cluster_id,
],
},
},
}
replacement = {
NODE_DESCRIPTOR: zigpy.zdo.types.NodeDescriptor(
logical_type=2,
complex_descriptor_available=0,
user_descriptor_available=0,
reserved=0,
aps_flags=0,
frequency_band=8,
mac_capability_flags=132 & 0b1111_1011,
manufacturer_code=4627,
maximum_buffer_size=64,
maximum_incoming_transfer_size=0,
server_mask=0,
maximum_outgoing_transfer_size=0,
descriptor_capability_field=3,
),
ENDPOINTS: {
1: {
PROFILE_ID: zigpy.profiles.zha.PROFILE_ID,
DEVICE_TYPE: zigpy.profiles.zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
PowerConfiguration.cluster_id,
Identify.cluster_id,
Alarms.cluster_id,
IasZone.cluster_id,
],
OUTPUT_CLUSTERS: [
Ota.cluster_id,
],
},
},
} There is a guide about enabling custom quirks: Copy inside the current Add the proposed code in bottom of the file. |
@javicalle thanks a lot for the quirk! I tried it several times, but the local quirk wasn't loaded. Maybe I misconfigured something. Will check again later today. |
The signature seems OK. Have you tried to remove and pair the device again? |
Can you confirm that device isn't dropping with the quirk? |
Still available! Seems to work as it should! |
12h later: still available! |
Thanks for confirming. 👍🏻 |
@javicalle since version 2023.06 or 2023.05 the device is mostly offline again. After reconnecting I see it for about half an hour or an hour and then it disconnects again. The Energysource is "Battery or Unknown". The signature is {
"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=4627, maximum_buffer_size=64, maximum_incoming_transfer_size=0, server_mask=0, maximum_outgoing_transfer_size=0, descriptor_capability_field=<DescriptorCapability.ExtendedActiveEndpointListAvailable|ExtendedSimpleDescriptorListAvailable: 3>, *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": "0x0104",
"device_type": "0x0402",
"input_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0009",
"0x0500"
],
"output_clusters": [
"0x0019"
]
}
},
"manufacturer": "Heiman",
"model": "CO_CTPG",
"class": "zhaquirks.heiman.smoke.HeimanSmokCO_CTPG"
} |
There had not been changes in the applied quirk from the initial version. It would be changes at ZHA level, but would affect several devices for sure (the Can it be a low battery issue or noise network? |
@javicalle I will check that, thanks for your reply! |
Is your feature request related to a problem? Please describe.
Similar to #1826
When Heiman CO_CTPG Monoxide Carbon sensor is added to HA it reports as a "Mains" powerd device and after some hours drops out of the network
Describe the solution you'd like
If possible a custom quirk to correct it.
Device signature
Diagnostic information
Additional logs
Additional context
The text was updated successfully, but these errors were encountered: