According to their web site, the stick uses 2.4GHz
That’s why I thought it could use 802.11 instead, but regretfully not. They use a proprietary protocol.
Hi all,
I am just wondering what the last update is on the WAREMA Venetian blinds integration. I have the blind boxes installed, but have not yet the blinds, so I can still adapt to the best situation.
Like shown on the drawing attached, this is the setup I need. A Shelly (Pro series I have now) unit that is controlled by a manual switch on the wall and the HA. I know that in the past the Shelly HA script needs tweaking to make the tilt work, and I am not sure how this currently works with the wall switches in parallel. I am happy to buy additional WAREMA control system if that would allow for easy integration. I do try to stay away from Wifi or RF and like all wired as some blinds are to far away to reach that way.
Can anyone update me on this?
Appreciated, thanks!
veeeeeeeeeeeeeeeeeery slowly 
2 Likes
I have a big Warema setup with 15 raffstores around the house. I currently control this via Homee but the system is hopelessly under-developed and under-supported and I am keen to move this to HA. I finally received my stick and installed MQTT and the add-on from here: GitHub - fisch55/addon-warema-bridge
Unfortunately, I have no luck getting the network parameters from the logs. The stick confirms the scan, but then something goes wrong:
29 12:25:41.680 I *** Stick scanned by SNR 1024756.
29 12:25:55.000 I *** *** Waving and Hello! (requested from SNR 1024756)
/srv/node_modules/warema-wms-api/lib/wms-vb-stick.js:100
stickObj.vnBlindGet(stickObj.currentWmsMsg.snr).name +
^
TypeError: Cannot read properties of undefined (reading 'name')
at Timeout.cmdQueueTimeoutHdlr [as _onTimeout] (/srv/node_modules/warema-wms-api/lib/wms-vb-stick.js:100:57)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
Any idea?
Hi,
thank you for the Warema integration.
Unfortunately, I am facing a problem.
I have a Warema blind, the module is hidden somewhere and I don’t know the exact type. The blind is controlled via an EWFS Handsender 1K (hand-held transmitter 1K). I bought the Warema stick, installed Mosquitto and the Warema plugin. Unfortunately, however, the remote control is not found or it does not find the stick. I can press the learn button on the remote control as long as I want, the LED remains permanently red when I press it and the plugin search ends in timeout (Timeout occured detecting WMS network parameters. Please complete operation within 3 minutes.).
What am I doing wrong?
Edit:
oh damn, while writing I noticed the abbreviation EWFS, a quick google search shows: different radio protocol than WMS.
How do I get this integrated into HA…
Hi,
i have also Warema WMS Shutter installed.
I have the USB Stick and i have programmed in the Warema App.
Is there a Howto to intergrate it in HomeAssistant?
The Addon Warema Bridge - Fisch i have but what i must fillout?
cu
You need to start it and check the logs, there you get the instructions. But first you need to select the stick in the config and save.
Hi fisch, first of all thank you for this add-on. It works like a charme. The only issue I had was, that the stick must be very close to the Warema units.
I’ve just seen you made an update yesterday. Could you share the change log with us?
Thanks!
Hi, thx…. changed only Warema weatherstation from lm to lx. Nothing more ……Greetz
1 Like
Hello,
I have the Warema WMS Stick and want to use it with this add-on to control my two Warema WMS awnings.
My problem is that I don’t have the Key and PAN ID yet, so I can’t connect it…
How could I get these values?
In the Warema WMS studio pro, these are never displayed, and to use the WMS toolkit, I would need the project file which I either never got or I’ve lost it (our awnings are nearly 10 years old now…).
I got some values displayed in the WMS toolkit, but those are simply PANID as PAN ID and Key1 as Key, which is unfortunately too simple to be true and these credentials also don’t work in the Add-on.
Best regards
Aaron
I also have the problem that my HA server is too far away from my awnings for the stick to connect, so could I use my spare RPI3, connect the stick to it and pass the stick through to my HA host (an RPI4 with HAOS) that is further away, and if yes, how?
Gettong these errors when I control the blimds… i receive the blind positions every now and then while moving but everything is far from relible exept full open and close. I can‘t set it to 50%. It either opens or closes completely… i am at a point where i woule pay for a nice working adeon addon… i saw that the npm package was updates 4 month ago in a 2.0 version… maybe this could bring some improvement? #fingerscrossed
Since the recent OS update I’m facing an issue with the add-on.
It was working like a treat for at least a year but I’m not getting the add-on to start properly. The logs are not making any sense to me. Can someone point me in any direction?
It looks like there is some issue with the angle property. I’m only using awnings, so I could potentially remove angle from the code but I wonder how and why this is suddenly not working anymore as the same code did work for about a year until recently…
The EWFS protocol can be recorded from your current remote control and replayed with a BroadLink RM4pro universal IP remote controller for which an Integration into Home Assistant exists.
I‘ve done this successfully for OpenHab but this approach should work for Home Assistant as well.
Hi,
I have a stick and a warema handheld.
I do all steps and I see the stick scanned als othe waving and hello option. Unfortunately then I get a quick timeout and I do not see the login information.
What is wrong ?
Just FYI in case someone is looking for a way to integrate via the WMS WebControl pro: Warema WMS WebControl PRO integration - #9 by mback2k
Hi everyone,
I’m having trouble getting my warema bridge setup to work with my external MQTT server, which is on a different machine but within the same network. I am not using the Mosquitto MQTT Home Assistant add-on.
To troubleshoot, I temporarily installed the Home Assistant MQTT add-on to discover the PAN ID and key, which worked well. However, now that I want to use my regular MQTT server for production, I’m running into issues.
Here’s my current configuration.yaml:
wms_serial_port: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AU0JZKRB-if00-port0
wms_pan_id: BD45
wms_key: XYZXYZXY1811A4C2BE534519XYZXYZXY
wms_channel: 17
mqtt_server: 192.168.1.200:1883
mqtt_user: ha
mqtt_password: mypw
However, in the logs, I’m seeing the following:
[10:03:16] INFO: Setting WMS_SERIAL_PORT to /dev/ttyUSB0
[10:03:16] INFO: MQTT available, fetching server detail ...
[10:03:16] INFO: MQTT server settings not configured, attempting auto-discovery...
[10:03:16] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[10:03:16] INFO: MQTT credentials not configured, attempting auto-discovery...
[10:03:16] INFO: Configuring 'addons' mqtt user
MQTT Error: Error: getaddrinfo ENOTFOUND core-mosquitto
MQTT Error: Error: getaddrinfo ENOTFOUND core-mosquitto
It seems like the system is still trying to connect to core-mosquitto even though I’ve specified my own MQTT server. I’ve tried using the add-ons from @giannello and @santam , but both resulted in the same issue.
Can anyone point out what I might be doing wrong? Any hints or guidance would be greatly appreciated!
Thanks in advance!
I wanted to share that I’ve found a solution to the issue I was having with my own MQTT server on another machine. Initially, I was unable to get the MQTT settings to work correctly, and the server wasn’t being detected properly. The root cause seemed to be that the MQTT settings were not appearing in the add-on’s UI, which made it difficult to configure them correctly.
Solution:
After some troubleshooting with the help of ChatGPT, I decided to fork the original repository and make some adjustments to the config.json file. By modifying the schema section in config.json, I was able to include the MQTT settings in the UI, allowing the server to be found and configured correctly. This change solved the problem, and the add-on now works as expected!
@giannello / @santam , if you’re interested, I’d be happy to merge these changes back into your existing repositorys so others can benefit from this fix.