Woox R7049 Smoke Alarm

[RealBitfox]

Hello, I need help with the indecration of Woox R7049 smoke detectors in ZigbeeToMqTT. The device has been paired - the status is "Unsupported". What can I do? Thanks for help!!!

[nickrout]

https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

[cchristofr]

Hi @RealBitfox I don't have this device for the moment, but I'm interested to know if you have successfully integrated it with the tutorial given by @nickrout Regards Christophe

[RealBitfox]

Hello Christophe, I already knew the tutorial by @nickrout. Unfortunately, it was not helpful for me. I have not yet succeeded in integrating the detectors. I have not received any further help from the community.

Many greetings!

[cchristofr]

Hello Christophe, I already knew the tutorial by @nickrout. Unfortunately, it was not helpful for me. I have not yet succeeded in integrating the detectors. I have not received any further help from the community.

Many greetings!

Hello @RealBitfox from my point of view, if the requirement is to integrate a zigbee device in HA, then a gateway like ZiGate (or PiZiGate) is sufficient. And with HA you can use the data from the zigbee device to pilot other devices (zigbee or not). But, if you want to exchange information between devices then a broker like mqtt can be useful.

[nickrout]

I already knew the tutorial by @nickrout. Unfortunately, it was not helpful for me. I have not yet succeeded in integrating the detectors. I have not received any further help from the community.

How did you go with the tutorial? You have provided nothing about your experience of getting it working.

[RealBitfox]

Hello and good day! Yes, you are right. I have revealed too little information. I apologise for this! First of all, the general conditions: My English is not the best, I can speak German much better. ;) That makes it quite difficult. The instructions say: 1. pairing the device with Zigbee2MQTT. This works, the device is registered and listed as "not supported". Then it says: 2. adding your device #

The next step is to add an entry of your device to node_modules/zigbee-herdsman-converters/devices.js

That's where it ends for me. Where can I find this file?

Many greetings!

[cchristofr]

Hello Christophe, I already knew the tutorial by @nickrout. Unfortunately, it was not helpful for me. I have not yet succeeded in integrating the detectors. I have not received any further help from the community.

Many greetings!

Hello @RealBitfox Have you had a look to integrate "R7049 Smoke Alarm" in HA with a gateway like ZiGate ? Maybe the integration and use of data in HA would be easier. It seems that ZigbeeToMqTT supports more devices than ZiGate (or ConBee II) so if you (and me) want to use other zigbee devices , then ZigbeeToMqTT would be a better approach.

For the moment I have only z-wave devices and I hesitate to change for zigbee (cheaper).

[nickrout]

Really the instructions are very plain. How did you install z2m?

On Tue, 16 Feb 2021, 20:43 RealBitfox, notifications@github.com wrote:

Hello and good day! Yes, you are right. I have revealed too little information. I apologise for this! First of all, the general conditions: My English is not the best, I can speak German much better. ;) That makes it quite difficult. The instructions say: 1. pairing the device with Zigbee2MQTT. This works, the device is registered and listed as "not supported". Then it says: 2. adding your device #

The next step is to add an entry of your device to node_modules/zigbee-herdsman-converters/devices.js

That's where it ends for me. Where can I find this file?

Many greetings!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/6044#issuecomment-779650580, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG6PX4IVGGWK2QMGMEEAQDS7IO3RANCNFSM4W6FJ26A .

[RealBitfox]

Hey Christophe, I have to explain something: I don't want the smoke detectors to be integrated at my place, it's for a neighbour who I want to get interested in Home Assistant. I myself use a Conbee and I have many Zigbee devices running. Also Wlan devices with Tasmota and some ESP8266 and ESP32 as sensors. I have built a smoke detector with Zigbee. Works very well and was ready in 30 minutes! The neighbour's Woox smoke detectors are to be integrated via zigbeetomqtt, as other devices are to be registered...

[RealBitfox]

@nickrout Hi! Yes, Zigbee2mqtt,Current version: 1.17.1-4 is installed and working. At the moment, some devices are also registered. That all works. A Woox smoke detector is registered, but the manufacturer is shown as unsupported.

Thanks for your help!

[nickrout]

Add-on, docker or none of the above?

On Wed, 17 Feb 2021, 23:35 RealBitfox, notifications@github.com wrote:

@nickrout https://github.com/nickrout Hi! Yes, Zigbee2mqtt,Current version: 1.17.1-4 is installed and working. At the moment, some devices are also registered. That all works. A Woox smoke detector is registered, but the manufacturer is shown as unsupported.

Thanks for your help!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/6044#issuecomment-780463257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG6PX6AIGK2SAOSZ5KCBTTS7OLW5ANCNFSM4W6FJ26A .

