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
[New device support]: Outdoor Siren by Lexman (LDSENK07) #12818
Comments
Can I have some help on how to test what I should put in Should I better start with empty parentheses in the external converter instead of putting there something which appears as non-working? Thanks for any help... |
You can try to execute the squawk and warnings commands from the z2m gui (click on your device -> exposes tab) |
Thanks for this suggestion.
|
Update: many minutes later the Siren starts flashing and making sounds, with irregular frequency and nothing in the log. Edit:
In the meanwhile I had to tak the battery away to make it stop (it's late for today...) By the way, there is some progress here, even if I do not know where to go next. It looks like I still have no action available in Home Assistant for this device... |
This morning I reconnected the batteries and the siren stayed quiet.
Not sure of which one was effective (actually I do not know what's the difference among this two commands). Moreover, I had some error message later (which inclueded a 'timeout'...is this timeout related to the delay between the command and the noise produced?). They potentially appeared when the siren started to make noise:
Moreover, I am not sure that the noise-sequences of the siren corresponded to command. They were surely initiated by the command; however, they looked not so regular. And moreover, they never stopped. I tried with
|
Can you try to repair this device directly next to the coordinator and keep it there? This may solve the big delay you are seeing (maybe one of the routers is messing up) |
The siren Is already less than a meter away from the coordinator and I think it was already there when I last paired it. |
Can you try with the following external converter? Make sure to reapair the device after loading the new 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 definition = {
zigbeeModel: ['LDSENK07'], // The model ID from: Device with modelID 'lumi.sens' is not supported.
model: 'LDSENK07', // Vendor model number, look on the device for a model number
vendor: 'ADEO', // Vendor of the device (only used for documentation and startup logging)
description: 'Lexman Wireless Smart Outdoor Siren', // Description of the device, copy from vendor site. (only used for documentation and startup logging)
fromZigbee: [fz.battery, fz.ias_siren],
toZigbee: [tz.warning, tz.squawk],
exposes: [e.warning(), e.squawk(), e.battery(), e.battery_low(), e.tamper()],
configure: async (device, coordinatorEndpoint, logger) => {
device.defaultSendRequestWhen = 'immediate';
device.save();
await device.getEndpoint(1).unbind('genPollCtrl', coordinatorEndpoint);
},
};
module.exports = definition; |
Thanks for your support !!!
I can now call the siren from Home Assistant but only passing through the What should I then do next ? |
Great, added it now for support out-of-the-box. HA doesn't provide a nice way to integrate a siren device, so you should use the Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
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 |
Hi, @Sonyoyo, I own the same device and it seems that any "warning" "mode" I select in z2m UI, the siren produces the same sound. Also tested publishing via MQTT, same results:
|
Link
https://enki-home.com/produit/sirene-exterieure-connectee-sur-batterie-lexman/
Database entry
{"id":20,"type":"EndDevice","ieeeAddr":"0x04cd15fffe6390ed","nwkAddr":20687,"manufId":4727,"manufName":"ADEO","powerSource":"Battery","modelId":"LDSENK07","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":1027,"inClusterList":[0,3,32,1280,1282,2821],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"LDSENK07","manufacturerName":"ADEO","powerSource":3,"zclVersion":3,"appVersion":2,"stackVersion":6,"hwVersion":1,"dateCode":"20200521-15","swBuildId":"2.3"}},"ssIasZone":{"attributes":{"iasCieAddr":"0x00124b0024c315d8","zoneState":1}},"genPollCtrl":{"attributes":{"checkinInterval":6480}}},"binds":[{"cluster":32,"type":"endpoint","deviceIeeeAddress":"0x00124b0024c315d8","endpointID":1}],"configuredReportings":[],"meta":{}}},"appVersion":2,"stackVersion":6,"hwVersion":1,"dateCode":"20200521-15","swBuildId":"2.3","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1655132684738,"defaultSendRequestWhen":"active"}
Comments
I started using Home Assistant and Zigbee2MQTT a couple of month ago and this is my first 'unsupported' device.
I tried to add a dedicated converter following the instructions and now the siren looks like it is supported...but actually nothing is really working with the siren. Neither the battery status is showing up correctly.
To fill the converter I took a look to other sirens already supported. However, honestly, I do not know how I can check what really correspond to the functionalities of my device.
As far as I understood the process (and the Zigbee protocol), to discover features of devices such as remote controller, one can press the buttons and look at the log to see the messages which are sent. But in the case of a siren, no button is available to press and the functionalities are essentially services that can be called or states that can be read...if only I knew their names !
Thanks in advance for any help.
External converter
Supported color modes
No response
Color temperature range
No response
The text was updated successfully, but these errors were encountered: