Sorry, though I scrolled up quite a bit from your first post asking about the lack of check-in messages for hours, I must have missed this previous explanation of the routing to that door/window sensor end device.
With four link hops in the path between the end device (the Xiaomi Door/Window sensor) and the coordinator (Hubitat hub), with as much as I understand about ZigBee routing (which is not a heck of a lot), I place high suspicion on unsuccessful packet delivery.
If possible, I would recommend looking at the link cost of each of the hops to get a sense of the probability level of successful packet delivery. For a highly technical explanation of link cost / probability of successful packet delivery have a look under the heading ZigBee and IEEE 802.15.4 Protocol Layers, subheading 3.4.6 Routing here.
Without additional hardware, the only tool available with the Hubitat hub itself to get any sense of quality of ZigBee network route links is the getChildAndRouteInfo report page. Have you tried looking at that? To view it, in a browser on the same network as your hub, go to:
http://[hub_ip_address]/hub/zigbee/getChildAndRouteInfo
(replacing [hub_ip_address] with your hub's IP address, of course.)
Part of that report will look like this:
Neighbor Table Entry
[Name of Device 1, 0FA1] , LQI:254, age:3, inCost:1, outCost:1
[Name of Device 2, 0C19] , LQI:195, age:7, inCost:1, outCost:7
I'm no expert, but as I understand it, the LQI value represents the overall link quality, as explained by @Tony here:
Then, using this page as a guide, here's a rough guide on how the other values can be interpreted:
age
In EmberZNet Pro, the number of aging periods elapsed since a neighbor exchange message was last received from this neighbor. In stack profile 1, the number of aging periods since any packet was received. An entry with an age greater than 3 is considered stale and may be reclaimed. The aging period is 16 seconds.
inCost
The incoming cost for this neighbor, computed from the average LQI. Values range from 1 for a good link to 7 for a bad link.
outCost
The outgoing cost for this neighbor, obtained from the most recently received neighbor exchange message from the neighbor. A value of zero means that a neighbor exchange message from the neighbor has not been received recently enough, or that our ID was not present in the most recently received one. EmberZNet Pro only.
Really what you'd want to be looking in addition to the LQI value is inCost.
