Neo NAS-AB02B0 support new hardware identify

[leroyloren]

What happened

I have a new siren, but after successful pairing it does not transmit any information (only LQ). According to the information obtained, this is a new version of HW, which the existing integration of Z2M does not support.

What did you expect to happen

Z2M does not show any information from the device.

https://pastebin.com/6UVQu8gm

How to reproduce it (minimal and precise)

Pair the device with the Z2M

Debug info

Zigbee2MQTT version: 1.18.2-dev commit: 2446e17
Adapter hardware: CC2531, Conbee II
Adapter firmware version: zStack12 (20201127)

[zbuh]

I also received this new version.
Logs in debug:

Zigbee2MQTT:debug 2021-04-09 21:40:51: Received Zigbee message from '0x804b50fffe048344', type 'raw', cluster 'manuSpecificTuya', data '{"data":[9,10,17,0,27,68],"type":"Buffer"}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2021-04-09 21:40:51: No converter available for 'NAS-AB02B0' with cluster 'manuSpecificTuya' and type 'raw' and data '{"data":[9,10,17,0,27,68],"type":"Buffer"}'

[enigmaspb]

Some problem
check inside board
NAS-AB02B0-V3
20190910

[esion-net]

I ordered from 2 different shops at aliexpress, both had some trouble delivering in march (restock problem/version switch?), both delivered NAS-AB02B0-V3 version which is not working currently.

Debug Received Zigbee message from '0x804b50fffe0482a8', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID null Debug Received Zigbee message from '0x804b50fffe0482a8', type 'commandSetTimeRequest', cluster 'manuSpecificTuya', data '{"payloadSize":1792}' from endpoint 1 with groupID null Debug No converter available for 'NAS-AB02B0' with cluster 'manuSpecificTuya' and type 'commandSetTimeRequest' and data '{"payloadSize":1792}' Debug Received Zigbee message from '0x804b50fffe0482a8', type 'raw', cluster 'manuSpecificTuya', data '{"data":[9,3,17,0,8,68],"type":"Buffer"}' from endpoint 1 with groupID null Debug No converter available for 'NAS-AB02B0' with cluster 'manuSpecificTuya' and type 'raw' and data '{"data":[9,3,17,0,8,68],"type":"Buffer"}'

-> Full log on pastebin

[dfrome]

hello,
upvote:
I think I have the same problem. Pairs perfectly, but only sends linkquality. Zigbee2mqtt logs show:
No converter available for 'NAS-AB02B0' with cluster 'manuSpecificTuya' and type 'raw' and data '{\"data\":[9,111,17,0,229,68],\"type\":\"Buffer\"}'

[leroyloren]

Hi, has anyone found anything new or should I look for another supported siren? :-)

[Lefuneste83]

Zigbee2MQTT version 1.18.2 (commit #abd8a092)
Coordinator firmware version: '{"meta":{"maintrel":2,"majorrel":2,"minorrel":7,"product":2,"revision":20190523,"transportrev":2},"type":"zStack30x"}'

Hello. I confirm I see similar issues with the same HW version of this device (NAS-AB02B0-V3).
Pairing is fine and quite fast compared to usual Zigbee devices.

Zigbee2MQTT:info  2021-04-19 02:44:11: Successfully interviewed 'Alarme', device has successfully been paired
Zigbee2MQTT:info  2021-04-19 02:44:11: Device 'Alarme' is supported, identified as: Neo Temperature & humidity sensor and alarm (NAS-AB02B0)
Zigbee2MQTT:info  2021-04-19 02:44:11: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature & humidity sensor and alarm","exposes":[{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":3,"name":"humidity_alarm","property":"humidity_alarm","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Indicates if the battery of this device is almost empty","name":"battery_low","property":"battery_low","type":"binary","value_off":false,"value_on":true},{"access":3,"name":"temperature_alarm","property":"temperature_alarm","type":"binary","value_off":false,"value_on":true},{"access":3,"name":"alarm","property":"alarm","type":"binary","value_off":false,"value_on":true},{"access":3,"name":"melody","property":"melody","type":"enum","values":["1","2","3","4","5","6","7","8","9","10","11","12","13","14","15","16","17","18"]},{"access":3,"name":"duration","property":"duration","type":"numeric","unit":"second"},{"access":3,"name":"temperature_min","property":"temperature_min","type":"numeric","unit":"°C"},{"access":3,"name":"temperature_max","property":"temperature_max","type":"numeric","unit":"°C"},{"access":3,"name":"humidity_min","property":"humidity_min","type":"numeric","unit":"%"},{"access":3,"name":"humidity_max","property":"humidity_max","type":"numeric","unit":"%"},{"access":3,"name":"volume","property":"volume","type":"enum","values":["low","medium","high"]},{"access":1,"name":"power_type","property":"power_type","type":"enum","values":["battery_full","battery_high","battery_medium","battery_low","usb"]},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"NAS-AB02B0","supports_ota":false,"vendor":"Neo"},"friendly_name":"Alarme","ieee_address":"0x804b50fffe04825f","status":"successful","supported":true},"type":"device_interview"}'

Note that although properly paired as stated above the device continues to blink.

It also registers properly in my configuration file every time.

  '0x804b50fffe04825f':
    friendly_name: Alarme

Then it gets displayed properly in Z2MQTT-HA

And I can see the device and entities in HA

The entities are static and as if the device wasn't connected.

I have tried deleting the conf entry, repairing, restart everything... Same state is obtained.

I notice that upon restart Z2MQTT while definitely recognizing the device, all my devices are published to MQTT Queue but not this one as if it is not sending any data or not actually working.

`Zigbee2MQTT:info  2021-04-19 02:29:26: Alarme (0x804b50fffe04825f): NAS-AB02B0 - Neo Temperature & humidity sensor and alarm (EndDevice)`

Zigbee2MQTT:info  2021-04-19 02:29:32: Connected to MQTT server

Upon pairing I get some data under topic homeassistant/binary_sensor/0x804b50fffe04825f and homeassistant/sensor/0x804b50fffe04825f but these are static entries. I don't get any topic under zigbee2mqtt topic as it should.

[esion-net]

Is exact the same behaviour for me too, @Lefuneste83

The light stops after some time though.

I really would like to help and get the new version up and running but as I've mentioned in another thread already - I was not able to properly debug cause none of the tutorials for adding new tuya devices acutally work.

@Koenkk Can you please help out? :)

[Koenkk]

@kirovilya do you know the reason for this?

[zbuh]

I'm also available for help in this. I have a working sniffer if needed.

[kirovilya]

you need to sniff traffic with a native gateway. I made for my (old) version of the siren (now I no longer have it).

[dfrome]

Hope the other guys can do it.
I have no native tuya gateway, else I would have sniffed already.
I bought this hardware because it was listed as supported in HA, so I was confident that I don't need a Tuya gateway.

[leroyloren]

I wrote to the manufacturer, maybe it will provide us with more technical information :-)

[dfrome]

I'm also available for help in this. I have a working sniffer if needed.

hello @zbuh ,
what did you mean with this. Do you have a sniffer AND a Tuya gateway ? ( I understand the sniffer alone would not help, as it will not show the commandos expected by the device. )
regards.

[zbuh]

No I don’t have the Tuya gateway.

[kostas-gr]

Hello,
I also have the same issue. Very interested if you have made any progress yet

[pepsinio]

Any update on this one? I looked into the logs, and get the feeling that the pairing process does not succeed correctly.

[Boxter83]

