Cosy 6 #972
Comments
|
Hi and thanks for the feature request. This has been raised in the past and the consensus was that it would be better to use the heat pumps local API where possible for the best experience. I'm assuming the Cosy 6 doesn't have a local API and is not a white labeled product. If so, this could be added but as I don't have a Cosy 6 would be difficult to test. In the API there's is also multiple references to heat pumps (heat pump and octoheatpump), so will take some trial and error to work out which ones to use. This will require some additional demand before I attempt at adding it, unless you're wanting to contribute a solution for which I'm happy to collaborate on. |
BottlecapDave
added
the
More demand needed
|
I would be happy to share my key so you can connect and develop if you wish?
Josh
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: David Kendall ***@***.***>
Sent: Wednesday, August 14, 2024 6:18:05 PM
To: BottlecapDave/HomeAssistant-OctopusEnergy ***@***.***>
Cc: Josh ***@***.***>; Author ***@***.***>
Subject: Re: [BottlecapDave/HomeAssistant-OctopusEnergy] Cosy 6 (Issue #972)
Hi and thanks for the feature request.
This has been raised in the past<#811> and the consensus was that it would be better to use the heat pumps local API where possible for the best experience. I'm assuming the Cosy 6 doesn't have a local API and is not a white labeled product.
If so, this could be added but as I don't have a Cosy 6 would be difficult to test. In the API there's is also multiple references to heat pumps (heat pump and octoheatpump), so will take some trial and error to work out which ones to use.
This will require some additional demand before I attempt at adding it, unless you're wanting to contribute a solution for which I'm happy to collaborate on.
—
Reply to this email directly, view it on GitHub<#972 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEAWQR635CZIG7TX5ADPZJLZROGM3AVCNFSM6AAAAABMMENBOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBZGM4DKNBYGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Thank you for the offer, but I have a policy of not accepting other people's api keys. It might be in the future some diagnostic endpoints are added to try and track the endpoints down. |
|
For future reference, if this feature was to be picked up, it would be good to get an idea of what features/abilities people expect to be exposed. I don't have a heat pump, so Im not sure what is/isn't useful. It would also help in the future at prioritising features if/when this is implemented. |
|
There is a new undocumented service called |
|
Hi, ran the 'octopus_energy.diagnose_heatpump_apis' but no success. 2024-11-23 07:10:01.386 WARNING (MainThread) [custom_components.octopus_energy.api_client] Failed to send request (https://api.octopus.energy/v1/graphql/): 400; {"errors":[{"message":"Cannot query field 'countReset' on type 'HeatPumpConfiguration'.","locations":[{"line":74,"column":7}]}]} |
|
Traceback (most recent call last): |
|
my pump is finally turned on... File "/config/custom_components/octopus_energy/api_client/init.py", line 1693, in async_read_response |
|
Defo working :) |
|
@BottlecapDave i manually appiled the fix based on your recent commits. Failed to perform the action octopus_energy.diagnose_heatpump_apis. Script requires 'response_variable' for response data for service call octopus_energy.diagnose_heatpump_apis. Got {'type': 'execute_script', 'sequence': [{'action': 'octopus_energy.diagnose_heatpump_apis'}], 'id': 96} |
|
The latest update (v13.2.0) should fix the heatpump action. This action should be called via the developer tools, not an automation. Thank you @Joshuaharry120 for running the scripts manually. It looks like the Based on these findings, I want to echo my earlier question.
|
|
Removed id/serial numbers |
|
Thanks for the data. I've updated your comment just so it's a bit more readable. Out of interest, what sort of features are you looking for? |
I was thinking that we could the cosy pods(Z-wave) appear as devices so we can see eatch rooms tempature and humidaity. I'm exploring the API now to see if there is a way we can "press boost" vitually in the event of an extra IO Slot etc. Could be good also that if it detects an error it let's us know and maybe it's action status / history? |
|
It would be good to Lifetime Performance, Live Performance(30min snapshots) I've attached an output of all the ones that i'm able to do and there outputs to try and help |
|
@BottlecapDave attributes/functionality that would be really valuable to have in HA;
|
|
I've had a bit of time to work on this, and released the first beta which can be found at https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.3.0-beta.1 What's included?
Questions:
I have been building this blind, so none of it might work. It might also take me some time to fix any issues. The fact I've started this feature does not mean it will be released alongside the next release. It also means that not all requested features will be in the initial release. |
|
Many thanks for the 1st beta, I've installed it but it's not returning any of the values, it seems it's a date/time formatting issue and also, it's put every sensor into its own entity rather than 1 entity, cosy 6 and then the sensors etc. many thanks for your work so far -- |
Am seeing same of no results but its showing my cosy6 pods just no returns |
|
It may help if you can see what data actually is reported by the heat pump.
|
|
Your only able to see that info when in installer mode, connected to the device directly and we can only use the data from the API.
When in installer mode it stops the octopus app from controlling and blocking api
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: D3RON ***@***.***>
Sent: Wednesday, December 11, 2024 1:05:21 PM
To: BottlecapDave/HomeAssistant-OctopusEnergy ***@***.***>
Cc: Josh ***@***.***>; Mention ***@***.***>
Subject: Re: [BottlecapDave/HomeAssistant-OctopusEnergy] Cosy 6 (Issue #972)
It may help if you can see what data actually is reported by the heat pump.
IMG_8552.png (view on web)<https://github.com/user-attachments/assets/3ab779c9-f011-4ece-be7c-4db09e06389c>
IMG_8553.png (view on web)<https://github.com/user-attachments/assets/8d0ecb49-878a-4839-aa76-7f22ce6e838d>
IMG_8554.png (view on web)<https://github.com/user-attachments/assets/20c31b8f-7967-4b9f-94a5-4e73539f26b4>
IMG_8555.png (view on web)<https://github.com/user-attachments/assets/0f9632f6-01d6-45ac-8967-2220102b38b7>
—
Reply to this email directly, view it on GitHub<#972 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEAWQR53PIEBP2HUVHA7DYD2FA2BDAVCNFSM6AAAAABMMENBOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHEZTQMBXGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
All of this information is also in our Octopus Kraken accounts. So may be useful further down the line. |
|
But as its not on the API its cannot be used yet
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: D3RON ***@***.***>
Sent: Wednesday, December 11, 2024 1:43:08 PM
To: BottlecapDave/HomeAssistant-OctopusEnergy ***@***.***>
Cc: Josh ***@***.***>; Mention ***@***.***>
Subject: Re: [BottlecapDave/HomeAssistant-OctopusEnergy] Cosy 6 (Issue #972)
All of this information is also in our Octopus Kraken accounts.
So may be useful further down the line.
—
Reply to this email directly, view it on GitHub<#972 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEAWQRZ7SI3JGP276T3LU532FA6OZAVCNFSM6AAAAABMMENBOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZWGAZDOMJSGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I feel like you might be getting mixed up between entities and devices. Each sensor is it's own device, and each zone is represented by a single device. This corresponds to the real world devices and is recommended by HA. Each device then might have one or more entities. This means you can assign each device to the correct area (e.g. living room) which can be used to drive automations. As for the retrieval conversion, that will hopefully be a quick fix that I can try and rectify within the next week. This error is what's causing no data to be returned by the sensors. |
|
https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.3.0-beta.2 will hopefully fix the reported error and get us a bit further |
Working! |
|
just updating now, will advise |
|
I've managed to map out some sensors using the Octopus app. Here's what I understand so far based on discussions with my installer when it was being setup: Zones Configuration:
ADDC Zones and Heat Pump Status:
Heat Pump Status by Zone:
Errors and Sensor Observations:
|
Water-Side Stages of the Heat Pump1. Water Heating Boost – 2 Hours – Target 50°CHome Assistant View
Octopus App View
2. Water OffHome Assistant View
Octopus App View
3. Water On – Target 60°CHome Assistant View
Octopus App View
4. Water Schedule OffHome Assistant View
Octopus App View
5. Water Schedule On – Target 60°CHome Assistant View
Octopus App View
6. Water Schedule OverviewSchedule Overview
Heat-Side Stages of the Heat Pump1. Heat Boost – 2 Hours – Target 23.5°COctopus App View
Home Assistant View (Not Updating)
2. Heat OffHome Assistant View
Octopus App View
3. Heat On – Target 28.5°CHome Assistant View
Octopus App View
4. Heat Schedule On – Target 7°C (Off)Home Assistant View
Octopus App View
5. Heat Schedule On – Target 22°CHome Assistant View
Octopus App View
6. Heat Schedule OverviewSchedule Overview
|
|
Thanks for checking and supplying the OE app screenshots.
Based on your original data, it looks like I need to ignore zones that are not enabled. Based on your original data, you have "water" and "zone 1" enabled and the others disabled. This means I need to probably similarly ignore any sensors that are associated with disabled zones, as their data is probably not relevant either.
These are just readings to my knowledge, I think read from the pods you have around your room? You therefore don't set the temperature on the sensors, but instead via the zones? The error you get when attempting to change the zones is a silly omission on my part and I'll try and fix that within the next week. I'm not sure why the water target temperature isn't coming through when you're boosting. I'm also not sure why it's not coming through as -300 when off either. The app must be intepreting that value in some form. Couple of additional questions
|
Based on your original data, it looks like I need to ignore zones that are not enabled. Based on your original data, you have "water" and "zone 1" enabled and the others disabled. This means I need to probably similarly ignore any sensors that are associated with disabled zones, as their data is probably not relevant either.
These are just readings to my knowledge, I think read from the pods you have around your room? You therefore don't set the temperature on the sensors, but instead via the zones?
The error you get when attempting to change the zones is a silly omission on my part and I'll try and fix that within the next week.
|
|
I've just released a new beta (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.3.0-beta.3) which should
|
|
Hi @BottlecapDave, Many thanks for posting beta 3. I've tried setting the temperate etc but it does still return some issues, i believe it's as the temperature gage inside HA, is sending .1 .2 .3 .4 rather then 23 or 23.5 - however, disoute the error, i can see the .1 .2 .3 in my App - On our app, we can only increase by 0.5 as clicking tho, i do get a few errors etc which i've attatched for you Mode From Boost to "off" Set mode to "Heat" Updae Heat on Heat Pump: |
|
Thanks for providing the feedback. Release https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.3.0-beta.4 should hopefully get us a bit further. |
|
Hi, Thanks for providing Beta 4! It's really starting to take shape, and most features are working well. I've encountered a few remaining issues that I'd like to highlight: 1. Model/Manufacturer Display
2. Zone Issues
3. Heat Pump Sensor Status
4. Zone Reporting Issues
5. Preset Boost Errors
Steps to reproduce the error:
Alternatively:
6. Mode Off and Boost Reset
7. Rename Suggestions
Thanks again for your hard work on this. Let me know if you need more details! |
|
Thanks for the feedback. Glad it's getting closer :)
The API doesn't currently provide any of this information for the sensors which is why they're unknown. Technically for this scenario, Octopus is the manufacturer and cosy 6 is probably the model for the sensors as well, but I believe this functionality will work for other integrated heat pumps (e.g. daiken) where these assumptions can't be made.
I'm currently only including sensors where the owning heat pump zone and sensor are both enabled. I can't see anything else in the API which could be used to determine if the sensor should be removed.
The data is currently retrieved from a central location, as per HA recommendations. The sensor should be preserving the set values until it next polls where it will then overwrite the data with the latest information. When you say "click off and then back", do you mean you close the dialog and then reopen? Or you close HA and then reopen it? Or something else?
This was an omission on my side when it comes to temperature changes and in boost mode. This should be a quickish fix.
These names are dictated by HA and can't be changed. I tried to pick the names which were the closest possible. |
|
A new release is available in the form of v13.4.0-beta.1, which should fix the remaining issues as noted above. Because there was a new release, the generated changelog is a bit jumbled and includes things that were in previous releases. One thing to note, I am now using a different value to work out the target temperature for zones. Based on the test data I received, this seems to mean that the water zone is no longer configurable via the UI instead of having -300 as its value. It is my understanding that water can't currently be configured via the OE app, which might be why we're getting rubbish data back so I'm not sure if this zone should be excluded as well. |
|
I'll try having a go at adding flow temps and CoP sensors. Thanks for all the hard work @BottlecapDave! |
|
👀
|
|
Nice one. It's on my list to look at the PR once you've marked it as ready :) What outstanding issues do we have with the current beta's implementation? I'm wanting to make sure it's merged in and available before we expand the functionality (including @lwis's contribution) to make sure the correct people get the correct recognition. |
|
New beta released (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.5.0-beta.1) which includes
|
|
Not sure if this is generally useful information or not. Maybe someday a line in public doc. I've just had a heat pump installed, but not yet paid for. So presumably it is in some weird state. When I run the service, I get a properly formed response main:
errors:
- message: Unable to find device for given account.
locations:
- line: 3
column: 3
path:
- heatPumpStatus
extensions:
errorType: NOT_FOUND
errorCode: KT-CT-4301
errorDescription: >-
We were unable to find a device for the given account. Please check
that the account number (and property ID) is correct.
data:
octoHeatPumpControllerEuids:
- 00:<VALID LOOKING SERIAL NUMBER>
heatPumpStatus: null
euids:
- data:
octoHeatPumpControllerStatus:
sensors:
<VALID LOOKING SENSORS AND READINGS>Will update if I get it working, but nothing happened after that. I guess that's expected. Edit: The beta mentioned below worked 👍 |
|
@AdamLukeTaylor The service at the beginning of this thread was to determine which APIs were required for the cosy 6. There is an open beta linked above (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.5.0-beta.1) around exposing the heat pump within the integration. Please consult the FAQ on how to join the beta if you require help, or you can wait until the feature is released in the future. |
Describe the feature
Ability to control the Cosy 6 heat pump
Expected behaviour
Ability to toggle the heating/hot water via the octopus API with the Octopus heat pump Cosy 6 Octopus
Use Case
ability to trigger heat pump to run hot water/heating during off-peak periods ( EG: Extra IOG Slots )
Confirmation
The text was updated successfully, but these errors were encountered: