.aq2 motion sensor reconized but has no data

[albertovm]

I have an .aq2 motion sensor, and it reconizes the driver. But the app shows no data (only cloud icon) for data. How could I find the problem? Regards.

[albertovm]

[albertovm]

It works fine with Groovy Device Handler (bspranger : Xiaomi Aqara Motion Sensor), and the other one I have still working without Edge driver.

[veonua]

please attach logs, there are several known situations, issues that can cause this

• no events came from the device
• refresh feature on the current Hub firmware is broken, (try restart the app)

[albertovm]

This is my hub log. First I did remove the driver, than selected the driver again. The device works fine, because it was working with Groovy driver. Could you take a look in log information? Thanks.

2022-08-02T10:57:54.000918771+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T10:58:24.008423684+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T10:58:54.017415403+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T10:59:24.011161669+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T10:59:41.805613849+00:00 TRACE Xiaomi Motion Sensor Received event with handler device_lifecycle 2022-08-02T10:59:41.825870972+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received lifecycle event: removed 2022-08-02T10:59:41.847645729+00:00 TRACE Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received unhandled lifecycle event: removed 2022-08-02T10:59:41.863106956+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:41.889008879+00:00 TRACE Xiaomi Motion Sensor Received event with handler driver_lifecycle 2022-08-02T10:59:41.907190361+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:57.360757394+00:00 TRACE Xiaomi Motion Sensor Setup driver xiaomi-motion with lifecycle handlers: DeviceLifecycleDispatcher: xiaomi-motion default_handlers: driverSwitched: doConfigure: child_dispatchers: DeviceLifecycleDispatcher: xiaomi-motion -> LUMI Motion Handler default_handlers: doConfigure: added: child_dispatchers: DeviceLifecycleDispatcher: xiaomi-motion -> ikea motion sensor default_handlers: doConfigure: added: child_dispatchers: DeviceLifecycleDispatcher: xiaomi-motion -> zigbee plugin motion sensor default_handlers: child_dispatchers:

2022-08-02T10:59:57.366018877+00:00 TRACE Xiaomi Motion Sensor Setup driver xiaomi-motion with Capability handlers: CapabilityCommandDispatcher: xiaomi-motion default_handlers: refresh: refresh child_dispatchers: CapabilityCommandDispatcher: xiaomi-motion -> LUMI Motion Handler default_handlers: refresh: refresh child_dispatchers: CapabilityCommandDispatcher: xiaomi-motion -> ikea motion sensor default_handlers: child_dispatchers: CapabilityCommandDispatcher: xiaomi-motion -> zigbee plugin motion sensor default_handlers: refresh: refresh child_dispatchers:

2022-08-02T10:59:57.376588555+00:00 TRACE Xiaomi Motion Sensor Setup driver xiaomi-motion with Zigbee handlers: ZigbeeMessageDispatcher: xiaomi-motion default_handlers: attr: ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF02 ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF01 global: cluster: zdo: child_dispatchers: ZigbeeMessageDispatcher: xiaomi-motion -> LUMI Motion Handler default_handlers: attr: ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue global: cluster: zdo: child_dispatchers: ZigbeeMessageDispatcher: xiaomi-motion -> ikea motion sensor default_handlers: attr: global: cluster: ZclClusterCommandHandler: cluster: OnOff, command: OnWithTimedOff zdo: ZdoHandler child_dispatchers: ZigbeeMessageDispatcher: xiaomi-motion -> zigbee plugin motion sensor default_handlers: attr: ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy global: cluster: zdo: child_dispatchers:

