WAREMA WebControl pro Smart-Home-Integration, kostenlos und Open Source

WAREMA blinds, shutters, awnings, lights and scenes, through the WMS WebControl pro. Unofficial.

• Veröffentlicht von LM1LC3N7
• Geräte
• Version 0.1.1
• Erfordert Gladys >=5.1.0
• ★ 0

Auf GitHub ansehenAlle Integrationen

Info

Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.

This integration connects Gladys to your WAREMA WMS WebControl pro through its local API, and offers the channels of your installation in the Discovery tab of Gladys: roller shutters, venetian blinds, awnings, slat roofs, lights and switched loads, as well as your WAREMA scenes. Once a device is added, Gladys reads its state at the interval you choose and controls it through the box. Everything stays on your local network: no cloud. Unofficial, not affiliated with WAREMA.

Development version (0.1). Written from the WAREMA API documentation and the pywmspro library, and tested against a simulated box only: it has never been tested with a real WebControl pro yet. Feedback is welcome on the GitHub repository.

What you get

WAREMA channel	In Gladys
Roller shutter / blind	a shutter: open, close, stop, position, and the cause of its last movement
Venetian blind	a shutter: open, close, stop, position; the slats as their own device, on request
Awning	a curtain: open (= retract), close (= extend), stop, position; its valance too
Slat roof (slats only)	a shutter, read-only for now: position of the slats, cause of its last movement
Dimmer	a light: on/off and brightness (0-100 %)
Light switch	a light: on/off
Switched load	a read-only state and "Turn on" / "Turn off" buttons, off by default
WAREMA scene	a "Run" button: the scene runs as from the WAREMA app

Blinds and shutters are never switches: a "turn everything off" scene does not close them. The position follows the Gladys convention: 100 % = open, 0 % = closed (WAREMA counts the other way: 0 % open, 100 % closed). Fully opening or closing a venetian blind also opens or closes its slats, as the WAREMA app does.

Awnings: Open = retract the awning (WAREMA 0 %, as in Home Assistant), Close = extend it; position 100 % = retracted. Gladys has no "awning" type, so awnings and their valance are curtains: beware, a "close the curtains" of a scene, Google, Alexa, HomeKit or an assistant (MCP) extends the awnings. Check the direction on yours, and tell us if it is the other way round.

Slat roofs are read-only for now (position of the slats and cause of the last movement): their direction and range are not checked on a real box yet.

Stop always goes first: it never waits behind another command of the same product, nor behind a read, and the moves of that product still waiting are dropped. A stop is sent without waiting for the detailed answer of the box; without an answer within 1 s, it is told "sent, without confirmation" and the product is read again.

Window drives, potential-free actuators, load dimmers and the "identify" command are not offered yet.

Wind, rain and ice protections

The protections of the WebControl pro (wind, rain, ice, frost, safety) always keep the upper hand: Gladys never tries to get around them. A command the box refuses is reported as the box said it (its error code), with the last protection it reported for that product, and Gladys never sends it again by itself. Each cover has a read-only "Last movement cause" text (sun, wind alarm, rain alarm, timer, manual…), usable in your scenes, and its badge turns orange while a protection is active, while the box reports the product as blocked, or while it no longer reaches it over the radio.

Requirements

• A WAREMA WMS WebControl pro (container version 11H or later, which brings the API) set up with WMS studio pro, on the same local network as Gladys.
• Its IP address, preferably fixed (reserved in your router).

The API of the WebControl pro has no password: anyone on your network can use it, with or without Gladys. Keep the box on a trusted network.

Setup

1. In Gladys, open the WAREMA WebControl pro integration, Configuration tab.
2. Type the IP address of the box (like 192.168.1.30) and save.
3. Click Test the connection: it shows the number of channels, scenes and rooms.
4. Open the Discovery tab and add the devices you want.

Options

• Read interval (30 s by default, 10 to 3600 s): how often the states of the devices you added are read. Only those are read: each read goes over the WMS radio, one channel every half second. After a command, the channel is read again a few times while it moves.
• Allow switched loads (off by default): a switched load often drives a patio heater. While the option is off, its buttons are refused, and the option is read again just before each request. They are buttons, never a switch: a "turn everything off" does not reach them. A WAREMA scene runs as it is, even when it holds a switched load (a heater) or a window: this option does not block it.
• Slats of venetian blinds as their own device (off by default): each venetian blind also offers a "<blind> – Slats" device (0-100 %). Beware: a "close all blinds" of Google, Alexa, HomeKit or an assistant (MCP) may target this device too.
• Language of the feature names: French or English.

Security and privacy

• Gladys talks only to the address you typed, over plain HTTP on your local network; redirections are never followed. There is no secret to keep.
• Commands leave one at a time per channel, within 3.5 s, or are refused. A command that may have left without an answer (a timeout once sent, an answer not understood) is told "sent, without confirmation" and the channel is read again; a refusal of the box is told "refused" with its code; a box unreachable before sending gives "not sent".
• A "429" or a server error of the box pauses everything (1 minute to 6 hours), and the pause survives a restart. After a failure, Gladys never asks the box more often than the read interval.
• Scenes are never relearnt, and nothing changes the configuration of the box.

Troubleshooting

• "Unreachable": check the IP address (no .local name, the container does not resolve them) and that the box is powered.
• "Does not answer like a WMS WebControl pro": the address answers, but not with the API; check the address, and that the box runs a version with the API.
• Orange badge: hover it: a protection is active, the product is blocked, out of radio reach, or a command was not confirmed yet.

Credits

Logic ported from pywmspro (Apache-2.0) and the Home Assistant wmspro integration (Apache-2.0), after the API documentation published by WAREMA. WAREMA is a trademark of WAREMA Renkhoff SE; this project is not affiliated with WAREMA.

Konfigurationseinstellungen

Diese Einstellungen fragt WAREMA WebControl pro in seinem Konfigurationsbildschirm in Gladys ab.

Einstellung	Typ	Pflichtfeld	Beschreibung
Your WAREMA installation in Gladys	section	Nein	The channels of your WMS WebControl pro are offered in the Discovery tab: roller shutters and venetian blinds (open, close, stop, position; slats on request), awnings and their valance (open = retract), slat roofs (read-only), lights (on/off, brightness), switched loads, and your WAREMA scenes as buttons. Everything stays on your local network, through the free local API of the box (plain HTTP, no password: keep it on a trusted network). The wind, rain and ice protections of the box always win: a command it refuses is reported as it is. Switched loads stay read-only until you allow them below. Never tested with a real WebControl pro yet. Unofficial, not affiliated with WAREMA.
Address of the WebControl pro	string	Ja	The local IP address of your WMS WebControl pro, like 192.168.1.30 (shown in your router, or in the WMS WebControl pro app). Preferably a fixed address reserved in your router.
Read interval (s)	number	Nein	How often the states of the devices you added are read (10 to 3600 s). Each read goes over the WMS radio, one channel every half second: keep it reasonable with many channels.
Language of the feature names	select	Nein	Used for the names of the features of the devices added from now on, and for the movement causes.
Allow switched loads	boolean	Nein	Off by default: a switched load of the WebControl pro (a patio heater is often wired to one) is read-only. On, its "Turn on" and "Turn off" buttons send the command, from the dashboard and the scenes. Never a switch: a "turn everything off" does not reach it. A WAREMA scene runs as it is, even when it holds a switched load (a heater) or a window: this option does not block it.
Slats of venetian blinds as their own device	boolean	Nein	Off by default. On, each venetian blind also offers a "<blind> – Slats" device in Discovery. Beware: a "close all blinds" of Google, Alexa, HomeKit or an assistant (MCP) may target it too.

So installierst du WAREMA WebControl pro in Gladys

1. Öffne in Gladys Integrationen: WAREMA WebControl pro erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
2. Klicke auf Installieren. Gladys lädt das Docker-Image (ghcr.io/lm1lc3n7/gladys-warema:0.1.1) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration).
3. Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
4. Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/LM1LC3N7/gladys-warema.

WAREMA WebControl pro benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.

Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.

Über externe Integrationen

WAREMA WebControl pro ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von LM1LC3N7 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.

• Alle Integrationen durchsuchen, native und aus der Community
• Deine eigene externe Integration bauen und veröffentlichen
• Quellcode auf GitHub — Quelle dieser Dokumentation

Abonniere den Newsletter von Gladys Assistant

Ein paar E-Mails im Monat zu neuen Releases und Neuigkeiten aus dem Projekt. Verschickt von Pierre-Gilles Leymarie, dem Gründer des Projekts. Jederzeit abbestellbar 🙂