Unable to use pushover from rule UI due to " Required input "message" of the condition "2" not connected"

[plysdyret]

Redirected here from the forum

Trying to create a rule that will send a message with pushover but unable to save it due to:

Validation of rule test_pushover has failed! Required input "message" of the condition "2" not connected

The generated code looks fine to me:

configuration: {}
triggers:
  - id: "1"
    configuration:
      cronExpression: 0 * * * * ? *
    type: timer.GenericCronTrigger
conditions: []
actions:
  - inputs: {}
    id: "2"
    configuration:
      message: Meep
      title: openHAB
      config: pushover:pushover-account:test
    type: pushover.sendHtmlMessage#9e8ead2776057c93222de16046c654cf

Expected behavior

Rule works

Steps to reproduce

Create a rule and try to use any pushover action with a message.

Your environment

Podman running openhab:latest

runtimeInfo:
  version: 4.3.3
  buildString: Release Build
locale: en-US
systemInfo:
  configFolder: /openhab/conf
  userdataFolder: /openhab/userdata
  logFolder: /openhab/userdata/logs
  javaVersion: 17.0.14
  javaVendor: Debian
  osName: Linux
  osVersion: 5.14.0-503.22.1.el9_5.x86_64
  osArchitecture: amd64
  availableProcessors: 12
  freeMemory: 114918136
  totalMemory: 486539264
  uptime: 18952
  startLevel: 100
addons:
  - automation-jsscripting
  - binding-amazonechocontrol
  - binding-androiddebugbridge
  - binding-androidtv
  - binding-astro
  - binding-boschindego
  - binding-boschshc
  - binding-chromecast
  - binding-exec
  - binding-homeconnect
  - binding-hpprinter
  - binding-icloud
  - binding-ipcamera
  - binding-ipp
  - binding-logreader
  - binding-meater
  - binding-mqtt
  - binding-pushover
  - binding-shelly
  - binding-sonos
  - binding-tradfri
  - binding-upnpcontrol
  - misc-openhabcloud
  - persistence-influxdb
  - transformation-exec
  - transformation-jinja
  - transformation-jsonpath
  - transformation-map
  - transformation-regex
  - transformation-xslt
clientInfo:
  device:
    ios: false
    android: false
    androidChrome: false
    desktop: true
    iphone: false
    ipod: false
    ipad: false
    edge: false
    ie: false
    firefox: false
    macos: false
    windows: true
    cordova: false
    phonegap: false
    electron: false
    nwjs: false
    webView: false
    webview: false
    standalone: false
    os: windows
    pixelRatio: 1
    prefersColorScheme: light
  isSecureContext: false
  locationbarVisible: true
  menubarVisible: true
  navigator:
    cookieEnabled: true
    deviceMemory: N/A
    hardwareConcurrency: 16
    language: en-US
    languages:
      - en-US
      - en-GB
      - en
      - da
    onLine: true
    platform: Win32
  screen:
    width: 5120
    height: 1440
    colorDepth: 24
  support:
    touch: false
    pointerEvents: true
    observer: true
    passiveListener: true
    gestures: false
    intersectionObserver: true
  themeOptions:
    dark: light
    filled: true
    pageTransitionAnimation: default
    bars: light
    homeNavbar: default
    homeBackground: default
    expandableCardAnimation: default
    blocklyRenderer: null
  userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML,
    like Gecko) Chrome/133.0.0.0 Safari/537.36
timestamp: 2025-02-24T17:44:23.906Z

Browser console

Nothing in the logs, error only showing in the UI.

Some screenshots:

This scripts works fine:

[TheNinth7]

I have the same issue with OH 4.3.3. When I test the thing's actions directly from the thing it works, and also via JavasScript I can call the action. However when I add the action directly to a rule, I get the following error when trying to save the rule:

Validation of rule 3183ba681c has failed! Required input "message" of the condition "7" not connected

Here is how the error looks like on the UI:

Here is the action on the UI:

And here is the code of the action:

  - id: "7"
    configuration:
      message: Test
      config: pushover:pushover-account:2a22be310e
    type: pushover.sendMessage#26aa5ea09027ad2b11b752652e808c6a

[florian-h05]

Rule validation is done in core based on the definitions provided by the add-on.
So this is either a core issue or an issue with the add-on.

@kaikreuzer Can you please move this issue?