AtlanticElectricalHeaterWithAdjustableTemperatureSetpoint not supported in Overkiz integration #65427
Comments
|
Hey there @iMicknl, @vlebourl, @tetienne, mind taking a look at this issue as it has been labeled with an integration ( overkiz documentation |
|
Hi, the Core integration is still a work in progress. While we haven’t yet fully backport the whole custom component, you can still use it. |
|
I am running both now because on custom component I got keyerror: username. Once added the overkiz integration my custom component started working again. All right. then i will wait the official release to get climate entities? |
|
If you got an error with the custom component, you can submit us an issue: https://github.com/iMicknl/ha-tahoma |
climate and water_heater will be addressed soon. For now they are not yet integrated into core... |
Hello, same plan for home alarm ?thanks |
|
Please have a look at iMicknl/ha-tahoma#697 for the roadmap. (subject to change, order could change). |
|
Stupid question wh it has been merged without being finished ? |
Not having support for all available devices does not equal 'not finished'. If you see the roadmap, you see the huge amount of pull requests that are required to get even basic functionality in. We are dependent on code reviews and the release cycle of core. In the past we have tried to bring our huge custom integration all at once, however this is just not doable. The review times will be too long and in the mean-time the project has already had so many changes, that you need to refactor your code again. The velocity of core is very fast and thus the best strategy is to bring integrations piece by piece. And to be honest, I don't even see why this would be an issue for end-users. The supported platforms are documented and in the mean-time you can still use the custom integration. |
|
@thundergreen To give you an idea of the required work: https://github.com/home-assistant/core/pulls?q=is%3Apr+label%3A%22integration%3A+overkiz%22+ |
|
Sorry all I don't want to offend at all sorry sorry sorry I really appreciate the hard work and awesome efforts in all your work . I should sometimes maybe just shit the fuck up and be patient |
|
I can't use the custom HACS tahoma because it says "You cannot use Overkiz from core and custom component at the same time" so now I'm without climate entities |
Please report this issue at ha-tahoma. Make sure you update to the last version of the custom component first. We added a check to make sure that users don't configure both integrations at the same time. |
|
Thank you, just updated though |
|
@thundergreen could you include your diagnostics file here? Go to your device page and click on "Download Diagnostics", now you can just drag and drop the text file here in a comment. (or your first post). |
|
Hello. Last version of overkiz gave me even less:
no climate entities at all . Also No sensors. Here attached my diagnosis: hope it helps. I have 2 Sauter Malao Heateers and 1x Interface IO for the Bathroom heater. If you need further info, please let me know. |
|
I don't understand what you mean with the last version of Overkiz. If you talk about core, nothing should have changed. If you talk about the custom component, the core repository is not the place to report issues. However, I will notify you when we implemented your climate devices: This one is already implemented in 2022.3.b0, and will thus be in the 2022.3 release. |
|
I use the custom component (Tahoma) as well as the core integration (Overkiz)
As you can see that core integration just has 3 entities where tahoma custom component has 57. I am bloody beta tester and will report once I got some more info. Thanks a lot. EDIT: I just saw i am already using core-2022.3.0b0
|
|
Hello, it seems i met some problem since yesterday with the overkiz integration, i tried to uninstall the custom component and let the new one overkiz (Hassio found automatically) and i tried to keep both but i have still an error when i check my configuration and i can't restart HA with this error, see my logs : Error occurred loading configuration flow for integration tahoma: Exception importing custom_components.tahoma.config_flow Any idea ?Thanks for your help, for information it was perfectly working before, i haven't done any HA upgrade, my version is Home Assistant 2022.2.9 |
|
@bran2000 you cannot load both components at the same time. Either Tahoma or core . But normally you should also see thos message on the integration widget itself. |
|
@bran2000 first of all, please create a new issue since this is not related. If you have an issue with the Overkiz integration, create it here on core, otherwise create it on ha-tahoma repository. As @thundergreen mentioned, you should not use both integration at the same time, however normally you should have a nice error message. Please update to the latest ha-tahoma integration and if it still has an error, turn on debug logging and create an issue on ha-tahoma repository. For now, I would advise to remove your current config entry and just set it up via Overkiz from core. |
|
THANKS for your replys i only leave the core version for the moment no error configuration, i'll restart my HA tomorrow. |
|
Hi, Like @thundergreen since the big update of Overkiz (by Somfy) i miss the climate entities for my Cozytouch Heaters With the last version of Overkiz (by Somfy) and the core_2021..., i can create for my Gyali radiator a Climate card. Do you have a solution or can you tell me if the climate card will be back or totally abandoned ? Thank you in advance. |
|
@brun0-t please create a new issue with your diagnostic information attached. However, on a quick glance it seems you use your temperature sensor and not your climate entity... |
|
Will they be implemented in future updates? |
I don't know actually... It's been I while since I'm following this issue : iMicknl/ha-tahoma#697. The tick box related to "Climate platform" remains unchecked, and moreover it shifts from month to month... Initially scheduled in February, then March then April... Finally "May+++" when climate platforms will be less useful than in winter. I don't know if there is any activity, I've seen 2 times the automatic robot setting the "no-issue-activity" label, and the admin systematically removes it... I really don't know. |
|
@arandax @Loustik implementation of climate devices is not a quick and easy task. We rewrite all old implementations to match the core codestyle, and without owning a device, this is hard sometimes. See https://github.com/home-assistant/core/pulls?q=is%3Apr+is%3Aopen+label%3A%22integration%3A+overkiz%22+ for the open pull-requests at core. Since the load on core is high (370 PR's open, 1.3K issues) the review time can be quite long. This means that we cannot just move the climate implementation as fast as with the custom component. Currently there are 2 new climate implementations waiting for review. What helps to see the demand, is to at least understand which climate devices we should prioritize. There are a lot of them, and some are just used by a single user. |
|
@iMicknl we know that, for sure... We are supporting you . Moreover, rewriting all legacy code to reduce technical debt & adapt to the new APIs is great, so I've forgotten to tell you, but at first thank you to do so... We, as end users, have some devices, and could test some features for you :) |
|
@Loustik what is your climate device? (just post the model + hardware here). And if possible, your diagnostics. |
|
I have 2 hitachi air-to-air heatpump / air conditioners with HLRR (SPX-TAG01) interface on both. |
|
@arandax you have the HitachiAirToAirHeatPump (HitachiHeatingSystem) - Does this current version in the custom component work 100%? |
raman325
changed the title
Thank you for your reply! |
|
My three Thermor radiators (Equateur 3) were working fine with the custom component but are not recognized (no climate entities created but a bunch of sensors, binary_sensors, etc...) I will continue to use the custom component... |
|
Hi, |
|
Hi 👋 |
|
Hi Thibaut,
Thanks for your reply... I won't be able to test it before 1 month, unfortunately not at home for a long period of time...
all the best for you!
Kind regards
Alain ROBIC
… Le 5 nov. 2022 à 18:28, Thibaut ***@***.***> a écrit :
Hi 👋
Sorry for this long delay, I was quite busy since few month, and still now.
I’ve applied latest modification to #72790
If some of you want to test this PR, feed back are welcome.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
|
@thundergreen @Voileux78 @browetd @Loustik If any of you can’t test the associated PR, will you accept to share with me on Discord your credentials (that will have change temporary of course), so I can confirm the behavior of my implementation? |
|
Hello will give you my temp credentials..would be awesome if we finally
could use core integration iso custom component
Get back in 30 minutes
Thibaut ***@***.***> schrieb am Mo., 7. Nov. 2022, 11:33:
… @thundergreen <https://github.com/thundergreen> @Voileux78
<https://github.com/Voileux78> @browetd <https://github.com/browetd>
@Loustik <https://github.com/Loustik> If any of you can’t test the
associated PR, will you accept to share with me on Discord your credentials
(that will have change temporary of course), so I can confirm the behavior
of my implementation?
—
Reply to this email directly, view it on GitHub
<#65427 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFUA7YCTLFSTG5RT7NNZOLWHDLH7ANCNFSM5NL75B7A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I installed the latest version of the custom components (V 2.14.0) and it is not working for me. The warning messages disappeared but now, I have the following error messages (I have three Equateur 3 radiators from Thermor): 2022-11-07 12:35:50.061 ERROR (MainThread) [custom_components.tahoma] Error fetching device events data: Too many requests, try again later. Not sure if the version of the custom component (V 2.14.0) is including this PR... Let me know if you need more details... |
|
@browetd the custom component is using totally different code and is quite outdated. This issue (+ PR) is for the core component and will hopefully fix all your issues. |
|
OK I will reinstall the core component but how can I apply this specific PR ? Update: I finally found a way to copy the code to a custom_components to test the PR... but unfortunately it is not working (custom_components not starting due to unknown modules) |
|
@browetd Yes indeed, it’s no so easy to test a PR from the Core repository :( Can you tell me if your device support any of these modes? {
"type": "DiscreteState",
"values": [
"antifreeze",
"auto",
"away",
"eco",
"frostprotection",
"manual",
"max",
"normal",
"off",
"on",
"prog",
"program",
"boost"
],
"qualifiedName": "core:OperatingModeState"
}
|
|
@browetd you can always come to our Discord for support! https://discord.gg/3Ee6s5Ar. |
|
@tetienne The modes/presets_mode I am using are: "auto", "off", "prog", "frostprotection" and "comfort"... |
The problem
I used to use the custom integration of https://github.com/iMicknl/ha-tahoma for my Atlantic Cozytouch Hub to control my heaters. Aber now this custom integration has found its way into core, i miss the climate entities for my Cozytouch Heaters (Malao). With the "old" Tahoma custom integration i get all entities created:
But with the new Overkiz integration those climate entities are completely missing:
What version of Home Assistant Core has the issue?
2022.2.0b6
What was the last working version of Home Assistant Core?
never
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Home Assistant OS
Link to integration documentation on our website
https://rc.home-assistant.io/integrations/overkiz
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
As you can see NO climate entity is being setup.
The text was updated successfully, but these errors were encountered: