NAS-AB02B2 Alarm mqtt /set only accepts first parameter

[weltmeyer]

What happened?

When sending a /set to an "NEO NAS-AB02B2" (alias _TZE204_t1blo2bj/TS0601) it only accepts the first parameter. Example:

{
    "melody": 3,
    "volume": "low",
    "alarm": false
}

Here only "melody" is changed. volume and alarm are not changed on the device.

When sending 3 consecutive messages with only 1 parameter each, they all are accepted.

What did you expect to happen?

Accept all sent parameters

How to reproduce it (minimal and precise)

as seen in "What happened"

Zigbee2MQTT version

1.31.0

Adapter firmware version

20221226

Adapter

POE Zigbee Stick, tested also on slaesh's directly via USB

Debug log

No response

[weltmeyer]

seems like stale/closed issue #12542, #12220

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[weltmeyer]

not stale

[Nafanya10]

This problem still exists. The issue the device has is it will randomly ignore commands. I send each command (duration, melody, volume, alarm) one after another, but the random failures still happen. Please help fix this issue.

Model: Alarm (NAS-AB02B2) Manufacture: Zigbee TZE204_t1blo2bj Zigbee2MQTT Current version: 1.32.1 Home Assistant Core 2023.7.2

This is my automation code and it always works differently, in most cases works not correctly (not all parameters change):

alias: Audible alarm - alarm
description: ""
trigger:
  - platform: state
    entity_id:
      - input_button.virtual_button_02_alarm
    enabled: true
condition: []
action:
  - service: mqtt.publish
    data:
      qos: 0
      retain: false
      topic: zigbee2mqtt/Audible alarm/set
      payload: "{\"volume\": \"medium\"}"
  - delay:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 40
  - service: mqtt.publish
    data:
      qos: 0
      retain: false
      topic: zigbee2mqtt/Audible alarm/set
      payload: "{\"melody\": 3}"
    enabled: true
  - delay:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 40
  - service: mqtt.publish
    data:
      qos: 0
      retain: false
      topic: zigbee2mqtt/Audible alarm/set
      payload: "{\"duration\": 15}"
  - delay:
      hours: 0
      minutes: 0
      seconds: 0
      milliseconds: 40
  - service: mqtt.publish
    data:
      qos: 0
      retain: false
      topic: zigbee2mqtt/Audible alarm/set
      payload: "{\"alarm\": \"true\"}"
mode: single

[Nafanya10]

Today I changed the way of automation, but the new way is also not stable. Automation works unpredictably, some parameters are updated, and some remain the same. The result of automation triggering is unpredictable, each time automation triggers differently.

Please help fix this issue.

My new code:

alias: Audible alarm - bells
description: ""
trigger:
  - platform: state
    entity_id:
      - input_button.virtual_button_04_bells
condition: []
action:
  - device_id: d756b4873254559f9d2c983ca2d10496
    domain: number
    entity_id: ae1aaf8d259d9deaaaae9a83da5e533a
    type: set_value
    value: 5
  - type: turn_on
    device_id: d756b4873254559f9d2c983ca2d10496
    entity_id: 8a614924a59f8a74253890b7561f421f
    domain: switch
  - device_id: d756b4873254559f9d2c983ca2d10496
    domain: select
    entity_id: 2ef0c1f8cedc25418acfaada3d7c0dc5
    type: select_option
    option: "1"
  - device_id: d756b4873254559f9d2c983ca2d10496
    domain: select
    entity_id: b400f1158ef903d7ab4dcbef00c2787b
    type: select_option
    option: medium
mode: single

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[Dreyk007]

Not stale. Same issue with this device

[wojtekzw]

Issue is still present. Even sending command one by one does not always help. Commands are ignored randomly