How to support Tuya outdoor Siren Alarm (_TZE200_nlrfgpny)?

[junbing2006]

I just bought a Tuya Outdoor Solar Siren Alarm (link https://www.aliexpress.com/item/1005005264809268.html).
It joins the Zigbee network okay, but shows not supported.
I tried to follow the "add new device" tutorial to add a new device, but did go very far.
Please give me some suggestions?

• Some related debug messsage

`
2023-04-13.22-33-37/log.txt:debug 2023-04-13 22:35:59: Received Zigbee message from '0xa4c138fb19fbd64b', type 'readResponse', cluster 'genBasic', data '{"65534":0,"appVersion":72,"manufacturerName":"_TZE200_nlrfgpny","modelId":"TS0601","powerSource":3,"zclVersion":3}' from endpoint 1 with groupID 0
2023-04-13.22-33-37/log.txt:info 2023-04-13 22:35:59: Successfully configured '0xa4c138fb19fbd64b'
2023-04-13.22-33-37/log.txt:debug 2023-04-13 22:36:02: Received Zigbee message from '0xa4c138fb19fbd64b', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":0,"appVersion":72}' from endpoint 1 with groupID 0
2023-04-13.22-33-37/log.txt:debug 2023-04-13 22:36:02: Received Zigbee message from '0xa4c138fb19fbd64b', type 'attributeReport', cluster 'genBasic', data '{"65503":"E?�+\u0013E@�+eF@�+\u0012"}' from endpoint 1 with groupID 0
2023-04-13.22-33-37/log.txt:debug 2023-04-13 22:36:03: Received Zigbee message from '0xa4c138fb19fbd64b', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0

2023-04-13.22-33-37/log.txt:debug 2023-04-13 22:52:45: Received Zigbee message from '0xa4c138fb19fbd64b', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":6}],"seq":3328}' from endpoint 1 with groupID 0
2023-04-13.22-33-37/log.txt-debug 2023-04-13 22:52:45: No converter available for '_TZE200_nlrfgpny' with cluster 'manuSpecificTuya' and type 'commandDataReport' and data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":6}],"seq":3328}'
2023-04-13.22-33-37/log.txt-debug 2023-04-13 22:52:46: Received Zigbee message from 'zb71_soil', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":2816}' from endpoint 1 with groupID 0

2023-04-13.23-19-15/.nfs000000000003e31000000002:debug 2023-04-13 23:19:46: Received Zigbee message from '0xa4c138fb19fbd64b', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":0,"appVersion":72}' from endpoint 1 with groupID 0
2023-04-13.23-19-15/.nfs000000000003e31000000002:debug 2023-04-13 23:19:46: Received Zigbee message from '0xa4c138fb19fbd64b', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0

2023-04-13.23-19-15/.nfs000000000003e31000000002:debug 2023-04-13 23:19:47: Received Zigbee message from '0xa4c138fb19fbd64b', type 'attributeReport', cluster 'genBasic', data '{"65503":"bJ�+\u0013�J�+e�J�+\u0012"}' from endpoint 1 with groupID 0

`

• my configuration _TZE200_nlrfgpny.js

`
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 = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE200_nlrfgpny',
},
],
model: 'TS0601_new',
vendor: 'TuYa',
description: 'Outdoor Siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints],

configure: tuya.configureMagicPacket,
exposes: [
    // Here you should put all functionality that your device exposes
    e.battery(),
],
meta: {
    // All datapoints go in here
    tuyaDatapoints: [
    ],
},

};

module.exports = definition;

`

[ParalaX002]

Hi, I just got one yesterday and have the same question :) I’ll be looking into it too, and post here if I find something.

[junbing2006]

Found one discussion here on the language I didn't understand.

https://community.jeedom.com/t/sirene-tuya-tze200-nlrfgpny/105678/4

[yoyey]

Hi,
I bought the same siren and I also try to make it working with zigbee2mqtt. For now, the switch to activate the siren is working but the alarm state don't.
This the the js file :
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 = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE200_nlrfgpny',
},
],
model: 'TS0601',
vendor: 'TuYa',
description: 'Outdoor siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints],
onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
configure: tuya.configureMagicPacket,
exposes: [e.battery(),e.tamper(),
exposes.binary('alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Alarm switch'),
exposes.binary('tamper_alarm_switch', ea.STATE, 'ON', 'OFF').withDescription('Tamper alarm switch'),
exposes.enum('alarm_ringtone', ea.STATE_SET, ['Ringtone 1', 'Ringtone 2', 'Ringtone 3']).withDescription('Ringtone of the alarm'),
exposes.enum('Set alarm state', ea.STATE_SET, ['Sound alarm', 'Light alarm', 'Sound and light alarm']).withDescription('Set Alarm state'),
exposes.enum('Alarm state', ea.STATE, ['No alarm', 'Voice alarm', 'Light alarm','Voice and light alarm']),
exposes.numeric('alarm_time', ea.STATE_SET).withValueMin(1).withValueMax(60).withValueStep(1).withUnit('min').withDescription('Alarm time'),
],
meta: {
// All datapoints go in here
tuyaDatapoints: [
[1, 'Alarm state', tuya.valueConverterBasic.lookup({'No Alarm': 1, 'Voice alarm': 2, 'Light alarm': 3,'Voice and light alarm': 4})],
[15, 'Battery level', tuya.valueConverter.raw],
[13, 'alarm_switch', tuya.valueConverter.onOff],
[101, 'tamper_alarm_switch', tuya.valueConverter.onOff],
[21, 'alarm_ringtone', tuya.valueConverterBasic.lookup({'Ringtone 1': 1, 'Ringtone 2': 2, 'Ringtone 3': 3})],
[102, 'Set alarm state', tuya.valueConverterBasic.lookup({'Sound alarm': 0, 'Light alarm': 1, 'Sound and light alarm': 2})],
[7, 'alarm_time', tuya.valueConverter.raw],
],
},
};

module.exports = definition;

Now I need to understand the tuyaDatapoints.

[junbing2006]

@yoyey Great job! I read somewhere that the protocol details can be found if you have a Tuya development account.

[medassi]

Hello, I also bought this siren _TZE200_nlrfgpny rated NAO NAS-AB06B (Ali express). I created a NAS-AB06B.js file and integrated the external converter. I manage to turn the siren sound on and off but many functions are missing: melody, sound volume,... . I tried to ask the Ali Express seller to send me much more complete technical documentation... without any real response. Thanks for sharing information above. I will keep you informed if I manage to do better than you. I have a Tuya Dev account but unfortunately no Tuya Zigbee gateway to "sniff" the frames. I follow your progress with attention.

[yoyey]

Hi,
I have the tuya gateway. You will find in attach the datapoint.
siren_datatpoint.txt
Maybe this can help us to make the siren working.

[xvolte]

Thanks for that. do you have one to change de melody for instance ? is it code 21?

[jakubjakubik]

One more datapoint I've found

exposes.binary('charge_state', ea.STATE, 'Charging', 'Not Charging').withDescription('Charging state'),

[6, 'charge_state', tuya.valueConverter.onOff],

shows if the usb charger is plugged in or not :)

[junbing2006]

@jakubjakubik, Great job!

[evirci]

does it really work?

[jakubjakubik]

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 tzLocal = {
        tamper_alarm_switch: {
                key: ['tamper_alarm_switch'],
                convertSet: async (entity, key, value, meta) => {
                        const lookup = {'off': false, 'on': true };
                        value = value.toLowerCase();
                        const pState = lookup [value];
                        await tuya.sendDataPointBool(entity, 101, pState);
                        return {state: {tamper_alarm_switch: value}};
                }
        },
        alarm_mode: {
                key: ['alarm_mode'],
                convertSet: async (entity, key, value, meta) => {
                        value = value.toLowerCase();
                        await tuya.sendDataPointEnum(entity, 102, {'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2 }[value]);
                        return {state: {alarm_mode: value}};
                }
        },
        alarm_melody: {
                key: ['alarm_melody'],
                convertSet: async (entity, key, value, meta) => {
                        value = value.toLowerCase();
                        await tuya.sendDataPointEnum(entity, 21, {'melody1': 0, 'melody2': 1, 'melody3': 2}[value]);
                        return {state: {alarm_melody: value}};
                }
        }
}

const definition = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE200_nlrfgpny',
},
],
model: 'TS0601',
vendor: 'TuYa',
description: 'Outdoor siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints, tzLocal.tamper_alarm_switch,tzLocal.alarm_mode,tzLocal.alarm_melody],
onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
configure: tuya.configureMagicPacket,
exposes: [
exposes.enum('alarm_state', ea.STATE, ['alarm_sound', 'alarm_light', 'alarm_sound_light', 'normal']),
exposes.binary('alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Alarm switch'),
exposes.binary('tamper_alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Tamper alarm switch'),
exposes.binary('tamper_alarm', ea.STATE, 'ON', 'OFF').withDescription('Tamper state'),
exposes.enum('alarm_melody', ea.STATE_SET, ['melody1', 'melody2', 'melody3']).withDescription('Ringtone of the alarm'),
exposes.enum('alarm_mode', ea.STATE_SET, ['alarm_sound', 'alarm_light', 'alarm_sound_light']),
exposes.numeric('alarm_time', ea.STATE_SET).withValueMin(1).withValueMax(60).withValueStep(1).withUnit('min').withDescription('Alarm time'),
exposes.binary('charge_state', ea.STATE, 'Charging', 'Not Charging').withDescription('Charging state'),
exposes.numeric('battery', ea.STATE),
],
meta: {
// All datapoints go in here
tuyaDatapoints: [
[1, 'alarm_state', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2,'normal': 3})],
[15, 'battery', tuya.valueConverter.raw],
[13, 'alarm_switch', tuya.valueConverter.onOff],
[101, 'tamper_alarm_switch', tuya.valueConverter.onOff],
[20, 'tamper_alarm', tuya.valueConverter.onOff],
[21, 'alarm_melody', tuya.valueConverterBasic.lookup({'melody1': 0, 'melody2': 1, 'melody3': 2})],
[102, 'alarm_mode', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2})],
[7, 'alarm_time', tuya.valueConverter.raw],
[6, 'charge_state', tuya.valueConverter.onOff],
],
},
};

module.exports = definition;

The settings for turning on/off the tamper alarm work, setting the alarm type (light/sound) work, picking the alarm melody works, turning it off and on works.
Not sure about the battery report yet.

The code is quick & dirty and probably not up to standards. I'd appreciate if somebody with more experience in quality of this code could take a look and make an official PR.

[medassi]

Very good Job. Thank you very much. I think the battery function is not working. I left it running for 1 day with no battery charge status feedback. Is this siren able to handle siren volume? Not sure with DP ID 5. Anyway, thanks again, I didn't understand how to add TzLocal, it's now OK. THANKS

[xvolte]

@jakubjakubik congrats for the file if it is now working :) i'm jalous :D
do you know DDF file? could you have a look here (dresden-elektronik/deconz-rest-plugin#6941) to help us troubleshoot ? no problem if you don't have the time and thank you very much for the file

[tm1981]

@jakubjakubik thanks for this, i have the same device, working great, about the battery in tuya iot platform the battery is called battery_percentage, attached picture, is this change anything?

https://i.postimg.cc/Pr5xv6qB/Screenshot-2023-05-03-231151.png

[evirci]

thak you for the job!
are you sure the the choice of alarm light, alarm sound and alarm sound/light is working properly?
The battery percentage not working

[tm1981]

i can confirm that sound, light, sound, and light are working for me
every function the device support is working for me except the battery

[xvolte]

just bougth one, and was wondering why i didn't see anything in HA.
Can you advise where i should put your JS script please ?

Thanks very much for that :D

[jakubjakubik]

@xvolte
in configuration.yaml you put

external_converters:
  - TS0601.js

and place the contents above into TS0601.js in the same directory as the configuration.yaml file

[xvolte]

Thank you very much !

So i was using the Deconz official addon, so i understood i needed to install Zigbee2MQTT which i wanted to do for a long time.

So i started installing ! However, i need to recreate my network : The whole mesh, all the sensors, and all the associated Nodered items... which seems to me a PAIN in the *ss having already 30+ sensors (doors, motion detection, wall plug, ...).

So far i don't have the time to test it right now,.. But anyway, i understand we are ALMOST there ;)

[xvolte]

btw, i opened a device support request for Deconz conbee 2 key : dresden-elektronik/deconz-rest-plugin#6941, in case anyother people are wondering how to use it on a conbee2 key

[xvolte]

Can someone tell me if you are able to change Volume, Duration or MELODY please? or only the switch works in your case?

[evirci]

HI, i have the same device and the same problems...
Add the battery level wrong

[tm1981]

Hi, this device doesn't have support to change volume, even when using it with tuya app.

[ParalaX002]

Hi. I confirm that it is working for me too. I also managed to get the battery once, but no luck since. I think it is something like:
e.battery().withUnit('%'),

or
exposes.numeric('battery', ea.STATE).withUnit('%'),

But it only worked one. Somebody had more luck?

[ParalaX002]

Ok, forget what I said:
e.battery().withUnit('%'),
seems to be working just fine :) Tried to power the device with a bench supply, and I get changing values when I change the input voltage :) Can someone confirm? If so I think everything works.

[tm1981]

hi, i have tried e.battery().withUnit('%') it's not working for me, can you share the full code ?

[stefanoaltissimo]

i also tried, and it is not working as I expected because i got a N/A but, probably, its needed to wait a change of the state of the battery to get a new message and a refresh of the state. May be there is a way to query the general state of the device?

[xvolte]

can you tell me the version of the siren in the software you are using please ?
I got =

[Pitt13]

Hi,
Do you think that will be integrated soon in the next versions Zigbee2Mqtt?

[evirci]

I hope so

[PV-Web]

Thank you so much all. I used the code from jakubjakubik which works great. For now the basics work and I can use the device. I will follow this post if someone has an update for the other features.

[stefanoaltissimo]

Hello, just to say that i am thinking that is no possible to get back from the device the battery status.I tried everything reading TUYa documentation but simply i have never been able to get the battery status in the payload. So... I do not know. Just I would be courious to have the whole batch from Parala since he says that he has been able to get back the battery data and to have any news about his bench supply; May be it has any meaning in the behaviur of the siren... anyway, battery aparat, everything is working and this is already a success. Thank you to all.

[ParalaX002]

Hi, sorry for the delay; don't have access at everything while I'm at work.

So here is the full code:
`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 tzLocal = {
tamper_alarm_switch: {
key: ['tamper_alarm_switch'],
convertSet: async (entity, key, value, meta) => {
const lookup = {'off': false, 'on': true };
value = value.toLowerCase();
const pState = lookup [value];
await tuya.sendDataPointBool(entity, 101, pState);
return {state: {tamper_alarm_switch: value}};
}
},
alarm_mode: {
key: ['alarm_mode'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 102, {'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2 }[value]);
return {state: {alarm_mode: value}};
}
},
alarm_melody: {
key: ['alarm_melody'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 21, {'melody1': 0, 'melody2': 1, 'melody3': 2}[value]);
return {state: {alarm_melody: value}};
}
}
}

const definition = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE200_nlrfgpny',
},
],
model: 'TS0601',
vendor: 'TuYa',
description: 'Outdoor siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints, tzLocal.tamper_alarm_switch,tzLocal.alarm_mode,tzLocal.alarm_melody],
onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
configure: tuya.configureMagicPacket,
exposes: [
exposes.enum('alarm_state', ea.STATE, ['alarm_sound', 'alarm_light', 'alarm_sound_light', 'normal']),
exposes.binary('alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Alarm switch'),
exposes.binary('tamper_alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Tamper alarm switch'),
exposes.binary('tamper_alarm', ea.STATE, 'ON', 'OFF').withDescription('Tamper state'),
exposes.enum('alarm_melody', ea.STATE_SET, ['melody1', 'melody2', 'melody3']).withDescription('Ringtone of the alarm'),
exposes.enum('alarm_mode', ea.STATE_SET, ['alarm_sound', 'alarm_light', 'alarm_sound_light']),
exposes.numeric('alarm_time', ea.STATE_SET).withValueMin(1).withValueMax(60).withValueStep(1).withUnit('min').withDescription('Alarm time'),
exposes.binary('charge_state', ea.STATE, 'Charging', 'Not Charging').withDescription('Charging state'),
e.battery().withUnit('%'),
],
meta: {
// All datapoints go in here
tuyaDatapoints: [
[1, 'alarm_state', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2,'normal': 3})],
[15, 'battery', tuya.valueConverter.raw],
[13, 'alarm_switch', tuya.valueConverter.onOff],
[101, 'tamper_alarm_switch', tuya.valueConverter.onOff],
[20, 'tamper_alarm', tuya.valueConverter.onOff],
[21, 'alarm_melody', tuya.valueConverterBasic.lookup({'melody1': 0, 'melody2': 1, 'melody3': 2})],
[102, 'alarm_mode', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2})],
[7, 'alarm_time', tuya.valueConverter.raw],
[6, 'charge_state', tuya.valueConverter.onOff],
],
},
};

module.exports = definition;`

Now, I didn't take the time to wait for the device to send the data. So what I did is plug the charger, add the bench supply (if you do this, be careful that the battery charger will send power to the supply, so you need one that is ok with that), and then plug - unplug the charger.
When doing so, I get battery data, at least I thought. Today, battery level is not updating correctly anymore; but at some point I definitely got some correct data.

When charging, I get those logs:
Debug 2023-05-10 21:03:13Received Zigbee message from '0xa4c1385267cd9440', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[1],"type":"Buffer"},"datatype":1,"dp":6}],"seq":768}' from endpoint 1 with groupID 0 Info 2023-05-10 21:03:13MQTT publish: topic 'zigbee2mqtt/0xa4c1385267cd9440', payload '{"alarm_melody":"melody1","alarm_mode":"alarm_light","alarm_state":"normal","alarm_switch":"OFF","alarm_time":5,"battery":66,"battery_level":86,"charge_state":"ON","linkquality":244,"tamper_alarm":"OFF","tamper_alarm_switch":"OFF"}'