2022-08-02T10:59:57.408039586+00:00 TRACE Xiaomi Motion Sensor Zigbee Device: 336d0f51-d3cc-4928-9afc-f07c77adbbac Manufacturer: LUMI Model: lumi.sensor_motion.aq2 [1]: Basic, 0xFFFF, OccupancySensing, IlluminanceMeasurement, IASZone, PowerConfiguration, Identify 2022-08-02T10:59:57.414184198+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T10:59:57.418540792+00:00 TRACE Xiaomi Motion Sensor Received event with handler _resync 2022-08-02T10:59:57.422414228+00:00 TRACE Xiaomi Motion Sensor Received event with handler environment_info 2022-08-02T10:59:57.432865346+00:00 TRACE Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received unhandled lifecycle event: init 2022-08-02T10:59:57.436948616+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:57.441262647+00:00 TRACE Xiaomi Motion Sensor Received event with handler environment_info 2022-08-02T10:59:57.445491448+00:00 DEBUG Xiaomi Motion Sensor Z-Wave hub node ID environment changed. 2022-08-02T10:59:57.450789283+00:00 TRACE Xiaomi Motion Sensor Received event with handler device_lifecycle 2022-08-02T10:59:57.454884830+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received lifecycle event: added 2022-08-02T10:59:57.460396334+00:00 TRACE Xiaomi Motion Sensor Found DeviceLifecycleDispatcher handler in xiaomi-motion -> LUMI Motion Handler 2022-08-02T10:59:57.467523834+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > > 2022-08-02T10:59:57.476610395+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > > 2022-08-02T10:59:57.484150518+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:57.488475950+00:00 TRACE Xiaomi Motion Sensor Received event with handler device_lifecycle 2022-08-02T10:59:57.492988935+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received lifecycle event: driverSwitched 2022-08-02T10:59:57.499122125+00:00 TRACE Xiaomi Motion Sensor Found DeviceLifecycleDispatcher handler in xiaomi-motion 2022-08-02T10:59:57.503216671+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:57.507129564+00:00 TRACE Xiaomi Motion Sensor Received event with handler capability 2022-08-02T10:59:57.552563457+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:57.558851370+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}} 2022-08-02T10:59:57.564084673+00:00 TRACE Xiaomi Motion Sensor Found CapabilityCommandDispatcher handler in xiaomi-motion -> LUMI Motion Handler 2022-08-02T10:59:57.570314807+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xFCC0 >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x04, mfg_code: 0x115F, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x010C, DataType: Uint8, data: 0x01 > > > > 2022-08-02T10:59:57.581949914+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: Uint16, data: 0x0002 > > > > 2022-08-02T10:59:57.593341919+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 00158D0004665B38, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 086BD7FFFEA0C173, dest_endpoint: 0x01 > > > 2022-08-02T10:59:57.602535847+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 00158D0004665B38, src_endpoint: 0x01, cluster: OccupancySensing, dest_addr_mode: 0x03, dest_address: 086BD7FFFEA0C173, dest_endpoint: 0x01 > > > 2022-08-02T10:59:57.613171683+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > > 2022-08-02T10:59:57.622027088+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0010 > > > 2022-08-02T10:59:57.629896646+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled 2022-08-02T10:59:58.299087949+00:00 TRACE Xiaomi Motion Sensor Received event with handler device_lifecycle 2022-08-02T10:59:58.306897914+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received lifecycle event: infoChanged 2022-08-02T10:59:58.313929970+00:00 TRACE Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received unhandled lifecycle event: infoChanged 2022-08-02T10:59:58.317618855+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled

[albertovm]

When I try to reload data pushing screen down an error message appears in ST app: "Connection error. Try again later". And I have this in my device log:

2022-08-02T11:05:27.826213945+00:00 DEBUG Xiaomi Motion Sensor driver device thread event handled 2022-08-02T11:05:28.212278649+00:00 TRACE Xiaomi Motion Sensor Received event with handler capability 2022-08-02T11:05:28.226339115+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}} 2022-08-02T11:05:28.239363704+00:00 TRACE Xiaomi Motion Sensor Found CapabilityCommandDispatcher handler in xiaomi-motion -> LUMI Motion Handler 2022-08-02T11:05:28.256657177+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xFCC0 >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x04, mfg_code: 0x115F, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x010C, DataType: Uint8, data: 0x01 > > > > 2022-08-02T11:05:28.283916+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: Uint16, data: 0x0002 > > > > 2022-08-02T11:05:28.311167846+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 00158D0004665B38, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 086BD7FFFEA0C173, dest_endpoint: 0x01 > > > 2022-08-02T11:05:28.336031033+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 00158D0004665B38, src_endpoint: 0x01, cluster: OccupancySensing, dest_addr_mode: 0x03, dest_address: 086BD7FFFEA0C173, dest_endpoint: 0x01 > > > 2022-08-02T11:05:28.376841722+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > > 2022-08-02T11:05:28.405763212+00:00 INFO Xiaomi Motion Sensor <ZigbeeDevice: 336d0f51-d3cc-4928-9afc-f07c77adbbac [0xFA0E] (Varanda Movimento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFA0E, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0010 > > > 2022-08-02T11:05:28.442375459+00:00 DEBUG Xiaomi Motion Sensor Varanda Movimento device thread event handled

[veonua]

When I try to reload data pushing screen down an error message appears in ST app: "Connection error. Try again later". And I have this in my device log:

it’s known HUB issue with latest firmware and has nothing to do with driver itself. Just don’t “pull-to-refresh” . i’ll disable this feature in the future

[albertovm]

I removed the device and resync... it is working now. All them!