You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 10 rf blinds and 9 rf switches. All controlled in 3 separate broadlinks rm. When I try to open or close all blinds (worse if I set them in a specific position since an stop command for each is needed) some blinds won’t respond to the rf command. I can tell that the commands are all being sent because I see the broadlink orange light but I think that because all 3 broadlinks start sending rf commands the blinds go crazy and some respond and others don’t.
Wouldn’t it be possible to add like a delay between commands? Configurable in the config.json?
I know that a possible solution would be to separate the automation in 3 or 4 automation at 7:00, 7:01, 7:02... and so on so to delay the rf commands in between but that’s not a nice solution.
Thanks!
The text was updated successfully, but these errors were encountered:
I can say now that the problem is when sending rf commands from more than 1 broadlink is what is making the mess, the rf commands get jammed up. If I send all the commands through only one it works ok because it sends them one by one
I have 10 rf blinds and 9 rf switches. All controlled in 3 separate broadlinks rm. When I try to open or close all blinds (worse if I set them in a specific position since an stop command for each is needed) some blinds won’t respond to the rf command. I can tell that the commands are all being sent because I see the broadlink orange light but I think that because all 3 broadlinks start sending rf commands the blinds go crazy and some respond and others don’t.
Wouldn’t it be possible to add like a delay between commands? Configurable in the config.json?
I know that a possible solution would be to separate the automation in 3 or 4 automation at 7:00, 7:01, 7:02... and so on so to delay the rf commands in between but that’s not a nice solution.
Thanks!
The text was updated successfully, but these errors were encountered: