SystemStartLevelTrigger partially works

Setup, Configuration and Use Scripts & Rules
1

OH 4.3 release

I have the script below to run when the SystemStartLevel reaches 100. The command to the front door inside dimmer is issued, I can see it in the event log. But the javascript action does not appear to run. There’s no error or any evidence of it trying to run in the log file. Manually running the script does cause the log line to work.

Why is this happening, and what can I do to get the script to run at start up? (I have more I want to run at start up, the log line is just a test to get this debugged.)

configuration: {}
triggers:
  - id: "1"
    configuration:
      startlevel: 100
    type: core.SystemStartlevelTrigger
conditions: []
actions:
  - inputs: {}
    id: "2"
    configuration:
      command: OFF
      itemName: FrontDoorEntranceInsideDimmer
    type: core.ItemCommandAction
  - inputs: {}
    id: "3"
    configuration:
      type: application/javascript
      script: >-
        console.log("turned off Front Door Inside Dimmer");
    type: script.ScriptAction
2

You can see what in events.log? The startlevel event or the rule running event or both? To get either in the logs you need to modify your logging settings which I assume you’ve done. Or are you watching the event stream in the Developer Sidebar?

This will help to diagnose the problem.

Note, if you have a Thing that fails to come ONLINE, runlevel 100 will never be reached.

3

My mistake, I had some Things that blocked getting to startlevel 100.

But I have a question on this. The docs say that startlevel 80 is defined as:

80	All Things have been initialized.

What exactly is ‘initialized’? I have discovered that ONLINE, OFFLINE, and DISABLED are considered ‘initialized’. Is there a list of Thing statuses that are not ‘initialized’?

4

If you set the openhab.event.ThingStatusInfoEvent logger to INFO you’ll see all the Thing status changes in events.log. I beleive the only status that doesn’t count as initialized is INITIALIZING. This is the status of the Thing when it’s first loaded and passed to the binding to set up and configure. After that point it’s up the the binding to transition the Thing through the states as it establishes connectivity with the device and such.