Great, thankyou very much for the hard work @ggravlingen it’s great to have them in there so fast!
1 Like
Okay,
So we are agreed it’s both correct and unalterable.
So it’s a given and we should live with 10% open etc.
I can live with that.
Thanks, that’s as unequivocal as it can get 
Cheers
Mutt
Not quite following you here. Do you mean that when you press close, it stays 10% open? If so, that’s not intentional.
@ggravlingen No, I think @Mutt refers to the fact that the % refers to how much light it gives, and not how extended the blind is.
So 10% means that it is almost closed, where as 90% means that it is almost open.
I don’t see that in the tests at least, it performed perfectly according to what was set up as guidelines.
1 Like
@ggravlingen, sorry, I was agreeing with the way you have it coded and that it appears in the interface.
Earlier in the thread @fribse suggested that it should operate the reverse from this.
I have no complaint and would commend you both on your communication skills in a language that is not your first, a little misunderstanding occasionally is to be expected.
In short, keep going 
2 Likes
I really can’t believe you have only 3 votes so far, I truly believe that blinds are going to be a major part of home automation. Given the ability to help control both light and heat in a room. And given that IKEA have launched a moderately priced entry into this market (I think they will get cheaper and that others will enter this currently spare sector to compete) , I’m sure that many people will be using the fruit of your labour’s here.
Update: the code for blinds was merged into Home Assistant yesterday so this thread can be closed. As mentioned above, it will take until the next release for the feature to be available.
3 Likes
Thanks to everyone who worked on this, I’ve been looking forward to this integration for some time now.
2 Likes
I’m impressed with the work done and the speed with which it was incorporated. We’ll done
2 Likes
Great work!
I got some issues with my blinds. If the blinds are fully open and I restart my HA, the down button is greyed out and not working. Also the slider doesn’t seems to update the position. If I slide to 50% for example, it show 50%, but when I return to that blind, it show the value set when HA was restarted.
That is odd, that was the behaviour we saw in the early beta.
I think there is trouble in paradise @ggravlingen
I just got it updated and integrated, and it looks like it’s the old code.
I’ve made a small video here:
As you can see the status is not updated during movement as it did in the latest beta, and the ‘arrow up’ and ‘arrow down’ are not updated either.
Moving the slider, does move the blind as per the command given, but the behaviour with the beta was that when you released the slider, it jumped to the current position and updated it until it was stationary.
This is very odd. Did you run the beta branch of HA and the blinds worked?
No, I was talking about your branch, the testing we did with that, that I installed on a seperate RPi3 (my production is RPi4)
That was the code that was merged. I did have some issues when updating the branch to track the rest of the dev branch and that might have caused it. Do you still have the working code on any device?
I might be able to dig it up on an sd card somewhere, what are you thinking?
To test it as a custom component and see if it works. Please post the cover.py file contents here:
https://github.com/home-assistant/home-assistant/issues/27461
I think the issue with the greyed out arrows can be related to the position of the blinds when HA starts. If the blinds are in either of the end positions (open or closed) that arrow gets greyed out. So if my blinds are fully open when I restart HA, the upper arrow gets greyed out. And vice versa if the blinds are fully closed.
I solved this temporary by slightly open all blinds and then restart HA. I then get both arrows working. The slider doesn’t update though.
Thanks for checking!
I’ve simultaneously had 1-to-1 discussions with the poster of the GitHub issue and he found a solution that will be posted to the issue soon.