KNX - cant turn switch on or off

Dim · May 31, 2017, 5:46pm

Check this out:

There is a lot of info in that thread related to this topic.

ilikiler · May 31, 2017, 6:23pm

Hi Dim,

Pysical adress is the same as individual adress?
if yes i changed it too 1.0.4. I couldn’t set it to 1.0.0.

I’m still reading the other thread about a dummy application

Dim · June 1, 2017, 12:49am

Yes. PA = IA (they are used as synonyms in KNX literature)

To change it to x.y.0 you will need to change your Backbone Line medium from TP to IP.
There is some info about this in the thread above.

ilikiler · June 8, 2017, 3:43pm

HI,
thanks for all the help.

So i changed some settings and got it working. Then something happend and i wasn’t able to open the webinterface of openhab.

So after 2days of figuring it out, i decided to start over.

So after setting evrything back up.
I was able to turn the light on and off.

My configuration.

-----------------------services\knx.cfg----------------------------------

KNX gateway IP address

(optional, if serialPort or connection type ‘ROUTER’ is specified)

ip=192.168.0.112

Local KNX Binding bus address.

Use it, when two or more openHAB Instances are connected to the same KNX bus.

(optional, defaults to 0.0.0)

#busaddr=

Ignore local KNX Events, prevents internal events coming from

‘openHAB event bus’ a second time to be sent back to the ‘openHAB event bus’.

Note: To send back events second time is a Bug, but for backward compatibility, the behavior is not changed.

For new installations, its recommend to set “ignorelocalevents=true”

(optional, defaults to false)

ignorelocalevents=true

KNX IP connection type. Could be either TUNNEL or ROUTER (optional, defaults to TUNNEL)

Note: If you cannot get the ROUTER mode working (even if it claims it is connected),

use TUNNEL mode instead with setting both the ip of the KNX gateway and the localIp.

type=TUNNEL

KNX gateway port (optional, defaults to 3671)

Note: If you use eibd, setting to 6720

port=3671

Local endpoint to specify the multicast interface, no port is used (optional)

localIp=192.168.0.132

-------------------items\encora.items----------------------------------
Switch lamp_vier “lamp 4” {knx=“0/0/4+0/0/14”}

Switch Dimmer_LEEN “dimmer lamp” {knx=“0/0/1”}

Dimmer Dimmer_een “Dimmer [%s]” {knx=“0/0/1, 0/1/0, 0/0/11”}

