Slide (Smart Curtains)

The ‘slide’ ( smart curtains are integrated in Home Assistant 0.99, this is the official thread for discussing things.

1 Like

For Dutch people, you can checkout the forum:

Hi ualex,

Weinig feedback in verband met SLIDE en hassio

Kan je me even vertellen waar ik de documentatie kan vinden om SLIDE mee te integreren in hassio ?

Dank je !



Je kan het gewoon toevoegen aan je yaml configuratie, dit staat ook beschreven in: Slide - Home Assistant

Het is niet mogelijk om het via de GUI te configureren.

Ik krijg deze fout:

Logger: homeassistant.setup
Source: components/slide/
First occurred: 21:39:42 (1 occurrences)
Last logged: 21:39:42

Error during setup of component slide
Traceback (most recent call last):
File “/usr/local/lib/python3.9/site-packages/goslideapi/”, line 84, in _dorequest
async with aiohttp.request(
File “/usr/local/lib/python3.9/site-packages/aiohttp/”, line 1186, in aenter
self._resp = await self._coro
File “/usr/local/lib/python3.9/site-packages/aiohttp/”, line 634, in _request
File “/usr/local/lib/python3.9/site-packages/aiohttp/”, line 721, in exit
raise asyncio.TimeoutError from None

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/”, line 229, in _async_setup_component
result = await task
File “/usr/src/homeassistant/homeassistant/components/slide/”, line 167, in async_setup
await update_slides()
File “/usr/src/homeassistant/homeassistant/components/slide/”, line 58, in update_slides
result = await[DOMAIN][API].slides_overview()
File “/usr/local/lib/python3.9/site-packages/goslideapi/”, line 264, in slides_overview
result = await self._request(“GET”, “slides/overview”)
File “/usr/local/lib/python3.9/site-packages/goslideapi/”, line 141, in _request
resp = await self._dorequest(reqtype, urlsuffix, data)
File “/usr/local/lib/python3.9/site-packages/goslideapi/”, line 137, in _dorequest
raise ClientTimeoutError(“Connection Timeout”)
goslideapi.goslideapi.ClientTimeoutError: Connection Timeout

Enig idee ? :slight_smile:

The cloud integration works, however the current state of the curtains never updates? Any ideas?

Help is much appreciated.

I’ve been using Slide via Home Assistant successfully for a while.
Recently it stopped working though. Initially, I removed the slide from my entities and after a restart it got added back in. After some time it against lost its connection to the entity and I deleted it again.

However, now it does not work at all. It keeps trying to connect, but constantly fails. Could you check what’s going wrong here?

2023-10-11 09:14:17.054 ERROR (MainThread) [goslideapi.goslideapi] RES: API=, type=GET, HTTPCode=429, Data={"message":"Too Many Attempts."}

2023-10-11 09:14:17.056 ERROR (MainThread) [goslideapi.goslideapi] Missing key 'slides' in JSON=null

2023-10-11 09:14:17.058 ERROR (MainThread) [homeassistant.components.slide] Slide API does not work or returned an error

2023-10-11 09:14:46.971 ERROR (MainThread) [goslideapi.goslideapi] RES: API=, type=GET, HTTPCode=429, Data={"message":"Too Many Attempts."}

2023-10-11 09:14:46.973 ERROR (MainThread) [goslideapi.goslideapi] Missing key 'slides' in JSON=null

2023-10-11 09:14:46.974 ERROR (MainThread) [homeassistant.components.slide] Slide API does not work or returned an error

Change your scan_interval to 300 seconds and it should work again.

1 Like

I’m trying to get my slides working locally, but keep getting this error:

Failed request with Local API. Received HTTPCode=200, expected HTTPCode=401

What can I do to fix this? I would expect code 200 would be good, but somehow it’s expecting 401?

The local API is activated on all slides and I can control them through postman without issue.

The local api is broken, after the latest firmware update.

Do you mean in the integration or on the Slides themselves?
Because I can control the Slides locally from Postman without any issue.


I also encountered bellow error when using the local Slide API.
Failed request with Local API. Received HTTPCode=200, expected HTTPCode=401

When I change the api_version from 1 to 2 in configuration.yaml this seems resolved and both my Slides are showing up in HA with the correct position state. But when I try to open or close the Slides through HA, below error shows up in the logs:

(Changing the Slide position with Postman works without any problems)

Any ideas?

I’m having issues with the slide integration. It will work for a few days and then suddenly the entities are no longer available. No changes in my configuration.yaml
Restarting HA has no effect whatsoever.

It’s not broken, but the Set position formating has changed.
Used to be: {"pos": 0}
Now it’s : {\n\t"pos": 0\n}

Using the Postman files from the beta enrollment email, it works fine locally, and the stop command works fine with local API V2, it’s just that setpos needs to be fixed, would be great if this could be address now that the clouded api is shutting down.

On Kickstarter it was announced that will stop their business (it will be liquidated). Also their “Cloud” servers will stop working (I don’t know when). But switching over to a local API control is now essential. Does somebody has a guide on how to switch from the Cloud API to the local API. (I have beta access.)

1 Like

Can you share the API v2 with me? I do not have it … Also, technically it should not matter if it:
{“pos”: 0}
{\n\t"pos": 0\n}
Normally \n and \t should be ignored.

I´ve tried with and without, and it only works with line breaks.
Here, try this link :slight_smile:

The Slide app still works. Does this mean the cloud_api should be working also?

I get the errors below:
Logger: goslideapi.goslideapi
Bron: components/slide/
RES: API=, type=GET, HTTPCode=429, Data={“message”:“Too Many Attempts.”}

  • Missing key ‘slides’ in JSON=null

How can I reduce the attempts? Could that solve the issue?

I have tested “GitHub - ualex73/slide: Slide Component for Home Assistant” with the local API, and all is working fine on my end.

I would switch to the local API, then you are free with number of attempts per minute/hour/etc. De cloud api will be closed in the near future.