Warema WMS WebControl PRO integration

Feature Requests
41

Sorry, the pending pull-request needs to have some more unit tests added. Unfortunately, I am too busy with other things in life at the moment. I will get back to working on the integration as soon as possible, which may still take a couple of weeks.

42

any chance that i will get the feature for controling my Lamaxa L70 slat roof any time soon ?

43

Is there maybe anything I can help with? Gladly will do my best to support :slight_smile: - currently it looks like ā€œanotherā€ dead patient ā€¦ :grimacing:
Cheers Mate

44

Iā€™m also ready to help, I would feel very bad if this ended here.

45

I am sorry, but I was busy with more important things in life recently. But now I found the time to get back to work on open source like this. The PR for roller shutters and blinds has been updated and is now ready for review again. Hopefully it can be merged this way.

After this is done, I plan to work on venetian blinds and/or slat drives next.

4 Likes
46

Great to hear this Marc! Just let us know if testing is needed, especially for the slats.

1 Like
47

The PR for roller shutters and blinds was merged, so this will be in 2025.5. Also device identification support will probably land for 2025.6 and now I will try to implement support for covers with slat drives next.

3 Likes
48

Thank you so much for your work - everything is running perfectly and lightning fast now!

1 Like
49

Great News, works like a charm.
Thank you!

Canā€™t wait for the venetian blinds support to complete my automation setup :wink:

50

Iā€™m a bit lost in the terminology here. Iā€™m not sure I know what the cover with slat drive is. Isnā€™t it the venetian blind? The documentation mentions there is support awnings, and earlier you mentioned existing support for shutters and blinds. So what is missing?

51

Venetian blinds have slat drives according to my understanding since they can be rotated, right?

I basically need to implement the correct mapping for each device type of animation and action types according to this file in a way that Home Assistant understands it:

52

Okay, I tried to add support for slat-based covers based on some provided diagnostics.

This is a very early draft and I need to get feedback in terms of movement behavior and direction correctness before I move forward. I cannot test this myself in reality since I do not have access to such covers.

Please give those changes a try if you can: Add support for slat-based covers like venetian blinds to WMS WebControl pro by mback2k Ā· Pull Request #145005 Ā· home-assistant/core Ā· GitHub

53

Iā€™m away now from my home, in about two weeks I can test this. Since Iā€™m not a real HA developer yet, in the meantime (never done core builds), can you pls point me to a description how to build this draft integration and deploy it into HA?

54

Python code is not really built, so following the steps described here is sufficient:

55

Additionally it would also be helpful to get diagnostic files with the covers being in different states including a description of the real world physical state and position. Since I donā€™t have access to such covers, I cannot map the virtual state to the physical state myself.

56

Jumping in here. How can i help to add the slate based covers into HA? I ā€žinstalledā€œ the custom components. The roof is now being shown as a device in the integration. But so far no options to control it. How can i support to add this? (Not being a programmer, sorry)

Edit: after messing around with the API, I can control the slate roof via POST calls out of Home Assistant, which is a huge deal already. itā€™s just not done via the integration. if it helps someone, here are the components I am using:

in the configuration.yaml:

rest_command:
  dach_steuerung:
    url: "http://192.168.xxx.xxx/commonCommand"
    method: POST
    headers:
      Content-Type: "application/json"
    payload: >
      {# 1. Rohwert holen #}
      {% set val = states("input_number.dach_rotation") | int %}
      {# 2. Oberen Grenzwert ziehen #}
      {% set top = [val, 90] | min %}
      {# 3. Unteren Grenzwert ziehen #}
      {% set clamped = [top, -45] | max %}
      {# 4. JSON mit tojson ausgeben #}
      {{ {
         "protocolVersion": "1.0",
         "command":         "action",
         "source":          2,
         "responseType":    0,
         "actions": [
           {
             "destinationId": 19254,
             "actionId":      6,
             "actiontype":    2,
             "parameters": {
               "rotation": clamped
             }
           }
         ]
      } | tojson }}



input_number:
  dach_rotation:
    name: Dach Rotation
    initial: 0
    min: -45
    max: 90
    step: 1
    unit_of_measurement: 'Ā°'

and on the dashboard:

type: vertical-stack
cards:
  - type: entities
    title: Dachsteuerung
    entities:
      - entity: input_number.dach_rotation
  - type: button
    name: Rotation setzen
    tap_action:
      action: call-service
      service: rest_command.dach_steuerung

this is kind of a workaround, but it lets me control the roof from home assistant. you would need to replace the IP address and the destinationID (you can get that from the getconfig command in the api).
Also: the api gives min/max values for ā€œrotationā€ with -127 and 127, but I found out that -45 and 90 are the min/max values for my roof (-45 being closed, 90 being opened all the way)

1 Like
57

and its me again. I didnā€™t like the template stuff in my yaml-files and I am not good enough with git and coding to actually contribute to the official integration, so I created a small integration just for the slate roof controls.
you can find it here:
[GitHub - Reongard/HA_warema_lamaxa: custom integration for a Warema Lamaxa slate roof into Home Assistant] (GitHub - Reongard/HA_warema_lamaxa: custom integration for a Warema Lamaxa slate roof into Home Assistant)

I hope this helps enhancing the official integration

1 Like