-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Atlantic Optimocosy - Double Flow CMV (io:AtlanticHeatRecoveryVentilationIOComponent) #376
Comments
Thanks for your very very detailed report, @tillstaff. This makes implementing way easier. 🥳 I need to have a look if this should be mapped to the fan entity in Home Assistant, or to climate. |
Thanks to you for this integration! Just to know, you could also have a sensor for the speed of each motors (inlet and outlet). The values are here in m3/h (cubic meter per hour):
|
Thanks. Currently that isn't possible, we depend on #223 for that to be technically possible. As a workaround, all device states and attributes are added to Home Assistant as attributes. See a cover as an example; When this device is added, you can use those states via the attributes. |
Ok, that's not a problem for me. In Home-Assistant, we can add new sensors from entities attributes with the template platform. |
I am currently implementing this device, where I started with a This device is pretty complex, but your post is helping a lot :). If the device is not cooling, is it heating? Should I add an option to cool (cooling = on) and an option to heat (cooling = off), or does it work differently? |
@tillstaff could you give https://github.com/iMicknl/ha-tahoma/archive/feature/AtlanticHeatRecoveryVentilation.zip a try? Extract this file and place |
Thanks for this test build @iMicknl The discovery is now ok :
But I didn't find any new climate entity, do you need some specific logs? (although, the CO2 sensor is missing too) |
@tillstaff that is weird. Is there no other error in the log? Could you share a screenshot of your integrations -> devices -> detail pages? |
@iMicknl, I have this error in the logs but I don't know if it's related to this issue :
And here is my device in hassio (only temperature sensors are available as entities) : |
@tillstaff are you sure that the entity isn't added as well? (it could be that it is not correctly linked to a device). Otherwise, would you be willing to work with me via Discord and to share your credentials temporarily? It would speed up the development a lot, since those climate devices are hard to understand and implement. With other users I have seen that this helps to create a basic version in less than an hour, instead of going back and forth. (Discord: https://discord.gg/ENPcXd9j, or iMick#1903) |
@iMicknl, yes I'm sure. When I search for "climate" entitites, I only find the two heaters with "Cozytouch Interface". I will try to join the Discord when I have time to make a live debug session. |
@tillstaff a new version has been published for you :). From here I believe you are able to do some debugging yourselves! |
'There hasn't been any activity on this issue recently. Is this issue still present? |
@segaura could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/feature/AtlanticHeatRecoveryVentilation.zip a try? Extract this file and place Even though the name is (here) still TaHoma, it will also work with Cozytouch ;-). |
Only now I understand how to use the zip, sorry. I see the climate entity, wow! In the "ventilation" section, the "Boost command" I needed works, thank you.
All the presets fail:
The actual presets on the unit remote and Cozytouch app are "manual", "prog" and "auto" and in manual mode you set a target air intake into the house, not a temperature. Other control/commands do not make sense for this unit, like the temperature setpoint and the heating/cooling selector, let me know if I am wrong or if you want to customize the entity to better fit the real object. By now I have not set the log to debug, and I see failing the "cooling" commands (cooling <- off)
and also the heating command (cooling <- off). I have some debug log I can upload but I'm not sure if they contain personal data, e.g. some uuid or other coordinates specific of my unit/bridge/account/... |
@segaura no worries! Great to hear that it did work. Indeed, this is just a test version and quite some things need to be fixed, thus your feedback is more than welcome. @tillstaff did you already make changes to this device? Or didn't you own this device, I don't recall :-). |
@iMicknl I did'nt make any changes on this device and I own the first version of the Optimocosy. For my side:
@segaura the -40°C sensor is for the optional "Canadian well" I think and the cooling mode is for the "freecooling" mode of the Optimocosy. It could be more understandable if the freecooling mode is declared as a FAN mode instead of HVAC mode, but can we have a climate entity without HVAC MODE? Or maybe just use this HVAC MODE : HVAC_MODE_FAN_ONLY? If it's possible, we could use this device as follows :
|
Possible fan states: I am not sure if we can add other fan modes.
Do you know how this works via the official app? Are they calling the refresh commands?
How would that look like and which commands need to be executed? And if you need cooling, why not map this to a
Does it make sense to link a temperature sensor? In your screenshots they show two temperature values. I am not sure if we linked the correct sensor to the climate entity currently. |
I made some debugs and tried to correct each commands. @segaura Could you test this build?
I confirm that the official app is doing refresh commands and it needs to be delayed a little after set commands. (0.5s sleep was needed in the code)
I'm staying with your initial construction, it's working fine. Maybe we could replace HVAC_HEAT by HVAC_MODE_FAN_ONLY, it would be more understandable.
Yes, it does and you choose the best value to display! |
I am testing the new file you provided (extracting it from the zip, the direct link does not work for me). Regarding the "fan only mode" maybe I need to better understand two things:
Regarding the command/sensor/functionalities to map on the custom component, my unit have two set of them:
my question is: are we trying/able to reverse engineer and manage, set (1) or (2) ? |
Back from the first tests.
notes are:
|
We choose to use the "Climate" entity to define this device and we have to map the functionality of the device according to HA mechanism. You can find some guidelines here : https://developers.home-assistant.io/docs/core/entity/climate
We can only manage (1), because only the API deployed for the Cozytouch app is available. We don't have local access to the Cozytouch bridge. |
Thanks @segaura for your tests!
"Kitchen boost" is not well named, it's just a boost with a lower speed (240m3/h instead of 264m3/h in my case)
I suppose that there is a planning handled by Cozytouch, so the Overkiz server can send commands to start and stop the away mode at planned hours.
I don't have this countdown with boost command in the app, but there is a countdown of 60 minutes in the app with the kitchen boost (this countdown doesn't appear on the remote control, so the countdown is handled by Overkiz server). When you launch kitchen boost from the remote control, I have a 30 minutes countdown directly handled by the remote control (can work without cozytouch) but the app did'nt show any timer. It's a little messy!
It was working for me on some conditions when the temperature from the house is above 22°C (temperature set on my side for the bypass) and when it works there is a countdown of 10 hours visible on the remote control but it stops immediatly if the temperature goes to 22°C. If it stops because of temperature, the API is not updated and the cooling state stay at "on". |
Great work, @tillstaff and @segaura. Happy to see such contributions :-).
Perhaps we should set fan mode to auto, when you activate cooling mode? |
You're right, I have set it with the new "Bypass Boost" fan_mode. |
I made a new commit with the following remap :
With the same trick, I have a 30 minutes countdown with boost. Maybe there is some differences between our units. I have the first generation of the "optimocosy" before it was labeled "optimocosy HR plus". @segaura : could you retest the last build? https://github.com/tillstaff/ha-tahoma/blob/feature/AtlanticHeatRecoveryVentilation/custom_components/tahoma/climate_devices/atlantic_heat_recovery_ventilation.py |
I tested each command in both directions, action in ha and aknowledge in cozytouch app and viceversa. Mine is a quite recent model, labeled Optimocosy HR Plus, with cozytouch bridge included in the CMV package and bought in december 2019. |
@segaura Thanks for your feedback! For the app update, the integration send a refresh command after each set command to force the update of the cozytouch API. @iMicknl : do you need some changes in the code? |
@tillstaff @segaura I cleaned up some of the code! Let's see if we can add this device to our upcoming release. Could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/feature/AtlanticHeatRecoveryVentilation.zip a try? Extract this file and place |
'There hasn't been any activity on this issue recently. Is this issue still present? |
I'll be back at home tomorrow and I'll hope I manage to try it and let you know. |
'There hasn't been any activity on this issue recently. Is this issue still present? |
I had some issue this month with HA upgrades.
do you want me to tweak something or, maybe, try the |
@segaura you would need to download the latest version of this branch. Give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/feature/AtlanticHeatRecoveryVentilation.zip a try. Extract this file and place This should accommodate for the beta fix. |
'There hasn't been any activity on this issue recently. Is this issue still present? |
Device information
Atlantic Optimocosy (Double flow CMV) not recognized as a Climate entity.
Would like to be able to set the operating mode (MANUAL, PROG, AUTO, BOOST, AWAY).
Temperature and CO2 sensors are discovered (but no entity created for CO2 sensor).
Device details
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticHeatRecoveryVentilationIOComponent - VentilationSystem - AtlanticHeatRecoveryVentilation - io://xxxx-xxxx-xxxx/15021786#1)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:CO2IOSystemDeviceSensor - AirSensor - CO2Sensor - io://xxxx-xxxx-xxxx/15021786#2)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:TemperatureInCelciusIOSystemDeviceSensor - TemperatureSensor - TemperatureSensor - io://xxxx-xxxx-xxxx/15021786#3)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:TemperatureInCelciusIOSystemDeviceSensor - TemperatureSensor - TemperatureSensor - io://xxxx-xxxx-xxxx/15021786#4)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:TemperatureInCelciusIOSystemDeviceSensor - TemperatureSensor - TemperatureSensor - io://xxxx-xxxx-xxxx/15021786#5)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:TemperatureInCelciusIOSystemDeviceSensor - TemperatureSensor - TemperatureSensor - io://xxxx-xxxx-xxxx/15021786#6)
2021-02-04 09:32:46 DEBUG (MainThread) [custom_components.tahoma] Added device (io:TemperatureInCelciusIOSystemDeviceSensor - TemperatureSensor - TemperatureSensor - io://xxxx-xxxx-xxxx/15021786#7)
Hub:
Cozytouch
Device commands
Set Auto mode :
Set Prog mode :
Set Manual mode :
Set "Over-ventilation House" mode :
Set "Over-ventilation kichen" mode :
Stop "Over-ventilation" modes :
Set "Cooling" mode :
Stop "Cooling" mode :
Set Away mode :
Cozytouch Interface
I'm new with this integration and it's really a great job!
If needed, I can share some other details about my configuration or I can test some others commands.
The text was updated successfully, but these errors were encountered: