[2.0.76] Logistic chests can't access logistic network wirelessly for logic purposes

[tryton984]

It seems to be more of an oversight than a bug per se and can easily be reproduced:

In the inserter and belt UI one can press the "logistic network" button (on the top right) to allow the machine to read contents of logistic network remotly and have logic implemented based on its contents.

inserter.png (263.79 KiB) Viewed 84 times

However, logistic chests (all types) don't have this button and don't have this functionality. It leads to silly situations, for example in order to turn a requester chest on or off based on the network's contents, one needs to manually connect it with wire to a roboport.

requester.png (284.77 KiB) Viewed 84 times

It is especially annoying with blueprints, as one can't create a blueprint without a roboport when in need of such a mechanism. In both of the examples below the machine (inserter/chest) is turned on or off based on the network, but one of those blueprints is much more cumbersome:

Inserter blueprint.png (268.96 KiB) Viewed 84 times

Chest blueprint.png (491.91 KiB) Viewed 84 times

[Rseding91]

Thanks for the report however this is not a bug. Logistic containers can not use logistic network contents wirelessly because when they are disabled they are *removed* from the logistic network. If they were using the network wirelessly when disabled, they would never turn themselves back on because they would never get any new signals.