That is also very useful thank you. If a well powered system is taking 45 seconds, then I probably shouldn’t expect an rPi to boot in less than a minute. I may push my initialisation flag out to 2 or 3 minutes - I don’t have a massive number of rules, I have 11 files and 2000 lines total, but the genuine LOC in there is probably more like 1000, I like verbose commenting and whitespace.
I did look at the ticket regarding things running before the boot sequence is finished Introduce a "ESH start level" functionality · Issue #1896 · eclipse-archived/smarthome · GitHub, and it looks a bit like these things often do - there’s a specific problem that someone has generalised, and then realised that making a generalised “these dependencies are complete you can now do your thing” is really hard. And the thing that 80% of people might need is therefore undone - what I imagine to be less hard, which is working out when all your item files and rule files have been parsed and are ready.
I did see this ticket which suggests a workaround to delay rule loading: Delay Rule loading after Startup in OH2? - #15 by killercorny, and also says moving from “update received” to “command received” means that a bunch of rules aren’t triggered on startup, of course I need to change many of my “sendUpdate” instructions to “sendCommand”, but that’s not an unreasonable chore.
Anyway, a timer works, I’ve already done the code for it, I just need to pick a longer value for the time.