Tesla powerwall fails

briansheets · February 13, 2024, 2:36pm

Brand new HA. Powerwall 2, I’m able to connect via the web interface.

2024-02-12 21:51:06.195 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home Energy Gateway for powerwall
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 133, in async_setup_entry
    base_info = await _login_and_fetch_base_info(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 219, in _login_and_fetch_base_info
    return await _call_base_info(power_wall, host)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 241, in _call_base_info
    raise e.exceptions[0] from None
  File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/powerwall.py", line 127, in get_batteries
    return [BatteryResponse.from_dict(battery) for battery in batteries]
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/responses.py", line 305, in from_dict
    grid_state=GridState(src["pinv_grid_state"]),
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 744, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 1158, in __new__
    raise ve_exc
ValueError: '' is not a valid GridState
2024-02-12 22:07:03.881 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home Energy Gateway for powerwall
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 133, in async_setup_entry
    base_info = await _login_and_fetch_base_info(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 219, in _login_and_fetch_base_info
    return await _call_base_info(power_wall, host)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 241, in _call_base_info
    raise e.exceptions[0] from None
  File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/powerwall.py", line 127, in get_batteries
    return [BatteryResponse.from_dict(battery) for battery in batteries]
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/responses.py", line 305, in from_dict
    grid_state=GridState(src["pinv_grid_state"]),
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 744, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 1158, in __new__
    raise ve_exc
ValueError: '' is not a valid GridState

nugget · February 23, 2024, 9:30pm

This likely indicates that one or more of your Powerwall batteries is offline or disabled. You may have some luck using the Netzero for Tesla mobile app to further diagnose your local setup.

There are two open issues on GitHub related to this:

github.com/home-assistant/core

Tesla Powerall integration fails to load when one Power Wall is failing

opened 03:24AM - 14 Feb 24 UTC

matellis

integration: powerwall

### The problem I have four powerwalls connceted to one gateway. One of the pow…erwalls is failing, in the Tesla One app it says "Unable to Read Data" for that unit. Consequently the Tesla Powerwall integration fails to load at start and when instructed to reload. Error message in logs says "ValueError: '' is not a valid GridState'. See logs for specific error stack. It would be great if the integration could handle this and still load, and even better if it could flag that there may be a fault. Tesla didn't tell me until I investigated and found this. ### What version of Home Assistant Core has the issue? core-2024.2.1 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Tesla Powerwall ### Link to integration documentation on our website https://www.home-assistant.io/integrations/powerwall/ ### Diagnostics information ``` 2024-02-13 18:51:55.793 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry PDX-2 (Right/9Y/4U/Primary) for powerwall Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 133, in async_setup_entry base_info = await _login_and_fetch_base_info( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 219, in _login_and_fetch_base_info return await _call_base_info(power_wall, host) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/powerwall/__init__.py", line 241, in _call_base_info raise e.exceptions[0] from None File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/powerwall.py", line 127, in get_batteries return [BatteryResponse.from_dict(battery) for battery in batteries] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/tesla_powerwall/responses.py", line 305, in from_dict grid_state=GridState(src["pinv_grid_state"]), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 744, in __call__ return cls.__new__(cls, value) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/enum.py", line 1158, in __new__ raise ve_exc ValueError: '' is not a valid GridState ``` ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt "ValueError: '' is not a valid GridState'" The faulty powerwall is returning no data. ``` ### Additional information _No response_

github.com/jrester/tesla_powerwall

Disabled battery causes traceback

opened 08:01PM - 23 Feb 24 UTC

nugget

This is a followup from the [Home Assistant core issue 110516](https://github.co…m/home-assistant/core/issues/110516) I have 4 Powerwall batteries in my install and one of the batteries is inoperative and disabled. This causes a traceback when attempting to call `power_wall.get_batteries()` (called from Home Assistant's [_call_base_info](https://github.com/home-assistant/core/blob/dev/homeassistant/components/powerwall/__init__.py#L221) function. The traceback causes my Home Assistant integration to fail to provision correctly and the Powerwall device is not registered in Home Assistant. Here's the raw output for my disabled battery from inside [get_batteries](https://github.com/jrester/tesla_powerwall/blob/89a8ce242f9a9b8a96e8b29bfe5101ff7191413e/tesla_powerwall/powerwall.py#L121) in the module. ``` { 'Type': '', 'PackagePartNumber': '3012170-05-E', 'PackageSerialNumber': 'REDACTED', 'disabled_reasons': ['DisabledExcessiveVoltageDrop'], 'pinv_state': '', 'pinv_grid_state': '', 'nominal_energy_remaining': 0, 'nominal_full_pack_energy': 14714, 'p_out': None, 'q_out': None, 'v_out': None, 'f_out': None, 'i_out': None, 'energy_charged': None, 'energy_discharged': None, 'off_grid': False, 'vf_mode': False, 'wobble_detected': False, 'charge_power_clamped': False, 'backup_ready': False, 'OpSeqState': 'Standby', 'version': 'eb113390162784' } ``` I can prevent the traceback by adding an empty key to the GridState enum in `const.py` like this: ``` class GridState(Enum): COMPLIANT = "Grid_Compliant" QUALIFYING = "Grid_Qualifying" UNCOMPLIANT = "Grid_Uncompliant" DISABLED = "" ``` I'm happy to turn this +1 line change into a PR if that's helpful, but I have no opinions on if this is the correct solution or not. It definitely "fixes the glitch" on my end. It might make more sense to probe `disabled_reasons` instead to bypass any attempt to parse the empty valued `pinv_grid_state` as an alternative solution.