Hey, you can add https://github.com/giannello/addon-warema-bridge this as a repository to your add-on store and install the add-on.
Thanks Florian.
The scanRequest is not returning any item, which usually means that the shades are out of range.
After the last HA updates (yesterday), my home setup is behaving the same way - maybe something changed and it’s not playing nice with usb devices? I’ll take some time this weekend to downgrade and see exactly when and why it breaks.
If you feel extra motivated, you can also run the docker image of the add-on on a computer, and point it to HA’s MQTT server.
From my tests, looks like USB3 is the culprit.
When updating, I also moved the USB stick I use as a boot drive to one of the USB3 ports on my RPI4. If I move it back to USB2, I can scan devices again. To make it work while booting from USB3, I have to connect the stick to an USB extension cord, and keep it a few centimeters away from the RPI4.
You might want to try with an extension cord 
erm - I don’t know how to do this … When I try to build the docker image from the git-repository it tells
COPY failed: file not found in build context or excluded by .dockerignore: stat rootfs/srv/package-lock.json: file does not exist
Blockquote[quote=“giannello, post:17, topic:272124”]
From my tests, looks like USB3 is the culprit.
When updating, I also moved the USB stick I use as a boot drive to one of the USB3 ports on my RPI4. If I move it back to USB2, I can scan devices again. To make it work while booting from USB3, I have to connect the stick to an USB extension cord, and keep it a few centimeters away from the RPI4.
You might want to try with an extension cord
[/quote]
I’m not running homeassistant on RPI but on VMware ESXi with the official HA-OVA. I directly passed the USB-Stick to the HomeAssistant virtual-machine - and this is although USB2.0 because the VM does not support USB3.
Anyhow I recognised that there is a error-message on the console when I attach the USB-Stick to it
[somenumber] ftdi_sio ttyUSB1: error from flowcontrol urb
from my short googling It points out that this maybe is an kernel-problem with the ftdi-chipset of the USB-Stick.
I’ve realized the docker image won’t work outside hassio without changes, so I’ve published a “standalone” version that doesn’t depend on hassio to work.
docker run -e WMS_KEY=XXX -e WMS_PAN_ID=XXXX -e WMS_SERIAL_PORT=/dev/ttyUSB0 -e MQTT_USER=warema -e MQTT_PASSWORD=changeme -e MQTT_SERVER=mqtt://homeassistant.local:1883 --device=/dev/ttyUSB0 -it giannello/addon-warema-bridge-standalone
Make sure the mqtt broker is configured to allow username/password authentication, in hassio it’s enough to add
logins:
- username: warema
password: changeme
If you can see the messages coming from the weather station, then the USB stick is being correctly initialized, and I think that error in the console is nothing but a warning.
Also, it doesn’t matter that the VM doesn’t support USB3: it’s not a software/OS problem. USB3 interferes with the stick at the hardware level. If the stick is in the proximity of a USB3 port, and that USB3 port is in use, the radio signal is drowned in electromagnetic noise (paper from Intel here) - I’m even surprised that we can receive signals from the weather station, but I assume that it has a more powerful radio, as it’s a device that’s supposed to stay outdoor.
Hi again,
I would never have believed the thingy about the extension-cable to be honest if I had not seen it with my own eyes now 
I tried now on the same Port with the mentioned extension-cable and voila - It recognizes my blinds and I can control up and down. Currently only full up (0%) and full down (100%) and Stop is possible - correct?
But I think this is just a matter of time 
Until this I think I can manage positions with nodred and timers for stopping at the correct position then.
I will give you a big thanks in the meantime as you helped me really a lot with pointing into the right direction!
I am happy to make myself available for testing!
Cheers
Right now it supports UP/DOWN/STOP and position - just click on the entity and use the slider - you don’t need any timer
UP and DOWN are disabled if the shade is already in the fully-up or fully-down position. If you STOP it while it moves, it might take up to 30 seconds to detect the position, as the position is scanned only twice per minute. I’ll fix this eventually.
Glad to hear I’ve solved a problem also for you please report any issue on github, let’s keep this thread clean for more generic info.
1 Like
Ah yes - I’ve overseen the slider - this works! Thx!
Maybe just one thing - Is it “works as designed” - in my case if the slider is completely left - the blinds are closed by 100% and vice versa - this is a little bit confusing
Cheers
interesting, it’s the other way around for me - 0% is fully closed, 100% is fully open.
Would you mind sending me a copy of the logs, via private messages?
You’ve mail 
Thx!
And tilting works too
Hi,
First of all, my salutations to you for doing this! Really appreciated.
Now to my request: I have the Warema WMS webcontrol unit - not the stick (https://www.der-sonnenschutz-shop.de/warema-2003877-wms-webcontrol.html). So in my case I’d like to connect to the Webcontrol server over IP. Would that be possible with this implementation?
Hi,
No, this add-on works with the stick only. You could try this but I haven’t personally tested it.
Hey Siggy,
Trust me - you need a stick for this - it’s around 50€ + shipping in EU.
You are really restricted with the webcontrol itself. - There is a python-library anyhwere (don’t remember) which is for webcontrol (but only the older version not the webcontrol-pro (for alexa-integration) I have for example)
Hi Giuseppe,
the integration is great. But unfortunately my Raspy is too far away. And spontaneously I don’t have a solution for placing it closer, just for testing.
@siggy:
i have a provisional solution for the webcontrol.
In NodeRed I have created http requests for every roller shutter / blind in the usual positions.
Then I trigger the commands time-controlled, wind or sun-dependent:
ip-address / protocol.xml? protocol = 9004082100000364AAffffff & _ = 1586803111 ’
ip address from your web control
then the code:
90 - I don’t know
04 - Counter it always has to be different, I have the first digit for the room and the second for the position, but I can also make something that automatically counts up
0821 - move command
00 - room (as in the web interface, starts counting at 0)
00 - roller shutter in the room (as in the web interface, starts counting at 0)
03 - Fixed value I have no idea
64 - Position for roller shutters or external venetian blinds (Pos * 2 in Hex)
AA - Angle (only with external venetian blinds) I have a table, but no access at the moment, but if necessary I can search for the determined values.
I didn’t do anything to the rest.
If you copy the “Link” into your browser, you can test whether it works like this.
It is laborious and unconvincing, but currently a solution for me because our house is large and the actuators forward the signals from the WebControl.
Unfortunately, there is no feedback either, I thought about creating input_booleans, which I then also control, then at least I know at which position. I am.
I don’t have a weather station from Warema.
I also have major problems with the WebControl, I often have no connection, then I have to restart it, I have installed a relay in my distribution, so that it is always restarted at night, then it works. The support can’t help me here, they don’t know anything about that.
Unfortunately, the request to an API was also unsuccessful.
And you have to delay the control of the roller shutters / venetian blinds (I have it for two seconds, then it works)
Greetings Stephan
Oh that’s a bummer.
If you have the serial numbers in webcontrol, you can try adding them to the force_devices configuration field (comma-separated) - this prevents the add-on from scanning, and just proceeds to create the devices.
I have the same issue, one of my rollos doesn’t show up during scanning as it’s too far from the stick, but works just fine when added like this.
Hi again,
I’ve posted a “wanted enhancement” to the git repo regarding the weather station.
Cheers Flo
Hey guys,
at first let me thank you for this integration. It hopefully will cover an important part of my smarthome, which I wasn’t able to integrate into home assistant until yet.
Is there an easy way to install this add-on in home assistant, when one (like I did) had not taken the hassio route and therefore is missing the add-on store?