sorry for late answer…
it works !
great, thanks for your feedback!
Thanks for making this. Do you have a donate button somewhere?
Hey @nickvae - thanks! And actually I do, on my github page (https://github.com/kesteraernoudt/dobiss) I have a Buy me a coffee link. Appreciate it!
Hi kester,
I install the new update this morning… did you add some features or correctif ?
thx
jean-pierre
no, it was an automatically generated pull request that updates the dependencies - in this case just pip that got updated
But if you have any feature requests, let me know 
I’ve pushed a new version, that includes an extra configuration option:
“Added option to set cover position to closed using the internal flag. If covers are stopped halfway, the arrow in that same direction will be disabled then…”
I don’t really use this, but it was asked for :). Let me know if this works for you, or if there are any issues!
1 Like
Many thanks!
I’ve updated a new version that implements a simple timer mechanism to decide if covers are closed or not. By default, it’s disabled, and in the options you can select a number of seconds > 0 to enable it. That number will be the number of seconds the ‘down’ relais needs to be active for the cover to be closed completely.
To use this, the ‘Set Cover End position after move’ has to be disabled, as this forces the end position at every move.
Ideally, I would have an up and down timer per cover, and set the estimated position of that cover with that information. However, for my use-case, knowing if the covers are completely closed is enough :).
Have fun!
Hi @kester
I installed the earlier version yesterday … what is the “set cover end position after move” doing in the background? To be honest, it’s working pretty well.
First experience with your integration and it’s really rocking!
I suppose this is one value that is applicable for all covers? So best is to putt the longest time?
1 Like
this is using the internal status of the last move (up or down) to tell HA the cover is either open or closed. Downside of using this is that one arrow will always be disabled, even when the cover is stopped halfway…
correct! In my NXT config, the relais are automatically disabled after one minute. So I’ve set this time for me at 55 seconds. This means that unless someone actively stops a cover, it will show to be in an end position in HA - for me this works perfectly now: both arrows available when a cover is stopped halfway, and the correct state is shown otherwise…
Can’t you fix this with setting an assumed state? I do that too with my covers on dobiss evolution system…
Then there is always an arrow , regardless the state
Cause I do it with a polling sensor , so if I stop the cover before the polling, and move it back, state could be wrong…
Allthough in theory it will never happen, since I now have a toggle function on my Niko buttons, finally!!
I had looked at that, but couldn’t find a way to use the ‘assumed state’ programmatically. When using template covers in a yaml file, that is an option, but not in a custom component (at least I haven’t found it).
Ah ok, well I did in customize.yaml
mmm, I just found how to do so! So now I can indeed set the assumed state, but keep the arrows available :). I’ll push out an update shortly…
1 Like
Couple of updates:
I’ve created a release of the current stable version, which is v1.0.
This allows me to also create test versions on the dev branch on github.
So by default, HACS will suggest you to install a released version. However, if you want, you can switch to the dev branch as well (select Reinstall in the HACS configuration for dobiss):
With this, I’m actually looking for beta testers! I’ve implemented a first version of Timed Positional Covers, where you see and can set the actual position of a cover:
This works with 2 extra attributes I’ve added:
These, by default, are both set to 25 seconds. They can be changed through the standard way of customizing entities, see https://www.home-assistant.io/docs/configuration/customizing-devices/. I haven’t found a clean way to get these updated values in a custom component, but I worked my way around this. Hopefully I’ll get some feedback Get notified when customize.yaml changes attributes of my component…
The way I’ve implemented it, is that it should behave nicely when the covers are operated outside of HA as well: I do update the assumed position in HA in that case, but don’t actually stop or move covers when the initial movement is not done through HA.
@tvds - this is what you’ve been interested in I believe
If you have tested this, please let me know if it works fine, or if you have any issues and/or suggestions!
Hi @kester
Thanks for your continuous support!
Count me in 
Are the traveling time “up” and “down” related to the time settings in the NXT for activation of the opening/closing relais? Or isn’t there any correlation? Just to know if I need to change also these values in the Dobiss NXT itself.
In my case in my NXT, all my relais are configured to be active for 60s during opening / closing of covers. However in reality many of them only need 15-25s to fully open/close.
they are not related no, but the dobiss settings should be larger of course. The idea is that HA will manage the start/stop of the covers independently.
So to start using this, just leave the Dobiss NXT config to 60s, and put the exact times (I’d suggest to add 1 or 2 seconds though) in the customization for the covers in HA.
I’ve released v1.1 (https://github.com/kesteraernoudt/dobiss/releases/tag/v1.1) which includes the support for these timed covers. They are disabled by default, and can be enabled in the options. If you want to use them, enable them, and then customize the timings for each of your covers.
Enjoy!
Great work thanks! 