Quantcast
Channel: Configuration - Home Assistant Community
Viewing all articles
Browse latest Browse all 95919
↧

HomeMatic CCU (OCCU) with ELV HmIP-RFUSB and HMIP-eTRV-2

December 25, 2019, 8:56 am
$
0
0

@Layer8Fail wrote:

HI guys,

summary:
I don’t have an offical ccu2 or ccu3 from homematic. ELV HmIP-RFUSB and HomeMatic CCU addon v 9.6 on a raspian with hassio 193. Stick is recognized, Addon starts, however pairing with homematic manager fails.
Why can’t I pair the devices? How can I mitigate this error?
I tried to follow:

long version:
I have the

  • ELV HmIP-RFUSB
  • HomeMatic HMIP-eTRV-2

I’m running raspian and have home assistant and hassio in docker via offical installation.

## Hass.io supervisor
Version 193

|Hostname |homerpi|
|System |Raspbian GNU/Linux 9 (stretch)|

I assembled the usb stick and attached it to my raspberry and added the kernel module via a script on startup:

if lsusb | grep -q 1b1f:c020; then
        modprobe cp210x
        echo 1b1f c020 >/sys/bus/usb-serial/drivers/cp210x/new_id
        if [[ -e /dev/ttyUSB0 ]]; then
                HMIP_DEV="HMIP-RFUSB"
                HMIP_DEVNODE="/dev/ttyUSB0"
        fi
fi

I attached the stick to my raspi and it shows up:
serial:

/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0019367103-if00
/dev/ttyACM0
/dev/ttyUSB0
/dev/serial/by-id/usb-Silicon_Labs_eQ-3_HmIP-RFUSB_3014F711A061A7C00010CECF-if00-port0
/dev/ttyAMA0

Note: I do have another USB stick for zigbee running with no errors

I installed the official HomeMatic CCU addon version 9.6.

Add-on Config:

{
  "rf_enable": false,
  "rf": [
    {
      "type": "CCU2",
      "device": "/dev/ttyAMA0"
    }
  ],
  "wired_enable": false,
  "wired": [
    {
      "serial": "xy",
      "key": "abc",
      "ip": "192.168.0.0"
    }
  ],
  "hmip_enable": true,
  "hmip": [
    {
      "type": "HMIP_CCU2",
      "device": "/dev/ttyUSB0"
    }
  ]
}

In my /config/configuration.yaml I have:

homematic:
  interfaces:
    rf:
      host: core-homematic
      port: 2001
    wired:
      host: core-homematic
      port: 2000
    hmip:
      host: core-homematic
      port: 2010

It starts successfully:

