Startup rule does not work anymore

[the-ninth (Robert)]

Since one of the latest updates my startup rule does not run anymore on startup. I can run it manually without problem, but it is not automatically executed on startup.

I am running OH 3.4.2 as Docker Container on a Synology NAS.

Here is the rule as shown on the UI:

Here is the code that defines the trigger:

configuration: {}
triggers:
  - id: "1"
    configuration:
      startlevel: 100
    type: core.SystemStartlevelTrigger
conditions: []

Is there anyone else seeing such an issue? Any advice on how I might fix that?

[sihui]

@the-ninth

my startup rule does not run anymore

OH 4.2.0 (Windows) - the system has reached start level 100 - rule dosn't work

Probably the system isn’t reaching startLevel 100. If you have Things that are not ONLINE you won’t reach runlevel 100. There are all sorts of ways you can determine the startLevel. One of the easier ways is to go to Help & About → View Details and startLevel will be among the information shown. [image] Other options are to create a rule that triggers at each level or enabling runlevel logging to events.log by setting the level of openhab.event.StartlevelEvent to INFO.

[the-ninth (Robert)]

Thanks, that was it. One of the bindings I use did not survive the update, and therefore the Things did not initialize. After reinstalling the binding, it goes to 100 again and the script is executed.