Pushover not sending messages

Add-ons Bindings
1

Since a recent update to 5.1.2 I get this message whenever I try to use pushover:

Script execution of rule with UID ‘defaultNew-24’ failed: ‘sendMessage’ is not a member of ‘org.openhab.core.thing.binding.ThingActions’; line 447, column 4, length 49 in defaultNew

Running this code copied exactly from the documentation which has always worked in the past:

val actions = getActions("pushover", "pushover:pushover-account:account")
// send HTML message
actions.sendHtmlMessage("Hello <font color='green'>World</font>!", "openHAB")

pushover.things is still where it belongs in /etc/openhab/things and still looks correct.

I’m lost as I seem to be doing everything right. I did uninstall and then reinstall Pushover in case something had changed but that didn’t help.

2

if you use javascript, it should be

var messageService = actions.Things.getActions("pushover", "pushover:pushover-account:12345");

and sending the message I use

messageService.sendMessage(text, 'from OH');
3

I don’t use javascript. I just do it in the old Openhab DSL script language.

4

I tested you script on 5.1.2 and 5.2.0.M1 and it works fine.

Screenshot_20260220-093536.Pushover
Screenshot_20260220-093536.Pushover1080×498 33.9 KB

rule "test pushover"
when
    Item Test1_Switch changed to ON
then
	val actions = getActions("pushover", "pushover:pushover-account:pushover")
    // send HTML message
    actions.sendHtmlMessage("Hello <font color='green'>World</font>!", "openHAB")
end

Make sure you have the correct syntax in your action:

Screenshot 2026-02-20 093928
Screenshot 2026-02-20 093928822×233 5.27 KB

5

It’s been working perfectly for 7 years and I’ve not changed anything in years, so I’m at somewhat of a loss. It doesn’t fail on the getActions() line so it assume it thinks Pushover is installed. I just installed 5.2 and the problem remains. Is there any way to test if Pushover is correctly installed?

6

Go to karaf, type bundle:list and check if pushover is active.

7

And now after a second reboot, it works again.

1 Like