2019-12-25 16:44:06,123 [INFO] GenericFactory - @GenericFactory
Init Hardware Info
2019-12-25 16:44:06,260 [INFO] GenericFactory - created instance of HMServerConfiguration with parameter(s)
2019-12-25 16:44:06,260 [INFO] GenericFactory - passed 1 parameter(s), in declarative order [String]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.PlatformDependent0$1 (file:/opt/HMServer/HMIPServer.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of io.netty.util.internal.PlatformDependent0$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

......


2019-12-25 16:44:24,105 [ERROR] RouterKeyServerWorker - Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
2019-12-25 16:44:24,108 [INFO] VertxManager - SYSTEM: start of RouterKeyServerWorker succeeded (2a469d86-5fca-47fe-8834-a1e581909364)
2019-12-25 16:44:25,035 [INFO] VertxManager - SYSTEM: start of KryoPersistenceWorker succeeded (73f6f65d-c8d1-4328-8ca9-9e88cac9152c)
2019-12-25 16:44:25,076 [INFO] VertxManager - SYSTEM: start of LocalServerPersistentDataLoader succeeded (e3978fc3-2c2f-4ce1-8239-1233f3a21712)
2019-12-25 16:44:25,181 [INFO] DeviceLiveUpdateSubsystem - SYSTEM: DeviceLiveUpdateSubsystem started
2019-12-25 16:44:25,186 [INFO] VertxManager - SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (0b04c69d-b161-42ab-8dea-df600d08b34e)
2019-12-25 16:44:25,186 [INFO] VertxManager - SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (8e3b6d11-cd30-4235-b13a-a5ca05529999)
2019-12-25 16:44:25,186 [INFO] VertxManager - SYSTEM: start of CheckDeviceExistHandler succeeded (31267613-002b-4bda-9055-a90dc29abad9)
2019-12-25 16:44:25,192 [INFO] VertxManager - SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (59961df4-2a65-4c27-86ff-64c448db69d4)
2019-12-25 16:44:25,464 [INFO] VertxManager - SYSTEM: start of RemoteCommAdapterInitialization succeeded (bfb6064f-edc4-4be3-8cf5-b8c543b72304)
2019-12-25 16:44:25,465 [INFO] VertxManager - SYSTEM: start of WebSocketManager succeeded (60c2db7a-97a7-482a-9e38-6d1c85392271)
2019-12-25 16:44:25,469 [INFO] FirmwareLoaderFileSystem - SYSTEM: Firmware update directory is set to /share/hmip-firmware
2019-12-25 16:44:25,480 [INFO] VertxManager - SYSTEM: start of AccessPointAuthorisationHandler succeeded (ed209c30-e907-45f5-95e9-9edfe8777dd1)
2019-12-25 16:44:25,480 [INFO] VertxManager - SYSTEM: start of FirmwareLoaderFileSystem succeeded (2cbbdf60-2ec6-4e6d-8bf8-0bdefa196dd7)
2019-12-25 16:44:25,488 [INFO] VertxManager - SYSTEM: start of AccessPointMessageDispatcher succeeded (143ccd27-d727-4fcf-853f-01c31c9c5176)
2019-12-25 16:44:25,507 [INFO] VertxManager - SYSTEM: start of AccessPointWatchdog succeeded (d12605ab-905d-4c58-b5de-f428069aeadc)
2019-12-25 16:44:25,511 [INFO] VertxManager - SYSTEM: start of AccessPointCommDevice succeeded (c0da5d60-143e-4938-9146-72403e623ce1)
2019-12-25 16:44:25,520 [INFO] VertxManager - SYSTEM: start of BackendCommandHandler succeeded (ebfe36c3-3d2f-4a76-a6c0-cafdd1bdb426)
2019-12-25 16:44:25,552 [INFO] VertxManager - SYSTEM: start of IncomingHMIPFrameHandler succeeded (5ac91783-66c8-47c9-a643-b11b09a3b4cf)
2019-12-25 16:44:25,553 [INFO] VertxManager - SYSTEM: start of DeviceInclusionAcceptHandler succeeded (20b6b52d-1391-4fb6-85ad-72e6fa419f1f)
2019-12-25 16:44:25,741 [INFO] VertxManager - SYSTEM: start of LocalServerAdapterInitialization succeeded (e10b5499-642c-4029-b1fb-4790e89015cf)
2019-12-25 16:44:25,775 [INFO] HMIPTRXInitialResponseListener - TRX adapter state 1: HMIP_TRX_App
2019-12-25 16:44:25,776 [INFO] HMIPTRXInitialResponseListener - TRX adapter application is already running or started
2019-12-25 16:44:25,776 [INFO] HMIPTRXInitialResponseListener - No NWK, try to set address ...
2019-12-25 16:44:25,777 [INFO] HMIPTRXInitialResponseListener - Try to set radio address 11786715...
2019-12-25 16:44:25,800 [INFO] HMIPTRXInitialResponseListener - Set max send attempts for 3014F711A000041709ADFEED to 3
2019-12-25 16:44:25,822 [INFO] HMIPTRXInitialResponseListener - Try to get application version...
2019-12-25 16:44:25,928 [INFO] HMIPTRXInitialResponseListener - Application version 2.8.6
2019-12-25 16:44:25,928 [INFO] HMIPTRXInitialResponseListener - Bootloader version 1.0.12
2019-12-25 16:44:25,929 [INFO] HMIPTRXInitialResponseListener - hmos version 1.20.3
2019-12-25 16:44:26,034 [INFO] HMIPTRXInitialResponseListener - MCU type: EFM32G200F64_CM3
2019-12-25 16:44:26,139 [INFO] HMIPTRXInitialResponseListener - Duty Cycle: 0.0
2019-12-25 16:44:26,139 [INFO] HMIPTRXInitialResponseListener - set DutyCycle limit to ffffffc8
2019-12-25 16:44:26,244 [INFO] HMIPTRXInitialResponseListener - Set Duty Cycle Limit
2019-12-25 16:44:26,266 [INFO] HMIPTRXInitialResponseListener - Current Security Counter: 34048
2019-12-25 16:44:26,266 [INFO] HMIPTRXInitialResponseListener - Update security counter to calculation: 41960
2019-12-25 16:44:26,375 [INFO] HMIPTRXInitialResponseListener - TRX adapter has no linkpartner
2019-12-25 16:44:26,405 [INFO] HMIPTRXInitialResponseListener - Adapter with Access Point id 3014F711A000041709ADFEED initialized
2019-12-25 16:44:26,408 [INFO] LocalServerAdapterInitialization - HMIPTRXInitialResponseListener said that Adapter was initialized
2019-12-25 16:44:26,979 [INFO] VertxManager - SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (ed8928d5-2b60-41b4-bd08-120a4d3ddfb5)
2019-12-25 16:44:26,985 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: Checking all devices on all accesspoints for updates
2019-12-25 16:44:26,986 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: There are 0 APs queued with updatable devices (RF)
2019-12-25 16:44:26,986 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: There are 0 APs queued with updatable devices (WIRED)
2019-12-25 16:44:26,989 [INFO] VertxManager - SYSTEM: start of RemoteCommAdapterFinalization succeeded (96c2be06-e2ef-4a17-aaef-08f2e662e935)
2019-12-25 16:44:27,008 [INFO] VertxManager - SYSTEM: start of LegacyNotificationHandler succeeded (bfd0d510-e8f5-4117-b180-06a350f3e957)
2019-12-25 16:44:27,041 [INFO] VertxManager - SYSTEM: start of LegacyBackendNotificationHandler succeeded (b3afd87f-5cd8-4177-aafa-58af1c6e617e)
2019-12-25 16:44:27,074 [INFO] UdpServer - UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 172.30.33.1
2019-12-25 16:44:27,204 [INFO] VertxManager - SYSTEM: start of LegacyAPIWorker succeeded (6108e943-7045-41ff-8c79-dc6d3d72b46d)
2019-12-25 16:44:27,687 [INFO] LanRoutingWorker - AP 3014F711A000041709ADFEED: Could not initialize routing of access point, version is 2.8.6
2019-12-25 16:44:27,699 [INFO] UdpServer - UDP Routing established on network interface eth0 : 0.0.0.0 (172.30.33.1)
2019-12-25 16:44:27,714 [INFO] UdpServer - UDP Routing multi cast established on network interface eth0 : 172.30.33.1
2019-12-25 16:44:28,483 [INFO] VertxManager - SYSTEM: start of LegacyInitializion succeeded (6a33f42f-9b61-4e74-b1c2-6fc5994865e4)
2019-12-25 16:44:28,691 [INFO] AccessPointCommDevice - SYSTEM: Started Access Point WebSocket server with port 9293
2019-12-25 16:44:28,693 [INFO] AccessPointCommDevice - SYSTEM: connector open
2019-12-25 16:44:28,694 [INFO] VertxManager - SYSTEM: start of LanRoutingWorker succeeded (6d2bf7c0-c2c5-4691-90cc-d425526323e7)
2019-12-25 16:44:28,776 [INFO] VertxManager - SYSTEM: initial deployment complete _____________________________________________________
2019-12-25 16:44:28,784 [INFO] LocalServer - SYSTEM: Bind XML-RPC api to port 2010
2019-12-25 16:44:31,270 [INFO] BaseHMServer - Default MaxEventLoopExecuteTime: 2000000000
2019-12-25 16:44:31,271 [INFO] BaseHMServer - Default BlockedThreadCheckInterval: 1000
2019-12-25 16:44:31,271 [INFO] BaseHMServer - Default MaxWorkerExecuteTime: 60000000000
2019-12-25 16:44:31,271 [INFO] BaseHMServer - Default EventLoopPoolSize: 8
2019-12-25 16:44:31,284 [INFO] VertxManager - SYSTEM: added for deployment [BackendWorker] (1) *worker
2019-12-25 16:44:31,286 [INFO] VertxManager - SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
2019-12-25 16:44:31,288 [INFO] VertxManager - SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
2019-12-25 16:44:31,291 [INFO] VertxManager - SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
2019-12-25 16:44:31,293 [INFO] VertxManager - SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
2019-12-25 16:44:31,295 [INFO] VertxManager - SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
2019-12-25 16:44:31,297 [INFO] VertxManager - SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
2019-12-25 16:44:31,300 [INFO] VertxManager - SYSTEM: added for deployment [RegaClientWorker] (1) *worker
2019-12-25 16:44:31,303 [INFO] VertxManager - SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
2019-12-25 16:44:31,307 [INFO] VertxManager - SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
2019-12-25 16:44:31,308 [INFO] VertxManager - SYSTEM: deploying 10 classes to Vert.x
2019-12-25 16:44:31,326 [INFO] VertxManager - SYSTEM: start of BackendWorker succeeded (415cafb8-27b5-4a0b-8816-811c924ec7cd)
2019-12-25 16:44:31,342 [INFO] VertxManager - SYSTEM: 10 VertxDeployers initialized
2019-12-25 16:44:31,356 [INFO] VertxManager - SYSTEM: start of EnergyPriceRequestWorker succeeded (def0f0ed-3091-4e5a-944a-92f421ef73df)
2019-12-25 16:44:31,378 [INFO] VertxManager - SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (883e0559-3182-4d0f-bcda-bc24aa7289a2)
2019-12-25 16:44:31,381 [INFO] VertxManager - SYSTEM: start of RegaClientWorker succeeded (b2d9a459-47a5-47d7-8576-9213c19c5613)
2019-12-25 16:44:31,387 [INFO] VertxManager - SYSTEM: start of CouplingRequestWorker succeeded (9c50fbd1-0a8c-46dc-952a-a2d9cac2a412)
2019-12-25 16:44:31,389 [INFO] VertxManager - SYSTEM: start of StorageRequestWorker succeeded (9fcd009f-8c9b-4798-862f-6656e7d37092)
2019-12-25 16:44:31,562 [INFO] VertxManager - SYSTEM: start of DiagramRequestWorker succeeded (f2c7dd22-1909-44a6-99d0-aaac9465943a)
2019-12-25 16:44:31,562 [INFO] VertxManager - SYSTEM: start of GroupRequestWorker succeeded (18035f9b-d507-445d-ac92-cdd2320eacf3)
2019-12-25 16:44:31,564 [INFO] VertxManager - SYSTEM: start of DeviceFirmwareRequestWorker succeeded (e76147ed-a6da-40e8-9f76-ff0a20bd97b7)
2019-12-25 16:44:31,931 [INFO] VertxManager - SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (10fef983-4e9c-4c3b-8c8f-036e60cfb18d)
2019-12-25 16:44:31,944 [INFO] VertxManager - SYSTEM: initial deployment complete _____________________________________________________
2019-12-25 16:44:31,946 [INFO] BaseHMServer - Starting HMServer at 127.0.0.1:9292
2019-12-25 16:44:31,947 [INFO] BaseHMServer - Read Configuration
2019-12-25 16:44:32,318 [INFO] BaseHMServer - Create Bidcos Dispatcher
2019-12-25 16:44:32,437 [INFO] BaseHMServer - InitBidCosCache
Generating a RSA private key
...............+++++
successfully loaded "/data/homematic.regadom"

Load interfaces from file
HTTP server started successfully (6 workers)
Waiting for child to finish
Executing /bin/hm_startup in child 171
.........................................+++++
writing new private key to '/etc/config/server.pem'
-----
2019-12-25 16:44:35,751 [INFO] BaseHMServer - Create groupDefinitionProvider

If I now start homematic-manager v 2.6.2 (https://github.com/hobbyquaker/homematic-manager/releases/tag/2.6.2) and want to add a device I get a message box in the UI

undefined setInstallMode
{}

In the HomeMatic Addon I get

Dec 25, 2019 4:44:51 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-3,5,main] has been blocked for 9446 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at java.base@11.0.5/jdk.internal.misc.Unsafe.park(Native Method)
	at java.base@11.0.5/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at java.base@11.0.5/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at java.base@11.0.5/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at java.base@11.0.5/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base@11.0.5/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base@11.0.5/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base@11.0.5/java.lang.reflect.Method.invoke(Method.java:566)
	at app//de.eq3.cbcs.legacy.communication.rpc.internal.rpc.AnnotationAwareRpcHandler.execute(AnnotationAwareRpcHandler.java:80)
	at app//de.eq3.ccu.server.internal.RpcMessageHandler.handle(RpcMessageHandler.java:70)
	at app//de.eq3.ccu.server.internal.RpcMessageHandler.handle(RpcMessageHandler.java:24)
	at app//io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
	at app//io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
	at app//io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
	at app//io.vertx.core.eventbus.impl.EventBusImpl$$Lambda$108/0x6c40d028.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$84/0x6d754828.run(Unknown Source)
	at app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
	at app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
	at app//io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
	at java.base@11.0.5/java.lang.Thread.run(Thread.java:834)

2019-12-25 16:44:51,866 [INFO] LegacyServiceHandler - (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999
2019-12-25 16:44:51,874 [INFO] LegacyServiceHandler - init finished
2019-12-25 16:44:51,874 [INFO] InterfaceInitializer - Added InterfaceId: 1008
2019-12-25 16:47:46,221 [INFO] LegacyServiceHandler - (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.21:2000
2019-12-25 16:47:46,232 [INFO] LegacyServiceHandler - init finished
2019-12-25 16:47:46,233 [INFO] InterfaceInitializer - Added InterfaceId: hmm_HmIP
2019-12-25 16:47:46,251 [INFO] DeviceUtil - updateDevicesForClient hmm_HmIP -> 52 device addresses will be added

if I run version 2.3.0 of the homematic Manager
I don’t get this message. However the devices (I pressed the button on the HMIP-eTRV-2) is not detected.

The Addon Log in HomeAssistant says:

2019-12-25 16:47:46,233 [INFO] InterfaceInitializer - Added InterfaceId: hmm_HmIP
2019-12-25 16:47:46,251 [INFO] DeviceUtil - updateDevicesForClient hmm_HmIP -> 52 device addresses will be added
2019-12-25 16:49:23,890 [INFO] LegacyServiceHandler - (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.21:2000
2019-12-25 16:49:23,911 [INFO] LegacyServiceHandler - Removed InterfaceId: hmm_HmIP
2019-12-25 16:49:25,184 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: 0 Accesspoints in Queue
2019-12-25 16:49:25,185 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
2019-12-25 16:49:25,185 [INFO] DeviceBackgroundUpdateSubsystem - SYSTEM: Eventlistener Handler utilization: 0/50 used
2019-12-25 16:49:39,196 [INFO] LegacyServiceHandler - (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.21:2000
2019-12-25 16:49:39,202 [INFO] LegacyServiceHandler - init finished
2019-12-25 16:49:39,203 [INFO] InterfaceInitializer - Added InterfaceId: hmm_HmIP
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2928]
Message: found: CHARACTERS, expected START_ELEMENT or END_ELEMENT
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseResponse(XmlRequestResponseProcessor.java:173)
	at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:107)
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
	at com.sun.proxy.$Proxy23.listDevices(Unknown Source)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:139)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:144)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:109)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
	at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
	at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
	at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2928]