When unplugging, I get this:
Debug 2023-05-10 21:04:30Received Zigbee message from '0xa4c1385267cd9440', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":6}],"seq":1536}' from endpoint 1 with groupID 0 Info 2023-05-10 21:04:30MQTT publish: topic 'zigbee2mqtt/0xa4c1385267cd9440', payload '{"alarm_melody":"melody1","alarm_mode":"alarm_light","alarm_state":"normal","alarm_switch":"OFF","alarm_time":5,"battery":66,"battery_level":86,"charge_state":"OFF","linkquality":240,"tamper_alarm":"OFF","tamper_alarm_switch":"OFF"}'
As you can see, there is a battery item that was present at some point. I think the "battery_level" is a reference to a test I did before and is not relevant.

Now, maybe that there need to be an event so that the battery is sent.
I also saw that the Tuya datapoint given earlier mentioned a request. So initially, I tried to use "ea.STATE_GET", but zigbee2mqtt complained that it didn't have any converter for battery.

I'll continue to look into that, but I don't have much time at the moment :s

[stefanoaltissimo]

Veramente grazie mille,
but probably there is something wrong at my side, may be a different firmware, I just copied your code (that it is totally similar to mine) with the same result. I connected and disconncted the charger but, well, no payload with these events! :(

[exico91]

Hello, mine is working with a mix of @ParalaX002 and @jakubjakubik templates. The only thing that is not working is the battery:

`
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 tzLocal = {
tamper_alarm_switch: {
key: ['tamper_alarm_switch'],
convertSet: async (entity, key, value, meta) => {
const lookup = {'off': false, 'on': true };
value = value.toLowerCase();
const pState = lookup [value];
await tuya.sendDataPointBool(entity, 101, pState);
return {state: {tamper_alarm_switch: value}};
}
},
alarm_mode: {
key: ['alarm_mode'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 102, {'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2 }[value]);
return {state: {alarm_mode: value}};
}
},
alarm_melody: {
key: ['alarm_melody'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 21, {'melody1': 0, 'melody2': 1, 'melody3': 2}[value]);
return {state: {alarm_melody: value}};
}
}
}

const definition = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE200_nlrfgpny',
},
],
model: 'TS0601',
vendor: 'TuYa',
description: 'Outdoor siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints, tzLocal.tamper_alarm_switch,tzLocal.alarm_mode,tzLocal.alarm_melody],
onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
configure: tuya.configureMagicPacket,
exposes: [
e.battery().withUnit('%'),
exposes.enum('alarm_state', ea.STATE, ['alarm_sound', 'alarm_light', 'alarm_sound_light', 'normal']),
exposes.binary('alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Alarm switch'),
exposes.binary('tamper_alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Tamper alarm switch'),
exposes.binary('tamper_alarm', ea.STATE, 'ON', 'OFF').withDescription('Tamper state'),
exposes.enum('alarm_melody', ea.STATE_SET, ['melody1', 'melody2', 'melody3']).withDescription('Ringtone of the alarm'),
exposes.enum('alarm_mode', ea.STATE_SET, ['alarm_sound', 'alarm_light', 'alarm_sound_light']),
exposes.numeric('alarm_time', ea.STATE_SET).withValueMin(1).withValueMax(60).withValueStep(1).withUnit('min').withDescription('Alarm time'),
exposes.binary('charge_state', ea.STATE, 'Charging', 'Not Charging').withDescription('Charging state'),
],
meta: {
// All datapoints go in here
tuyaDatapoints: [
[15, 'battery', tuya.valueConverter.raw],
[1, 'alarm_state', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2,'normal': 3})],
[13, 'alarm_switch', tuya.valueConverter.onOff],
[101, 'tamper_alarm_switch', tuya.valueConverter.onOff],
[20, 'tamper_alarm', tuya.valueConverter.onOff],
[21, 'alarm_melody', tuya.valueConverterBasic.lookup({'melody1': 0, 'melody2': 1, 'melody3': 2})],
[102, 'alarm_mode', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2})],
[7, 'alarm_time', tuya.valueConverter.raw],
[6, 'charge_state', tuya.valueConverter.onOff],
],
},
};

module.exports = definition;
`

[emilianogetino]

For me it worked after restarting Homeassistant, but not the operating system but the host, unplugging the minipc where everything is installed from the power, since that day it has worked perfectly for me.

[averter]

Hi all, I must be doing something very stupid since it keeps saying that it's not supported. I've 1) added the code from @jakubjakubik
into a TS0601.js file and the two extra lines in configuration.yaml, 2) restarted zigbee2mqtt, and 3) tried to re-interview it or re-pair the siren. There are no errors, but as said it still says that it's not supported, so I'm not sure what to do next...Any help is very welcome

