I strongly support this feature request. It is clear, does not obscure existing functionalities.
Also in general some more clarification is needed on what happens during startup. I do see some rules are evaluating and firing up - although i have never analyzed the program's behavior in this respect in detail.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I never added this feature because my first idea was that if linknx is stopped and re-started, nothing should happen, and the re-start should not be noticed.
Now experience shows that some internal state of rules can be lost during re-start and it's sometimes needed to re-synchronize it.
But another tricky question is when exactly should this "startup" action be triggered. When system starts? or when connection to EIBD is established? But even then, are we sure that EIBD is already connected to the KNX bus? Or perhaps we should wait until we receive the first telegram from KNX bus? or perhaps not? And do we have also to monitor for "disconnect" from EIBD?
Or another approach could be to "ping" periodically a configurable group address with a KNX read request and let the condition become true when answer is received. And false in case the read request timed-out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I strongly support this feature request. It is clear, does not obscure existing functionalities.
Also in general some more clarification is needed on what happens during startup. I do see some rules are evaluating and firing up - although i have never analyzed the program's behavior in this respect in detail.
I never added this feature because my first idea was that if linknx is stopped and re-started, nothing should happen, and the re-start should not be noticed.
Now experience shows that some internal state of rules can be lost during re-start and it's sometimes needed to re-synchronize it.
But another tricky question is when exactly should this "startup" action be triggered. When system starts? or when connection to EIBD is established? But even then, are we sure that EIBD is already connected to the KNX bus? Or perhaps we should wait until we receive the first telegram from KNX bus? or perhaps not? And do we have also to monitor for "disconnect" from EIBD?
Or another approach could be to "ping" periodically a configurable group address with a KNX read request and let the condition become true when answer is received. And false in case the read request timed-out.