Edge Driver for Aqara Smoke Sensor JY-GZ-01AQ?

Devices & Integrations
1

Since I got all my other Aqara Devices (Water Leak, Window/Door Magnet, Vibration, Weather) to link up with the Aeotec Hub with Edge Drivers from the community, but not the Smoke Sensor, I wonder if someone has a tip? Maybe this is a fairly new device, as it was the only one coming in pure chinese, with no english manual. I’m not sure how to get it to pair, since the button on it pressed long launches alamr sequences, a loud and a very loud one a bit later when pressed even longer.

It doesn’t even link up as Zigbee Thing, so I’m not sure how to help developers more.

1 Like
2

I got a bit further now by randomly trying things :slight_smile: I tried pushing its button quickly several times (I think 3 times did the trick? Maybe 2 is enough) and it started blinking green, which has let me quickly pair it with my Aeotec Hub and it now shows up as a Zigbee Thing. The driver says:

Model: lumi.sensor_smoke.acn03
Manufacturer: LUMI
Zigbee EUI: 54EF44100048431A
ZCL Version: 3
Server Clusters: 01={0000,0500,0003,0001}
Client Clusters: 01={00019}

Does this help?

3

@veonua can you add this to your drivers? Or if it’s already existing then I must have missed it myself . TIA

4

the fingerprint is added hopefully it works the same way as Xiaomi Honeywell Fire Alarm Smoke Detector JTYJ-GD-01LM/BW Zigbee compatibility

1 Like
5

Is this the “Zigbee Water Leak/Smoke Sensor” driver in veons channel? I tried that before but it still shows up as Zigbee Thing. Is there some time to wait till this driver is actualized on the channel?

I also wonder about these drivers:

  1. Do I need to delete/reinstall newer drivers or do they auto update an nothing is required?
  2. Can the Zigbee Thing driver I have installed take precendence over a more specific driver? I.e. do I have to delete the “Thing” driver everytime I try to connect something? So far this seems not needed, as the specific one always grabbed my aqara devices first?
6

you should be able to swap the driver in the app @voon

7

Which driver is it? I ask, because the “Zigbee Water Leak/Smoke Sensor” driver in your channel has a version from June, when I freshly install it and check the drivers Info in the App.

8

re-published the driver with prefix 1.1 now

9

Tested it. It does recognize it in Smartthings, but seems not to report anything, just striked cloud symbols for Smokedetector, Voltage and Battery. Also went to the fireplace to trigger the detecor, which it did (boy is that thing loud), but that didn’t register in smartthings.

10

well, apparently it doesn’t.
I put my second guess into v1.2. but I would recommend installing CLI and getting logs

11

Ok, the CLI doesn’t tell me that much, but I tried something and maybe this helps you. I clicked the button on the device (which does nothing on the device visibly), that created a few log lines. I also went to test with some smoke and launched the alarm again, which I think also caused a trigger … but I’m not sure which lines as I was at the fireplace, not my pc. But maybe this helps you?

─────────────────────────────────────────────────────────────────────────────────

Driver Id Name

─────────────────────────────────────────────────────────────────────────────────
1 c09c02d7-d05d-4bf4-831b-207a1adeae2f Xiaomi Temperature
2 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d Zigbee Aqara Water Leak Sensor Mc
3 5ab64dc7-5d08-44a4-9806-5a5b823a18d2 Zigbee Sensors Edge Driver [YG] 1.8.14
4 3724840a-2b1d-4f6b-9683-e8e0155445ee Zigbee Thing [YG] v1.0.2
5 a6994e70-93de-4a76-8b5d-42971a3427c9 Zigbee Valve Mc
─────────────────────────────────────────────────────────────────────────────────
6 dfdb7a46-3b9a-49af-b08a-2e4624648a42 Zigbee Water Leak/Smoke Sensor 1.2
─────────────────────────────────────────────────────────────────────────────────
? Select a driver. 6
connecting… connected
2022-10-15T19:22:02.404139746+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:22:03.394385747+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Received event with handler zigbee
2022-10-15T19:22:03.403467747+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 <ZigbeeDevice: c6d8bc38-fb43-441a-9adb-37a21379e9a8 [0xF6A0] (Smart Smoke Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF6A0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC0, rssi: -52, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xE9, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1F > > > >
2022-10-15T19:22:03.417325747+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Found ZigbeeMessageDispatcher handler in xiaomi-water → Smoke
2022-10-15T19:22:03.422430413+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2022-10-15T19:22:03.428199747+00:00 WARN Zigbee Water Leak/Smoke Sensor 1.2 The device reported a voltage, but the driver was not configured to handle it.
2022-10-15T19:22:03.434356413+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 Smart Smoke Detector device thread event handled
2022-10-15T19:22:32.408195094+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:23:02.418172108+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:23:06.185195776+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Received event with handler zigbee
2022-10-15T19:23:06.194037110+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 <ZigbeeDevice: c6d8bc38-fb43-441a-9adb-37a21379e9a8 [0xF6A0] (Smart Smoke Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF6A0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xB0, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xEA, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1F > > > >
2022-10-15T19:23:06.208900443+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Found ZigbeeMessageDispatcher handler in xiaomi-water → Smoke
2022-10-15T19:23:06.214134776+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2022-10-15T19:23:06.219955776+00:00 WARN Zigbee Water Leak/Smoke Sensor 1.2 The device reported a voltage, but the driver was not configured to handle it.
2022-10-15T19:23:06.226492110+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 Smart Smoke Detector device thread event handled
2022-10-15T19:23:32.428065825+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:24:02.438240173+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:24:32.438212854+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:25:02.448222535+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:25:32.448117216+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:25:52.028429225+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Received event with handler zigbee
2022-10-15T19:25:52.038030892+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 <ZigbeeDevice: c6d8bc38-fb43-441a-9adb-37a21379e9a8 [0xF6A0] (Smart Smoke Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF6A0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xE0, rssi: -44, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xEB, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1F > > > >
2022-10-15T19:25:52.060803892+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Found ZigbeeMessageDispatcher handler in xiaomi-water → Smoke
2022-10-15T19:25:52.066402892+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2022-10-15T19:25:52.074109225+00:00 WARN Zigbee Water Leak/Smoke Sensor 1.2 The device reported a voltage, but the driver was not configured to handle it.
2022-10-15T19:25:52.082241892+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 Smart Smoke Detector device thread event handled
2022-10-15T19:25:59.108352229+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Received event with handler zigbee
2022-10-15T19:25:59.118027895+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 <ZigbeeDevice: c6d8bc38-fb43-441a-9adb-37a21379e9a8 [0xF6A0] (Smart Smoke Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF6A0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xD8, rssi: -46, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xEC, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1F > > > >
2022-10-15T19:25:59.138005895+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Found ZigbeeMessageDispatcher handler in xiaomi-water → Smoke
2022-10-15T19:25:59.143587229+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2022-10-15T19:25:59.152570229+00:00 WARN Zigbee Water Leak/Smoke Sensor 1.2 The device reported a voltage, but the driver was not configured to handle it.
2022-10-15T19:25:59.159196229+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 Smart Smoke Detector device thread event handled
2022-10-15T19:26:02.448934564+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:26:32.456584911+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:26:44.576760250+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Received event with handler zigbee
2022-10-15T19:26:44.777467250+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 <ZigbeeDevice: c6d8bc38-fb43-441a-9adb-37a21379e9a8 [0xF6A0] (Smart Smoke Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF6A0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xE0, rssi: -44, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xED, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1F > > > >
2022-10-15T19:26:44.840726917+00:00 TRACE Zigbee Water Leak/Smoke Sensor 1.2 Found ZigbeeMessageDispatcher handler in xiaomi-water → Smoke
2022-10-15T19:26:44.868458917+00:00 INFO Zigbee Water Leak/Smoke Sensor 1.2 Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2022-10-15T19:26:44.874224250+00:00 WARN Zigbee Water Leak/Smoke Sensor 1.2 The device reported a voltage, but the driver was not configured to handle it.
2022-10-15T19:26:44.940596250+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 Smart Smoke Detector device thread event handled
2022-10-15T19:27:02.458126592+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:27:32.468632425+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:28:02.478176772+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:28:32.478960787+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled
2022-10-15T19:29:02.488219801+00:00 DEBUG Zigbee Water Leak/Smoke Sensor 1.2 driver device thread event handled

12

Also saw this:

13

ok, I can see the battery voltage report a dozen of times.

is it the only thing missing? have you tested the smoke reporting ?

14

While it was logging, I went to the fireplace and set off the alarm with some smoke, if that is your question? It did not change anything in the device in the app … the status remained on smokeless.

15

can you tell the part of the log when it happened?
exact time?

16

That’s the problem, I can’t … but I can try to repeat it. Let me try.

17

i would recommend to press enter several times to add the indents before running experiment

18

Hm I just tried it … and it does nothing. I only connected the CLI, and the usual “driver device thread even handled” messages appear every few seconds … then went to the fireplace to launch an alert and came back to the CLI … and there’s nothing. Just the same continuous “driver device thread even handled” message. Only if I press the button on the deivce, you get a few lines with the battery voltage eetc, but the smoke alarm going off on the deivce caused nothing visible in the cli log :frowning:

19

tomorrow I’ll check the links you have sent earlier. so far it seems the detector requires some extra initialization to get the reports.

20

No stress, I’m thankful that you look into it. I think the second link might provide something … there’s huge table sof data I can not understand, but maybe you can :slight_smile: Have a good night then!