Ikea outlets (UK) dropped out of newtwork

[james-fry]

Bug Report

What happened

All (two) of my ikea outlets dropped off the network today.
They are both switched on. (I saw unexpected lights on in my home from this)
They are both unreachable (failures in log when trying to switch)
They both show in the network map with 0 lqi to all other routers and coord:

Short log of attempt to switch the unresponsive outlet (if more logging needed will use pastebin)

zigbee2mqtt:debug 9/4/2019, 9:23:31 PM Received MQTT message on 'zigbee2mqtt/Fireplace Lights/set' with data 'ON' zigbee2mqtt:info 9/4/2019, 9:23:31 PM Zigbee publish to device 'Fireplace Lights', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - 1 zigbee2mqtt:error 9/4/2019, 9:23:31 PM Zigbee publish to device 'Fireplace Lights', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - null failed with error Error: AF data request fails, status code: 233. MAC no ack. zigbee2mqtt:info 9/4/2019, 9:23:31 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Error: AF data request fails, status code: 233. MAC no ack.","meta":{"entity":{"ID":"0x000d6ffffe2647c8","type":"device","friendlyName":"Fireplace Lights"},"message":"ON"}}'

What did you expect to happen

For them not to drop out of the network.
They were worrking great for 1-2 weeks.

How to reproduce it (minimal and precise)

Unsure how to reproduce.
I have tried resetting (power on/off) - didnt work
Factory resetting the outlet and repairing restored functionality.

Debug Info

zigbee2mqtt version: 1.5.1 via latest hassio
CC253X firmware version: CC2530_CC2591_SOURCE_ROUTING_20190619.zip

[james-fry]

It happened again today with both outlets.
I didnt see anything specific in the logs to indidate where the failure event happens, but here are some notes:

1. I have a scheduled automated in HA that executes zigbee map update every hour
2. From 4am today I started getting warnings for 10sec timeouts on map lqi scans for one of the outlets:

9/5/2019, 4:00:11 AM - warn: Failed network lqi scan for device: '0x000d6ffffe2647c8' with error: 'Error: Timed out after 10000 ms'

3. Even after this time I still saw debug messages with periodic updates from that outlet until 09:49. This is the final update from that outlet:

9/5/2019, 9:49:23 AM - debug: Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'TRADFRI control outlet' (0x000d6ffffe2647c8) of endpoint 1
9/5/2019, 9:49:23 AM - info: MQTT publish: topic 'zigbee2mqtt/Fireplace Lights', payload '{"state":"OFF","linkquality":104}' 

After this point no more updates from the device, not more successful lqi scans and the device is unresponsive to commands: e.g.

9/5/2019, 11:19:25 AM - debug: Received MQTT message on 'zigbee2mqtt/Fireplace Lights/set' with data 'ON'
9/5/2019, 11:19:25 AM - info: Zigbee publish to device 'Fireplace Lights', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - 1
9/5/2019, 11:19:31 AM - error: Zigbee publish to device 'Fireplace Lights', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - null failed with error Error: AF data request fails, status code: 233. MAC no ack.
9/5/2019, 11:19:31 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Error: AF data request fails, status code: 233. MAC no ack.","meta":{"entity":{"ID":"0x000d6ffffe2647c8","type":"device","friendlyName":"Fireplace Lights"},"message":"ON"}}'

[james-fry]

NB I didnt yet scour the logs for the 2nd outlet. Can do if needed?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[james-fry]

This issue has not manifested for a long time now using 1.6 dev and source routing f/w.
I am closing the issue.