Missmatch between system:start-level and openhab.event.StartlevelEvent
Closed this issue · 5 comments
Hello,
I played around with the start level trigger in my rules and find a missmatch between the logger openhab.event.StartlevelEvent and cli
system:start-level
I tested it today.
events.log shows this:
[INFO ] [openhab.event.StartlevelEvent ] - Startlevel '30' reached.*
[INFO ] [openhab.event.StartlevelEvent ] - Startlevel '40' reached.*
[INFO ] [openhab.event.StartlevelEvent ] - Startlevel '50' reached.*
[INFO ] [openhab.event.StartlevelEvent ] - Startlevel '70' reached.*
But i the CLI I see this just before any message is written to events.log:
openhab> system:start-level
Level 80
openhab> system:start-level
Level 100
So it looks like CLI query and events.log output do not match regarding start-level value.
HaKuNa from the forum see the same
https://community.openhab.org/t/timeline-picker-to-setup-heating-light-and-so-on/55564/879
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/timeline-picker-to-setup-heating-light-and-so-on/55564/881
That's two different start levels.
One is the openHAB start level, there is no console command to get that. You can request it from the StartLevelService or in Main UI (About / Technical Information / Show Details). This is based on the state of openHAB (things initialized, automation add-ons loaded, ...).
The other one is the Karaf/OSGi start-level. It is 100 when all bundles are ready. Most openHAB bundles start at level 80 (and that is when the openHAB start level reaches 10).
Can I ask one more question about it? @J-N-K
Why is it possible to set system:start-level ?
I don't know of any use-case in the openHAB context. The system: commands are provided directly by karaf, maybe you can control bundle deploying by that.
Understood....
Thanks