-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 NAS-AB02B0 pairs but does not work #7407
Comments
Hi Bernd. |
No I don't have a Tuya Gateway. There is an App for mobile phones (iOS, Android), but I did not use it. Alos not sure if this app talks WiFi or ZigBee!? I'm not a real expert in ZigBee. I just realized that the pairing works great and the report of the available values looks promising. |
Now I bought an Tuya coordinator and an additional CC2531 and were able to create some sniffing files.
This looks as expected (from my point of view)! But please remember, that the initial problem is that the device seems not to pair completely. Not sure about that statement, but the siren keeps blinking when pairing with zigbee2mqtt. Keys (to encrypt the Wireshark files, see attached zip file): ZigBeeToMQTT log: (Plese note the last few messages)
|
Hi,
So this looks like a time issue (or not... one again, not a Zigbee expert). IMHO, the issue is in the converter, not in zigbee2mqtt |
The more I try to figure this out, the more the "raw" data triggers me! @BerndK this might be usefull reading : https://medium.com/@dzegarra/zigbee2mqtt-how-to-add-support-for-a-new-tuya-based-device-part-2-5492707e882d I'll try to understand the zigbee sniffing you did but not exactly used to! |
I really have hard time understanding that Zigbee protocol! I thought that the Sequence number was used to identify request/response but in the Tuya gateway sniffing, for the 0x24 command, the "request" Seq is 99 (packet 406), and the response one is "71" (packet 412) Another "weird" thing (for me... pretty sure this is not so weird) is the "never responded" 0x10 command (packet 459) So ... I'm a bit lost ... my guess is that the 0x24 can be ignored (like fz.ignore_tuya_set_time might), is it the OTA command missing (I think I tried to add it, but got error message something like "type of undefined") or is it something else completly different... I don't know .... BTW, still trying to figure out the "raw data [9,2,17,0,7,68]" which I wasn't able to find in the z2mqtt sniff |
I might have something for that "raw" thing!! Let's look at packet 244 for exemple: So, according to @dzegarra in is article part 2 that I posted earlier: With the same reasoning, packet 260 might be related to DP 0x71 => 113 : neoTempAlarm Now, even with this findings... I don't know how to try to implement that behaviour in the neo.js device file (ie using the 0x09 "I don't know what" to read measured data instead of "I don't know what") If this might help someone.... |
To go deeper, if reading are done on the 0x09 "I don't know what", it looks like the writing (settings) are done in the 0x11 "I don't know what" Looking at the "Alarm On/off" sniffing: Packet 32 : Same as Packet 5, but with Data : 00 08 68 01 00 01 00 All others 0x02 commands are the readings of the other values: |
Well... I tried various things, but none gives results... :( I think that I have successfully added the "Writes" from packet 174
with a configure block:
But this doesn't seems to change anything (device still keeps blinking) ...
I tried
But only get "Timeout", and looking at the others look-a-like packet (232 for exemple) 0x00, 0x53 become 0x00 0x54 so i must be some kind of counter, not identifier.... |
Hi, I don't have a tuya gateway, did someone try the procedure described here ?: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html |
@Enjoy-Combi |
Pity, I would enjoy to try but have to find a gateway. |
Forget about packet 210, it's the device sending this packet, not the hub... I'm trying to implement a "defaultResponse" to this, but still no luck |
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 |
this workaround worked for me (see also discussion here #7051): |
Closing as is duplicate of #7051 |
Can anyone give me the way to learn how to develop the solution to this problem? I have this siren standing here, and I want to help fix the problem. Any idea how to get started? |
I'd like to buy a good Tuya gateway to debug stuff (and get more devices to work with zigbee2mqtt) so could someone here point me one? |
Was not able to use Zigbee Siren https://www.zigbee2mqtt.io/devices/NAS-AB02B0.html
What happened
I pressed the button in the back of the siren (close to the batteries) for 3 secs, a beep and Device joined and paired.
I paired the siren more or less successfully. System reports successful pairing and reports proper description (see log below).
Using Assistant GUI also reports the correct picture, so something seems to work
perhaps a duplicate of Koenkk/zigbee-herdsman-converters#1932 or #7051 ?
What did you expect to happen
I would expect to receive some messages with payload like humidity, temperature and other values (similar to the last line in log which is another device).
Next thing I expect is that I will be able to send data to the siren like
zigbee2mqtt/0x804b50fffe0482ae/set { "alarm": true }
nothing happens.
While playing around for hours once I got this error:
Zigbee2MQTT:error 2021-05-09 12:53:18: Publish 'set' 'alarm' to '0x804b50fffe0482ae' failed: 'Error: Command 0x804b50fffe0482ae/1 manuSpecificTuya.setData({"status":0,"transid":10,"dp":104,"datatype":1,"length_hi":0,"length_lo":1,"data":[1]}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))'
Was not able to reproduce the error. After normal sending data just nothing happens. I'm able to send data to other devices like e.g an OSRAM Plug switch without problems.
How to reproduce it (minimal and precise)
I pressed button 3 secs, beep, got the log below. Siren is constantly blinking when powered up with USB. Blinking continues after pairing and after repower...
Debug info
Device: NAS-AB02B0
Zigbee Id is 0x804b50fffe0482ae.
Address on Zigbee Network is 0x6474.
Link quality is 102/255.
Model is TS0601 by _TZE200_d0yu2xgi.
Hardware version is 1.
Firmware version is unknown.
This device type is EndDevice
I did not flash the device with other firmware!? It should run original FW.
Version of Zigbee2Mqtt: 1.18.1 [Update] updated to Version 1.18.3, same observation
Coordinator version: 20190425
Coordinator Zigbee Id: 0x00124b0018df4239
Adapter hardware: CC25xx USB Dongle Rev 1.0
Adapter firmware version: ?
This is the log I see:
All items belong to the siren (0x804b50fffe0482ae) except the last lane that shoudl show that ohter items works well, so the overall setup is not broken.
The text was updated successfully, but these errors were encountered: