Same error here. I even reported it on GitHub but my ticket was closed because this was supposed to be fixed with update 2022.8.2. Well, it didn’t fix it for me.
For me there also is no response, but it does see and displays the curtain properties. I’ve also had it found it twice. I added it, and a few hours later it found it again… that one immediately didn’t work and displayed connection issues, while the original one does display all properties, just doesn’t respond. When I readded it without password it actually connected quicker (and yes now this also has me worried anyone can add a curtain bot?). But no change.
My logs don’t show use errors. bascially just one saying the connection is lost.
Switchbot communication failed. Stopping trying
7:53:01 PM – (ERROR) /usr/local/lib/python3.10/site-packages/switchbot/devices/device.py
I also have an actual switchbot, that one cannot be found at all.
What I noticed is that in the switchbot app you can set a bluetooth password for a switchbot, but not for a curtainbot. Perhaps that is what the password is for? So it’s perhaps on Switchbot to make the curtains saver?
I had a similar issue and opened a GitHub issue (see above). The Dev replied that they are going to remove the name and password dialog for curtain as they are not required.
I’m one of the lucky ones and mine now work fine. About 30 secs delay from clicking close to any response from the curtain though
I got it working by removing, restarting and waiting for ha to discover them, not manually adding
The Switchbot Curtain devices don’t support a password.
The Switchbot Bots however do.
I think for a bot potentially opening a door the password makes sense, for the curtains I don’t need it.
Passwords need to be setup in the Switchbot app on your phone.
The updates did not change anything for me but some messages that the command failed. Still not working.
Works with ESP and mobile app but not with HA.
It worked once… after a few times sending the open request it did indeed open the curtains (I find both of them separately, but they do seem to work as one). It does seem that was the only time.
Out of curiosity. What is the difference between a Reboot Host and a more regular reboot?
reboot host would get your system reboot at the OS level.
restart essentially would just restart the HA service - without touching the OS, nor other services (think those addons you might have), nor the supervisor.
Typically when you changes your config or integration, you’d want to restart the HA service.
But then this bluetooth thing touches deeper into your hardware, sometimes a proper reboot at the OS level would help.
And, for people wishing to control curtains … I’d say give it some more time.
The native bluetooth thing is not available until earlier this month (Aug. 2022), so it’s still new. The dev’s initial intensions (as I understand from watching the release) were to at least get a bunch of sensors working (temp sensors, weather sensors, etc.) so that HA could at least read those data feeds and use those data feeds.
… at least that’s the short term focus at the moment.
