So i have some automations where i usa a xiaomi socket to give out exactly timed signals for my Siemense Logo controller. The idea is that i can use one input for different tasks. I used this with xiaomi smart home application and it worked perfectly. Now i use it with Rasspberry pi 3+ and hassbian and the delay time isn´t always the same. Sometimes it triggers and the other time it does not. With mi home i used 1s signals. Socket turns on and after 1 second it turns off. Worked without problems. Now if i insert 1000 milliseconds delay then i will get something completely different. I have to set the delay to about 700 milliseconds and then it almost always works but still sometimes it does not. Is this a bug or am i doing something wrong?
I think only increments of 1 second are fully supported.
Anything below 1 second will just be triggered when the next second rolls around from my experience.
Current resolution of HA’s timer is 1 second, and under some circumstances, it may missed one or more tick depends on your system’s load and maybe some bad component.
See the architect discussion on this topic.
This is intresting because if i change the delay from 1s to 700milliseconds it works better.
Thanks for the answers. I increased the time window and now it works but do i understand it correctly that if i use one second then it can be more than one second but not less?
Yes, the resolution is currently 1s meaning that timers can be up to one second late.
Thanks for the reply.