Message: found: CHARACTERS, expected START_ELEMENT or END_ELEMENT
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1361)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseObject(XmlRpcParser.java:437)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseValue(XmlRpcParser.java:394)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseArray(XmlRpcParser.java:521)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseValue(XmlRpcParser.java:387)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodResponse(XmlRpcParser.java:164)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseResponse(XmlRequestResponseProcessor.java:171)
	... 16 more
2019-12-25 16:49:40,535 [ERROR] InterfaceInitializer - Serialization Exception: Could not add interface: hmm_HmIP
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2928]
Message: found: CHARACTERS, expected START_ELEMENT or END_ELEMENT
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseResponse(XmlRequestResponseProcessor.java:173)
	at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:107)
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
	at com.sun.proxy.$Proxy23.listDevices(Unknown Source)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:139)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:144)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:109)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
	at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
	at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
	at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,2928]
Message: found: CHARACTERS, expected START_ELEMENT or END_ELEMENT
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1361)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseObject(XmlRpcParser.java:437)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseValue(XmlRpcParser.java:394)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseArray(XmlRpcParser.java:521)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseValue(XmlRpcParser.java:387)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodResponse(XmlRpcParser.java:164)
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseResponse(XmlRequestResponseProcessor.java:171)
	... 16 more

Question
Now the question: what’s wrong with this? How can I mitigate this and get it up and running?
Has anyone this config up and running?