[RealBitfox]

Hassos auf Raspberry 3B.....

[nickrout]

Then I think the instructions are here

https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/blob/master/zigbee2mqtt/DOCS.md#adding-support-for-new-devices

On Thu, Feb 18, 2021 at 8:11 PM RealBitfox notifications@github.com wrote:

Hassos auf Raspberry 3B.....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/6044#issuecomment-781110713, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG6PXZCYUKW4VWTUO6QQIDS7S4T5ANCNFSM4W6FJ26A .

[Miswu13]

I too have the same Woox smoke detector, and the same problem. I followed the instructions from link, but can't find node_modules/zigbee-herdsman-converters/devices.js in my zigbee2mqtt folder on Home Assistant. Is there a separate program that i have to install? The log, it says: Zigbee2MQTT:warn 2021-03-20 18:57:05: Device '0xbc33acfffe3317e9' with Zigbee model 'TS0601' and manufacturer name '_TZE200_aycxwiau' is NOT supported, please follow https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html Zigbee2MQTT:warn 2021-03-20 18:57:46: Device '0xbc33acfffe3317e9' left the network

Where can i find devices.js file, so that i can modify it?

L.E. : I have enabled debug, deleted the sensor, and pair it again - and the log is: Info Device '0xbc33acfffe3317e9' joined Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xbc33acfffe3317e9","ieee_address":"0xbc33acfffe3317e9"},"type":"device_joined"}' Info Starting interview of '0xbc33acfffe3317e9' Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xbc33acfffe3317e9","ieee_address":"0xbc33acfffe3317e9","status":"started"},"type":"device_interview"}' Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0xbc33acfffe3317e9"},"type":"device_connected"}' Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0xbc33acfffe3317e9"},"type":"pairing"}' Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID null Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[1],"type":"Buffer"},"datatype":4,"dp":1,"fn":0,"status":0,"transid":31}' from endpoint 1 with groupID null Debug No converter available for 'TS0201' with cluster 'manuSpecificTuya' and type 'commandGetData' and data '{"data":{"data":[1],"type":"Buffer"},"datatype":4,"dp":1,"fn":0,"status":0,"transid":31}' Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[0],"type":"Buffer"},"datatype":5,"dp":11,"fn":0,"status":0,"transid":32}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'commandGetData', cluster 'manuSpecificTuya', data '{"data":{"data":[2],"type":"Buffer"},"datatype":4,"dp":14,"fn":0,"status":0,"transid":33}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'raw', cluster 'manuSpecificTuya', data '{"data":[25,85,36,0,56],"type":"Buffer"}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'raw', cluster 'manuSpecificTuya', data '{"data":[9,86,17,0,57,128],"type":"Buffer"}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"_TZE200_aycxwiau"}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"appVersion":65}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"stackVersion":0}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{"dateCode":""}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Debug Received Zigbee message from '0xbc33acfffe3317e9', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID null Debug Skipping message, definition is undefined and still interviewing Info Successfully interviewed '0xbc33acfffe3317e9', device has successfully been paired Warning Device '0xbc33acfffe3317e9' with Zigbee model 'undefined' and manufacturer name '_TZE200_aycxwiau' is NOT supported, please follow https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":null,"friendly_name":"0xbc33acfffe3317e9","ieee_address":"0xbc33acfffe3317e9","status":"successful","supported":false},"type":"device_interview"}' Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"friendly_name":"0xbc33acfffe3317e9","supported":false},"type":"pairing"}' Debug Saving state to file /config/zigbee2mqtt/state.json

[nickrout]

How did you install z2m?

[Miswu13]

I added a new repository in Home assistant addon store, and after that i installed z2m. Why? Should i add, another repository, What repository? Or did i installed it wrong?

[nickrout]

There is now an ability to add external convertors via the gui. Click settings and follow your nose.

[Miswu13]

