When I was testing the receiver, I found that the power received by the receiver is incorrect.

As shown below, Network Power * Network Efficiency is not equal to Available Power(3.703*0.8716=3.228, not 1.980). When I click on the "Disable Receiver" button, the Available Power number becomes correct. After clicking the "Activate Receiver" button, the Available Power number becomes incorrect again.
KSPI-E version is 1.26.7, running on KSP 1.10.1

For comparison, I tested the same configuration of the craft in 1.24.3.5 KSPIE and the Available Power number is correct:

I have also tested other kinds of transmitters and receivers, still same problem.

I just re-tested beamed power in the latest version of KSPIE(1.26.12), using the same configuration of the ship as before, and had the same problem as before. It looks like beamed power is not being fixed correctly. @sswelm

seems to me this is a display issue rather than a logical error because there are multiple inefficiencies at work that affect the final received power. There are 2 main efficiencies, which are network inefficiency (caused by the actual transmission) and beam to wall inefficiency (where the beam is converted into electrical power). What is going wrong here I think is that not all inefficiencies are properly applied at all times.

Notice there is also something called atmospheric efficiencies which isn't properly displayed, but does affect the overal available power. It depends on the angle of the beamed signal through the atmosphere, the wavelength, and moisture in the atmosphere (which varies).

seems to me this is a display issue rather than a logical error because there are multiple inefficiencies at work that affect the final received power. There are 2 main efficiencies, which are network inefficiency (caused by the actual transmission) and beam to wall inefficiency (where the beam is converted into electrical power). What is going wrong here I think is that not all inefficiencies are properly applied at all times.

@sswelm
I don't think it's just a display issue.
I did a new test, to exclude atmospheric interference, with two vessels in orbit (transmitter and receiver) and they are tens of km apart. [Figure1]

1. From the transmitter [Figure2] , wall to beam power value has been multiplied by the conversion efficiency, and network power is equal to wall to beam power.
2. From the beam transmission path, no atmospheric interference, meaning no loss
3. from the receiver [Figure3] , spot size is much smaller than the receiver diameter, 100% facing, the receiver's power capacity is greater than the network power, so it should be able to get all the energy (not considering the receiver efficiency).
4. power receiver interface shows 100% network efficiency [Figure3] , if this value is only related to atmospheric loss, receiver diameter to spot size ratio, facing, then this value should be correct

If there are no other interference factors, then the actual available power of the receiver should be equal to network power * network efficiency * receiver efficiency, which is total current beamed power in the power receiver interface.

However the actual available power (available powe = network power * network efficiency) is not equal to the calculated value, about half of it [Figure3] . I don't think there is any other inefficiency in the transmission process.
I also don't think this formula is wrong, because I try to adjust the receiver facing, so that facing value gradually reduced to 0%, and then network efficiency will drop. At first available power will not drop with network efficiency, however, when network efficiency down to about half, available power began to drop, now the available power is equal to the above formula calculation value.

So I think some unknown factor makes available power can't be greater than half of network power, maybe it's a logic error in the code, or maybe it's something else.
And I don't see the above problem in the 1.24 version of kspie, this problem seems to appear from some sub version of 1.25.

Figure1

Figure2 Transmitter

Figure3 Receiver

Problem identified and solved in 1.26.15

Problem identified and solved in 1.26.15

Great! Glad it's back to normal