Wake on LAN rule in Main UI fails to init

[DrRSatzteil (Thomas Lauterbach)]

Hi everyone,

I’m facing a problem with the “send a WoL Packet” action in a rule. When OH is restarted the rule remains in the state UNINITIALIZED and shows the error: “Missing handler ‘network.sendWakeOnLanPacketViaIp’ for module ‘3’”.

When I disable and enable the rule again it works without problems. To me it looks like a rece condition during startup or a wrong order of things in the startup sequence but I don’t have a deep technical insight in this.

The rule is defined as follows:

configuration: {}
triggers:
  - id: "1"
    configuration:
      command: ON
      itemName: bd_player_on
    type: core.ItemCommandTrigger
conditions: []
actions:
  - inputs: {}
    id: "3"
    configuration:
      config: network:pingdevice:839955dc60
    type: network.sendWakeOnLanPacketViaIp

Am I doing something wrong here or might this be a bug?

[rlkoshak (Rich Koshak)]

I agree, there does seem to be a case where the Thing is coming online after the rule is loaded. The rule engine is loaded at runlevel 40 but Thing don’t get loaded until runlevel 80 so this is not unexpected. The rule should become initialized when the Thing does come online.

Please file an issue on openhab-core. How to file an Issue.

Thanks

[DrRSatzteil (Thomas Lauterbach)]

Thanks Rich, issue filed:

Wake on LAN rule in Main UI fails to initialize