generated from ludeeus/integration_blueprint
-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
Problem
The V-ZUG integration throws a "400 Bad Request" error when trying to fetch configuration data from an AdoraWash V6000 washing machine that is in standby mode.
Environment
- Home Assistant Version: 2025.09.4
- V-ZUG Integration Version: v0.4.5
- Device: AdoraWash V6000
- Device IP: 10.0.0.7
Error Log
Logger: custom_components.vzug.shared
Source: helpers/update_coordinator.py:392
Integration: V-ZUG
First occurred: [timestamp]
Unexpected error fetching config data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 392, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 293, in _async_update_data
return await self.update_method()
File "/config/custom_components/vzug/shared.py", line 137, in _fetch_config
return await self.client.aggregate_config()
File "/config/custom_components/vzug/api/__init__.py", line 481, in aggregate_config
await asyncio.gather(
*(handle_command_key(command_key) for command_key in command_keys)
)
File "/config/custom_components/vzug/api/__init__.py", line 478, in handle_command_key
command_raw = await self.get_command(command_key)
File "/config/custom_components/vzug/api/__init__.py", line 567, in get_command
return await self._command(
"hh", command="getCommand", params={"value": value}, expected_type=dict
)
File "/config/custom_components/vzug/api/__init__.py", line 343, in _command
return await once()
File "/config/custom_components/vzug/api/__init__.py", line 299, in once
resp.raise_for_status()
httpx.HTTPStatusError: Client error '400 Bad Request' for url 'http://10.0.0.7/hh?value=ecomXstatXtotalXclear&command=getCommand&_=1759308791'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
Steps to Reproduce
- AdoraWash V6000 goes into deep standby mode (WLAN still connected but device in low-power state)
- Home Assistant starts or integration tries to fetch config data
- Error occurs when trying to retrieve ecomXstatXtotalXclear command
Expected Behavior
The integration should gracefully handle devices in standby mode, either by:
- Skipping non-essential commands when device is in standby
- Implementing proper error handling for 400 responses
- Retrying the command later when device becomes fully active
Actual Behavior
The integration throws an unhandled HTTP 400 error, causing error logs and delayed startup warnings.
Additional Context
- The device works perfectly fine once it's active (door opened, program started)
- Other V-ZUG devices (Tumbler, Dishwasher, Oven MSLQ) don't show this issue
- The AdoraWash V6000 doesn't have a "WLAN always active in standby" setting
- This appears to be specific to the eco statistics command
Suggested Solution
Add error handling for commands that may not be available in standby mode, or mark these commands as optional/non-critical so they don't cause errors during initialization.
Metadata
Metadata
Assignees
Labels
No labels