I’ve been having issues with my tradfri motion sensors triggering by them self.
My only theory is that maybe they loose connection and when they reconnect they update status resulting in HA thinking they triggered ? Any ideas ?
I’m having the same problem, but with ZHA.
Logs seem like a normal motion detection:
2020-11-17 13:02:15 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'020401060001ff000100001790c07a91ffff080129420008070000'
2020-11-17 13:02:15 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_MULTICAST: 2>, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=255, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=23), 144, -64, 0x917a, 255, 255, b'\x01)B\x00\x08\x07\x00\x00']
2020-11-17 13:02:15 DEBUG (MainThread) [zigpy.zcl] [0x917a:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=False disable_default_response=False> manufacturer=None tsn=41 command_id=66>
2020-11-17 13:02:15 DEBUG (MainThread) [zigpy.zcl] [0x917a:1:0x0006] ZCL request 0x0042: [0, 1800, 0]
2020-11-17 13:02:15 DEBUG (MainThread) [zigpy.zcl] [0x917a:1:0x0006] No handler for cluster command 66
2020-11-17 13:02:15 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x917A:1:0x0006]: received 'on_with_timed_off' command with [0, 1800, 0] args on cluster_id '6' tsn '41'
Same for me, also with ZHA and deconz stick. No ideea what triggers the sensor. I have the original battery and it’s 47%.
What is your battery level?
Hello to everyone!!!
I have the same problem
did someone have found a solution for this problem?
Hello
Same problem here… Any idea why or how to mitigate?