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
Neo NAS-PD07 incorrectly recognized as TuYa TS2020 "manufName":"_TZ3000_kmh5qpmb" "modelId":"TS0202" #10822
Comments
Could you check if this issue has been fixed with the following external converter: const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const definition = {
fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_7hfcudw5'},
{modelID: 'TS0202', manufacturerName: '_TZ3000_kmh5qpmb'}],
model: 'NAS-PD07',
vendor: 'Neo',
description: 'Motion, temperature & humidity sensor CUSTOM',
fromZigbee: [fz.neo_nas_pd07],
toZigbee: [],
onEvent: tuya.onEventSetTime,
exposes: [e.occupancy(), e.humidity(), e.temperature(), e.tamper(), e.battery_low(),
exposes.enum('power_type', ea.STATE, ['battery_full', 'battery_high', 'battery_medium', 'battery_low', 'usb'])],
};
module.exports = definition;
external_converters:
- ext_converter.js
|
I copied the code exactly to the ext_converter.js that is now in the /opt/zigbee2mqtt/data -folder with the configuration.yaml And I got these errors with an endless restart loop for Z2M: ................................
|
@E1m0W think I found the issue, I've updated #10822 (comment) |
Then I'm afraid this device requires new converters since it uses different data points. Some documentation on how to add support for such devices: |
This might actually be problem with my outdated coordinator (CC2531) as it is running Zigbee 1.2 and the devices are Zigbee 3.0. |
I finally got my new Sonoff stick and the results are pretty much the same as before. The only difference is that for some odd reason one of the sensors no longer trigger the motion in Homeassistant (or more accurately the message is not converted correctly, this is without the ext_converter.js): The one that works correctly (regarding to motion):
The one that does not anymore work correctly even regarding to motion.
I don't see any traffic that could be traced to humidity or temperature, nor tampering. The only data comes when there is some motion. This is data is with the ext_converter.js mentioned earlier in this thread:
From log |
Does this one report also something after there has been no motion for some time? |
I recreated the situation last night and two of the sensors had that problem. Unfortunately I cleared the logs afterwards, but as I paired them all again (5pcs) (after a blackout that happened today) and tried to reproduce the situation, and now the motion seems to be working correctly with all of them. I believe that in order to check the humidity and temperature (and tampering) detection I need to get a TuYa gateway and debug through that as there is no indication of any messages (besaids motion) coming through at the moment. |
I have the same problem.
I've tried this but it still doesn't work. Report this: |
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 |
Jordiete...Have you open the device and compared? I have the same device (from Aliexpress) with the same problem |
Great,
many thanks for the photos!!!
I spend a lot of hours with Tasmota e Z2T finding temperature and Humidity
:-(
Where have you buy the original device?
Mine device is as the first...i will open a dispute with Aliexpress.
Have a good day.
Bye,
Maurizio
Bye,
Maurizio
…On Fri, Jun 3, 2022 at 9:02 AM Jordiete ***@***.***> wrote:
[image: IMG-20220310-WA0002]
<https://user-images.githubusercontent.com/23137070/171803876-3714a320-f4b8-4441-81bd-29c4d1b3f2a3.jpg>
[image: IMG-20220426-WA0000]
<https://user-images.githubusercontent.com/23137070/171803884-6aa19f45-7bee-44ef-a08c-744ae82c9b30.jpg>
The second is the original one, the first as you can see is so simple
compared with the original.
—
Reply to this email directly, view it on GitHub
<#10822 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMA3GKTEP7OIWPBAT6CXH7LVNGUYRANCNFSM5MBOW2BQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
UPD: no hum/temp sensors.hi! issue still here. i am trying to add the custom convertor but with no luck
|
What happened?
I just received 5pcs of Neo NAS-PD07 motion,humidity and temperature sensors, but for some reason Z2M recognizes them as TuYa TS2020 motion sensors (and thus I get no temp and humidity, and seems that the tampering might not work correctly when recognized as TS0202).
I have never had any other device incorrectly recognized.
There is Neo NAS-PD07 recognized in the converters, (the last one in neo.js, but the information to recognize the device is in the tuya.js TS0202 section.
I updated Z2M today with the master branch 1.22.2 (before that it was not recognized at all).
The database.db shows these items as:
{"id":10,"type":"EndDevice","ieeeAddr":"0xa4c138171e4fc6a2","nwkAddr":53374,"manufId":4417,"manufName":"_TZ3000_kmh5qpmb","powerSource":"Battery","modelId":"TS0202","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[1,1280,3,0],"outClusterList":[4096,6,25,10],"clusters":{"genBasic":{"dir":{"value":1},"attributes":{"stackVersion":0,"dateCode":""}},"genPowerCfg":{"dir":{"value":1},"attributes":{}},"genIdentify":{"dir":{"value":1},"attributes":{}},"genOnOff":{"dir":{"value":2},"attributes":{}},"genTime":{"dir":{"value":2},"attributes":{}},"genOta":{"dir":{"value":2},"attributes":{}},"ssIasZone":{"dir":{"value":1},"attributes":{"61441":1,"iasCieAddr":"0x00124b00193685b6","zoneState":1,"currentZoneSensitivityLevel":1}},"lightLink":{"dir":{"value":2},"attributes":{}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1642272145699}
{"id":11,"type":"EndDevice","ieeeAddr":"0xa4c138c80243f2d4","nwkAddr":31192,"manufId":4417,"manufName":"_TZ3000_kmh5qpmb","powerSource":"Battery","modelId":"TS0202","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[1,1280,3,0],"outClusterList":[4096,6,25,10],"clusters":{"genBasic":{"attributes":{"stackVersion":0,"dateCode":""}},"ssIasZone":{"attributes":{"61441":1,"iasCieAddr":"0x00124b00193685b6","zoneState":1,"currentZoneSensitivityLevel":1}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1642281335212,"useImplicitCheckin":true}
{"id":12,"type":"EndDevice","ieeeAddr":"0xa4c1387ecc1522e9","nwkAddr":17418,"manufId":4417,"manufName":"_TZ3000_kmh5qpmb","powerSource":"Battery","modelId":"TS0202","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[1,1280,3,0],"outClusterList":[4096,6,25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0202","manufacturerName":"_TZ3000_kmh5qpmb","powerSource":3,"zclVersion":3,"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":""}},"ssIasZone":{"attributes":{"61441":1,"iasCieAddr":"0x00124b00193685b6","zoneState":1,"currentZoneSensitivityLevel":1}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1642281492887,"useImplicitCheckin":true}
{"id":13,"type":"EndDevice","ieeeAddr":"0xa4c1389ab6f05762","nwkAddr":35207,"manufId":4417,"manufName":"_TZ3000_kmh5qpmb","powerSource":"Battery","modelId":"TS0202","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[1,1280,3,0],"outClusterList":[4096,6,25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0202","manufacturerName":"_TZ3000_kmh5qpmb","powerSource":3,"zclVersion":3,"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":""}},"ssIasZone":{"attributes":{"61441":1,"iasCieAddr":"0x00124b00193685b6","zoneState":1,"currentZoneSensitivityLevel":1}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1642281584023,"useImplicitCheckin":true}
{"id":14,"type":"EndDevice","ieeeAddr":"0xa4c138073451c367","nwkAddr":20215,"manufId":4417,"manufName":"_TZ3000_kmh5qpmb","powerSource":"Battery","modelId":"TS0202","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1026,"inClusterList":[1,1280,3,0],"outClusterList":[4096,6,25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0202","manufacturerName":"_TZ3000_kmh5qpmb","powerSource":3,"zclVersion":3,"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":""}},"ssIasZone":{"attributes":{"iasCieAddr":"0x00124b00193685b6","zoneState":1}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":67,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1642281650708,"useImplicitCheckin":true}
What did you expect to happen?
Them to be recognized as NAS-PD07 and have motion, temperature and humidity sensor data.
Now i apparently only get the motion data, and possibly tampering and battery level.
How to reproduce it (minimal and precise)
After unboxing I set the zigbee2mqtt to allow join, plugged the sensors to usb power source and pressed reset button for 10s for each of the Neo NAS-PD07 sensors until they appeared in Homeassistant.
I have zigbee2mqtt running with Mosquitto on Raspberry PI 3.
HA is running in docker
(unfortunately I'm not able to flash the adapter FW version to the latest at the moment.)
.
Zigbee2MQTT version
1.22.2
Adapter firmware version
20181024
Adapter
CC2351 stick
Debug log
log.txt
The text was updated successfully, but these errors were encountered: