Fix Z-Wave discovery crash with unknown node firmware version

[TheJulianJES]

Proposed change

This fixes an issue (#169932) where the Z-Wave JS integration does not start if a "Fibaro FGMS001" motion sensor is part of the network but has no known firmware version. The issue is partly caused by this recent PR:

• Discover Fibaro FGMS001 v2.8 as a motion sensor for Z-Wave #169276

This PR fixes the issue by skipping the version comparison if the device's firmware version is not known.
A regression test is also added.

Explanation / AI summary

When a node has not reported its firmware version yet, value.node.firmware_version is None. Comparing AwesomeVersion(None) (an unknown-strategy version) to a schema's min_ver/max_ver raises AwesomeVersionCompareException, which aborts setup of the whole zwave_js entry.

This was not noticed until #169276 added the first schema using FirmwareVersionRange(max="2.8") for the Fibaro FGMS001 motion sensor. Users with FGMS001 sensors where the firmware version is unknown (for whatever reason) hit the crash on every setup after upgrading to 2026.5.0.

To fix this, we now skip schemas with a firmware_version_range when the node's firmware version is not known. If a device is re-interviewed, discovery will run again, and the entity for that schema may be discovered.

(cc @AlCalzone)

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes AwesomeVersionCompareException in Z-Wave after 2026.5.0 #169932
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this pull request as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

This pull request fixes a Z-Wave JS discovery crash during config entry setup when a node’s firmware version is unknown (None) and a discovery schema specifies a firmware_version_range.

Changes:

• Skip schemas with firmware_version_range when value.node.firmware_version is None to avoid AwesomeVersionCompareException during discovery.
• Add a regression test ensuring setup completes with a Fibaro FGMS001 node that has no reported firmware version.
• Add a test fixture variant of the FGMS001 node state without firmwareVersion.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
homeassistant/components/zwave_js/discovery.py	Avoids comparing firmware ranges against unknown/None node firmware during discovery.
tests/components/zwave_js/conftest.py	Adds a fixture that removes firmwareVersion from the FGMS001 v2.8 node state.
tests/components/zwave_js/test_discovery.py	Adds a regression test that asserts the config entry remains loaded when FGMS001 firmware is unknown.

[MartinHjelmare]

Thanks!

[MartinHjelmare]

The codecov coverage diff looks weird. I don't trust it. Let's merge.

[TheJulianJES]

I just looked at it briefly and that continue was already uncovered by tests before. There seem to be no tests for min/max firmware discovery where the schema is skipped (and the firmware version known). We should probably add them in a future PR, but it was only marked here because the indentation changed (from one big if block to two nested ones).

[AlCalzone]

Thanks!