Controlling KNX lighting from a third-party touchscreen via HTTP, while preserving KN

[ADEHS]

Hello,
I’m working on a project using a LogicMachine 5 (Lite or KC) as an interface to a KNX-based lighting system.
We plan to control some KNX lighting functions — ON/OFF, dimming, and scenes — from a third-party touchscreen interface (AMX Varia SL50), using HTTP commands sent from a NetLinx controller.
At the same time, the KNX system includes automation logic (e.g., light sensors for daylight-based control), and it is important that this automation remains functional after manual control. For example, if someone turns a light off from the touchscreen, the KNX system should later be able to turn it back on based on sensor input or time schedules.
I’d like to ask:

• Is it technically possible to control the same KNX lighting objects from HTTP commands (NetLinx) without disrupting the existing KNX automation logic?
  
• Are there any best practices or configuration steps in LogicMachine to handle priorities, overrides, or ensure recovery to automatic behavior?
  
• Additionally, we plan to monitor the lighting status via BACnet/IP from a Niagara BMS. Is it possible to expose these KNX objects to BACnet in parallel with HTTP control?
  

This is my first LogicMachine project, so I appreciate any guidance or examples.

[Daniel]

1. Use this: https://kb.logicmachine.net/misc/remote/
2. There is nothing like that in KNX as priority, last telegram wins. You can use script and create priority in it based on date from few objects and write to another.
3. Yes no problem.

[ADEHS]

Thanks again for the help.

I’ll be reviewing the link you shared and looking into how HTTP control can be managed from the NetLinx controller, since I don’t handle that part of the system directly. Once we begin the integration with LogicMachine, I’ll share how it goes or follow up if any questions come up along the way.

[ADEHS]

Sorry for the late reply; the project has only recently been completed.

Regarding the NetLinx controller and the AMX screens, the team ultimately decided to use a KNX IP Router for the lighting integration.

However, for a future phase of the project, we plan to fully integrate the touchscreens through the LogicMachine. This upcoming stage will involve creating lighting scenes and implementing the BACnet integration we discussed.

Thanks again for your help and guidance!

[PedroPinto]

Hello, i'm new in this forum and to avoid creating a new topic i have a couple questions that are almost the same subject of this topic.

I have lets say 4 buildings each one with their own knx installation and each one has an IP Router with their own distinct IP Address. I wish to read some specific group addresses from each IP Router and then export this data into bacnet also to some sort of BMS thats reading this data through that protocol(bacnet), i want to know if this is possible, first approach i'm only interested to read group addresses not locally by TP but by IP. Right now i have Logicmachine Lite (HW: LM5 Lite (i.MX6)
SW: 20240426), IP Router, IP Interface and a couple of actuators as test bench.

[Daniel]

Are those building on the same network/subnet?

[PedroPinto]

Are those building on the same network/subnet?

right now i dont have access to the topology of the network but they should all be on the same local network/subnet

[Daniel]

If they are on the same network then no problem. LM will talk to the routers over KNX multicast. You will need to add objects to filter table for LM to see them and then LM will convert them to bacnet.
https://kb.logicmachine.net/integration/bacnet-server/

[PedroPinto]

If they are on the same network then no problem. LM will talk to the routers over KNX multicast. You will need to add objects to filter table for LM to see them and then LM will convert them to bacnet. 
https://kb.logicmachine.net/integration/bacnet-server/

Thank you for the help, so every ip router from the network has to have the same multicast address that we set up on KNX connection mode IP Routing correct?

[Daniel]

Yes and LM

[PedroPinto]

Hello i finally have 2 ip routers, one on line 1.1, the other on line 1.2, LM its set up at KNX connect mode as IP routing.

Now i guess what i'll ask now its not something related to LM but about ETS.

If i have both ip routers with Routing (IP-KNX) group telegrams set up as "Route", from the LM i can write into the group addresses. These group addresses only have objects from the devices of the same line. If i set up the group telegrams as "Filter" (to avoid KNX telegrams crossing one line to another), it just doesn't work, LM doesnt read (i guess the IP routers are blocking). I have ETS 6.3.0 and i can't manual edit the filter tables of the IP Routers, they are just blank, the only way i can see something on the filter table is if i have a group address with a group object from a device of line 1 and a group object from a device of line 2, that group address gets automatically added to the filter table of both ip routers and then LM can read the state.

[Daniel]

Add a dummy device to main line and link it to groups.

[PedroPinto]

Add a dummy device to main line and link it to groups.

After applying that it worked fine, thank you.

[savaskorkmaz]

A small note: We have a 10-inch touch panel that we have been developing for the past 7 years for this purpose, and it has been used in dozens of projects in our country. This panel displays the visualization and Visu graphics in Logic Machine as a full-screen HMI. There is no browser-based solution here. It runs a dedicated HMI application in kiosk mode.

When the panel is first powered on, a setup wizard welcomes the user. Step by step, the wizard guides through assigning the panel IP address, entering the Logic Machine IP address, username and password, configuring the screensaver settings, and setting up alarm information and related parameters. Once all steps in the wizard are completed, the installation is finished.

After installation, the LM graphics are displayed and controlled in a full-screen experience. Access to the settings page is protected by a dedicated password. If the panel loses and regains power, it automatically reopens the graphics page—there is no need to re-enter login credentials. The panel automatically detects network errors and provides on-screen notifications. It is also possible to exit the screensaver using a password.

This is an industrial-grade IP65 touch panel solution.