[gregoriusus]

Why are you using external converter. Siren is supported in Zigbee2Mqtt natively. No need for external converter. Mine is working ok and also shows battery status

[averter]

How come? Initially I've tried to add it without the external converter, Im on the latest version 1.40.1 commit: 403d3c09, and the siren was flagged as not being supported, hence why I've tried to use an external converter.

[gregoriusus]

Hmm, funny. Under model I have https://www.zigbee2mqtt.io/devices/NAS-AB06B2.html

I don't know, maybe helper is still in use? Or maybe you have strange version of sirene. I brought from Moes, but a lot of others is offering same sirenee, at least looks the same.

[averter]

@gregoriusus Are you using the development version of zigbee2mqtt by any chance? Could that be the reason why it is not working for me?

Thanks in advance for any help.

[averter]

Hmmm, I might be wrong but that siren seems to be from NEO not TUYA (although it looks the same) which is what's covered in this discussion thread. The model code is also different, which reinforces that we might not be discussing the same device?

[averter]

It seems that @yalec38 had the same issue and the trick was to reboot the raspberry pi. I've tried that but no luck, it is still unsupported.

[kwetnico]

For me, same problem.
No battery after 6 month on zigbee2mqtt..1.40.1. 😪

[kurdybanek]

Gregz, what do you have as zigbee manuracturer? My siren shows sane model as yours, though it doesn't show battery status Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Gregz ***@***.***> Sent: Wednesday, September 25, 2024 5:14:30 pm To: Koenkk/zigbee2mqtt ***@***.***> Cc: kurdybanek ***@***.***>; Comment ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] How to support Tuya outdoor Siren Alarm (_TZE200_nlrfgpny)? (Discussion #17325) Hmm, funny. Under model I have https://www.zigbee2mqtt.io/devices/NAS-AB06B2.html I don't know, maybe helper is still in use? Or maybe you have strange version of sirene. I brought from Moes, but a lot of others is offering same sirenee, at least looks the same. — Reply to this email directly, view it on GitHub<#17325 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56RUIQXMMHWFLBLPQQTZYLHNHAVCNFSM6AAAAAAW5UOKYSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZVGI4DMNQ>. You are receiving this because you commented.Message ID: ***@***.***>

[gregoriusus]

This is my device. Could it be, that only shows when battery changes and since it is batery powered, it could take a long time? Also, I think, it showed, when I turned off raspberry and turned it on...

[kurdybanek]

