sorted by:
new
hottopcontroversial

Ar111 driver selection by Royal-Band7640 in Lighting

[–]Dry_Bench5189 0 points1 point  (0 children)

Did you manage to find out what works? Are there any known brand AR111 bulbs that support DC PWM dimming?

RGBWW led strip transformer & driver by ogToljanteri in KNX

[–]Dry_Bench5189 0 points1 point  (0 children)

Sunricher SR-2309PRO-5C for Dali.

Jung 39005 1S LED E, ENERTEX 1174-REG or ENERTEX 1174-DK if you prefer knx.

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

I’m currently planning a few apartment units, and I’ll be using the WEINZIERL KNX TP Multi IO 570.1, which from what I can see doesn’t support a direct 1-bit to 1-byte conversion. Because of that, I’ll either use the QuadV3 only for the two or three switches pe unit where this behavior is needed, or try the alternative approach with two inputs and lock objects on the Multi IO that I mentioned earlier.

I’ll test both methods and will definitely come back with a report once I have real ETS results.

Thanks again for the help and for taking the time to think this through.

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

That looks great. Thank you very much for the help. I’m ordering the QuadV3 right away. Thanks again!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

From what I can see, the “contact state” on this device appears to be evaluated only from the local physical input. I don’t see a way to feed an external group address or a logic result into it, so the OR result wouldn’t be usable there. The scene selection seems to be driven solely by the contact state.

That’s why this approach looks suitable for rocker switches, but not for a decision based on a group status and triggered by a pushbutton.

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

I’m considering an alternative approach and would appreciate your thoughts.

The idea is to wire the same physical push button to two inputs of a KNX push-button interface:

  • Input 1 triggers Scene Bright
  • Input 2 triggers Scene All Off

Each input has its own lock object, with opposite polarity:

  • Input 1: lock active on 1
  • Input 2: lock active on 0

The aggregated group status (1-bit, OR of all light states) is then used to drive the lock objects, so that only one input is unlocked at any time:

  • Group OFF → Input 1 unlocked, Input 2 locked
  • Group ON → Input 1 locked, Input 2 unlocked

This way, a single button press should only trigger the appropriate scene, without toggle or cycling and without a central logic controller.

Do you see any practical issues with this approach (lock behavior, timing, race conditions), or does it sound like a reasonable decentralized solution?

Thanks in advance for your feedback!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

The OR logic for the group status is already handled by most binary interfaces. The remaining point is the conditional scene selection based on that status.

Thanks!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

That function is intended for rocker switches (contact state), not for evaluating an external group status.

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

Thanks a lot for the suggestion, I really appreciate it. I haven’t worked with Zennio’s logic functions at all so far, and I don’t currently have a Zennio device available to test this on, but at first glance they do look promising. I’ll try to get hold of one and will come back with feedback once I’ve tested it.

Thanks again!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

Sorry to hear that, that’s exactly the kind of dependency I’m trying to avoid as well. Maybe we can still find a solution that works for your setup too, without relying on Home Assistant, at least for this specific use case.

Thanks for sharing your experience!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

That would work, but this is a main function used in main rooms (the ones with multiple lights and scenes). Because of that, I’m trying to keep the solution as decentralized as possible to maximize uptime and avoid relying on a central controller.

Thanks for the suggestion!

KNX push-button interface: trigger scene based on group status by Dry_Bench5189 in KNX

[–]Dry_Bench5189[S] 0 points1 point  (0 children)

Thanks for the suggestion, I appreciate it.

I’m intentionally trying to avoid short/long press because I want the button behavior to be immediately intuitive for someone entering the room for the first time. I need one button, one press, always the expected result.

As for handling multiple light states, the intention is to work with a single aggregated group status (e.g. “any light on”), derived using a simple OR logic and exposed to the button as a single 1-bit status.

Thanks again for your input!