-----------------------sitemap\encora.sitemap---------------------
sitemap encora label=“lampVier”
{
Frame
{
Switch item=lamp_vier icon=“light” mappings=[OFF=“uit”, ON=“aan”]
Switch item=Dimmer_LEEN icon=“light” mappings=[OFF=“uit”, ON=“aan”]
}
Frame
{
Switch item=Dimmer_een label"lamp2 [%d %%]" mappings[INCREASE=“hoger”, DECREASE=“lager”]
Slider item=Dimmer_een label=“lamp [%d %%]”
}

The issues i have.
Issue 1: When i togle the switch it is sometimes slow.
Toggle on takes sometimes up to 5sec to turn on or off.
Also when the light is on and i refresh the page it doesnt show the correct state.
Issue 2: The dimmer works so on/off works and decrease and increase works.
But i can’t enter an 8 bit value trough the slider.
Am i doing something wrong?

I want to thank everyone for helping me.

Greetings

ilikiler · June 8, 2017, 5:48pm

Hi,

The dimmer does work now. But it is slow in response.

greetings,

Dim · June 8, 2017, 6:37pm

It sounds to me that something is not optimized in your KNX installation side…
Since OH2 can connect with mode=TUNNEL and can control the endpoints, you may be experiencing delays due to some kind of KNX Bus issues. I can’t pin point the issue but it’s worth to try to analyze the telegram traffic using Bus Monitor with ETS.

Ugo_Perillo · January 18, 2019, 3:41pm

Hello,
Thank you for the support,

please can you help with configuration?

I have a Gira 2167, configured in ETS with the address 1.1.0
these are the info:

Device Info of Device 1.1.0

General

Item	Value	Resource name	Unformatted value
Mask Version	091A		2330
Serial Number	0008:128104A5	DeviceSerialNumber	0008128104A5
Programming Mode	Off	ProgrammingMode	false
Max. APDU Length	220	MaxApduLength	220

IP

Item	Value	Unformatted value
Name	KNX/IP router	KNX/IP router
MAC Address	00-0A-B3-27-5C-07	000AB3275C07
IP Address	192.168.1.103	C0A80167
Subnet Mask	255.255.255.0	FFFFFF00
Default Gateway	192.168.1.1	C0A80101
Additional Addresses	1.1.15 1.1.16 1.1.17 1.1.18	4367 4368 4369 4370
Routing Multicast Address	224.0.23.12	E000170C

Line Coupler

Item	Value	Resource name	Unformatted value
Main > Sub Configuration	Indiv. adressed: transmit always

The application is on address 1.1.105
these are the info:

Device Info of Device 1.1.105

General

Item	Value	Resource name	Unformatted value
Mask Version	07B0		1968
Individual Address	1.1.105	IndividualAddress	4457
Device Manufacturer	GIRA Giersiepen	DeviceManufacturerId	8
Order Number	$00000000000000000000	DeviceOrderId	00000000000000000000
Serial Number	0008:128104A6	DeviceSerialNumber	0008128104A6
Firmware Version	[0] 0.1	FirmwareVersion	1
Bus Voltage	30,0V (±0.5V)	DeviceBusVoltage	30
Programming Mode	Off	ProgrammingMode	false

Application Program

Item	Value	Resource name	Unformatted value
Application program	GIRA Giersiepen Applicazioni router V3.5 V3.5	ApplicationId	0008901A35
Load State	Loaded	ApplicationLoadStatus	1
Run State	Running	ApplicationRunStatus	1

Application Program 2

Item	Value	Resource name	Unformatted value
Application program	0 0000 V0.0	PeiprogId	0000000000
Load State	Loaded	PeiprogLoadStatus	1
Run State	Running	PeiprogRunStatus	1

Group Communication

Item	Value	Resource name	Unformatted value
Address Table Load State	Loaded	GroupAddressTableLoadStatus	1
Association Table Load State	Loaded	GroupAssociationTableLoadStatus	1
Group Object Table Load State	Loaded	GroupObjectTableLoadStatus	1

these are the ETS devices

1.1.0 Quadro Principale KNX/IP router V3.5 X X X X X GIRA Giersiepen 2167 00 KNX/IP router
1.1.1 Quadro Principale Camino/Caldai… Switch actuator,4 fold,universal X - X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.2 Quadro Principale Schalten, Treppenlicht 4f X X X X X MDT technologies AKS-0410.01 AKS-0410.01 Schaltaktor 4-fach, 4TE, 1…
1.1.3 Quadro Principale Switch actuator,4 fold,universal X X X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.4 Quadro Principale Switch actuator,4 fold,universal X X X X X Video-Star 1A10xxA01R Switch actuator, 4 fold, universal
1.1.5 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.6 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.7 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.8 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.9 Quadro Principale Dimmer 4 fold X X X X X Video-Star 1A04XXB03D KA/D 04.xx.1 4 fold dimmer
1.1.10 Quadro Principale Universal Interfaces, 4 fold X X - X X Video-Star 1M10xxC01K Universal Interfaces, 4 fold
1.1.11 Quadro Principale Logik, Zeitglied, Temperaturvergleich X - X X X MDT technologies SCN-LOG1.01 SCN-LOG1.01 Logikmodul, 2TE
1.1.12 Quadro Principale Riscaldamento Switch PWM 2067/0.1 X - - - X Schneider Electric Industries SAS MTN645129 Heizungsaktor REG-K/6x230/0,05A
1.1.13 Quadro Principale Tapparelle Jalousie, Rollade 8f 10 A X X X X X MDT technologies JAL-0810.01 JAL-0810.01 Jalousieaktor 8-fach, 8TE, …
1.1.14 Quadro Principale Tende Jalousie, Rollade 8f 10 A X X X X X MDT technologies JAL-0810.01 JAL-0810.01 Jalousieaktor 8-fach, 8TE, …
1.1.105 Quadro Principale Applicazioni router V3.5 X X X X X GIRA Giersiepen 2167 00 KNX/IP router
1.1.250 Quadro Principale iKnix ETS KNiX Port Gateway X X X X X iKNiX KNiX Port Gateway KNiX Port Gateway

PAPERUI Things configuration:

Configuration Parameters

Configure parameters for the thing.

IP Connection Type

Router

The ip connection type for connecting to the KNX bus. Could be either TUNNEL or ROUTER

()

Network Address

Network address of the KNX/IP gateway

Port

Port number of the KNX/IP gateway

Local Network Address

Network address of the local host to be used to set up the connection to the KNX/IP gateway

Local Device Address

The Physical Address (Individual Address) in x.y.z notation for identification of this KNX/IP gateway within the KNX bus

Use NAT

Set to “true” when having network address translation between this server and the gateway

Reading Pause

Time in milliseconds of how long should be paused between two read requests to the bus during initialization

Response Timeout

Seconds to wait for a response from the KNX bus

Read Retries Limit

Limits the read retries while initialization from the KNX bus

Auto Reconnect Period

Seconds between connection retries when KNX link has been lost, 0 means never retr

I connect the interface in ROUTER mode, it says ONLINE, and in the LOG i can see this:
2019-01-18 16:30:38.835 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.107’ to ‘2/2/2’ with value ‘[1]’

2019-01-18 16:30:39.558 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is disconnecting from the KNX bus

2019-01-18 16:30:39.614 [DEBUG] [nx.internal.client.AbstractKNXClient] - The KNX network link was detached from the process communicator

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:39.668 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from ONLINE to OFFLINE

2019-01-18 16:30:39.704 [me.event.ThingUpdatedEvent] - Thing ‘knx:ip:08beb4b1’ has been updated.

2019-01-18 16:30:39.713 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from OFFLINE to OFFLINE (CONFIGURATION_ERROR): The ‘ipAddress’ of the gateway must be configured in ‘TUNNEL’ mode

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:48.847 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is disconnecting from the KNX bus

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:48.836 [me.event.ThingUpdatedEvent] - Thing ‘knx:ip:08beb4b1’ has been updated.

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:48.868 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is connecting to the KNX bus

2019-01-18 16:30:48.871 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.

==> /var/log/openhab2/events.log <==

2019-01-18 16:30:48.877 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from OFFLINE (CONFIGURATION_ERROR): The ‘ipAddress’ of the gateway must be configured in ‘TUNNEL’ mode to UNKNOWN

2019-01-18 16:30:48.912 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from UNKNOWN to ONLINE

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:30:49.744 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.108’ to ‘2/0/5’ with value ‘[12, 41]’

2019-01-18 16:30:49.763 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.108’ to ‘2/2/3’ with value ‘[0]’

2019-01-18 16:30:51.586 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/0/6’ with value ‘[7, -38]’

2019-01-18 16:30:51.606 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/2/4’ with value ‘[0]’

2019-01-18 16:30:53.282 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.115’ to ‘3/1/7’ with value ‘[1]’

2019-01-18 16:30:56.586 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.47’ to ‘3/1/6’ with value ‘[1]’

So i assume that the connection is weel done, i read the knx bus broadcast telegram

BUT…
i can’t turn switch on or off…

ITEMS:
[16:38:37] openhabian@openHABianPi:/etc/openhab2/items$ cat knx.items
Switch BComSpecchio “Luce Specchio” [ “Lighting” ] { knx=“0/0/23+0/1/23” }
Switch BPadSpecchio “Luce Specchio Padronale” [ “Lighting” ] { knx=“0/0/30+0/1/30” }
Switch PadTestaSx “Testaletto sx” [ “Lighting” ] { knx=“0/0/25+0/1/25” }
Switch PadTestaDx “Testaletto dx” [ “Lighting” ] { knx=“0/0/26+0/1/26” }

SERVICES:
[16:40:54] openhabian@openHABianPi:/etc/openhab2/services$ cat knx.cfg
type=ROUTER
[16:41:00] openhabian@openHABianPi:/etc/openhab2/services$

Please, can you HELP?

Ugo_Perillo · January 18, 2019, 3:49pm

some more logging:

2019-01-18 16:44:43.899 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to ‘Europe/Rome’.

2019-01-18 16:44:43.951 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to ‘40.6643757208513,14.806257176866714’.

2019-01-18 16:44:43.963 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to ‘it_IT’.

2019-01-18 16:44:44.309 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel

2019-01-18 16:44:44.815 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder

2019-01-18 16:44:59.965 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘knx.items’

2019-01-18 16:45:09.286 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007

2019-01-18 16:45:12.817 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘KNX.things’

2019-01-18 16:45:12.829 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘KNX.things’ is either empty or cannot be parsed correctly!

2019-01-18 16:45:14.173 [WARN ] [e.jetty.util.thread.ThreadPoolBudget] - Low configured threads: (max=8 - required=1)=7 < warnAt=8 for QueuedThreadPool[ServletModel-15]@d3ed2c{STARTING,8<=0<=8,i=0,q=0}[ReservedThreadExecutor@284ed9{s=0/1,p=0}]

2019-01-18 16:45:14.905 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.1.113:8080

2019-01-18 16:45:14.913 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.1.113:8443

==> /var/log/openhab2/events.log <==

2019-01-18 16:45:15.729 [hingStatusInfoChangedEvent] - ‘hue:bridge:0017880ae670’ changed from UNINITIALIZED to INITIALIZING

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:45:16.648 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui

2019-01-18 16:45:17.685 [DEBUG] [org.openhab.binding.knx ] - BundleEvent STARTING - org.openhab.binding.knx

2019-01-18 16:45:17.693 [DEBUG] [org.openhab.binding.knx ] - BundleEvent STARTED - org.openhab.binding.knx

2019-01-18 16:45:17.783 [DEBUG] [org.openhab.binding.knx ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.profiles.ProfileAdvisor}={service.id=361, service.bundleid=206, service.scope=bundle, component.name=org.openhab.binding.knx.internal.profiles.KNXProfileAdvisor, component.id=217} - org.openhab.binding.knx

2019-01-18 16:45:17.856 [DEBUG] [org.openhab.binding.knx ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=362, service.bundleid=206, service.scope=bundle, component.name=org.openhab.binding.knx.internal.factory.KNXHandlerFactory, component.id=218} - org.openhab.binding.knx

==> /var/log/openhab2/events.log <==

2019-01-18 16:45:18.088 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from UNINITIALIZED to INITIALIZING

2019-01-18 16:45:18.192 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from INITIALIZING to UNKNOWN

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:45:18.439 [DEBUG] [org.openhab.binding.knx ] - ServiceEvent REGISTERED - {org.openhab.binding.knx.KNXTypeMapper}={service.id=363, service.bundleid=206, service.scope=bundle, component.name=org.openhab.binding.knx.internal.dpt.KNXCoreTypeMapper, component.id=219} - org.openhab.binding.knx

2019-01-18 16:45:18.692 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is disconnecting from the KNX bus

2019-01-18 16:45:18.766 [DEBUG] [nx.internal.client.AbstractKNXClient] - Bridge knx:ip:08beb4b1 is connecting to the KNX bus

2019-01-18 16:45:18.770 [DEBUG] [binding.knx.internal.client.IPClient] - Establishing connection to KNX bus on 224.0.23.12:3671 in mode ROUTER.

==> /var/log/openhab2/events.log <==

2019-01-18 16:45:19.027 [hingStatusInfoChangedEvent] - ‘hue:bridge:0017880ae670’ changed from INITIALIZING to OFFLINE: Hue bridge connection lost.

2019-01-18 16:45:19.467 [hingStatusInfoChangedEvent] - ‘knx:ip:08beb4b1’ changed from UNKNOWN to ONLINE

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:45:19.993 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.108’ to ‘2/0/5’ with value ‘[12, 36]’

2019-01-18 16:45:20.304 [INFO ] [eemulation.internal.ConfigManagement] - Hue Emulation pairing disabled. Service available under /api

2019-01-18 16:45:21.570 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/0/6’ with value ‘[7, -38]’

2019-01-18 16:45:26.377 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.10’ to ‘2/2/39’ with value ‘[0]’

2019-01-18 16:45:27.184 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.111’ to ‘2/0/2’ with value ‘[12, -115]’

2019-01-18 16:47:21.567 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.109’ to ‘2/0/6’ with value ‘[7, -38]’

==> /var/log/openhab2/events.log <==

2019-01-18 16:47:23.418 [ome.event.ItemCommandEvent] - Item ‘PadTestaDx’ received command ON

2019-01-18 16:47:23.501 [vent.ItemStateChangedEvent] - PadTestaDx changed from NULL to ON

2019-01-18 16:47:24.857 [ome.event.ItemCommandEvent] - Item ‘PadTestaDx’ received command OFF

2019-01-18 16:47:24.880 [vent.ItemStateChangedEvent] - PadTestaDx changed from ON to OFF

==> /var/log/openhab2/openhab.log <==

2019-01-18 16:47:27.181 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.46’ to ‘2/0/8’ with value ‘[18, 13]’

2019-01-18 16:47:27.204 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.111’ to ‘2/0/2’ with value ‘[12, -125]’

2019-01-18 16:47:27.225 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.111’ to ‘2/2/6’ with value ‘[0]’

2019-01-18 16:47:31.484 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.113’ to ‘2/0/1’ with value ‘[12, 66]’

2019-01-18 16:47:34.909 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from ‘1.1.110’ to ‘2/2/5’ with value ‘[0]’