I don't think this is the case, as I have it for couple of months now and still no battery info. Initially I used external converter but when it became supported, I moved to the standard one (mine shows exact same info as yours). Maybe reconfiguring or excluding re-including would help, but I doubt (I think I already did that once, but I'm not sure). HA encountered several restarts or switches off during that time, so that is not a solution either Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Gregz ***@***.***> Sent: Wednesday, September 25, 2024 9:05:56 PM To: Koenkk/zigbee2mqtt ***@***.***> Cc: kurdybanek ***@***.***>; Comment ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] How to support Tuya outdoor Siren Alarm (_TZE200_nlrfgpny)? (Discussion #17325) This is my device. Could it be, that only shows when battery changes and since it is batery powered, it could take a long time? Also, I think, it showed, when I turned off raspberry and turned it on... Screenshot_2024-09-25-21-02-40-02_c3a231c25ed346e59462e84656a70e50.jpg (view on web)<https://github.com/user-attachments/assets/6da9ec66-fd49-44ef-803d-4c8392a1aa6e> — Reply to this email directly, view it on GitHub<#17325 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56QFMUPFWHVK2MRIB5TZYMCRJAVCNFSM6AAAAAAW5UOKYSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZVGUZTQOI>. You are receiving this because you commented.Message ID: ***@***.***>

[gregoriusus]

Could it be that on daily light could battery fill to 100%, because zigbee doesn't use much power and sirene is not updating it's state that frequently? This is a thought...

[xmatr1x69]

Hi, I got the siren with the new zigbee manufacturer code: "_TZE284_nlrfgpny". Everything else is the same. Editing the code in the 46 line worked for me. You can add PR or something so all the other people with new models have it supported!

edit: choosing sound melody and alarm mode (lights, sound) is not working

[xmatr1x69]

@averter with the external converter in the exposes tab I can select melody1-3 and alarm mode, but siren is still using default (melody1, mode_sound_light) nad my battery % is working fine

[averter]

@xmatr1x69 So basically we have two sirens of the same manufacturer, and both of us have changed the code in the same way to support it, but I cannot see the battery while you can, and you cannot change the melody and alarm mode but I can. Terrific!
First things that come to mind is to compare our software versions, and ideally if you can double check that your change of code is the same as the one which has been submitted in the PR mentioned above. Thanks.

[xmatr1x69]

@averter I disabled external converter, so now I am using official PR from Z2M, battery at 100% (charged it a week ago), but still no luck with melody change. (TS0601, _TZE284_nlrfgpny)

[averter]

@xmatr1x69 and @tuzibeast : are you using the Z2M dev version, as the herdsman-converters are not yet up-to-date with the current Z2M version?

[tuzibeast]

Not sure if my version is Z2M dev, I just went to HA system settings and clicked on Z2M update.

With the external converter I couldn’t see the battery % so I did a test and removed the external converter and unpaired the siren from network.

as a result, the siren was still recognised (supported) automatically but I couldn’t get it to work I.e. I couldn’t trigger the alarm

so I went back to using ext converter. Everything works fine excepts for battery%

[Sabjul33]

I have th same siren and same trouble.
I test it with launch the light.
After that i have this

and not the ?
I wait if i see the battery purcentage maybe a miracle

[xmatr1x69]

Charge it and wait, mine is showing real battery % after one day

[Sabjul33]

I have the siren for several months.

[kwetnico]

It never worked for me either

[Sabjul33]

I have a second siren same model but i haven't opened it yet..
May be i should test it if i have the same problem.

[gregoriusus]

So, the solution would be to change part of battery code in official converter with external converter?

Or there is a difference based on manufacturer? You can check my previous post, screenshot, which model and manufacturer I am using... As for me, everything is working with official converted.

[tuzibeast]

I recently bought Tuya outdoor Siren Alarm with Solar from Aliexpress, everything seems to be the same except the Zigbee manfuacturer is : _TZE284_nlrfgpny. Device shows as Not supported in Zigbee2MQTT. Exposes tab is completely blank.

Can anyone kindly suggest what needs to be changed in the js. file or config.

I'm using HA OS 13.2
Add-on Zigbee2MQTT 1.40.2-1

generated_external_definition
const definition = {
zigbeeModel: ['TS0601'],
model: 'TS0601',
vendor: '_TZE284_nlrfgpny',
description: 'Automatically generated definition',
extend: [],
meta: {},
};

module.exports = definition;

In the .js file I modified fingerprint: manufacturerName: '_TZE284_nlrfgpny'

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 tzLocal = {
tamper_alarm_switch: {
key: ['tamper_alarm_switch'],
convertSet: async (entity, key, value, meta) => {
const lookup = {'off': false, 'on': true };
value = value.toLowerCase();
const pState = lookup [value];
await tuya.sendDataPointBool(entity, 101, pState);
return {state: {tamper_alarm_switch: value}};
}
},

alarm_mode: {
key: ['alarm_mode'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 102, {'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2 }[value]);
return {state: {alarm_mode: value}};
}
},

alarm_melody: {
key: ['alarm_melody'],
convertSet: async (entity, key, value, meta) => {
value = value.toLowerCase();
await tuya.sendDataPointEnum(entity, 21, {'melody1': 0, 'melody2': 1, 'melody3': 2}[value]);
return {state: {alarm_melody: value}};
}
}

}

const definition = {
// Since a lot of TuYa devices use the same modelID, but use different datapoints
// it's necessary to provide a fingerprint instead of a zigbeeModel
fingerprint: [
{
// The model ID from: Device with modelID 'TS0601' is not supported
// You may need to add \u0000 at the end of the name in some cases
modelID: 'TS0601',
// The manufacturer name from: Device with modelID 'TS0601' is not supported.
manufacturerName: '_TZE284_nlrfgpny',
},
],
model: 'TS0601',
vendor: 'TuYa',
description: 'Outdoor siren',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints, tzLocal.tamper_alarm_switch,tzLocal.alarm_mode,tzLocal.alarm_melody],
onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
configure: tuya.configureMagicPacket,
exposes: [
e.battery().withUnit('%'),
exposes.enum('alarm_state', ea.STATE, ['alarm_sound', 'alarm_light', 'alarm_sound_light', 'normal']),
exposes.binary('alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Alarm switch'),
exposes.binary('tamper_alarm_switch', ea.STATE_SET, 'ON', 'OFF').withDescription('Tamper alarm switch'),
exposes.binary('tamper_alarm', ea.STATE, 'ON', 'OFF').withDescription('Tamper state'),
exposes.enum('alarm_melody', ea.STATE_SET, ['melody1', 'melody2', 'melody3']).withDescription('Ringtone of the alarm'),
exposes.enum('alarm_mode', ea.STATE_SET, ['alarm_sound', 'alarm_light', 'alarm_sound_light']),
exposes.numeric('alarm_time', ea.STATE_SET).withValueMin(1).withValueMax(60).withValueStep(1).withUnit('min').withDescription('Alarm time'),
exposes.binary('charge_state', ea.STATE, 'Charging', 'Not Charging').withDescription('Charging state'),
],
meta: {
// All datapoints go in here
tuyaDatapoints: [
[15, 'battery', tuya.valueConverter.raw],
[1, 'alarm_state', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2,'normal': 3})],
[13, 'alarm_switch', tuya.valueConverter.onOff],
[101, 'tamper_alarm_switch', tuya.valueConverter.onOff],
[20, 'tamper_alarm', tuya.valueConverter.onOff],
[21, 'alarm_melody', tuya.valueConverterBasic.lookup({'melody1': 0, 'melody2': 1, 'melody3': 2})],
[102, 'alarm_mode', tuya.valueConverterBasic.lookup({'alarm_sound': 0, 'alarm_light': 1, 'alarm_sound_light': 2})],
[7, 'alarm_time', tuya.valueConverter.raw],
[6, 'charge_state', tuya.valueConverter.onOff],
],
},
};

