Replies: 5 comments 7 replies
-
|
Hello and sorry you're having issues. These sensors will only be unknown if the integration is failing to retrieve then latest rate information.
|
Beta Was this translation helpful? Give feedback.
-
|
HI Dave This error originated from a custom integration. Logger: custom_components.octopus_energy.coordinators.current_consumption Failed to retrieve smart meter consumption data - using cached version. Next attempt at 2024-05-02 00:54:48.293695+01:00 This error originated from a custom integration. Logger: custom_components.octopus_energy.api_client Failed to connect. Timeout of ClientTimeout(total=None, connect=None, sock_read=20, sock_connect=20, ceil_threshold=5) exceeded. |
Beta Was this translation helpful? Give feedback.
-
|
If you're getting client timeout issues, then there is very little I can do as this suggests a connection issue either with your HA instance or between you and the API. However, a failure to retrieve current consumption data shouldn't effect rate based sensors. The fact the download diagnostics doesn't work enforces this as it makes a call to get your account information. Has your API key changed? I also need the full tariff code (e.g. E-1R-xxx-A) so that I can look up the rates and make sure they're available (although I don't think this is your issue). Are you doing anything else with the API or have any other OE related integrations installed (and therefore getting rate limited)? |
Beta Was this translation helpful? Give feedback.
-
|
I wonder if this is the same issue as me... A few days ago, a lot of entities became "unknown". I also have lots of warning logs: |
Beta Was this translation helpful? Give feedback.
-
|
Like Thorr, your instance of HA looks like it's having issues connecting to the OE API which is something beyond my control. If the integration can't get the data, then it can't update the sensors. Have you also tried reloading the integration or your HA instance? The instance in your log which is curious is where it states "Errors in request". |
Beta Was this translation helpful? Give feedback.
-
|
I have found today no Gas data coming through |
Beta Was this translation helpful? Give feedback.
-
|
Are you still having issues? Have you tried reconfiguring the api key like @Psai? Have you tried updating to the latest release? |
Beta Was this translation helpful? Give feedback.
-
|
Fyi, I was wrong. Offpeak/intelligent dispatching hasn't triggered since my first message. I've reconfigured multiple times Including removing via hacs and restarting the home assistant machine completely. |
Beta Was this translation helpful? Give feedback.
-
|
@Psai have you tried upgrading to the latest version. Based on some of the warnings it looks like you're on an old version of the integration. |
Beta Was this translation helpful? Give feedback.
-
|
Verrrryyy interesting.
I refreshed the API key, and it looks like it *might* now be working again
(although the previous API key was correct)
…On Thu, May 2, 2024, 17:17 David Kendall ***@***.***> wrote:
Like Thorr, your instance of HA looks like it's having issues connecting
to the OE API which is something beyond my control. If the integration
can't get the data, then it can't update the sensors. Have you also tried
reloading the integration or your HA instance?
The instance in your log which is curious is where it states "Errors in
request".
—
Reply to this email directly, view it on GitHub
<#861 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6OH6KO4UQKB55M5RZUBKTZAJRJXAVCNFSM6AAAAABHBXJEE6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEOJXGYYDO>
.
You are receiving this because you commented.Message ID:
<BottlecapDave/HomeAssistant-OctopusEnergy/repo-discussions/861/comments/9297607
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I'm on the v11.0.0
…On Thu, May 16, 2024, 10:01 David Kendall ***@***.***> wrote:
@Psai <https://github.com/Psai> have you tried upgrading to the latest
version. Based on some of the warnings it looks like you're on an old
version of the integration.
—
Reply to this email directly, view it on GitHub
<#861 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6OH6ISBDHDLIFCADCMUUTZCRYV3AVCNFSM6AAAAABHBXJEE6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINJVGI4TO>
.
You are receiving this because you were mentioned.Message ID:
<BottlecapDave/HomeAssistant-OctopusEnergy/repo-discussions/861/comments/9455297
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I only asked as your screenshot referenced "EntityType is used..." which was fixed in v11. Are you getting similar warnings of not being able to connect? |
Beta Was this translation helpful? Give feedback.
-
Octopus Missing Entities
How can i fix these please
sensor.octopus_energy_electricity_1Redacted74_Redacted_next_rate
sensor.octopus_energy_electricity_1Redacted74_Redacted_previous_rate
Gas
sensor.octopus_energy_gas_Redacted_Redacted_next_rate
sensor.octopus_energy_gas_Redacted_Redacted_previous_rate
Beta Was this translation helpful? Give feedback.
All reactions