Page 1 of 1

[2.0.77] ElectricEnergyInterface - inconsistent displays

Posted: Mon Jun 01, 2026 8:23 pm
by hgschmie
I have an entity that is an ElectricEnergyInterface:

Code: Select all

{
	type = 'electric-energy-interface',
	name = 'control-station,

	energy_source = {
		type = 'electric',
		buffer_capacity = '400kJ',
		input_flow_limit = '12250kW',
		output_flow_limit = '0W',
		usage_priority = 'secondary-input',
		drain = '250kW',
	},
}
energy_production and energy_usage are unset.

my math (400kJ * 60 ticks) = 12000kW + 250kW drain = 12250kW seems to check out and that thing fills its internal buffer in tick if necessary. There is some custom code that takes out energy if needed. It is working fine for me.

However, the regular box shows the drain as minimum consumption (correct) but no maximum consumption. The energy usage shows up as "consumption" which can be less than "minimal consumption" which is very confusing.
Screenshot 2026-06-01 at 12.47.11.png
Screenshot 2026-06-01 at 12.47.11.png (1.32 MiB) Viewed 377 times
I assume those are static values; I have code that is taking energy out of the buffer every tick, so there is a steady influx of energy which is visible on the electric network info:
Screenshot 2026-06-01 at 12.49.32.png
Screenshot 2026-06-01 at 12.49.32.png (61.96 KiB) Viewed 377 times
What I would have expected on the device info under "Consumes Electricity":

- the "min consumption' represents the drain from the buffer. So in my case, it would be 250kW
- the "max consumption' represents the input flow limit (which is the maximum that the energy source can pull from the network). It would be 12250kW in my case.
- consumption represents both the drain and the energy usage.

The actual consumption (as shown on the electric network info) seems to be fine.

Re: [2.0.77] ElectricEnergyInterface - inconsistent displays

Posted: Thu Jun 25, 2026 3:20 pm
by Rseding91
Thanks for the report however I don't believe we will be changing this. These values are largely based on the prototype and the combination complexity to try to make them work with all possible ways they can be configured runtime isn't currently worth it.