That’s the same issue I guess?
Yes, this is the same issue.
looks like this is still broken in the latest release, i’d already started a new post before i found this
Yep the work around still works but it’s depressing to see your comment with the 1 YEAR LATER heading… still waiting for a fix.
D.
honestly did not really notice i was so far behind, is frustrating now though, i want to update but i don’t want to have to do a work around to make the latest version work, when the old one still works…
Agreed but it is a minor work around and you are heading towards a major headache when you do decide to upgrade, the have been many changes in the past year and you will have a big catch up to do.
Most of the updates in the last 7 months have broken at least one thing on my system thats needed a small tweak in the config to fix, naming, zwave, emulated hue on the latest release etc etc, which has been manageable one at a time but all at once will be a headache.
Also you may need a Python update!
I think that if the bug has been around for over a year then your only option may be to fix it yourself and then do a pull request.
time to have a do over for the config of 14x blinds in the house, i’d actually already done the RPI python update, then figured i really should just plug it into the main server and use the docker version.
unfortunately i guess this will be the case
It will give you something to do between Christmas and new years eve! 
Ya it’s been an issue for a longgg time. I’ve got used to doing the opposite to control my blinds. I haven’t tried it yet (was holding out for an official fix) but you could always add a Switch Template to your configuration.yaml. See https://www.home-assistant.io/integrations/switch.template
Similar topic at https://community.home-assistant.io/t/rfxtrx-specific-query-inverted-blinds-up-down/153552
WOW finally fixed in 104.0 and it works
change log:-
RFXtrx - Bump pyRFXtrx to 0.25. This update switches the commands for open and close for RFXtrx covers of the “Rollertrol” type, as they were switched (clicking open resulted in closing of the cover and vice versa). Existing automations should be updated. - (@Ernst79 - #30566) (rfxtrx docs)
1 Like
Praise the lord! Just saw it on the 0.104 notes. Delighted 
@rosscullen @david_b You are welcome. I saw that the fix by Danielhiversen was still open in the pyRFXTRX package, so it was only a matter of asking him to merge the fix and to bump the pyRFXtrx version.
I’m currently working on adding the state to rfxtrx cover devices (so you can see open or closed as the state), which I already figured out. But I now need someone who can do a final test for me, to see if it updates the state if you use a remote. (I don’t have a cover device myself, other than a dummy).
We already found out that updating the state when using the remote is not going to work for RFY protocol (as the RFXtrx433 device can only send signals, not receive it for RFY), but I need someone to test is for the other protocols. Do one of you have a cover that does not use the RFY protocol and have a remote? If your are willing to do a little test for me, I would be grateful. Instructions are in this topic
1 Like
Much appreciated @Ernst. The ‘current state’ would be an excellent addition!
I’m happy to do some testing for you. I’m using Louvolite battery powered blinds (I believe are same as Dooya) ‘DC106 T6 Blinds’ type if that’s any use to you?
Yes, sure. I don’t have a cover device myself, so every test by you is helpful. My program skills are limited, so at least a test by others is very welcome.
Was indeed fixed in 0.104 version of HA, restored my old automations now.
1 Like
yay, well, lucky i was too busy to do the workaround in the meantime, time to get back into it. thanks guys
I think it was only a fix for some devices.
For my Dolat Blinds its the wrong fix.
My covers are going reversed.