Don't allow setting "Default (EU)" controller region

[kpine]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?

Another user set their region to "Default (EU)" in ZUI's Z-Wave settings for a Zooz ZST39 (defaulting to US), believing it resulted in the controller being set to their region, EU (Europe).

This setting doesn't seem to be allowed by the controller, so it reverts to the previous. The user was unable to include or exclude devices until switching to the "Europe" region.

What did you expect to happen instead?

Driver should not allow setting this region, it seems to only exist it indicate a device is set to the default, which must be Europe.

Steps to reproduce the behavior:

1. Set region to "Default (EU)"
2. Notice in the driver logs the command fails

Anything else we should know?

Based on the public Simplicity SDK code, it appears the controller doesn't allow this setting, which aligns with the response received by the driver:

1. https://github.com/SiliconLabs/simplicity_sdk/blob/aa5ce2e835dfdce8c20fb828f27d3a261946f946/protocol/z-wave/Apps/zwave_ncp_serial_api/cmds_management.c#L240-L255
2. https://github.com/SiliconLabs/simplicity_sdk/blob/aa5ce2e835dfdce8c20fb828f27d3a261946f946/protocol/z-wave/ZAF/ApplicationUtilities/_commonIF/ZAF_Common_interface.c#L134-L154
3. https://github.com/SiliconLabs/simplicity_sdk/blob/aa5ce2e835dfdce8c20fb828f27d3a261946f946/protocol/z-wave/dist/include/zpal/zpal_radio.h#L327-L356

I did notice #7118 was implemented, which might fix this for "newer" firmware? Not sure as that code doesn't look like it's public yet.

Software versions

No response

Device information

No response

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwavejs.log

[zwave-js-bot]

👋 Hey @kpine!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[robertsLando]

@kpine Fixed on zui side: zwave-js/zwave-js-ui@a9c8e3a