module.exports = definition;

Added an extra line for external converter in /homeassistant/zigbee2mqtt/configuration.yaml

.
.
.
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
external_converters:

• TS0601.js
  .
  .

ISSUE still there :(
The devices is still shown as Not supported, no error messages, no notifications. I restarted Zigbee2MQTT a number of times. Also tried to add external converter from the UI. The device is still Not supported.

[averter]

If you update to 1.41 you should be able to see something

[tuzibeast]

I've just updated Z2M and it works !! thanks so much

[Sabjul33]

I've just updated Z2M and it works !! thanks so much

What is your device model ?
I've update Z2M to 1.41 and nothing for me.
I have this
Modèle Zigbee
TS0601
Constructeur Zigbee
_TZE200_nlrfgpny

In state :
"battery": null,

So finally no battery %.

[averter]

yes, the battery is not working for many others as well. There's even a separate issue for that specific purpose, although with limited/no clear solution in sight...I'm starting to think that it's impossible to have that information in Z2M...

[tuzibeast]

I have TZE284_nlrfgpny and using the external converter with the code I posted earlier in the thread.

I can changed between 3 melodies, changed the mode (alert, sound or alert plus sound)

The only thing that doesn’t work is the battery %

[kurdybanek]

Similar here, in exposes tab, "charging" and "battery" are both N/A TS0601, _TZE200_nlrfgpny_, z2m 1.41.0-1

…

________________________________ From: Sabjul33 ***@***.***> Sent: Wednesday, November 6, 2024 7:44:26 PM To: Koenkk/zigbee2mqtt ***@***.***> Cc: kurdybanek ***@***.***>; Comment ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] How to support Tuya outdoor Siren Alarm (_TZE200_nlrfgpny)? (Discussion #17325) I've just updated Z2M and it works !! thanks so much What is your device model ? I've update Z2M to 1.41 and nothing for me. I have this Modèle Zigbee TS0601 Constructeur Zigbee _TZE200_nlrfgpny In state : "battery": null, So finally no battery %. — Reply to this email directly, view it on GitHub<#17325 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZSO56SL5RGMQGTD5KQ467DZ7JPQVAVCNFSM6AAAAAAW5UOKYSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJWHE4TGMY>. You are receiving this because you commented.Message ID: ***@***.***>

[Sabjul33]

For me "charging": false,
Battery ? and in state i don't have battery (I try to activate the alarm "light only" to use battery after i have % and in state battery null).

So i have a question in my Z2M configuration i have a file siren.js so i don't remember if is it a file with Z2M or a file i've created with external converter.

[kwetnico]

For me "charging": false, Battery ? and in state i don't have battery (I try to activate the alarm "light only" to use battery after i have % and in state battery null).

So i have a question in my Z2M configuration i have a file siren.js so i don't remember if is it a file with Z2M or a file i've created with external converter.

This is your file I had created it too.

It never works I think our battery with this siren under z2M