alandtse/tesla

Powerwall operation mode does not update from the cloud following HA restart

Open

#618 opened on May 29, 2023

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Python (122 forks)github user discovery
buggood first issuehelp wanted

Repository metrics

Stars
 (741 stars)
PR merge metrics
 (Avg merge 13d 8h) (14 merged PRs in 30d)

Description

Version of the custom_component

3.12.2

Configuration

From core.config_entries

      {
        "entry_id": "<redacted>",
        "version": 1,
        "domain": "tesla_custom",
        "title": "<redacted>",
        "data": {
          "token": “<redacted>“,
          "access_token": "<redacted>",
          "expiration": 1685400615,
          "username": "<redacted>",
          "domain": "https://auth.tesla.com",
          "include_vehicles": true,
          "include_energysites": true,
          "initial_setup": false
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": null,
        "disabled_by": null
      },

Describe the bug

Following HA restart the OperationMode sensor is always empty 'unknown' and does not update from the cloud, even after many hours (tested up to 11 hours).

Debug log

Debug log attached below but the following may be relevant.

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:560
First occurred: 6:11:47 PM (1 occurrences)
Last logged: 6:11:47 PM

Entity select.my_home_operation_mode (<class 'custom_components.tesla_custom.select.TeslaEnergyOperationMode'>) is using self.async_update_ha_state(), without enabling force_update. Instead it should use self.async_write_ha_state(), please report it to the custom integration author.


home-assistant_tesla_custom_2023-05-29T06-46-22.585Z.log

Contributor guide