Why can an inserter Enable/Disable wirelessly based on Logistics network content but a Requester chest can not?

[VonFlaffenhausen]

This feels like an oversight or at least quite inconsistent.
It would be nice to be able to enable or disable requests based on the contents of the logistical network.

I know it can be done by connecting a wire to a roboport, it just does not make sense that a non logistical network related entity like an inserter can wirelessly connect but a requester chest, being an integral part of the logistical network needs an extra wire.

Chest-vs-Inserter.png (328.72 KiB) Viewed 167 times

[Rseding91]

This is not a bug. To disable requester chest means it’s removed from the logistic network logic and once that’s done it means it can’t *read* the network contents to disable itself.

It’s a catch 22, it has to be enabled to disable itself.

[VonFlaffenhausen]

Ah, so basically the "wireless wire" is severed when you disable the chest and therefore the chest has no way of reading the contents of the logistics network and the "wired wire" stays connected and operational after disabling a chest?
Is that correct?

And I guess it would be naive to suggest to just not sever the connection when disabling? Especially on a requester chest, its contents are not added to the logistics network so it would not matter right?

Anyway, thanks for your reply.