Error connecting to KNX bus: Invalid argument on pi, works on windows computer

481 views
Skip to first unread message

Martin Tellblom

unread,
Feb 1, 2013, 2:27:05 PM2/1/13
to ope...@googlegroups.com
I have a very strange error. I create the config files on my windows computer and when they work i transfer them to my raspberry pi.
The problem I have now is that the config that works on my windows computer doesn't work om my pi.
 
The windows computer connect to the KNX interface:

Launching the openHAB runtime...
osgi> 20:17:31.735 INFO  o.o.c.internal.CoreActivator[:90] - openHAB runtime has been started (v1.1.0).
20:17:31.079 INFO  o.o.b.o.i.OneWireBinding[:118] - Established connection to OwServer on IP '10.0.0.160' Port '4304'.
20:17:32.450 INFO  o.o.b.k.i.c.KNXConnection[:176] - Established connection to KNX bus on 10.0.0.84:3671 in mode TUNNEL.
 
While when running the exact same config on my pi gives an error:
root@raspberrypi:/opt/openhab# ./start.sh
Launching the openHAB runtime...
osgi> 16:24:37.004 INFO  o.o.c.internal.CoreActivator[:90] - openHAB runtime has been started (v1.1.0).
16:24:55.079 INFO  o.o.b.o.i.OneWireBinding[:118] - Established connection to OwServer on IP '10.0.0.160' Port '4304'.
16:24:56.517 ERROR o.o.b.k.i.c.KNXConnection[:183] - Error connecting to KNX bus: Invalid argument
 
 
I have restarted the pi several times but I still get the same error.
Am I missing a dependency ? What could be wrong?
 
 
 

Victor Belov

unread,
Feb 1, 2013, 2:29:02 PM2/1/13
to ope...@googlegroups.com
Hi,

Do you have local address configured in openhab.cfg ?

Best regards,
Victor Belov

 
 
 

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Thomas Eichstädt-Engelen

unread,
Feb 1, 2013, 2:37:39 PM2/1/13
to ope...@googlegroups.com
yep, that would be my assumption as well.

Victor refers to the config parameter: "knx:localIp" ...

Regards,

Thomas E.-E.

Martin Tellblom

unread,
Feb 1, 2013, 2:47:02 PM2/1/13
to ope...@googlegroups.com
My KNX config looks like this:
 
knx:ip=10.0.0.84
knx:type=TUNNEL
# KNX gateway port (optional, defaults to 3671)
#knx:port=
# Local endpoint to specify the multicast interface, no port is used (optional)
#knx:localIp=
# Serial port of FT1.2 KNX interface (ignored, if ip is specified)
# Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux
#knx:serialPort=
# Pause in milliseconds between two read requests on the KNX bus during
# initialization (optional, defaults to 50)
#knx:pause=
# Timeout in milliseconds to wait for a response from the KNX bus (optional,
# defaults to 10000)
#knx:timeout

# Number of read retries while initialization items from the KNX bus (optional,
# defaults to 3)
#knx:readRetries

 
Should I set  knx:localIp= to something?
 
 
 
 

Thomas Eichstädt-Engelen

unread,
Feb 1, 2013, 2:48:11 PM2/1/13
to ope...@googlegroups.com
yes, please set it to the IP of the openHAB-machine ...


Martin Tellblom

unread,
Feb 1, 2013, 2:59:38 PM2/1/13
to ope...@googlegroups.com

 Still the same error after setting knx:localIp=to openhab server ip

Thomas Eichstädt-Engelen

unread,
Feb 1, 2013, 3:04:53 PM2/1/13
to ope...@googlegroups.com
did you remove the '#' symbol?

On Feb 1, 2013, at 8:59 PM, Martin Tellblom <tell...@gmail.com> wrote:


 Still the same error after setting knx:localIp=to openhab server ip

Martin Tellblom

unread,
Feb 1, 2013, 3:15:20 PM2/1/13
to ope...@googlegroups.com
Yes but I did Another stupid mistake :)  I put the wrong IP :)
It works a lot better now :)  Thanks
 
But why does it work on the windows computer without this set? 

Thomas Eichstädt-Engelen

unread,
Feb 1, 2013, 3:18:58 PM2/1/13
to ope...@googlegroups.com
great :-) 

admittedly i don't really know why ... i assume it has to do with the default ip configuration settings of "localhost", "etc/hosts", etc ...


Reply all
Reply to author
Forward
0 new messages