Customizable delay between actions for multiple entities in a single schedule

[piogas]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.

Proposal

When selecting the "multiple" option and connecting several devices, it would be beneficial to have the ability to add a delay (in milliseconds) between actions.

Use Case:

In my scenario I have four blinds connected via RFLink. When all commands are sent simultaneously, a random number of blinds receive the command, while others do not. Adding a delay of 500-1000ms between each action would resolve this issue by ensuring sequential execution of commands.

[hacscred]

This is not a useful feature request, because you didn't design the feature (e.g. how should the UI or API look like) and on top of that, there are known bugs to the point that arguably this software is not maintained despite many users.

It would be time for additional developers or for a fork.

The original author did do useful work in providing a missing feature for Home Assistant and filling a gap, but there are limits ro a single developer. I am not volunteering, but it's obviously needed.

Please just close it and open a new one that's really well thought out with how the UI should look like on mobile platforms as well.

[tomlut]

@piogas you can ignore hacsred. No one cares what they think and this is probably one of the few remaining repositories they have not been banned from.

[hacscred]

@tomlut People using the word "probably" do not know what they are talking about, so unless you have something to say that you actually know, stop producing noise.

Are you just a bot harassing people? If not, try sharing your real name such that we can all find out how irrelevant you are.

[tomlut]

Oh! You found me out without even asking me how many "r"s are in strawberry.

There's only one person harassing here and it is not me. Your issue is not going to be dealt with any quicker by harassing others to close theirs.

As for real names your parents must have really hated you to call you "hacscred".

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[tomlut]

Not fixed.

[hacscred]

@tomlut There's nothing to be fixed without a plan. Also, the right solution is for whoever that produced those blinds to fail in the marketplace, because obviously they created something that sucks. OP and you are whining at some random dude (Niels) for a feature that shouldn't even exist.

If you want the feature, write a PR. I'd it's not merged, fork, but please just grow up.

[tomlut]

Thanks for continuing to help prevent this from going stale.

[nielsfaber]

In my opinion it is the issue described here is caused by RFLink, it should internally implement some queuing in case multiple commands have to be sent quickly.
I don’t feel much for adding some text field in scheduler card to enter time delay between actions.
Adding this would only increase complexity, most users don’t want to have to define this and also won’t need this for proper operation of the scheduler.
Perhaps I can implement some fixed delay on the backend side instead. This delay would then always be applied in case scheduler has to do multiple tasks at once.
The delay time can be made configurable in the integration settings.
@piogas Would this be an OK solution for you?

[hacscred]

Adding such a delay would only hide broken systems and IoT is broken enough as it is. Also, it means that systems made by competent vendors would use more power only to help their broken competitors.

If a protocol were to implement some kind of broadcast feature, adding the delay would turn an efficient system by default into potentially a broken system at scale.

I can understand the urge to help a random user, but all you are doing is making software you already can't maintain even harder to maintain.

[tomlut]

The other option is to schedule running of a script instead of all the blinds. The script can easily implement a delay between sending the commands to each blind.

[piogas]

@nielsfaber It's definitely a problem with RFLink, and only a delay can help in this kind of case. I can imagine that some other devices might have the same problem when someone adds multiple devices to the schedule.

Right now, I've made a workaround - I prepared a script with delays that is triggered by this component, and it works fine. If you feel that the proposed feature would make this project more complicated, please feel free to close it.

Your proposal would be great for this case, as it would help keep the schedule configuration in one place.

So, from my point of view, this could help with RFLink or other components facing the same problem as mine.