I’ve been having an issue for a couple of years now, figured its time to get this resolved.
I have 4x Somfy RTS shades, all within ~50 ft or so of the Bond Bridge (ZZ). Every few days or so, at least 1 RTS shade cannot be controlled via Bond. If I power cycle the Bond, it works fine again for another few days. When this issue occurs, I can still use the original Somfy RTS remote control on the shades, so its just an issue with the Bond. I don’t believe it’s a range issue as I’ve moved the Bond around (to be within ~10 feet of a couple shades) and the issue still occurs.
I don’t think it’s a defective Bond, as I’ve also tried a Bond Bridge Pro and get the same behavior – every few days it seems to go into a state where it fails to control at least 1 shade and needs a power cycle.
hmm. If you told me that it was one shade that stopped working entirely, I’d think that perhaps one of the records of the counter value for that one RTS motor was lost. But if it comes back after power cycle, especially if it happens repeatedly and to different motors, that explanation doesn’t fit.
Are you sure that power cycling the Bridge really helps to restore control of the shade that stops working? Or could it be that it actually is just more or less random?
[I just DMed to ask you for the full bond id of this bridge. I’d like to take a look at some logs to see if we can see any patterns.]
I have found it to be random. The thread below helped somewhat. I also created a set of redundant commands for the offending shade with a slightly different parameters, i.e., time or percent open.
I am using Home Assistant with the Bond plugin. I have a “Good Morning” scene which triggers a bunch of lights and opens all of the blinds. Since the Bond HA plugin doesn’t allow me to control a Bond group, I had to make an automation called “All Blinds Open” which opens each blind individually, but I did put a 3 second delay between each action (which did not help with this issue). Note that when this occurs, I’ve used the Bond app (instead of HA) to try to re-gain control of the unresponsive blind, but it remains unresponsive even when using the Bond app.
I do recall a couple of instances where this issue has occurred but I’ve forgotten to power cycle the bond, and the following day the blinds are again working as expected. However, in my experience so far - power cycling the Bond has brought the unresponsive blind control back to life every time.
@merck I will let you know the next time this issue occurs (its usually every few days or so) so you can take a look at the logs. Thank you!
You’re not alone in this. I have an open support ticket for my Bond Pro exhibiting the same behaviour. I also use Home Assistant and have essentially the same process as you (commanding multiple shades with small delays between each).
The timing of when a power cycle is needed seems to vary.
Currently with support we’re investigating if calls to SetPosition are an underlying factor. I’m on day 2 without any SetPosition calls to see if that changes the anything.
Another thing of note was that when the problem is occuring the Bond app (and home assistant) act like the shades moved. The open/close/position updates in HA and in the app, but no movement occurs.
It’s been about 5 days since I turned off all SetPosition calls and switched to using open/close/my commands. Since the change I have not had to reboot the Bond Pro. This also seem to align with only the SetPosition command ever getting an error back from the Bond.
This is all via Home Assistant (but as mentioned one it stops working even trying to use the Bond app won’t control the shades, it just thinks it did).
Are you using the set position (choosing an open/close %) functions? If so, I suggest to try setting your automations / schedules to only use open/close/my temporarily and see if the issue still pops up.
When you mentrion the Set Position setting are you referring to HA or Bond? I have Rollease Acmeda and had to enable Set Position in Bond app. I will be tranistioning to Somfy next year so am interested in this issue you have.
I’m calling the HA cover.set_cover_position action in my automations. Before I disabled that for testing I would see log entries where HA was getting back a 500 error from the Bond once it would stop working. I provided full log output with stack trace in my support ticket (#119843).
I just looked and yes, that setting is turned on. However, I don’t recall having to turn that on. I’ve only had the Bond for about a month so the setup is pretty fresh in my mind.
I paired them and reloaded the integration in HA after adding each shade and they just worked with all 4 commands (open, close, stop/my, and set position).
This is across 10 channels (running 21 shades).
As an aside, I changed to the Bond Pro from a Somfy MyLink. The MyLink was okay, but super picky about being on its own VLAN when it was time for any config changes and it would lock up (or just skip over) if too many commands were sent at once so it needed safety delays. And every reset of the integration caused HA to lose track of its state. And no “set position” ability. All things I moved to the Bond for.
The Somfy integration? Doing a reload was all that was needed to get it working again, I even had a HA automation to handle it for me. I could also restart HA but it wasn’t needed. The problem it exhibits when it needs a reload is a long open issue on the integrations repo. The workarounds people found were switching to a Somfy Tahoma bridge or just switching to a Bond, which is what I did. I didn’t want to give Somfy more money and the Bond gives me options with other future devices.
The Bond Pro has solved all my problems, except for the set position (which Somfy doesn’t do). Set position was a plus on the side of switching from the MyLink.
Ah. Tried that. It doesn’t help. The integration reloads just fine, and everything happily looks like it’s working. Just as the Bond app does once the problem occurs.
When it’s “broken” everything behaves normally, except no RTS signals are being sent. The Bond behaves like it’s sending them. Updating state in the app and in HA. No shades move. I can open the Bond app, run commands, nothing. But everything acts like it did.
I have to cycle power to the Bond to get anything physically moving. Luckily it’s PoE and I can cycle that port via HA.
(edit: forgot to mention, the integration has been reinstalled a few times as part of my troubleshooting, but since it also exhibits the same problem in the app, it leads me to believe it’s a Bond software issue)
I haven’t abandoned this thread, just been of town for several days and haven’t seen the issue in the recent few days I’ve been back at home. The next time I see the issue occur I’ll reach out to @merck to see if he can grab the logs.
