"All Off" group adress truning lights off when status request

[Goaheadz]

I agree with you. Server does not have that group address configured.
I suspect that , server asks for actuator status, but since it also belongs to several group address, it will report all group address status, and that's the problem.

Bu well..like I said above, its now working, even though a dont understand why!

[meti]

The server shouldn't ask for it in the first place. See discord on how to find out why it does.

For "sending" see https://support.knx.org/hc/en-us/art...-Group-Address

Note that without the "update" flag, the channels won't react to their primary (when the "all-off"-GA is secondary) GAs GroupValueResponse telegrams either.

[Goaheadz]

The status of this address is not important, as long as if the server asks for it, it will not turn off all ligths inside group address

[Goaheadz]

Hi everyone.

A lot of good information you shared here. thank you all for help so far.

Not perfect yet, but I was able to play with flags, and now when I read 4/0/0 I get no response, so lights stay the same state. perfect, and off course, if i press push button 2 all lights go OFF.
So I guess this is working, just dont know if all flags are ok.

Another thing I dont understand is the "Sending flag". Is present in the push button and first channel of 0.0.1 device.
What is the propose of that flag? I do have some buttons with LEDs. Is this related? Should I remove them?

Capture_knx1.PNG

Capture_knx2.png

[mumpf]

Hi,

technically you can solve this by removing the Update-Flag from your GroupObjects, which are affected.

Semantically, you wrongly implemented your "All OFF" Status. You cannot simply connect a GroupAddress to all GroupObjects returning an On/Off-Status assuming, this is a unique Status for all affected GroupObjects. If you want to have a Status "All OFF", you have to combine all affected Group-Objects by a logical OR. The result of this OR would be the "All OFF" status: 0=all off, 1=any on.

The initially mentioned technical solution will solve, that all lights switch off in case you do a GroupValueRead, but will not return a correct status.

Regards,
Waldemar

[meti]

Just to avoid translation issues: what the previous answers meant by "KO" and "GO" are group objects.

I wouldn't think it's a wrong update flag, but a wrong read flag. A common group address switching multiple devices should imho be stateless. It shouldn't be read by other devices, and it definitely shouldn't answer to a read request.

[HubertUnterfranken]

Propably a problem with the update flag of your GOs. You can search the ETS help for Flags and take a look at the description of the Update flag.

GO = Group Object
GA = Group Address

[gbglace]

wrong connections KO and GA and perhaps wrong flags at KO.

please post a Screenshot with all connected KO but not from the GA tree.

[Goaheadz]

If I read individual address of each ligth status is ok and they keep state.
If I read "All OFF" address (status of all entities are reported, some off others on) but imediatly after they all go off.

need help

[Goaheadz]

Sorry no German speaker

I am having trouble with a group address that contains several switch actuators and one buttom switch.
Everything works fine when I press the buttom sending only Off command to this group address and all lights go off.

The problem is that now I connected the instalation to a server that requests staus of all actuators (I dont ask status for this one), but I can see in ETS monitor, that this address is queried, and all lights go OFF.

The same is valid in ETS group monitor. If I request status of that address, all participants respond to the status call (some on others off), but after that, all lights go immediately off.
Probably the buttom is reporting OFF?

Can you point me to right direction on how to solve a status request of several actuators?

Kind regards
Goahead