On a side note, I finally managed to get in touch with the developer of the NPM package, trying to get them to either publish the code on github, or to give me permission to do that.
3 Likes
Hello,
i have successfully found a stick and my warema, how can i add this to the user interface and control it? I couldnāt find anything about it, because everyone seems to know how to do it except me.
THANKS
17 09:07:11.212 I - Press Ctrl-C to abort.
17 09:07:22.828 I *** Stick scanned by SNR 673724.
17 09:07:23.819 I *** Stick scanned by SNR 673724.
17 09:07:24.811 I *** Stick scanned by SNR 673724.
17 09:07:39.385 I *** *** Waving and Hello! (requested from SNR 673724)
17 09:07:39.432 I *** *** Waving and Hello! (requested from SNR 673724)
17 09:07:41.401 I wmsTimeout 2000 ack 000000 ā{a}ā.
17 09:07:43.415 I wmsTimeout 2000 ack 000000 ā{a}ā.
17 09:08:07.700 I *** WMS Network parameters successfully detected:
17 09:08:07.700 I Channel: 17
17 09:08:07.701 I PanId: 4562
17 09:08:07.701 I Key: 40B39B971C46A01F218E51FE7EC74XXX
17 09:08:07.701 I - Write down and remember the network parameters.
17 09:08:07.702 I - Briefly press the learn button on the back of WMS Handheld transmitter to
17 09:08:07.702 I stop the scanning process.
17 09:08:07.702 I - Press Ctrl-C to stop program.
Edit: found the solution
wms_serial_port: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A908E06V-if00-port0
wms_key: 40B39B971C46A01F218E51FE7EC74XXX
wms_pan_id: ā4562ā
wms_channel: ā17ā
force_devices: 834800,643800,720959
mqtt_server: mqtt://192.168.178.XXX:1883
mqtt_user: mqtt
mqtt_password: XXX
Hi, any news on this?
Hi,
not sure if Iām doing something wrong or if type 25 isnāt supported. I can see the messages on mqtt but cannot control the blinds. Any hints what Iām doing wrong?
11 13:35:12.018 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:12.022 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:12.207 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:12.210 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:12.284 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:12.307 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:12.682 I wmsTimeout 750 scanRequest 000000 ā{R04FFFFFF702004A902}ā.
11 13:35:12.831 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:12.920 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.040 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.445 I wmsTimeout 750 scanRequest 000000 ā{R04FFFFFF702004A902}ā.
11 13:35:13.538 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.540 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.567 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:13.692 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:13.724 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.756 I /dev/ttyUSB0 Scanned device: 89400E Type 25
11 13:35:13.845 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:13.847 I /dev/ttyUSB0 Scanned device: 593E0E Type 25
11 13:35:14.207 I wmsTimeout 750 scanRequest 000000 ā{R04FFFFFF702004A902}ā.
Scanned devices.
Registering 933465
Adding device 933465 (type 25)
Registering 934025
Adding device 934025 (type 25)
Sorry, have to revise what I said. The blinds are working now.
I didnāt touch it for some time as I got frustrated and now itās working as isā¦
The weather station is on the mqtt traffic but not displayed in the HA entity.
I need some assistance to get things going. My issue is described here:
Hi,
I am testing this add-on (thank you!). I would like to try some changes (and eventually contribute back to the code). To that end, I naively forked the repo on github and tried to install from https://github.com/thauer/addon-warema-bridge but failed with Not Found (āpull access denied for thauer/addon-warema-bridge, repository does not exist or may require ādocker loginā: denied: requested access to the resource is deniedā). Could somebody point me to the right way ā¢?
Thanks a lot
T
Hi all, I tried to read through all the comments, Iām wondering if there is any news since August. Iām getting my Warema WMS in April next year (venetian blinds and weather station), I would be happy to test it then, can you tell me which approach is the best? I checked Github and saw that none of the integrations are under development currently.
Hello @giannello
Thanks a lot for this addon. I got both of my awmings from warema working. But it shows open when its closed and closed when its opened. Any idea where I did something wrong?
Update:
After every move I get this in the log (even though it works!):
UNKNOWN MESSAGE: {ātopicā:āwms-vb-cmd-result-set-positionā,āpayloadā:{āerrorā:"",āsnrā:123456,āsnrHexā:āABCDEFā,ānameā:āABCDEFā,āpositionā:0,āangleā:171}}
And after a few minutes the device is āunavailableā.
you can ignore the āUNKNOWN MESSAGEā log, as long as it works.
Regarding the device going unavailable and open/closed being reversed, itās something I canāt really tell you without logs at hand.
On a side note, Iām currently rewriting the library that handles the USB stick, so a new version of the add-on might be out before Christmas, with the hope that having more control will let me fix some of the low-level issues with the current implementation.
3 Likes
I am booting my raspberry pi 4 from usb-stick on usb-2-port.
When wms-stick is plugged into the 2nd usb-2-port homeassistant wonāt boot.
Does anybody else have this setup or a solution to the problem?
Hey there, just to say I am jumping right now on the adventure to configure my WMS blinds and sensors on home assistant. I am new to it so hopefully I can get support from everyone here, but I am an experienced software engineer. I hope to be able to help you improve the integration, as I have access to both the WMS web-control (very poor range, not happy with the absence of integrations with the usual suspects) and the red usb key to provision Warema devices.
@giannello I plan on running HA and this add-on on a docker installation without the use of the add-on store, could you please give me some pointers on the required config parameters and if your Docker image would support this?
Hi Marco,
you can run the container without going through the add-on store. addon-warema-bridge/run at 715f0f32c4b4e806ead86ba4c311a42a26097280 Ā· giannello/addon-warema-bridge Ā· GitHub here you can find the environment variables you will need to pass to make it work, make sure to pass the correct TTY to the container. You will also need to create the MQTT user, if your broker needs authentication. Feel free to open a PR and add documentation!
I will absolutely add some step-by-step info to the readme as soon as I get it working!
I think I am close: I managed to read the network acess information from the remote, and I seem to have connection to the mqtt server. How do I configure home assistant so that itās aware of the devices discovered?
the add-on registers the devices with homeassistant on startup, so they should show up automatically
Ah yes I managed, I can see them successfully but they regularly time out during detection because of the poor range of the stick. If I force adding the devices with the environment variables they get added as type 25 which is not correct for all of them, will do a PR to allow specifying a type ad add a readme.
@giannello I forked your repo and refactored the code slightly to address some issues I was having with devices availability, and added some logging options here: GitHub - santam85/addon-warema-bridge. Iāve been testing it for a few days and seems very stable and reliable now. I am using the standalone version, so i did not change the addon files much, I donāt think it was required but I couldnāt test it with the add-on mechanism of HAOS.
Since iāve done some major changes, including the usb stick npm lib source and updating it to the latest serialport lib version, I did not open a PR to your repo, but happy to do so if you think the improvements are worthwile. Yoy can also find there a GHA example on how to automate the releasing of a new docker image, I will work on some basic guide on how to configure it and run it standalone.
I am still having major range issues: with one specific device (which is not even the furthest from the usb dongle). It seems the WMS network is not a very robust mesh even if they claim it is, and suffers from major interferences from WiFi networks on the 2.4g band. Any suggestions to augment the range? I already tried a USB extension, the only thing that seems to work is opening my windows 
.
There is already a major refactoring in progress, havenāt finished it yet tho. Iād say it would be great to see a PR from you, so I can integrate the improvements in the new version. The new version will have both an HAOS and a standalone version.
Regarding range, I think your best shot might be to crack open the dongle and add an external antenna to it.
4 Likes
Hi Guys,
is there any progress so far? Iām currently using the fork from Santam. Btw I also have serious range-problems - sometimes my third blind (which is exactly behind the other two) is not recognized how could this even be if it is a mesh network? 
Iām currently considering throwing away the Warema stuff and switching to Shelly 2.5PM Plus.
cheers
It is most definitely not a mesh network. I tried reaching out to Warema directly to see if they were open to share some information with us so we could improve our reverse engineering of the protocol, but no luck so far.
I cracked open the usb key and the antenna is clearly identifiable on the pcb. Doing some tests soon by soldering a u.fl connector on it and attaching a 2.4ghz antenna to it. I noticed that some of the blinds I have installed do come with an external antenna wire, while others donāt have it, and coincidentally the latter are the ones with range problems. Investigating if itās a shortcoming of the installer or if the wire is just tucked in somewhere weird.
How do you intend using the shelly modules? I only have 3 wires sticking out of my motors for phase, neutral and groundā¦
Do you have the antenna wires sticking out of your blind motors?