Delaying schedulers to prevent missed telegrams in LM5

[Fahd]

Hi everyone,

I have more than 10 schedulers, and I’ll be adding more. Currently, all of them run at the same time because the client sets the schedule times. This has caused the LM5 to miss some telegrams for the lighting status.

For example, when a schedule runs at 6:00 AM to turn on the lights, the status group address in the LM5 doesn’t update correctly. This issue doesn’t happen when there’s a time difference between the schedulers, but as I mentioned, the client controls the schedule times.

Is there a way to implement a delay between the schedulers so they don’t run simultaneously? I want to avoid asking the client to adjust the schedules manually by adding a few minutes between them.

[Erwin van der Zwart]

Create a virtual address, attach the scheduler to the virtual address and add a script to it with a delay and grp.write to the original address that the scheduler is now attached to..

Something like:

os.sleep(120)
grp.write('1/1/1', event.getvalue())

Set the execution mode of the script to “last instance”

[admin]

We will increase the delay between scheduler events to spread the bus load.

You should check that status telegrams are acknowledged by any device on the bus. Otherwise each status telegram is sent 4 times. This can cause other telegram to be dropped by the sending devices due to bus overload.