[Bug]: Flooding Logs with unmapped status 17

[trutru21]

Narwal Model

Narwal Flow 2

Home Assistant Version

2026.06.2

Integration Version

v1.0.0

Installation Method

HACS

Description

The integration is flooding the Home Assistant logs due to an unmapped working_status value (17). When the vacuum reports this status, models.py treats it as UNKNOWN (0), which subsequently causes vacuum.py to flood the logs with warnings because it cannot map UNKNOWN while the device is off-dock.

Log 1: The root cause (models.py)
This error originated from a custom integration.

Logger: custom_components.narwal.narwal_client.models
Source: custom_components/narwal/narwal_client/models.py:696
Integration: Narwal Flow Robot Vacuum (documentation, issues)
First occurred: 13:08:21 (288 occurrences)
Last logged: 13:47:05

Unknown working_status value: 17 — treating as UNKNOWN. Please report this value at the GitHub repo.

Log 2: The consequential error (vacuum.py)
This error originated from a custom integration.

Logger: custom_components.narwal.vacuum
Source: custom_components/narwal/vacuum.py:103
Integration: Narwal Flow Robot Vacuum (documentation, issues)
First occurred: 13:08:23 (2071 occurrences)
Last logged: 13:48:50

Unmapped working_status UNKNOWN (0) while off-dock — reporting CLEANING

Port Scan Results

Debug Logs

Additional Context

This happens when the vacuum is cleaning in the "custom" mode, maybe the unmapped status is connected to this.