Neo NAS-AB02B2: Intermittent ignored commands

[IAmTheMilkManMyMilkIsDelicious]

What happened?

Due to the way NAS-AB02B2 is setup in z2m (or firmware) only one command can be sent at a time. When using the siren for multiple purposes (door bell, house alarm, notification beeps) you have to send each command (duration, melody, volume, alarm) one after another.

For example a door bell script:

1. payload: '{ "duration": 4 }'
   topic: zigbee2mqtt/Siren/set
2. payload: '{ "melody": 18 }'
   topic: zigbee2mqtt/Siren/set
3. payload: '{ "volume": "medium" }'
   topic: zigbee2mqtt/Siren/set
4. payload: '{ "alarm": true }'
   topic: zigbee2mqtt/Siren/set

The issue the device has is it will randomly ignore commands. There seems to be no specific command it will or won't ignore. Sometimes I will run this script and it won't set the duration, causing the alarm bell to play forever. Other times it doesn't set the volume and it's too quiet. Many times it just won't play a sound at all.
I figured this was to do with sending multiple commands in succession at the same time, so I added a 5 second delay between each command, and the random failures still happen.

What did you expect to happen?

When running the script I mentioned, it should always play the correct melody for the correct duration

How to reproduce it (minimal and precise)

I used homeassistant so my script looks like this:

alias: Set Door Bell
sequence:
  - service: mqtt.publish
    data:
      topic: zigbee2mqtt/Siren/set
      payload: '{ "duration": 4 }'
  - service: mqtt.publish
    data:
      payload: '{ "melody": 18 }'
      topic: zigbee2mqtt/Siren/set
  - service: mqtt.publish
    data:
      payload: '{ "volume": "medium" }'
      topic: zigbee2mqtt/Siren/set
  - service: mqtt.publish
    data:
      payload: '{ "alarm": true }'
      topic: zigbee2mqtt/Siren/set
mode: single
icon: mdi:bell

But I would also have another script such as:

alias: Set Siren House Alarm Mode
sequence:
  - service: mqtt.publish
    data:
      topic: zigbee2mqtt/Siren/set
      payload: '{ "duration": 900 }'
  - service: mqtt.publish
    data:
      payload: '{ "melody": 7 }'
      topic: zigbee2mqtt/Siren/set
  - service: mqtt.publish
    data:
      payload: '{ "volume": "high" }'
      topic: zigbee2mqtt/Siren/set
  - service: mqtt.publish
    data:
      payload: '{ "alarm": true }'
      topic: zigbee2mqtt/Siren/set

mode: single
icon: mdi:volume-vibrate

To reproduce, I simply run one script then the other a few times. I will always run into random issues where the device ignores certain commands.

Zigbee2MQTT version

1.25.0 commit: 6f1460e

Adapter firmware version

20210120

Adapter

zzh (CC2652R Stick)

Debug log

The debug log doesn't show any warnings or errors and based on my scripts actually does successfully send every command to the device:

Publishing 'set' 'alarm' to 'Siren'
Received MQTT message on 'zigbee2mqtt/Siren/set' with data '{ "alarm": true }'
Publishing 'set' 'alarm' to 'Siren'
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":13}],"seq":52992}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":13}],"seq":53248}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":13}],"seq":53504}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[15],"type":"Buffer"},"datatype":4,"dp":21}],"seq":53760}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[15],"type":"Buffer"},"datatype":4,"dp":21}],"seq":54016}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":4,"dp":5}],"seq":54528}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":1,"dp":13}],"seq":54784}' from endpoint 1 with groupID 0
Received MQTT message on 'zigbee2mqtt/Siren/set' with data '{ "melody": 16 }'
Publishing 'set' 'melody' to 'Siren'
Received MQTT message on 'zigbee2mqtt/Siren/set' with data '{ "volume": "high" }'
Publishing 'set' 'volume' to 'Siren'
Received MQTT message on 'zigbee2mqtt/Siren/set' with data '{ "alarm": true }'
Publishing 'set' 'alarm' to 'Siren'
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[16],"type":"Buffer"},"datatype":4,"dp":21}],"seq":55040}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[2],"type":"Buffer"},"datatype":4,"dp":5}],"seq":55296}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":1,"dp":13}],"seq":55552}' from endpoint 1 with groupID 0
Received Zigbee message from 'Siren', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":1,"dp":13}],"seq":55808}' from endpoint 1 with groupID 0

[github-actions]

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

[IAmTheMilkManMyMilkIsDelicious]

Still an issue on current version 1.25.2

[github-actions]

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

[alb1981]

The problem exists. Zigbee2MQTT 1.27.0-1.

[alb1981]

Zigbee2MQTT Current version: 1.27.2-1
The problem still exists.

[IAmTheMilkManMyMilkIsDelicious]

Yes I still have this issue too, I think this device is either unpopular or this issue only affects a small amount of users. I will likely replace it with the HEIMAN HS2WD-E, hopefully that device may be more reliable.

[jerrm]

I have several of the units. I experienced the issue. I now have a script that has been reliable, it adds a 40ms delay between commands, and issues each command twice, ie: melody, wait, melody, duration, wait, duration, wait, volume, wait, volume, wait, alarm, wait, alarm.

I use standard HA service calls (select_option, set_number, turn_on) vs direct mqtt settings, but doubt that makes a difference.

Obviuosly this is a woraround, not 100% solution, but I haven't had problems since. YMMV.

[jhron]

I have several of the units. I experienced the issue. I now have a script that has been reliable, it adds a 40ms delay between commands, and issues each command twice, ie: melody, wait, melody, duration, wait, duration, wait, volume, wait, volume, wait, alarm, wait, alarm.

I use standard HA service calls (select_option, set_number, turn_on) vs direct mqtt settings, but doubt that makes a difference.

Obviuosly this is a woraround, not 100% solution, but I haven't had problems since. YMMV.

I have the same experience with this sensor. It is not reliable. I have to send only one item per payload and every message 2x with some delay in between. And last is always "alarm": true. Last message can be send only once (I am still testing it, so I can be wrong)
In addition I have to always send everything. Otherwise when I send just "alarm": true, it sometimes set volume and duration back to low and 30s, and sometimes it is just blinking but there is no sound at all from the device.

Originally I had NAS-AB02B0 and it was working ok (until it felled to ground and power connector was broken).

[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 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

[albarts]

I have several of the units. I experienced the issue. I now have a script that has been reliable, it adds a 40ms delay between commands, and issues each command twice, ie: melody, wait, melody, duration, wait, duration, wait, volume, wait, volume, wait, alarm, wait, alarm.

Still same issue with this Siren.
Adding those delays and sending twice each command seems to work ok until a proper fix.