[worxlandroid] Fix NumberFormatException when sending a Command to mode Channel

[cweitkamp]

• Fix NumberFormatException when sending a Command to mode Channel

2026-08-06 16:29:32.109 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.worxlandroid.inte
rnal.handler.WorxLandroidMowerHandler@6b491d39': For input string: "Party"
java.lang.NumberFormatException: For input string: "Party"
        at java.base/java.lang.NumberFormatException.forInputString(Unknown Source)
        at java.base/java.lang.Integer.parseInt(Unknown Source)
        at java.base/java.lang.Integer.parseInt(Unknown Source)
        at org.openhab.binding.worxlandroid.internal.handler.WorxLandroidMowerHandler.internalHandleCommand(WorxLandroidMowerHandler.java:244)
        at org.openhab.binding.worxlandroid.internal.handler.AWSClientThingHandler.handleCommand(AWSClientThingHandler.java:227)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:149)
        at org.openhab.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59)
        at jdk.proxy135783/jdk.proxy135783.$Proxy135940.handleCommand(Unknown Source)
        at org.openhab.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:97)
        at org.openhab.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49)
        at org.openhab.core.thing.profiles.StateProfile.onCommandFromItem(StateProfile.java:42)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:149)
        at org.openhab.core.internal.common.Invocation.call(Invocation.java:52)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

A different solution might be adding command options to the channel-type like this:

	<channel-type id="schedule-mode-type">
		<item-type>String</item-type>
		<label>Schedule Mode</label>
		<description>Sets Normal or Party mode</description>

		<state readOnly="false">
			<options>
				<option value="NORMAL">Normal</option>
				<option value="PARTY">Party</option>
			</options>
		</state>
		<command>
			<options>
  				<option value="1">Normal</option>
				<option value="2">Party</option>
			</options>
        </command>
	</channel-type>

Signed-off-by: Christoph Weitkamp github@christophweitkamp.de

[Copilot]

Pull request overview

Fixes schedule mode command conversion for Worx Landroid mowers.

Changes:

• Passes raw schedule commands to channel-specific handling.
• Adds mode-to-protocol-code mapping.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
WorxLandroidMowerHandler.java	Converts mode commands to mower codes.
WorxLandroidModeCodes.java	Defines Normal and Party mode codes.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[clinique]

LGTM

[wborn]

I'd go for dropping backwards compatibility and have the more readable commands/enum values (update docs, add upgrade instruction). Also looks like Copilot found a real issue.

[cweitkamp]

I applied the comments from Copilot review and added a hint to the docs.

[lsiepel]

Thanks, LGTM