Failed to setup
- Dominant language
- Python
- Stars
- 30
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Getting the following error when trying to setup - could be a me problem :)
```Logger: custom_components.evnex
Source: custom_components/evnex/coordinator.py:65
integration: Evnex EV Charger ([documentation](https://github.com/hardbyte/ha-evnex), [issues](https://github.com/hardbyte/ha-evnex/issues))
First occurred: 10:53:26 AM (26 occurrences)
Last logged: 11:21:28 AM
Unhandled exception while updating evnex info err=1 validation error for EvnexGetChargePointsResponse data.items.1.connectors.0.meter.power Field required [type=missing, input_value={'frequency': 50, 'powerT...25-07-01T19:45:00.000Z'}, input_type=dict] For further information visit https://errors.pydantic.dev/2.11/v/missing
Unhandled exception while updating evnex info err=1 validation error for EvnexGetChargePointsResponse data.items.2.connectors.0.meter.power Field required [type=missing, input_value={'frequency': 50, 'powerT...25-07-01T19:45:00.000Z'}, input_type=dict] For further information visit https://errors.pydantic.dev/2.11/v/missing
Traceback (most recent call last):
File "/config/custom_components/evnex/coordinator.py", line 65, in _async_update_data
charge_points = await self.client.get_org_charge_points(org.id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/tenacity/asyncio/__init__.py", line 189, in async_wrapped
return await copy(fn, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/tenacity/asyncio/__init__.py", line 111, in __call__
do = await self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/tenacity/asyncio/__init__.py", line 153, in iter
result = await action(retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/tenacity/_utils.py", line 99, in inner
return call(*args, **kwargs)
File "/usr/local/lib/python3.13/site-packages/tenacity/__init__.py", line 398, in
self._add_action_func(lambda rs: rs.outcome.result())
~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 449, in result
return self.__get_result()
~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/usr/local/lib/python3.13/site-packages/tenacity/asyncio/__init__.py", line 114, in __call__
result = await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/evnex/api.py", line 199, in get_org_charge_points
return EvnexGetChargePointsResponse.model_validate(json_data).data.items
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/pydantic/main.py", line 705, in model_validate
return cls.__pydantic_validator__.validate_python(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
obj, strict=strict, from_attributes=from_attributes, context=context, by_alias=by_alias, by_name=by_name
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
pydantic_core._pydantic_core.ValidationError: 1 validation error for EvnexGetChargePointsResponse
data.items.1.connectors.0.meter.power
Field required [type=missing, input_value={'frequency': 50, 'powerT...25-07-01T19:45:00.000Z'}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with custom_components/evnex/coordinator.py:65 and the Evnex client entry point at evnex/api.py:199, then inspect the response model involved in EvnexGetChargePointsResponse. Reproduce a charge-point response whose meter lacks power and determine the expected handling; done means setup completes without the Pydantic validation error and charge-point updates continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100