[BUG] zhaquirks.tuya.ts0601_valve.ParksidePSBZS attribute timer_duration missing

Describe the bug I have a strange issue with two identical Parkside Irrigation Zigbee Smart Valves, which come up in HA as zhaquirks.tuya.ts0601_valve.ParksidePSBZS One comes with the attribute timer_duration (and the related Entity) and it can be used as intended, whereas the other one misses that attribute/Entity.

To Reproduce N/A

Expected behavior Having attribute/entity timer_duration in each zhaquirks.tuya.ts0601_valve.ParksidePSBZS device

Screenshots

Device signature of both devices is the same:

Device 9-Parkside-Irrigation-Back (this one comes with the timer_duration attribute/entity as expected):

{
  "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=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, 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": "0x0000",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_htnnfasr",
  "model": "TS0601",
  "class": "zhaquirks.tuya.ts0601_valve.ParksidePSBZS"
}

Device 9-Parkside-Irrigation-Front (this one misses the attribute/entity):

{
  "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=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, 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": "0x0000",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_htnnfasr",
  "model": "TS0601",
  "class": "zhaquirks.tuya.ts0601_valve.ParksidePSBZS"
<details>
<!-- Device signature can be acquired by clicking on the "Zigbee Device Signature" button in the device settings view -->
<summary>Device signature</summary>

Diagnostic information of both devices

zha-c75dae519ffd301f071295c2f25c56db-_TZE200_htnnfasr TS0601-1d3d630694311be16d326839d7768180.json.txt zha-c75dae519ffd301f071295c2f25c56db-_TZE200_htnnfasr TS0601-c0d8e18371d419989d842a5aae1162ad.json.txt

Paste the diagnostic information here.
Don't remove the extra line breaks outside the ``` marks.

Additional logs

Paste any additional debug logs here.
Don't remove the extra line breaks outside the ``` marks.

Additional context Add any other context about the problem here.

[DieterTHeck]

Hi,

I have basically the same issue - but only a single device. It was never “initialized” with the vendor’s tuya interface / App.

time_left sensor is available - it shows 0 when off, and always showed 1 when enabled. So the valve turned back to off after 1 minute. (my tactical solution: send “ON” message every 55 seconds).

timer_duration is NOT shown.

I tried to GET/SET it via Cluster commands as indicated above, but it always shows NONE This is independent of whether the valve is currently ON or OFF.

Now funnily, after SET Value to 15, the Cluster panel still shows None when querying. BUT: the time_left sensor shows now 15 minutes when I switch the valve on. I can replicate this by setting whatever value I want. It shows next time as time_left.

Still, I’d be interested in getting timer_duration into the UI as proper entity.

[DieterTHeck]

@mglaabde I don’t see the write_attributes in your logs. Have you tried to re pair your device?

I believe that this device also have some function to turn on without any time out, but I don’t remember where I see it.

Over at Zigbee2MQTT I saw this. https://github.com/Koenkk/zigbee2mqtt/issues/7695#issuecomment-1180640196 So try sending a null to it. Havent tested myself.

Is there actually a way to send these cluster commands in a automation / NodeRed or whatever?