Like a similar post here, I too am experiencing issues specifically with the Bond integration controlling my window shades that were not present prior to this upgrade. I have RM rules that open and close shades and sometimes they open, sometimes not and affect different shades randomly. Logging on the rule will show the open/close or on/off command is sent, and if you look at the Events tab on the shade itself, you see the command, but its state doesn't change. If you then open or close the shades using the controls on the device page itself, it always works, so it seems this issue is related to triggered rules only.
I tried an updated app and driver from another fork of the Bond Integration and got the same results.
Something in 2.4.1.157 has changed that is impacting my rules and their expected outcome (randomly) related to the Window Shades. Other rules controlling lights, switches, custom integration for Google Nest etc.. have been working as expected.
There's nothing new in the Bond integration in 2.4.1.157.
Since the Bond integration is RF dependent, my suspicion is that there is something new in your RF environment that is interfering with the Bond bridge controlling your shades. Can you control your shades with no issues directly from the Bond app?
However, you can roll your platform back to the previous version you had, and update this post with the outcome.
Thanks but it's not RF related. Commands are not getting to the Bond device in some scenarios. Both the Bond App and controlling the shades from the Device page controls manually in Hubitat work as expected. This is only an issue with rules that trigger shades.
Here is a scenario from tonight. The All Upstairs Bond shade is a single channel that closes all the upstairs shades. The command to close was issued by the RM action and a single event generated on the Events tab of the "All Upstairs Bond" device. There should be 3 events always, with the critical event being the "Bond Home Integration" event proving the command was sent to the Bond Hub. The end result was the All Upstairs group status changed to "closed" on my Sharptools dashboard but shades didn't close.
Included in that channel group is a shade called Theater. It went down and was closed.
I have another rule that closes each individual shade (after a delay) once the "All downstairs" group closes, to ensure the open/close status is kept in sync. That RM rule ran, but again it only generated the 1 event for the Theater Shade:
The end result was a shade that was closed by the ALL Downstairs Bond group device, but the actual device page for the individual Theater shade showed otherwise:
I don't use the Bond integration but I've also had failures with blinds since upgrading to the latest version. Maybe it's just coincidence, but I have two IKEA Zigbee blinds that are controlled by a room lighting app. Twice in the last week, one of them had closed but the other has not when the RL app tried to close both of them at sunset. The logs show a command sent to each blind.
In both cases, running the action again worked on the first try. I can't remember the last time one of these blinds failed to respond to a command before this. They're in the same room as the hub and I have a reliable Zigbee mesh.
I turned on the command retry logic on both blinds and am waiting to see if it happens again.
Yes, same thing here with 2 internal blinds in another room, still on Bond but I'm positive thats not where the issue is. One blind goes down, the other not (not always, but most times). There is another post of issues with the latest update as well, very similar behaviors:
I've now rolled back to 155 and will observe tomorrow's rules and behaviors.
[Update] I rolled back first to 2.4.1.155 and got similar issues. I then remembered I had actually jumped from the 2.4.0.151 to the 2.4.1.157 release. So rolled back to 2.4.0.151 now 24 hours ago.
So far, all triggered rules have worked with the shades all operating and their devices updating the open/close status. I therefore believe the issue has presented itself in the major upgrade from 2.4.0.x to 2.4.1.x, which has a lengthy list of improvements, bug fixes, etc...
I will give it a couple more days of observation before seeking input from Hubitat support themselves. I'm staying on 2.4.0.151.
