Closed LukasA83 closed 3 years ago
Start level 80 means that all your things are initialized. I assume that you have some things for which the binding might be missing or their handlers cannot be found for other reasons. Have you checked that?
I had two disabled Things, because the loan mower is taking some winter rest... after enabling it has been triggered. Is that the desired behaviour that intentionally disabled things are preventing level 80/100?
No, this is clearly not intended. So thanks for your report and your analysis - I have created #1968 as a fix.
Kai, this is a current scenario while you uninstall temporarily a binding, keeping the things. Does it mean that OH will not start if you don't have 1 binding for each thing? Maybe you could consider a timeout, long enough.
And you have the standard user that will uninstall definitely a binding without even thinking about the things he created.
If you deinstall stuff and do not deactivate the according things, you seem to be fine to not reach the "all thing initialized" start level. There is no reason to define any rules with startlevels higher 70 and the system will work just fine - it itself does nowhere depend on any of the higher start levels.
Ok, thank you for the clarification.
I'm using openhab 3 snaphost, build 2090 on raspi 4 docker environment. I'm struggling to get the new startuptrigger to work. I realized, by putting the StartLevelService log level to DEBUG, that my system shows at latest "Reached start level 70", but never 80 or 100 and therefore my startuptrigger at 80 or 100 is not fired for the rule. The rule has been defined in WebUI. Tried Blocky and ruledsl format with the same result.
Log: