Mine respond immediately and reliably, but I still have three issues including the refresh:
The status never refreshes unless I press the ‘stop’ button in the UI control (haven’t tried sending a stop command after the blinds have finished opening/closing, maybe a solution)
I can’t find how to get Google Assistant to see it as something that can be opened/closed, it only shows it as a status
I can’t see how to get the ‘close’ command on the UI control to close up, which gives a tighter close for my old-ish blinds
By ‘UI’ control, I’m talking about this thing:
Haven’t tried faking it with a grid of custom buttons yet, but that would be next.
Yep, that’s what I’m using. Usually, 7 or 8 out of nine tilts work reliably - just a different 7 or 8 each time. And clicking open or close doesn’t always work - sometimes I need to go into the switching app, which tells me the blind isn’t connected, but still works.
You’re right; service cover.stop_cover_tilt needs to be sent after adjusting the position each time otherwise it stays in an opening or closing state. Once the stop command is sent it goes in to the correct state (open, closed, or %open).
I’m seeing the position update correctly regardless i.e. it knows if the blinds are at 50%, etc. it’s the state that doesn’t change unless stop is issued.
Feels like a bug. Need to figure out what relevant logs to send or if it’s enough just to explain the problem in a bug report.
@planetix
There was originally discussion about the tilt positions and the stopping, and I know the HA Team fixed it on release with the close command with some kind of hacky work around.
This is not unique to Switchbot though, the SOMA Tilt motors do exactly the same thing. The work around I found with SOMA was to use the Homekit integration for them, not the actual SOMA one, as the Home kit integration seems to set full open as 100% and closed up as 0% (or closed down as 0% if selected in the SOMA connect). Maybe looking at the code in Homekit integration can show how it handles tilt blinds?
Not unique to Home Assistant though. Connect Switchbot tilts directly to Google with the Switchbot skill and fully closed up is reported as 100% in Google Home and fully open is reported as 50%. This seems to be common with how automated tilt motors report the position.
@withay
I find the exact same thing using the Switchbot Hub Mini too. Reliability does not seem to be a Home Assistant thing on it’s own. I use timers and light level to adjust the tilt directly in the Switchbot app and 90% of the time it does not work at all with light levels, and 20% of the time timers fail also.
So, I have five tilts in my Living Room, and two in my Dining Room. Two separate automation to open them in the morning (Dining Room at sunrise, Living Room triggers off of a motion detector) and they all close at sunset.
At this point, at least one of the Living Room and one of the Dining Room tilts don’t operate, twice a day, every day, usually a different one each time… It’s annoying, and I hate not being able to depend on something automated…
Until this morning - everything opened! Which first made me happy and excited that everything worked, then made me sad and annoyed, because I shouldn’t NOTICE that everything worked.
Questions:
Fourth line “office_blinds_simple” What do I change that to?
20th line: “{{ int(states.cover.office_blinds.attributes.current_tilt_position)*2 }}” What do I change THAT to?
When I enter this template into my configuration.yaml (that IS where these go, right?), and I have one for all seven of my blinds, do I just do seven entries, one after the other, no skipped lines?
So im having problems also using the BlindTilt integration, maybe someone else has seen this?
When I use the HA integration over BLE, and set the blinds to 50% (which should be “fully open”) they never fully open. I have 2 blinds in my kitchen and each will randomly “open” to somewhere between 80-92% but never land on “fully opened”. For example:
Then when I try to close them (either way - to 0% or 100%) via the HA integration them they will frequently jam.
However if I use the local Switchbot app (over BLE or cloud) OR when I use the SmartThings integration they will work flawlessly to both open or close.
nope last update didnt make a difference. I dont think the integration can read the position of the sensor; it just know where it thinks its being “sent to”.
Not sure who’s still following, but the template gives an error. Both the example on the integration info page, and when changed for personal use. I opened a github issue for it - someone posted and agreed when they looked. Waiting for the authors to help.