Hi! I have the same problem with my Neo NAS-AB02B0, successful pairing but cant`t do anything.

Looks like i also have V3

[Enjoy-Combi]

+1, same issue wirh v3

[yjp909]

The same issue...Pairs perfectly, but only sends linkquality, No any operration !

[yjp909]

[dfrome]

There are more and more people having this issue indeed.
@pepsinio @Boxter83 @Enjoy-Combi @yjp909 anyone has a tuya gateway, or know someone who has one ? Our HA specialists can help us only if someone can sniff the messages between our device and a tuya gateway.

[Enjoy-Combi]

Hi,

Is this one could help ? https://fr.aliexpress.com/item/1005001585660474.html?spm=a2g0o.productlist.0.0.1a5050cbMqmusI&algo_pvid=null&algo_expid=null&btsid=0bb0622a16215001006558699e7122&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

I can buy it.

[nmaster2042]

+1 same issue here.

[dfrome]

Hi,

Is this one could help ? https://fr.aliexpress.com/item/1005001585660474.html?spm=a2g0o.productlist.0.0.1a5050cbMqmusI&algo_pvid=null&algo_expid=null&btsid=0bb0622a16215001006558699e7122&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

I can buy it.

I would say yes, this one should work : "Le hub vous permet de contrôler jusqu'à 32 appareils Tuya ZigBee".

[BerndK]

As long as this might a duplicate to #7407 I want to point to my latest post: #7407 (comment)
I'm now able to analyze the traffic. Please let me know if there is something missing.
To check if we have duplicated issues: my siren keeps blinking after pairing to zigbee2mqtt, it does stop bloinking when pairing it to tuya hub. Is this the same behavior as here?

[nmaster2042]

@BerndK : yes it's same issue.

[ristomatti]

Is the data packet sequence logged with the "No converter found" message relevant in identifying the correct converter to use? If it is, I might be out of luck since I didn't find the same mentioned on any issue thread (besides my previous post):

No converter available for 'NAS-AB02B0' with cluster 'manuSpecificTuya' and type 'raw' and data '{"data":[9,4,17,0,6,68],"type":"Buffer"}'

[Lefuneste83]

Congratulations for the debug work !!

I confirm that the alarm properly pairs in Dev Branch.
In current Master branch, the alarm seems to pair as well as I get all entities published in HA, but the alarm itself keeps blinking and I get repeating "device left the network" messages every now and then in Z2M console. So the alarm itself is not happy with the pairing.

How do we know when this commit will be pushed to the master branch ?

[Koenkk]

fix will be included in the next release on 1 december

[ristomatti]

@Koenkk Sorry but did you notice my comment above? Or should I open a new issue as this clearly worked for some. Dev version unfortunately did not fix the issue on my device.

[whiskeytangocharlie]

This has worked for me! Thank you very much! I am a man of my word and will be donating to you @Koenkk

[Koenkk]

@ristomatti

• could you share the data/database.db entry of your device?
• could you share the debug log when pairing this device?
• are you sure you are on the latest-dev?
• what coordinator + firmware are you using?

[ristomatti]

are you sure you are on the latest-dev?

I was pretty sure I was, but I decided to double check to not waste your time. I had indeed rebuilt my Docker image with the tag latest-dev... but I had not pulled an update to the image first 🤦‍♂️. It worked on the first try. Thanks @Koenkk!

The issue shall remain closed.

And for the record for others who might still be having issues:

Zigbee2MQTT version 1.22.0-dev commit: d192bbd
Coordinator CC2652R (Electrolama zzh) / zStack3x0
Coordinator revision 20210708

Database entry

{
  "id": 41,
  "type": "EndDevice",
  "ieeeAddr": "0x804b50fffe046f18",
  "nwkAddr": 6881,
  "manufId": 4098,
  "manufName": "_TZE200_d0yu2xgi",
  "powerSource": "Battery",
  "modelId": "TS0601",
  "epList": [
    1
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 81,
      "inClusterList": [
        0,
        4,
        5,
        61184
      ],
      "outClusterList": [
        25,
        10
      ],
      "clusters": {
        "genBasic": {
          "attributes": {
            "65506": 31,
            "65508": 1,
            "modelId": "TS0601",
            "manufacturerName": "_TZE200_d0yu2xgi",
            "powerSource": 3,
            "zclVersion": 3,
            "appVersion": 85,
            "stackVersion": 0,
            "hwVersion": 1,
            "dateCode": ""
          }
        }
      },
      "binds": [],
      "configuredReportings": [],
      "meta": {}
    }
  },
  "appVersion": 85,
  "stackVersion": 0,
  "hwVersion": 1,
  "dateCode": "",
  "zclVersion": 3,
  "interviewCompleted": true,
  "meta": {
    "configured": -925140590
  },
  "lastSeen": 1636913362609,
  "useImplicitCheckin": true
}

[ristomatti]

@Koenkk The duration setting seems to behave a bit weird* but I'll need to play around with it a bit to understand if this is a property of the device, bug or perhaps a side effect of the setting homeassistant_legacy_triggers: true. It would be a separate issue regardless.

*) Setting the duration has an effect if done immediately before enabling the alarm but resets to null afterwards. It also resets to null after changing any other setting.

[beatmag]

Hi everyone. My sirens arrive just yesterday.
I updated the code to the dev branch and tried to pair the siren.
It does the interview and seems ok. No errors nothing.

But the lights keep flashing and don't really get any status updates at all.

I'm on cc2531. Latest 3.0 coordinator firmware.

I pressed the reset button till it beeps once then it leaves and pairs again. But I can't get the lights to switch off and no status updates.

Can anyone think of anything?

[beatmag]

Forgot to mention I also don't have batteries installed into the siren yet.

[ristomatti]

@beatmag Batteries were not needed for me. When I properly had the dev branch running, it "just worked".

[beatmag]

Thanks everyone.

I followed the switch to dev instructions and now it's working fine!!!!

Getting status updates etc. will test more.

Blinking lights have disappeared.

[jusxon]

After updating to 1.22.1-1 and adding my second Neo NAS-AB02B0 it paired fine and everything works great, however, the other NAS-AB02B0 that I paired while on 1.22.0-3 last week still continues to blink and only shows link quality. I have tried removing it from Z2M and resetting the alarm multiple times with the reset button, but the same issue persists.

Any tips from anyone experienced using these or what are the chances the alarm is bad?

[BillPil]

@jusxon This is exactly what I am facing too.

[Koenkk]

try to reconfigure the device from the frontend (yellow refresh button)

[jusxon]

I was able to get it working by deleting the alarm from Z2M, resetting the alarm, pairing back to Z2M, and then reconfiguring.

[BillPil]

I followed the above and worked for me well too.
Thanks!

[whiskeytangocharlie]

Is it possible to deliver a payload that does more than one thing? At the minute when I send a payload to turn the volume up and set the melody to something else it will only send the first part of the payload and turn the volume up.
Payload = {"volume":"high"," melody":3}
If I send Payload = {" melody":3,"volume":"high"}
Then it only sets the melody and doesn't change the volume.

[dfrome]

hello, I upvoted this topic in April 2021, and wanted to say I'm happy it has been resolved. I updated today my zigbee2mqtt version to 1,22 and tested the siren successfully.
For my original purpose (call children for dinner!), I had in between crafted a makeshift siren with an MQTT-driven-electric motor and an old bell, this has been working for months already, so I don't even know if I'm going to replace it with the NEO siren, but at least now I have an additional toy to play with...

thanks and keep up the good work.

[Vladyno]

Has anyone in the NR already been able to change melodies and other parameters at the same time? It's not working yet.

[losip]

Works for me - but I do publish separate messages for each parameter I want to change, e.g melody, volume and duration

[Vladyno]

@losip Would you please have a pattern of your flow there?

[losip]

This is what I use to make the dog bark when the postman presses the button on the door:
alias: Door Bell pushed
description: ''
trigger:

• platform: device
  domain: mqtt
  device_id: fda4c23aeaca1b6497ba0914e80650c5
  type: action
  subtype: single
  discovery_id: 0x00158d00023e41f3 action_single
  condition: []
  action:
• device_id: ecd4504a1cf4c420022a8b8e16f6d410
  domain: select
  entity_id: select.neo_siren_melody
  type: select_option
  option: '10'
• device_id: ecd4504a1cf4c420022a8b8e16f6d410
  domain: number
  entity_id: number.neo_siren_duration
  type: set_value
  value: 10
• device_id: ecd4504a1cf4c420022a8b8e16f6d410
  domain: select
  entity_id: select.neo_siren_volume
  type: select_option
  option: high
• type: turn_on
  device_id: ecd4504a1cf4c420022a8b8e16f6d410
  entity_id: switch.neo_siren_alarm
  domain: switch
  mode: restart

[losip]

Sorry, when pasting my - signs have been changed to bullets (dots) but you get the idea

[smpillai11]

@Koenkk when will this fix be available in stable for HA addon? Thanks