Posts: 1

Participants: 1

Read full topic

↧
Search
Viewing all articles
Browse latest Browse all 95919

Trending Articles

Practice Sheet of Right form of verbs for HSC Students

September 22, 2019, 11:40 pm

Download: FK ft Shenky – Nakuyewa ”Prod by: Shenky”

February 16, 2017, 4:24 pm

How to win at Markstrat (Markstrat Tips and Tricks) – Vodites

January 5, 2014, 10:34 pm

Ominde Commission Report and Recommendations – Ominde Report of 1964

March 16, 2015, 5:14 am

Bureau of Internal Revenue: Regional Offices (Directory)

January 9, 2014, 11:06 pm

GO 53 on Enhancement of Ex-gratia upto 5 Lakhs Toddy Tappers in Telangana

March 26, 2017, 11:23 pm

Cakewalk CA-2A Leveling Amplifier v2.0.1.97 WiN, v2.0.1.96 OSX Incl Keygen

October 17, 2016, 7:20 am

Mp3 Download: Mdu - Kunjenjenjena

December 7, 2017, 8:16 am

How the kill the job , when DTP request running for long hours.

July 26, 2013, 2:41 am

Microsoft Intune から展開しているアプリのアップデートについて

October 17, 2016, 4:11 am

18-year-old girl was beaten for half an hour by two Northampton men in 'an...

September 1, 2017, 10:00 pm

Car crash in Dunton Bassett leaves driver in critical condition

October 7, 2014, 7:51 am

Macky 2, Two Others In Road Accident

March 29, 2015, 5:34 am

Application log 00000000000000089514: Could not convert queue DLVST90CLNT

May 14, 2015, 11:27 pm

Detroit mafia: D’Anna Brothers agree to plea deal

April 21, 2016, 6:56 am

Delivery block field greyed out using VA02

January 26, 2016, 2:52 pm

Muloraki Au

June 22, 2016, 1:44 am

【個人撮影】スマホのプライベート映像♪「中に出さないで///」カラオケ屋での生ハメ撮りが流出ｗ【リベンジポルノ】＠PornHub

October 12, 2017, 2:23 pm

BREAKING NEWS: Diamond Platnumz Is Reported Dead After Ghastly Car Accident

February 9, 2018, 4:56 am

FIAT 500 B0111 B0112

July 5, 2018, 10:31 am
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>