Selective ACK with spinel ?

[bitcoin1192]

Had some issue with some of tuya zigbee router where it select the worse link to transmit to. Out of nearest router it can find, including coordinator, it seems to prefer direct connection to coordinator where the lqi is not symmetric (i.e coordinator could hear the device faintly but their device can hear coordinator quite loudly, 64 vs 4 lqi). Is there a way to filter ack message to certain rssi as a way to steer them to other router instead ? since ack-ing is done on hardware, maybe there is some way to tell the radio to ignore receive message with lower rssi or lqi ?

[Nerivec]

I'm not aware of any in Spinel conf. That would likely need a custom in-firmware implementation.

Note: I wouldn't pay much attention to LQI values at this time, or at least not base any reasoning on them. The algorithm likely needs tweaking, it has not been a priority since it's almost always a "not so great" indicator anyway, even for current NCP solutions... I did go with LQA instead of LQI in underlying computations, but still not fantastic.

Note 2: We use some properties from the firmware to calculate LQI (e.g.), I'm not sure how that gets assigned in Espressif firmware. May need to tweak that too.

[bitcoin1192]

Alright, i think assumed a lot with my limited setup here. Definitely not a straight forward problem to solve as i would have thought. There is also HW frame filtering, which i hope could filter address in 802.15.4 frame but couldn't find any in spinel doc above. It's dependent on hardware and firmware, so definitely not an assignment for now. I will try to move the coordinator instead.