Overkiz integration - Local API [Development / Testers topic]

Here ya go…and to answer your question, yes, I can control the shades from the somfy entity itself, just not the template cover.

template:
    - trigger:
        - platform: state
          entity_id: cover.closet_shade
          id: open
          to: opening
        - platform: state
          entity_id: cover.closet_shade
          id: closed
          to: closing
      sensor:
        - name: Closet Shade Helper
          unique_id: e9424fd9-e3a6-4ce2-8f8d-f06ff0147257
          state: "{{ trigger.id }}"

cover:
    - platform: template
      covers:
        rts_closet_shade: # unique ID
          unique_id: 9c448fa2-e1c6-4608-8daa-c09a92a3e5c4
          device_class: shade
          friendly_name: "RTS Closet Shade" # your name
          value_template: "{{states('sensor.closet_shade_helper')}}"
          #optimistic: true # default when no state is available
          open_cover:
            - condition: state
              entity_id: sensor.closet_shade_helper
              state: "closed"
            - service: cover.open_cover
              target:
                entity_id: cover.closet_shade # change to your device id
          close_cover:
            - condition: state
              entity_id: sensor.closet_shade_helper
              state: "open"
            - service: cover.close_cover
              target:
                entity_id: cover.closet_shade # change to your device id
          stop_cover:
            - service: cover.stop_cover
              target:
                entity_id: cover.closet_shade # change to your device id
          icon_template: >-
            {% if this.state == 'opening' %}
              mdi:arrow-up-box
            {% elif this.state == 'closing' %}
              mdi:arrow-down-box
            {% elif this.state == 'closed' %}
              phu:shutter-100
            {% else %}
              phu:shutter-20
            {% endif %}

while I check your code, did you check the service works though ?

The service doesn’t work (maybe because of the dependency?).

service on the original Somfy entity I meant, not the new cover.

ie

            - service: cover.open_cover
              target:
                entity_id: cover.closet_shade # change to your device id

Oh, yea, that works. Sorry, I thought I mentioned that.

hmm it all should work then

Unless the helper condition is the issue? If I check the state in dev tools, it’s currently set to open. But hitting the close button on the template does nothing.

very strange, anything in system log ?

Would it make sense to create a new topic for this? This is not really relevant to this local API topic.

1 Like

Well, one if my question was if the local API was required for this to work properly.

Hi, thanks for the work on the local API, it is working great! As an unexpected bonus for me, I can now control my Somfy Elixo 500 3s io gate, which was not possible neither by using Homekit integration or cloud API (I thought this might be helpful for anyone searching in the forum for how to get a gate working).

Now I’d like to switch from using the Tahoma app for scenarios to Home Assistant, but I still miss one functionality for controlling venetian blinds - to do that comfortably, I need to set the position and tilt at the same time (pyoverkiz already supports that, I successfully tested it).

I opened a new feature request here Cover entity - new device action and service: Set position and tilt at the same time I’d be happy if you can comment on that or support it if you find it useful.

I have moved back to the Overkiz Local API again, now with IP-address and disabled SSL check to prevent any mDNS issues.

So far it’s been stable since moving last night, will let you know if it stays connected properly now.

I had created a solution for ‘stateful’ scenes before in HA with Input Boolean Helpers so I have four presets for my curtains and shutters and use the ‘My’ button for the RTS curtains, which is triggered with Automations when the Input Boolean is turned on.

For anyone still wondering why we need a local integration…

Logger: homeassistant.components.overkiz
Source: helpers/update_coordinator.py:350
integration: Overkiz ([documentation]
First occurred: 10:02:49 (1 occurrences)
Last logged: 10:02:49

Error fetching device events data: Server is down for maintenance.

A remote server being down for maintenance shouldn’t mean I can’t open my shutters 2m away from the gateway… Local API works perfectly fine.

1 Like

Is here an easy way to move an existing cloud API config/integration to the local API? Or do I have to remove it completely and create a new integration?

1 Like

Exactly the same question here! :raising_hand_man:

I just deleted the cloud one and re-added the local one. I didnt have to do much more, all the new entities took up their old name, so I didn’t need to modify any of my automations.

1 Like

Hope this is still on topic, but does this also work with the IO verrsion?
I’m looking to buy 4 rollershades and looking to control these via automations locally?

Yes this works all locally. I have RS100 io cover motors and they work perfectly local with the tahoma switch.

Hey guys,

I have the following problem with the local API to control my Tahoma Switch.

I used the cloud API for a while and wanted to switch to the (now a core feature) local API.
I got the PIN-Code, Tahome Switch is in Dev Mode, credentials are correct (tested on somfy webpage). But is neither working for the .local nor the IP (with SSL off) way?!
For each scenario a get a “Connection failed” message without any further information.

What am I missing? I really appreciate your work and help here!!!

1 Like

Update:

This is now resolved for unknown reason. Altough, I had issues with my garage door as well when using a Somfy KeyGo IO. Opening the door would change the state correctly to open(ing) but after it was open and I used my KeyGo again, the door is closing but the state kept for ~1 hour on open, which as of cource incorrect. I fixed this by using an Ikea Parasoll. When the state of the parasoll changed from open to closed, I’m calling my local Somfy API to close the door so it changes the state to closed.

I’m using The Overkiz integration for my garage door and Awning cover. I’m also using the Homekit bridge function so I see these devices in my Apple Home. For some reason, the Awning cover is seen as ‘open’ , but it’s closed. My garage door has the correct status , closed if it’s closed.

Does anyone know if this is a issue with the overkiz implementation, or the homekit bridge integration?