Page 1 of 1

Significant delay with Tellstick Live in relaying commands

Posted: Fri Mar 17, 2023 9:45 am
by Nautilus
Hi,

there's a new problem that has immersed a few days ago. It now takes a significant time for Tellstick Live to relay the commands sent via the web interface. And with significant I mean in this case from 5 to 60+ seconds. Situation seemed to improve a bit after power cycling but not nowhere close to normal and now a few minutes later it's more or less the same. Also, I think the reliability of not as good anymore (or maybe this is just that the command takes so long to get delivered, not sure...)

For several weeks it has worked ok and there are no changes in the router, the network or anything. Only change is that I've been testing the XBMC plugin but I doubt that could have any effect on normal usage.

Any hints on troubleshooting this / improving the situation back to normal?

Re: Significant delay with Tellstick Live in relaying comman

Posted: Fri Mar 17, 2023 9:45 am
by Nautilus
At least for now the problem seems to have gone away and the responsiveness is back to normal level. Telldus support had this to say:
Telldus answers: 2012-11-05 - 15:33
Hello,
If this happens only by night, it might be due to high load on our servers. We have been getting some alerts about this, but it's only during a few 1-5 minutes periods, specially around even half ours, when the most schedules are being run. We are working to solve this of course. But after a few minutes there shouldn't be any more delay.

We are also trying to figure out the additional blinks. We first observed this this weekend, and suspect that the high load causes the server to think that the sent command disappeared, since no confirmation was received from TellStick Net for 2 seconds. The response to this is to try to send the command two more times, which of course pushes the load even higher if this is done for every message to all connected clients.
note: "additional blinks" above refer to the number of red blinks on the Tellstick Net after executing a command. There should be only one but also I observed minimum two, sometimes many more.