Hi Guy’s,
i have a littel issue with the homematic binding
i use homegear and openhab2 on a PI3 and it just worked fine until the last weekend.
I tired to expand homegear with a UBS300 for EnOcean and i followed this guide.
after i had setup the homegear gateway function the connection between openhab and homegear break down.
In the PaperUI the config just say “INITIALIZING”.
i just tried to find help in the homegear forum, but so far this has not helped.
In this post you find longer logs.
Here are mein Logs and configs
OpenHab2 Log direct after boot:
2018-04-22 12:40:24.968 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway 'My-SCC' not available, disabling support
2018-04-22 12:40:24.973 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway 'My-SCC' not available, disabling support
2018-04-22 12:40:24.978 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway 'My-SCC' not available, disabling support
2018-04-22 12:40:24.983 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'GROUP' on gateway 'My-SCC' not available, disabling support
2018-04-22 12:40:25.038 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=HOMEGEAR,type=Homegear,firmware=0.7.15-1580,address=VBC7766938,wired=false,hmip=false,cuxd=false,group=false]
2018-04-22 12:40:25.067 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception
java.lang.IncompatibleClassChangeError: Expected static field org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.scheduler
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.loadDevices(HomematicDeviceDiscoveryService.java:98) ~[?:?]
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.startScan(HomematicDeviceDiscoveryService.java:62) ~[?:?]
at org.eclipse.smarthome.config.discovery.AbstractDiscoveryService.startScan(AbstractDiscoveryService.java:208) ~[?:?]
at org.openhab.binding.homematic.handler.HomematicBridgeHandler.lambda$0(HomematicBridgeHandler.java:77) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
This is posted in the openhab log if i start searching things:
2018-04-22 12:41:02.665 [WARN ] [eclipse.jetty.servlet.ServletHandler] -
javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.IncompatibleClassChangeError: Expected static field org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.scheduler
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489) [171:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [171:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [171:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [171:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [171:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [15:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [86:org.eclipse.jetty.servlet:9.3.21.v20170918]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [86:org.eclipse.jetty.servlet:9.3.21.v20170918]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [187:org.ops4j.pax.web.pax-web-jetty:6.0.9]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [85:org.eclipse.jetty.server:9.3.21.v20170918]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [83:org.eclipse.jetty.security:9.3.21.v20170918]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [85:org.eclipse.jetty.server:9.3.21.v20170918]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [85:org.eclipse.jetty.server:9.3.21.v20170918]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [187:org.ops4j.pax.web.pax-web-jetty:6.0.9]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [86:org.eclipse.jetty.servlet:9.3.21.v20170918]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [85:org.eclipse.jetty.server:9.3.21.v20170918]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [85:org.eclipse.jetty.server:9.3.21.v20170918]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [85:org.eclipse.jetty.server:9.3.21.v20170918]
Homegear log
04/22/18 12:20:07.498 Starting Homegear...
04/22/18 12:20:07.499 Homegear version 0.7.15-1580
04/22/18 12:20:07.499 Git commit SHA of libhomegear-base: -
04/22/18 12:20:07.499 Git branch of libhomegear-base: -
04/22/18 12:20:07.499 Git commit SHA of Homegear: -
04/22/18 12:20:07.499 Git branch of Homegear: -
04/22/18 12:20:07.500 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
04/22/18 12:20:07.500 Info: Core file size now is "4294967295".
04/22/18 12:20:07.500 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
04/22/18 12:20:07.500 Info: Maximum thread priority now is "4294967295".
04/22/18 12:20:07.503 Warning: No database found. Trying to restore backup.
04/22/18 12:20:07.763 Warning: Database could not be restored. Creating new database.
04/22/18 12:20:07.805 Initializing database...
04/22/18 12:20:08.103 Info: Loading family module mod_miscellaneous.so
04/22/18 12:20:08.106 /etc/homegear/families/miscellaneous.conf
04/22/18 12:20:08.107 Info: Loading family module mod_homematicbidcos.so
04/22/18 12:20:08.118 /etc/homegear/families/homematicbidcos.conf
04/22/18 12:20:08.120 Info: Setting up physical interfaces and GPIOs...
04/22/18 12:20:08.122 Info: Dropping privileges to user homegear (110) and group homegear (116)
04/22/18 12:20:08.123 Info: Homegear is (now) running as user with id 110 and group with id 116.
04/22/18 12:20:08.129 Starting script engine server...
04/22/18 12:20:08.137 Initializing licensing controller...
04/22/18 12:20:08.137 Loading licensing controller data...
04/22/18 12:20:08.137 Loading devices...
04/22/18 12:20:08.137 Loading XML RPC devices...
04/22/18 12:20:09.308 Module HomeMatic BidCoS: Created HomeMatic BidCoS central with id 0, address 0xFDFA4E and serial number VBC7766938
04/22/18 12:20:09.320 Loading XML RPC devices...
04/22/18 12:20:09.331 Module Miscellaneous: Created Miscellaneous central with id 0.
04/22/18 12:20:09.337 Initializing RPC client...
04/22/18 12:20:09.337 Starting XML RPC server RPCServer1 listening on :::2001...
04/22/18 12:20:09.340 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
04/22/18 12:20:09.340 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
04/22/18 12:20:09.373 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
04/22/18 12:20:09.373 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
04/22/18 12:20:09.407 Starting CLI server...
04/22/18 12:20:09.407 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
04/22/18 12:20:09.408 Initializing event handler...
04/22/18 12:20:09.410 Loading events...
04/22/18 12:20:09.411 Starting flows server...
04/22/18 12:20:09.417 Starting IPC server...
04/22/18 12:20:09.422 Start listening for packets...
04/22/18 12:20:13.423 Startup complete. Waiting for physical interfaces to connect.
04/22/18 12:20:13.423 All physical interfaces are connected now.
04/22/18 12:20:13.423 Starting UPnP server...
04/22/18 12:20:13.425 Info: Created new UPnP UDN: B4620FED-1129-E075-B368-F97F24A4084F
04/22/18 12:20:13.425 Info: UPnP server: Binding to address: 192.168.1.190
04/22/18 12:20:13.425 UPnP Server: Info: Started listening.
04/22/18 12:20:13.755 HomeMatic BidCoS packet received (My-SCC, RSSI: -48 dBm): 0C0A865A3F810E000000A90728
04/22/18 12:20:18.113 HomeMatic BidCoS packet received (My-SCC, RSSI: -81 dBm): 0974A03F417D22FDCC20
04/22/18 12:20:26.335 HomeMatic BidCoS packet received (My-SCC, RSSI: -47 dBm): 0FF2861046B85B0000000A24F88C0040
04/22/18 12:20:33.113 HomeMatic BidCoS packet received (My-SCC, RSSI: -82 dBm): 0975A03F417D22FDCC20
04/22/18 12:20:33.243 HomeMatic BidCoS packet received (My-SCC, RSSI: -82 dBm): 0C56865A417D22000000B8F328
04/22/18 12:20:33.755 HomeMatic BidCoS packet received (My-SCC, RSSI: -52 dBm): 0C0A84703F810E000000010728
04/22/18 12:20:35.552 Info: CLI connection accepted. Client number: 18
04/22/18 12:20:45.307 HomeMatic BidCoS packet received (My-SCC, RSSI: -55 dBm): 1A0184003F810E0000001300AD4D4551313537323034385803FFFF
04/22/18 12:20:45.309 Module HomeMatic BidCoS: Info: Pushing pending queues.
04/22/18 12:20:45.401 Module HomeMatic BidCoS: COC "My-SCC": Info: Sending (My-SCC): 1001A001FDFA4E3F810E00050000000000
04/22/18 12:20:45.573 HomeMatic BidCoS packet received (My-SCC, RSSI: -55 dBm): 0A0180023F810EFDFA4E00
04/22/18 12:20:45.667 Module HomeMatic BidCoS: COC "My-SCC": Info: Sending (My-SCC):
homegear-gateway log
04/22/18 12:34:36.971 Starting Homegear Gateway...
04/22/18 12:34:36.972 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
04/22/18 12:34:36.972 Info: Core file size now is "4294967295".
04/22/18 12:34:36.973 Info: Dropping privileges to user homegear (110) and group homegear (116)
04/22/18 12:34:36.973 Info: Homegear Gateway is (now) running as user with id 110 and group with id 116.
04/22/18 12:34:38.040 Startup complete.
04/22/18 12:34:48.125 Warning: Too short packet received: 0F72DC0D
04/22/18 12:34:51.255 Warning: Too short packet received: ACC6A1D000088D
homematicbidcos-config
___________________________________________________________________________
---------------------------- HomeMatic BidCoS ----------------------------
___________________________________________________________________________
#######################################
########## General Settings ##########
#######################################
[General]
## The BidCoS address of Homegear. It is recommended to change this to a random 3 byte hexadecimal
## value starting with 0xFD (e. g. 0xFD43AB). Only change this, when no HomeMatic BidCoS devices
## are paired to Homegear as existing pairings will not work anymore!
#centralAddress = 0xFD0001
## Specify a 16 byte (32 characters) long AES key here to protect your wireless communication
## !!! IMPORTANT: It is highly recommended to change this key before pairing the first device.
## !!! IMPORTANT: Never ever lose this key. That would render your devices useless.
## To remove the key from your devices, you need to factory reset them using Homegear. The factory
## reset on the device is not possible!!!
rfKey = 00112233445566778899AABBCCDDEEFF
## With each key change currentRFKeyIndex needs to be
## incremented by 1
currentRfKeyIndex = 1
## When you change rfKey, put the old key here. To change the key Homegear needs to know the
## old and the new one.
## !!! Do not set oldRFKey when you set rfKey for the first time !!!
##oldRFKey = 00112233445566778899AABBCCDDEEFF
## When set to "true" unsigned broadcast packets are processed by Homegear. This could enable an
## attacker to make Homegear do things, you don't want. That means, this option is a security
## risk.
processBroadcastWithAesEnabled = false
#######################################
################# CUL #################
#######################################
## The device family this interface is for
#[CUL]
## Specify an unique id here to identify this device in Homegear
#id = My-CUL
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = cul
#device = /dev/ttyACM0
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 95
#######################################
########## Homegear Gateway ##########
#######################################
## The device family this interface is for
[Homegear Gateway]
## Specify an unique id here to identify this device in Homegear
id = My-Homegear-Gateway
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
deviceType = homegeargateway
## The host name or IP address of the gateway
host = MyGateway
## The port of the gateway
port = 2017
## The CA certificate
caFile = /etc/homegear/cacert.pem
## The client certificate
certFile = /etc/homegear/homegearclient.crt
## The client key file
keyFile = /etc/homegear/homegearclient.key
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101, "90" for Homegear Gateway and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 90
#######################################
### HomeMatic Wireless LAN Gateway ###
#######################################
## The device family this interface is for
#[HomeMatic Wireless LAN Gateway]
## Specify an unique id here to identify this device in Homegear
#id = My-HM-LGW
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = hmlgw
## IP address of your HM-LGW
#host = 192.168.178.100
## First Port number your HM-LGW listens on. Normally 2000.
#port = 2000
## Keep alive port number your HM-LGW listens on. Normally 2001.
#portKeepAlive = 2001
## Put the security key printed on your HM-LGW here
#lanKey = SecurityKey
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 60
## Default: sendFix = false
## Some LAN-Gateways do not send packets correctly. If sent packets are not received by the
## devices (you get error messages, that packets were not received after 3 retries), set
## sendFix to true.
## Note that the behavior of sendFix changed in version 0.6.13. If you had it set to true,
## set it to false now and the other way around.
#sendFix = false
#######################################
############# HM-CFG-LAN #############
#######################################
## The device family this interface is for
#[HM-CFG-LAN]
## Specify an unique id here to identify this device in Homegear
#id = My-HM-CFG-LAN
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = hmcfglan
## IP address of your HM-CFG-LAN
#host = 192.168.178.100
## Port number your HM-CFG-LAN listens on. Normally 1000.
#port = 1000
## Put the AES key printed on your HM-CFG-LAN here
#lanKey = 00112233445566778899AABBCCDDEEFF
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 60
#######################################
######### COC, SCC, CSM, CCD #########
#######################################
## The device family this interface is for
[COC, SCC, CSM, CCD]
## Specify an unique id here to identify this device in Homegear
id = My-SCC
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
## Also use "coc" for SCC, CCD and CSM
deviceType = coc
device = /dev/ttyAMA0
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
responseDelay = 95
## Default: gpio1 = 0
## "17" for COC, SCC and CCD. Empty for CSM.
gpio1 = 17
## Default: gpio2 = 0
## "18" for COC and SCC. "22" for CCD. Empty for CSM.
gpio2 = 18
## Default: stackPosition = 0 (= no stacking)
## Set stackPosition if you use the SCC and stacked multiple devices.
## Set stackPosition to "1" for the lowest device, to "2" for the device
## above that and so on.
# stackPosition = 0
#######################################
########### HM-MOD-RPI-PCB ###########
#######################################
## The device family this interface is for
#[HomeMatic Wireless Module for Raspberry Pi]
## Specify an unique id here to identify this device in Homegear
#id = My-HM-MOD-RPI-PCB
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = hm-mod-rpi-pcb
#device = /dev/ttyAMA0
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 95
## Default: gpio1 = 0
## "18" for HM-MOD-RPI-PCB
#gpio1 = 18
#######################################
################ CUNX ################
#######################################
## The device family this interface is for
#[CUNX]
## Specify an unique id here to identify this device in Homegear
#id = My-CUNX
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = cunx
## IP address of your CUNO
#host = 192.168.178.100
## Port number your CUNX listens on. Normally 2323.
#port = 2323
## Default: responseDelay = 95
## Should be "93" for CUNX
#responseDelay = 93
#######################################
########## TI CC1101 Module ##########
#######################################
## The device family this interface is for
#[TI CC1101 Module]
## Specify an unique id here to identify this device in Homegear
#id = My-CC1101
## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true
## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb, homegeargateway
#deviceType = cc1100
#device = /dev/spidev0.0
## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
#responseDelay = 100
## The interrupt pin to use. "0" for GDO0 or "2" for GDO2.
## You only need to connect one of them. Specify the GPIO
## you connected the interrupt pin to below.
#interruptPin = 2
## The GPIO GDO0 or GDO2 is connected to. Specify which GDO to use above.
#gpio1 = 24
### Additional TI CC1190 Config ###
## The GPIO high gain mode of the CC1190 is connected to.
## Default: -1 (disabled)
#gpio2 = 5
## The hexadecimal value for the PATABLE of the TI CC1101.
## Default:
## - Without high gain mode: 0xC2
## - With high gain mode: 0x27 (maximum legally allowed setting)
#txPowerSetting = 0x27
# vim: filetype=cfg
and the homegear-gateway.config
# Homegear Gateway configuration file
# The listen address of the gateway.
# Default: ::
listenAddress = ::
# The port number the gateway listens on.
# Default: 2017
port = 2017
# Default: runAsUser = root
# runAsUser = homegear
# Default: runAsGroup = root
# runAsGroup = homegear
# Default: debugLevel = 3
debugLevel = 4
# Default: memoryDebugging = false
memoryDebugging = true
# Set to false to disable core dumps. Currently to make fixing errors easier, core dumps are enabled by default.
# Default: enableCoreDumps = true
enableCoreDumps = true
# The working directory of Homegear. E. g. core dumps are written here. If workingDirectory is empty, the
# executable path is used.
# Default: workingDirectory =
workingDirectory = /var/log/homegear-gateway
# Default: logfilePath = /var/log/homegear-gateway
logfilePath = /var/log/homegear-gateway
### TLS options ###
# The path to the certificate authority's certificate
caFile = /etc/homegear/cacert.pem
# The path to the PEM encoded client certificate.
certPath = /etc/homegear/homegeargateway.crt
# The path to the PEM encoded client keyfile.
keyPath = /etc/homegear/homegeargateway.key
# The path to the Diffie-Hellman parameters.
dhPath = /etc/homegear/dh1024.pem
# Enable UPnP server for other devices to be able to discover this installation of Homegear Gateway
# Default: enableUPnP = true
enableUPnP = false
# Sets the IP address, the UPnP server listens on. By default auto discovery is used, but this might not work,
# if multiple interfaces exist. Only set specific IP addresses not "0.0.0.0". Alternatively the interface name can be
# specified here (e. g. "eth0").
# Default: uPnPIpAddress =
# uPnPIpAddress =
# Please change this setting! Set a unique UPnP UDN here.
# E. g.: 0660e537-dada-affe-cafe-001ff3590148
# Default: uPnPUDN =
uPnPUDN = 0660e537-dada-affe-cafe-001ff3590148
#{{{ EnOcean example config
## The device family the gateway is for.
## Options:
## - EnOcean, HomeMaticCulfw
#family = EnOcean
## The device to use
#device = /dev/ttyUSB0
#}}}
#{{{ HomeMatic CUL example config
## The device family the gateway is for.
## Options:
## - EnOcean, HomeMaticCulfw
#family = HomeMaticCulfw
## The device to use
#device = /dev/ttyACM0
#}}}
#{{{ HomeMatic COC/SCC example config
## The device family the gateway is for.
## Options:
## - EnOcean, HomeMaticCulfw
family = HomeMaticCulfw
## The device to use
device = /dev/ttyAMA0
#gpio1 = 17
#gpio2 = 18
#}}}