The external convertor, it doesn't work. I have put the code between the [ ], and after restart z2m, the gui gives me error, and doesn't load - tried multiple times. To repair it I have to manually modify the configuration.yaml, and delete the code i inserted. It is a waste of time and effort - i will send back the sensor, and buy one that it is already supported. Thanks for trying to help The data that I have entered: { fingerprint: [ R7049_Woox { modelID: 'TS0601', manufacturerName: '_TZE200_aycxwiau' }, ], model: 'R7049', vendor: 'Woox', description: 'Smart Smoke Alarm', supports: 'alarm', fromZigbee: [ fz.ignore_basic_report, fz.tuya_data_point_dump, fz.ias_smoke_alarm_1, fz.battery, ], toZigbee: [ tz.tuya_data_point_test, ], onEvent: tuya.setTime, meta: { configureKey: 1, }, configure: async (device, coordinatorEndpoint, logger) => { const endpoint = device.getEndpoint(1); await bind(endpoint, coordinatorEndpoint, ['genBasic']); }, exposes: [ exposes: [e.smoke(), e.battery_low(), e.tamper(), e.battery() ], },

[Miswu13]

Does anyone know, where can i find a list of smoke detectors supported by z2m?

[nickrout]

I am sure the z2m authors regret you wasting your time. Have you asked for help with your external converters file? I think not.

The zigbee2mqtt project has a list of supported devices. Look there.

[Miswu13]

I get your sarcasm, but it's ok. I was just saying that for me it is faster to buy another sensor, than it is to invest time to find out what is wrong with this one, especially when i haven't found a suitable file with necessary steps. I thought that it would be easy to create a file and insert some code in it, based on a example... Don't get me wrong, it is a good addon, i love it, and i will continue using it, but with the devices that it supports. Thank you again for your time and answer

[nickrout]

There are examples of external converters here: https://github.com/Koenkk/zigbee2mqtt.io/tree/master/docs/externalConvertersExample

And I must say yours looks nothing like that (I think, I find js pretty tough to read!)

[Miswu13]

Thank you for the link. I have succeded to make the the device supported in z2m, but at the Exposes tab, all are N/A, except e.warning(), that let's me select the sound efect - i don't know if i need that. The e.smoke() witch i think it is the most important, it is N/A.

[nickrout]

What happens if you [s]light a fire[/s] expose it to some smoke?

On Mon, Mar 22, 2021 at 10:36 AM Miswu13 @.***> wrote:

Thank you for the link. I have succeded to make the the device supported in z2m, but at the Exposes tab, all are N/A, except e.warning(), that let's me select the sound efect - i don't know if i need that. The e.smoke() witch i think it is the most important, it is N/A.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/6044#issuecomment-803663937, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG6PX5JDGQOR57B6QQRXMTTEZRFFANCNFSM4W6FJ26A .

[cchristofr]

Does anyone know, where can i find a list of smoke detectors supported by z2m?

hello I use this one: https://www.zigbee2mqtt.io/devices/HS3SA.html#heiman-hs3sa (I have also Fibaro FGSD002 but it is zwave).

[Miswu13]

Thank you @cchristofr, i will chek it out. I'll search for a zigbee model since i have already the conbee II stick ! @nickrout , I triggered the device with smoke, the alarm from the device goes on, but z2m sensor, doesn't trigger any of entities from Exposes tab. Even the battery entity, is N/A. The log from adon says something like this for every entity from Exposes: Zigbee2MQTT:debug 2021-03-22 17:07:41: Received MQTT message on 'homeassistant/sensor/0xbc33acfffe3317e9/battery/config' with data '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xbc33acfffe3317e9"],"manufacturer":"CR Smart Home","model":"Smart Smoke Alarm (TS0601)","name":"0xbc33acfffe3317e9","sw_version":"Zigbee2MQTT 1.18.1"},"device_class":"battery","json_attributes_topic":"zigbee2mqtt/0xbc33acfffe3317e9","name":"0xbc33acfffe3317e9 battery","state_topic":"zigbee2mqtt/0xbc33acfffe3317e9","unique_id":"0xbc33acfffe3317e9_battery_zigbee2mqtt","unit_of_measurement":"%","value_template":"{{ value_json.battery }}"}'

and the external converters file is this: `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 e = exposes.presets;

const device = { // zigbeeModel: ['myZigbeeModel'], fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE200_aycxwiau'}], model: 'TS0601', vendor: 'CR Smart Home', description: 'Smart Smoke Alarm', whiteLabel: [{vendor: 'Woox', model: 'R7049'}], fromZigbee: [fz.ias_smoke_alarm_1, fz.ts0216_siren, fz.battery, fz.command_status_change_notification_action, fz.ias_no_alarm, fz.ias_contact_alarm_1], toZigbee: [tz.ts0216_alarm, tz.ts0216_duration, tz.ts0216_volume, tz.warning], exposes: [e.contact(), e.gas(), e.smoke(), e.battery_low(), e.tamper(), e.battery(), e.warning()], };

module.exports = device;`

[cchristofr]

heiman-hs3sa works well with zigbee2mqtt (I use a zigate as coordinator). But it gives only info about "smoke".

The zwave Fibaro FGSD002, gives many more informations like temperature, delta of temperature and your can set different kind of alarm. Of course, it is more expensive. It works with zwave2mqtt.

[github-actions[bot]]

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