@david_b Thank you for testing. Hitting ‘stop’ will indeed report back as ‘open’, also when it is fully closed. Unfortunately, as you also say, I can’t do this differently, due to limitations of the rfxtrx protocol (it can’t report a state, it just receives commands (one way communication). I agree that this is the best option we can get.
Just to be sure, did you test it with a remote, not with the buttons in home assistant?
I will make a PR somewhere coming week, hopefully included in the next release.
@Ernst I’ve update to version 104.0 and I see that the state was not changing this morning. Or do I now have to delete the custom component because there is an update in this version?
Could you try to download the files from my github again and put them in your custom component folder (just overwrite them). I updated the files on my github a few days ago to have all the changes that are in 0.104, as well as the additions to get the state for covers. @david_b is reporting that it worked fine for him, but he has downloaded the updated files. Hopefully, that solves the problem, let me know.
Hi @Ernst I’m using Louvolite Battery Motorised Blinds (same as Dooya) Blinds T6 (under Blinds1 in RFXmngr). The states are changing when used in HA but not when using the remote.
PS: I had groups of blinds in some areas which already report state but your update appears to have fixed the state for individual entities… well done
Thanks for testing. Could you add debug logging (see instructions on my github) and post the debug messages from the log when you press the remote? It should show the command I need to add.
I also looked in the RFXtrx manual, and I’m not exactly sure if this is the model you have?
Transmitting (T) means that your RFXtrx433 device can only send signals, while RT means receiving ( R) and transmitting (T). This depends on the device you have and on the firmware you have installed. In order make the state change when using the remote, you need to have a cover and firmware that has RT in the table.
For the above mentioned cover, this means that it will only work on a RFXtrx433XL, with the right firmware version (ProXL1). The type2 firmware, which can be installed on a RFXtrx433e can only be used to receive the id, not to receive the command (open/close/stop) apparently (see the note in the table).
You also mentioned T6. For T6 covers, it looks like you could also use the RFXtrx433e, but you need to have the correct firmware (Pro1 or Pro2).
So, an important question is, what firmware version do you have installed on your RFXtrx433 and which hardware version do you have (RFXtrx433e or RFXtrx433Pro). See the table below for which firmware can be installed on which device.
It is also mentioned in the RFXtrx manual that to receive signals, you should enable the protocol. So, please check that the protocol is selected in the RFXmngr.
Hi @Ernst sorry for delay. I have the RFXtrx433XL and your right, it’s BlindsT0 i’m using for the rechargeable blinds (sorry for mixup!). Will get back to you as soon as I’ve had a chance to do more testing and gather logs. Thanks!
I think the best way to be able to know the real status of RFY (Somfy) blinds is to use another entity to know that.
I’m using Aqara Door Sensors and I’d like, as is already possible on other type of “cover”, to setup their status using the value_template property.
Do you think, as that’s an already existing option on other type of cover on Home Assistant, it would be relatively easy to decide about their status (open/closed) using one of these binary_sensor entities?
Hi @tcircuns. Yes, you will have to use a different sensor is you want to know the status, when using the original remote. A door sensor should do the trick.
I don’t understand your last question. Do you want to update the state of the rfxtrx cover entity, based on the state of the binary_sensor device? I guess that should be possible somehow, but I’ve never tried. I think you could use an automation to update the state.
Note that the PR hasn’t been merged yet. It’s still waiting for the review.
That is “as designed”. If you press stop, it assumes that the cover was moving (either going up or down), and that you have stopped it before it has fully closed (or opened). Unfortunately, RFXtrx signals don’t send the actual position, so there is no way to detect if it is fully closed.
Therefore, I decided to assume that if you press cover.stop, that it is still open (or at least a little bit open). Only cover.close will report back closed.
Unfortunately, the PR is still not reviewed. It has got the label “needs review” last week, so we have to be patient, I guess.
Is it with 109 also possible to send a command to use an automation to close your sunscreen (rfy somfy)
I’m now having problems to open the sunscreen when the sun is getting over xx lux.
I don’t have the possiblity to send a command.
Not sure. The PR only adds the current state (open/closed) to your cover device. You should be able to use an automation already in 0.108 or lower. The only automation possibility that (I think) will be added in 0.109 is that you can use conditions like “if cover is open”. Unfortunately, I don’t have a cover myself, but perhaps someone else can help you if you post your automation here.
I am running HA 0.110 and trying to get status updates in HA when using the remote that came with my blinds. I am able to very reliably use the buttons on the HA dashboard to move and stop the blinds without issue, but if I use the remote, no updates are displayed on the dashboard icon for the blind. I’m very new to HA (moved from Vera because it’s RfxCom plugin didn’t work reliably for me), so forgive me if I’m not understanding exactly what your plugin update does. The blinds are operating under the BlindsT1 protocol, subtype DC106. I’ve attached a pic of the core log which shows the response received when I use the remote, vs when I use the HA dashboard. Cheers for the help!
Sorry I didn’t see your message earlier (please use @ in front of names to make the forum send a notification). First of all, it’s not my plugin, it is developed by the HA community, I only made some recent small changes.
If I look in the RFXtrx User Guide, I can only find DC106 as being a BlindsT6 protocol, not BlindsT1. (page 65 of the manual). Only the Pro1, Pro2 and ProXL1 firmware support receiving and transmitting, the other firmware only supports transmitting, so make sure you have the right firmware on your RFXtrx device.
Unfortunately, I don’t have a cover myself, so it’s difficult to help you with this. I know from my kaku lights that the codes can slightly vary sometimes. The first two commands seem almost the same, only 2 different numbers. Can you show me your configuration?
Hi @Ernst
Sorry about the username thing, I’m very new to Home Assistant. You are right regarding the BlindsT6 protocol (for some reason, in RTXMGR on Windows, it shows received codes from ‘Packet Type BLINDS1’, ‘Subtype DC106’, but the user guide does state BLINDST6.
I’m on the Pro1 firmware, and when I use the Vera RXTCOM plugin, the blind status is updated in the Vera interface when I use the remote. I had other issues with Vera, hence why I’ve moved just recently to Home Assistant. The first code I sent is from the remote (hence the RECV tag for HA), the second one SEND from HA interface, plus another RECV response for some reason. You are right, the first two are very similar. Below is my configuration.yaml file (sorry for the pic format, I can’t even figure out how to copy from Nano to the clipboard!):
To copy from nano, juist select the text you want to copy, with your left mouse button. Then, right click in nano, having your cursor at the location where you want to paste text. Or use Ctrl+V in windows to paste the text. No need to use ctrl+C.
I would try to remove the cover from your config first, set automatic_add to true, restart home assistant and use the remote a couple of times. Make sure you look at the logs to see if the Id number changes (or not) for each press. Check whether the Id is the same as you have now. If you have different numbers, try each of them to see if it works.
