Good question. I suppose it depends on whether the command wasn't properly sent to the cloud API, or if it was sent but failed to make its way back to the SwitchBot hub and over BLE to the blind tilt device.
Although, in both cases, I think the various attributes on the device (position, tilt, level, and the rest) would only update if the position actually changed.. Can you confirm whether or not the attributes correctly indicate the physical position when the system is in this state?
If so, you might look in to ensuring that the attributes reach their desired state some time after the command is sent, else you could send the command again.
I'm curious if others have found any other good solutions to this.
Wondering if BLE is messed up being .5M from the Hub on the right and .5M from my Blink hub on the left. The blinds are 13M away but the spec says 100M straight line so should be ok.
This one opened properly:
Interestingly, tonight when my evening piston fired neither of my blinds closed when issued a Close command. I had to close them from HE and they responded fine.
Maybe I'll try On and Off instead of Close/Open.
This morning the tilt's were non-functional again via WebCore.
I could open them from HE in the devices area so weird.
My left blind went to 68 while my right blind went to 100 as instructed.
Again, weird.
OK, there are definitely some possible clues in all of those screenshots.
"unknown" for commStatus should only happen when you Initialize or Configure, like rebooting the hub, or saving settings on the SwitchBot System virtual device, or by doing either of those commands explicitly. Any idea where those changes are coming from?
Your screenshots in this post left me stumped, because they do look the same. All of the other screenshots seem like symptoms of range/connectivity issues on the BLE link between the SwitchBot hub and the blind/tilt devices. Just a hunch, which it seems like you already thought might be the case as well.
I have moved the hub to the living room, 4 M away from the office.
No errors in the logs since my last post.
Too much Yakity Yak with HE and 2 Blink hubs I suspect.
Quick puzzle for you @tomw
My blinds are working fine since moving the hub but I have a weirdo value I can't explain.
When I set my blinds to 60% from close one of my blinds goes to 60 and one goes to 40.
The Devices page confirms 60/40.
They are both at the same physical position upon inspection. I set the the errant blind to 60 and the motor hums, moves nowhere and stops at the same physical position but now registers as 60.
You can see it gets set in the morning to 60 at 10:34:17 and changes it's mind later on at 12:34:33 after a SetTiltDirection.
All I can figure out it that because the setTiltDirection is not followed by a SetPosition command like the morning command, as it would make no change (a WebCore optimization), the driver possibly send out an uncleared variable becuase it expected a setPosition to follow?
What a guess that is
I'll turn off that WC optimization and force it to always send the setPosition after a setTiltDirection and see if the tilt postion variable behaves.
Strange it doesn't afftect its partner blind though.
Check the device pages for the two blinds - do they have the same 'Start Position Change' values? Both open or both close? Are they both 60% Open or 60% Closed?
StartPositionChange both say Open.
They were both closed UP this morning.
WC issued an Open command, Right opened to 100% and Left opened to 68%, WTF
There are a few attributes I have never messed with as it all seemed straight forward.
How does StartPositionChange affect an Open command?
Edit:
My blinds adjust every hour and the next time it adjusted at 10:00 and Open command went out and the errant 68% went to 100%. Again the motor started up and shutdown without moving the blinds physically as they were already horizontal at 100%.
Seems I'm not alone:
startPositionChange() in my driver only does this: log.warn "startPositionChange not supported"
FYI, "Start Position Change" is a command. Its parameter value doesn't reflect anything about the current state of the blinds. I think the intended effect is to "start changing the position in the direction of <open, close>", but I never implemented it.
TomW, thanks for your integration, I got excited to install it and control my AV setup using HE and Switchbot's Hub2.
Although I've had HE for some time now, haven't done much with it but slowly getting up to speed. Past experiences with SmartThings, HomeSeer, and HAI Omni.
I've installed the Switchbot System virtual device, configured API and secret, can see "comm:good", all of the child devices are there, on the Hub device I see my temperature and humidity. Switchbot Events has my hub selected. But when I try to turn ON one of my child devices, it doesn't turn ON.
Deleted everything, re-installed, rebooted numerous times, all with the same results. Pilot error on my part, or is something broken in 2.3.7.145 on my C-5?
Does it work for controlling your AV component when you try it from the SwitchBot app on your phone?
If so, please enable logging on the SwitchBot System virtual device in Hubitat. Then try the commands on the SwitchBot IR Device page in Hubitat and check the output in Logs.
