If roboport is connected to the network that's empty, it will not start, while also eating a tons of steam.
I have save re-creating the bug https://drive.google.com/file/d/1HFw4Jw_uCln-g0ysADunsmQ35IszQupI/view?usp=drive_link
In same setup, when I disconnect roboport, let the storage tank charge, and re-connect it when it is full it starts correctly
here is patch (from a liebot, but appears to work exactly as needed)
--- a/rp_steam_roboports/steam/roboport/roboport_control.lua
+++ b/rp_steam_roboports/steam/roboport/roboport_control.lua
@@ -162,7 +162,7 @@
]]
if steam_info.amount > 0 and steam_needed > 0 then
if steam_info.amount <= steam_needed then
- storage_tank.clear_fluid_inside()
+ storage_tank.clear_fluids()
---@diagnostic disable-next-line: need-check-nil
roboport.force
.get_fluid_production_statistics(roboport.surface)
it was broken with some 2.1.7 changes.