[SOLVED] Upgrade from 4.3.4 to 5.0.0 fails on javaScript and ThingActions sendMail and publishMQTT

Setup, Configuration and Use Migration
1

Hi,
I use OH in a docker environment on debian.
4.3.4 is running fine
After upgrading to 5.0.0 I keep getting errors and most likely I missed to reconfigure something

2025-07-27 08:26:19.782 [ERROR] [.handler.AbstractScriptModuleHandler] - Script execution of rule with UID ‘apc-8’ failed: ‘sendMail’ is not a member of ‘org.openhab.core.thing.binding.ThingActions’; line 171, column 19, length 59 in apc
2025-07-27 08:26:42.311 [ERROR] [.handler.AbstractScriptModuleHandler] - Script execution of rule with UID ‘victron-14’ failed: ‘publishMQTT’ is not a member of ‘org.openhab.core.thing.binding.ThingActions’; line 479, column 2, length 62 in victron
2025-07-27 08:26:33.134 [WARN ] [nelTransformation$TransformationStep] - Failed to use TransformationStep{serviceName=‘JS’, function=‘| parseFloat(input) / 1000’}, service not found

I tried this 3 times. Always with same result. After downgrading to 4.3.4 everything is fine again.
I checked that JavaScript Scripting was loaded with 5.0.0.
For the ThingActions I have no idea what to watch out for.

Any suggestion welcome !

3

What do the specific lines look like? I’m using DSL and both work as (removed sensitive data).

getActions('mqtt', 'mqtt:broker:xxxxuid').publishMQTT('zwave1/_CLIENTS/ZWAVE_GATEWAY-zwave-js-ui/api/refreshCCValues/set', '{"args":[13,50]}', 'TRUE' === 'TRUE')

and
getActions("mail","mail:smtp:xxxxxuid").sendMail("myphone@vtext.com","Shock","Basement Window Vibration")

FWIW these worked in both OH4.x and OH5.0

Also this in the documents

4

Do these continue if you stick with 5.0? There is a chance these are just errors associated with the long time it takes for a newly upgraded OH to come on line. I saw a similar ThingActions error in my logs when I first updated and I often see similar JSScripting errors on first boot before the binding is fully ready.

I would suggest trying 5.0 again, giving it some time and then restarting to container to see if these errors and warnings continue.

5

@JustinG
Yes, i have seen JS errors at startup of 4.3.4 as well and they disappear. With 5.0.0 they stayed

@bandit7311
Yes, i read the release notes including the section of required manual interventions. I could not find any limitations which were mention or adaption which are required.

@apella12

		val actions = getActions("mqtt", "mqtt:broker:myMQTTBroker")
		actions.publishMQTT("wallpanel/mywallpanel/command", sBuffer)

and

val mailActions = getActions("mail","mail:smtp:samplesmtp")
val success = mailActions.sendMail("blabla@gmx.de", "Rauchwarnung", "more blabla")

As I have feedback now that others use these functions successfully with 5.0.0 I will do further tries to upgrade

6

@jlehre You will know if you’ve waited long enough by watching your Things. If the Things are offline I would expect to see these errors from your rules.

If the errors persist while the Things are online something else is going wrong. I can confirm that the MQTT action is working on my system on OH 5.0. I don’t use mail binding but the fact it happens with both points to some other issue.

Also, what sort of rules are these? File based or managed?

7

I had waited for 20 min. I checked all other components and they were fine. Checked release notes and then decided to give up.
I wasn’t even aware I could check the status of the thing :open_mouth:
Thank you for this hint. Rules are file based.

I will try again tomorrow and keep you posted.

8

If the Things fail to come online, they will probably tell you why in their status.

OK, in that case, just to be sure, is the line that pulls the actions inside the rule or outside the rule?

If they are outside the rule and OH loads the file with the rule before the Thing is ONLINE it will fail to get the action and won’t try to get the action again until the rules file is reloaded. You should always pull the action inside the rule so if the Thing is OFFLINE when the rule runs once, it will work when it runs again and the Thing is ONLINE.

Above you show the two lines together but I want to eliminate that as a potential source of problems.

9

knowing this is expected to work I upgraded to 5.0.0 again.
Disabling and enabling the things for smtp seems to fix that.
Unistalling and installing MQTT binding solved the publish MQTT issue.
I also uninstalled / installed JavaScript and then things settled.

5.0.0 is now up and running with no errors and the same configuration as 4.3.4.

Thank you for sharing your experience and help to solve the issue.