Hello,
i have a special question about the behavior of the group adress acknowledgement by homelynk/spycelynk/wiser/LM.
When i look to the KNX statistic in Spacelynk (see attached), i can see a lot of repeated telegrams there.
The first idea for the reason in another thread was, that there is a loop created with an other IP router on the KNX bus via LAN.
But the traffic and the repeats are the same, even with deactivated "KNX IP Features" in Spacelynk.
In my opinion these repeats are coming from the TP coupler for all the telegrams he lets into the KNX subline and which do only pass through his filter table because they are needed by Spacelynk.
They are repeated because there is no one else who would send an acknowledgement back to the line coupler, because there is no other recipient on this line but Spacelynk and Spacelynk does not acknowledge these telegrams by default.
So everyone should have this "problem" when there is a Spacelink installed in a mainline or in a subline and there are group telegrams coming into this line via couplers and there filter tables only to get to Spacelynk and no one else in this line. These group telegrams should all be repeated several times by the coupler.
But the question is now, how can it be realised, that Spacelynk does acknowledge a telegram when he is the only receiver for this telegram on the KNX line, so that the coupler has no need to repeat the telegram several times?
There is the option "ACK all group telegrams" in the options for the KNX connection, but this would in my opinion mean, that really all telegrams are acknowledged, even if the have nothing to do with the group adresses used in Spacelynk.
For example, when a switch sends a group telegram to an actuator in the same line, Spacelynk would acknowledge it, only because he receives it, but this acknowledgement should come from the actuator itself.
Maybe it would in the future (next firmware) be possible, to add an option in the objects list for especially these group telegrams, which shall be acknowledged by Spacelynk.
So there could be set a hook or something like that.
But maybe when this is realised, it could be done in this way, so that it could be seen at once when looking at the oojects list.
At the moment there is this option "Read during start-up" in the object settings, but this is really not practicable to check each object, whether the hook is set or not.
It would be much better to see this hook at once, when looking at the objects list itself.
Kind regards
Michael
i have a special question about the behavior of the group adress acknowledgement by homelynk/spycelynk/wiser/LM.
When i look to the KNX statistic in Spacelynk (see attached), i can see a lot of repeated telegrams there.
The first idea for the reason in another thread was, that there is a loop created with an other IP router on the KNX bus via LAN.
But the traffic and the repeats are the same, even with deactivated "KNX IP Features" in Spacelynk.
In my opinion these repeats are coming from the TP coupler for all the telegrams he lets into the KNX subline and which do only pass through his filter table because they are needed by Spacelynk.
They are repeated because there is no one else who would send an acknowledgement back to the line coupler, because there is no other recipient on this line but Spacelynk and Spacelynk does not acknowledge these telegrams by default.
So everyone should have this "problem" when there is a Spacelink installed in a mainline or in a subline and there are group telegrams coming into this line via couplers and there filter tables only to get to Spacelynk and no one else in this line. These group telegrams should all be repeated several times by the coupler.
But the question is now, how can it be realised, that Spacelynk does acknowledge a telegram when he is the only receiver for this telegram on the KNX line, so that the coupler has no need to repeat the telegram several times?
There is the option "ACK all group telegrams" in the options for the KNX connection, but this would in my opinion mean, that really all telegrams are acknowledged, even if the have nothing to do with the group adresses used in Spacelynk.
For example, when a switch sends a group telegram to an actuator in the same line, Spacelynk would acknowledge it, only because he receives it, but this acknowledgement should come from the actuator itself.
Maybe it would in the future (next firmware) be possible, to add an option in the objects list for especially these group telegrams, which shall be acknowledged by Spacelynk.
So there could be set a hook or something like that.
But maybe when this is realised, it could be done in this way, so that it could be seen at once when looking at the oojects list.
At the moment there is this option "Read during start-up" in the object settings, but this is really not practicable to check each object, whether the hook is set or not.
It would be much better to see this hook at once, when looking at the objects list itself.
Kind regards
Michael