From Somfy recommandation, we map open to deploy and close to undeploy for Awning devices. It’s the case for your Absenkmarkise and Hauptmarkise. But your Seitenmarkise is not reported as an Awning, it’s why you see a reverse state. FYI the same kind of motor can be used for a classic cover where this state is logic.
thank you for the explanation and I understand the logic of the non awning is coming from core then.
Template Covers are also problematic as the issue here is that value_template and position_template cannot been set concurrently in a template cover, so HA assumed the cover is open, when position is 100 and cover is closed when position is 0.
So I would need to use the orignal and template entity both to have a full working solution.
Edit: btw … I understand and support the Somfy logic. I think also for “other” covers many people would like to have 0 = closed = undeployed and 100 = open = deployed …
unfortunately core has no option to actually invert this.
Can you post your diagnostics information here? (or on GitHub gist and link it here). It would be interesting to see the device types, since we are revamping the cover entity.
hey and when revamping the cover entity … maybe also consider that many actuators actually report 1-3 % off … means when they fully open or close the motor itself might stop the motor a moment earlier than the actuator was calibrated which result in something like this:
Just the Somfy ones, there is a download diagnostics button in Home Assistant.
Do you have this issue with the Somfy covers? We will only rewrite the Somfy cover implementation. And even there, I am not in favor of this change. If this is an issue with a certain vendor / platform, they either need to fix this or the Home Assistant integration needs to handle this margin / offset.
Had the same issue. Got it working by patching the api.py file from PR Custom Component: on line 330, there’s a call to timeout(). I just removed the loop=asyncio.get_event_loop() parameter (and the comma of course), so that it reads:
async with async_timeout.timeout(TIMEOUT):
I don’t know if this is really a proper fix, but (after a restart of HA) I was able to install this native Somfy API component - and it has been working like dream (for now): response is like instantaneous!
I have an Atlantic Heat Pump which is connected to an Atlantic Cozytouch bridge : COZYTOUCH - Atlantic
I can pretty much control my HeatPump using Android CozyTouch app (not so great).
More interesting for me, I can control it using Overkiz API : https://ha110-1.overkiz.com/enduser-mobile-web/enduserAPI/login
For instance I can login, get all parameters value, and set whatever I want.
Great, but I do this with NodeRed, I’ve got a lot of flows and that’s a mess !
I’ve just found this Overkiz Component. I’ve tried to install it, choosing “Atlantic Cozytouch” hub, I set my email and my password, exactly the same that work fine with Overki API but I keep getting a message “Unvalid Authentication”.
I’ve done the test several times. I’ve also stopped my overkiz API requests for 2 hours because I know it does not support too many requests, but still the same.
Any idea how I can investigate on this ?
Did anybody succeeded with Atlantic hardware and overkiz component ?
I’ve been using it for 2 years now. But I did not use the CozyTouch app for a long time now, more than a year, using only overkiz http API to manage my HeatPump with curl commands.
I will have a look at this link, and I will also reinstall Coytouch Android app and check that everything still works fine from here.
What is strange is that using overkiz with curl commands, it works fine… but who knows…
Thanks for your help, I’ll be back after a few checks.
I’m not 100% sure if this is the right place to post but I’m new to Home Assistant and trying to add the devices connected to my Thomas hub
It’s detected the hub and I added the Homekit ‘variant’, but I see the Overkiz ‘variant’ and my credentials won’t be accepted…
I’m certain they’re correct as I can log in to the app with them, so I’m a little confused
I’m also uncertain if this is necessary if I’ve added the hub using the Homekit option, tho I don’t seem to be able to find the related devices and scenes based on that
@vaderag, which hub do you have exactly? The HomeKit controller in HA is a separate integration and device support is limited due to Somfy limitations. It should work with the same email address and password as you use for your TaHoma app.
I’m currently totally reworking the cover platform The goal is to ease the maintenance and be able to add new devices quickly
Obviously, I don’t own all the Somfy devices, so I need some help. Can some of you update the file overkiz/cover.py by this one and report me what’s work and does not work anymore? It should be compatible with both ha-tahoma and overkiz integration.