Sensors should transmit actual values instead of on/off, target buildings should process them

Please make sensors send the actual values they read instead of just on/off, and let other buildings process those values. The current implementation requires you to build n sensors for every n unique values you would like to use in automating other buildings, which quickly becomes a mess.

Say you have a reservoir. You put a depth sensor over it so you can pause a water pump when the level falls below 0.4. But you want to re-enable the pump at 0.2 – you're already out of luck since that requires a second depth sensor (and additional logic buildings). You want to close a valve at the bottom of the reservoir when the level falls below 0.7 – you need a third sensor. You also want a message through an indicator when the level goes back above 0.8 – fourth sensor. Etc. pp. All those sensors sense the exact same value, but for every value you're interested in, you need to build another, exactly identical sensor. Even disregarding the space issues that entails (let alone the ugliness), it just doesn't make any sense that you would have to do this. It's one physical property and every sensor (provided you can even stack them) reads it the same. No sane hardware designer would put 87 identical sensors in their product because they want the product to act differently under 87 conditions.

Let the sensor transmit the value it reads and move all conditions to the target buildings. Let me hook up my water pump, valve and indicator to ONE depth sensor, and let me set a condition using that received value there (i.e. valve closes at 0.7, pump closes at 0.4, indicator issues message at 0.8). If actually complex behaviors (e.g. pause/re-enable at different values) requires additional buildings, fine, but not basic building triggers.