Failed to initialize proxy for homeassistant-wired

avhoboken · May 2, 2021, 2:32pm

I want to integrate my existing Homematic environment, based on a CCU3 and multiple wireless (not IP) Homematic devices, into Home Assistant. So I’ve added the Homematic integration to my configuration.yaml using the below entry:

homematic:
interfaces:
wireless:
host: 192.168.20.230
port: 2001
resolvenames: “json”
username: “Admin”
password: “password”
wired:
host: 192.168.20.230
port: 2000
resolvenames: “json”
username: “Admin”
password: “password”
ip:
host: 192.168.20.230
port: 2010
groups:
host: 192.168.20.230
port: 9292
resolvenames: “json”
username: “Admin”
password: “password”
path: /groups
hosts:
ccu3:
host: 192.168.20.230
username: “Admin”
password: “password”

My Home Assistant device is running on a Raspberry 4 and in the same vlan as the CCU3. Also configured Full Access for both XML-RPC API and Scripts in the firewall section of the CCU3. Also added the HA IP address 192.168.20.4 to the allow list on the CCU3.

This seems to be working, all Homematic channels are created as entities in HA and I can control them. However I do get an error messages in the HA logfile:
=> Failed to initialize proxy for homeassistant-wired
=> Setup of homematic is taking over 10 seconds.
=> Skipping init for homeassistant-ccu3

Any suggestions how I can get rid of these errors? Not sure what the impact is because it seems to be working.
Other question, why are there not any devices created but only entities. Or might this be related to the error?

Any help is very appreciated.

Thanks

ChecksumDK · July 21, 2021, 12:53pm

I experience the same issue

danielperna84 · July 21, 2021, 11:22pm

If you don’t have HmIP devices, take out the ip section of your config. If you don’t have wired devices, take out the wired section of your config. Please share how the documentation could clarify, that you only need to add interface-configurations for device-types you actually use.

By removing the wired section you should get rid of the first error you have posted.
The second error won’t go away. That’s just normal with the HomeMatic integration.
The third message also is normal and can be ignored.

Regardind the devices: The HomeMatic integration is fairly old and hasn’t been upgraded to support devices. Sadly no one seems to be able to help with the new integration. Hence there’s no timeframe when (and if) a new integration will be available.

ChecksumDK · July 22, 2021, 11:43am

Thanks. I would love to help with a new integration.
I get some other warnings and error messages and some exception messages when calling the “de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand”.

[cont-init.d] certs.sh: exited 0.
[cont-init.d] env.sh: executing... 
[cont-init.d] env.sh: exited 0.
[cont-init.d] hm_ip.sh: executing... 
[cont-init.d] hm_ip.sh: exited 0.
[cont-init.d] hm_rfd.sh: executing... 
[cont-init.d] hm_rfd.sh: exited 0.
[cont-init.d] hm_wired.sh: executing... 
[cont-init.d] hm_wired.sh: exited 0.
[cont-init.d] interface.sh: executing... 
[cont-init.d] interface.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:30:48] INFO: Wait until HMServer is setup
[13:30:48] INFO: Initialize webinterface routing...
2021-07-22 13:30:48: mod_openssl.c.2475) SSL: ssl.use-sslv2 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv2.
2021-07-22 13:30:48: mod_openssl.c.2482) SSL: ssl.use-sslv3 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv3.
2021-07-22 13:30:48: mod_openssl.c.2475) SSL: ssl.use-sslv2 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv2.
2021-07-22 13:30:48: mod_openssl.c.2482) SSL: ssl.use-sslv3 is deprecated and will soon be removed.  It is disabled by default.  Many modern TLS libraries no longer support SSLv3.
[13:30:48] INFO: Starting HMServer...
[13:30:49] INFO: Starting Nginx...
2021/07/22 13:30:49 [notice] 447#447: using the "epoll" event method
2021/07/22 13:30:49 [notice] 447#447: nginx/1.18.0
2021/07/22 13:30:49 [notice] 447#447: OS: Linux 5.10.45
2021/07/22 13:30:49 [notice] 447#447: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2021/07/22 13:30:49 [notice] 447#447: start worker processes
2021/07/22 13:30:49 [notice] 447#447: start worker process 536
2021-07-22 13:30:49,373 [INFO] GenericFactory - @GenericFactory
Init Hardware Info
2021-07-22 13:30:49,380 [INFO] GenericFactory - created instance of HMServerConfiguration with parameter(s)
2021-07-22 13:30:49,380 [INFO] GenericFactory - passed 1 parameter(s), in declarative order [String]
2021-07-22 13:30:49,381 [INFO] BaseHMServer - Creating instance of HMServer... 
2021-07-22 13:30:49,400 [INFO] BaseHMServer - Default MaxEventLoopExecuteTime: 2000000000
2021-07-22 13:30:49,400 [INFO] BaseHMServer - Default BlockedThreadCheckInterval: 1000
2021-07-22 13:30:49,400 [INFO] BaseHMServer - Default MaxWorkerExecuteTime: 60000000000
2021-07-22 13:30:49,400 [INFO] BaseHMServer - Default EventLoopPoolSize: 4
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by io.netty.util.internal.PlatformDependent0$1 (file:/opt/HMServer/HMServer.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
2021-07-22 13:30:49,667 [INFO] VertxManager - SYSTEM: added for deployment [BackendWorker] (1) *worker
2021-07-22 13:30:49,668 [INFO] VertxManager - SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
2021-07-22 13:30:49,669 [INFO] VertxManager - SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
2021-07-22 13:30:49,670 [INFO] VertxManager - SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
2021-07-22 13:30:49,671 [INFO] VertxManager - SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
2021-07-22 13:30:49,672 [INFO] VertxManager - SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
2021-07-22 13:30:49,673 [INFO] VertxManager - SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
2021-07-22 13:30:49,674 [INFO] VertxManager - SYSTEM: added for deployment [RegaClientWorker] (1) *worker
2021-07-22 13:30:49,677 [INFO] VertxManager - SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
2021-07-22 13:30:49,682 [INFO] VertxManager - SYSTEM: deploying 9 classes to Vert.x
2021-07-22 13:30:49,696 [INFO] VertxManager - SYSTEM: 9 VertxDeployers initialized
2021-07-22 13:30:49,822 [INFO] VertxManager - SYSTEM: start of BackendWorker succeeded (44f386bb-8598-4564-8877-52aac8a9b1ed)
2021-07-22 13:30:49,826 [INFO] VertxManager - SYSTEM: start of RegaClientWorker succeeded (37290bdf-6955-4e29-bd3d-bee50d714353)
2021-07-22 13:30:49,824 [INFO] VertxManager - SYSTEM: start of StorageRequestWorker succeeded (7f9e4e6b-a543-48f3-b166-8ba6f1f5fdbd)
2021-07-22 13:30:49,823 [INFO] VertxManager - SYSTEM: start of EnergyPriceRequestWorker succeeded (2bc59a5a-11de-4383-b89a-efe3d6cfaeb8)
2021-07-22 13:30:49,823 [INFO] VertxManager - SYSTEM: start of CouplingRequestWorker succeeded (4915a992-2640-4dc6-896b-dc5e0d1d18e8)
2021-07-22 13:30:49,915 [INFO] VertxManager - SYSTEM: start of GroupRequestWorker succeeded (c4084347-7da9-4adc-a0b1-718cb8245300)
2021-07-22 13:30:49,917 [INFO] VertxManager - SYSTEM: start of DeviceFirmwareRequestWorker succeeded (fb179214-f8f0-416c-aad7-785a367cea2e)
2021-07-22 13:30:49,918 [INFO] VertxManager - SYSTEM: start of DiagramRequestWorker succeeded (bdf96bcb-f715-49fa-9776-c4c379a563be)
2021-07-22 13:30:50,058 [INFO] VertxManager - SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (7fee39eb-9937-4022-a66e-049772f7c541)
2021-07-22 13:30:50,103 [INFO] VertxManager - SYSTEM: initial deployment complete _____________________________________________________
2021-07-22 13:30:50,104 [INFO] BaseHMServer - Starting HMServer at 127.0.0.1:9292
2021-07-22 13:30:50,105 [INFO] BaseHMServer - Read Configuration
2021-07-22 13:30:50,192 [INFO] BaseHMServer - Create Bidcos Dispatcher
2021-07-22 13:30:50,203 [INFO] BaseHMServer - InitBidCosCache
2021-07-22 13:30:50,204 [INFO] BaseHMServer - Create groupDefinitionProvider
2021-07-22 13:30:50,666 [INFO] BaseHMServer - Create VirtualDeviceHolder
2021-07-22 13:30:50,669 [INFO] BaseHMServer - Create VirtualDeviceHandlerRega
2021-07-22 13:30:50,681 [INFO] BaseHMServer - Create GroupAdministrationService
2021-07-22 13:30:50,682 [INFO] BaseHMServer - Create GroupDeviceDispatcher
2021-07-22 13:30:50,683 [INFO] BaseHMServer - Create GroupDeviceHandler
2021-07-22 13:30:50,690 [INFO] GroupDeviceHandler - @GroupDeviceHandler - initializing...
2021-07-22 13:30:50,691 [INFO] GroupDeviceHandler - --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
2021-07-22 13:30:50,691 [INFO] GroupDeviceHandler - --> created virtualDeviceHandler (GroupDeviceService to ReGa)
2021-07-22 13:30:50,694 [INFO] GroupDeviceHandler - --> got groupDefinitionProvider
2021-07-22 13:30:50,698 [INFO] BaseHMServer - Create BidCosGroupMemberProvider
2021-07-22 13:30:50,716 [INFO] BaseHMServer - Init groupAdministrationService
2021-07-22 13:30:50,725 [INFO] BaseHMServer - Init Virtual OS Device
2021-07-22 13:30:50,728 [INFO] BaseHMServer - Init ESHLight Bridge
2021-07-22 13:30:54,385 [INFO] BaseHMServer - Create RrdDatalogging
2021-07-22 13:30:54,387 [INFO] BaseHMServer - Create MeasurementService
2021-07-22 13:30:54,390 [INFO] BaseHMServer - Init MeasurementService
2021-07-22 13:30:54,422 [INFO] BaseHMServer - Create HTTP Server
2021-07-22 13:30:55,069 [INFO] BaseHMServer - Create BidCos context and start handler
2021-07-22 13:30:55,101 [INFO] BaseHMServer - Create group context and start handler
[13:30:55] INFO: Starting ReGaHss...
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 591
2021-07-22 13:30:56,110 [INFO] BaseHMServer - Starting HMServer done
2021-07-22 13:31:02,463 [INFO] VirtualDeviceHandlerRega - (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999
2021-07-22 13:31:02,472 [INFO] VirtualDeviceHandlerRega - Added InterfaceId: 1007
2021-07-22 13:31:02,473 [INFO] BackendWorker - Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Jul 22, 2021 1:31:04 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 2036 ms, time limit is 2000
Jul 22, 2021 1:31:05 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 3036 ms, time limit is 2000
Jul 22, 2021 1:31:06 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 4036 ms, time limit is 2000
ReGa entering normal operation
Jul 22, 2021 1:31:07 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 5036 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at [email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at [email protected]/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$144/0xe03b0a28.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$79/0xe1ea5428.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 [email protected]/java.lang.Thread.run(Thread.java:829)
Jul 22, 2021 1:31:08 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 6036 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at [email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at [email protected]/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$144/0xe03b0a28.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$79/0xe1ea5428.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 [email protected]/java.lang.Thread.run(Thread.java:829)
Jul 22, 2021 1:31:09 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 7036 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at [email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at [email protected]/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$144/0xe03b0a28.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$79/0xe1ea5428.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 [email protected]/java.lang.Thread.run(Thread.java:829)
Jul 22, 2021 1:31:10 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 8037 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at [email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at [email protected]/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$144/0xe03b0a28.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$79/0xe1ea5428.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 [email protected]/java.lang.Thread.run(Thread.java:829)
Jul 22, 2021 1:31:11 PM io.vertx.core.impl.BlockedThreadChecker
WARNING: Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 9038 ms, time limit is 2000
io.vertx.core.VertxException: Thread blocked
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
	at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
	at [email protected]/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
	at app//de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega.registerCallback(VirtualDeviceHandlerRega.java:99)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at [email protected]/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at [email protected]/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at [email protected]/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$144/0xe03b0a28.handle(Unknown Source)
	at app//io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at app//io.vertx.core.impl.ContextImpl$$Lambda$79/0xe1ea5428.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 [email protected]/java.lang.Thread.run(Thread.java:829)

danielperna84 · July 22, 2021, 9:08pm

My plan would be to base the new integration on my new project hahomematic. Currently pyhomematic is being used, but that has some limitations which prevent us from integrating new devices. hahomematic is still in a rather early stage though. Have a look at this issue for more details.
I don’t know how / where you get these messages from. Home Assistant has no rega-related service. The log looks like it is taken directly from the CCU. If this is a real CCU, head over to the homematic forum. If it’s RaspberryMatic maybe as here.

ChecksumDK · July 23, 2021, 7:47am

I would love to help you getting the new integration rolling. I know a bit about html and css and stuff like that. Will you be able to work on the new integration if I can figure out how to make the configuration UI? Maybe we should continue the discussion private somehow. I am new to home assistant, homematic and all this. Can you PM me?
Its a real CCU. I will try to look in the homematic forums. Thanks.

ChecksumDK · July 23, 2021, 12:49pm

Hi Daniel
The add-on configuration cannot present dictionaries, but the more basic configuration text editor does.

danielperna84 · July 23, 2021, 1:54pm

I actually already got a blueprint from someone else privately for the configuration, so that part might be solved already. It’s implemented by repeating the UI steps based on a checkbox (Add another interface). I didn’t have the time to dive into it lately though. I currently have other projects that have a higher priority. So for now there won’t be much progress. I’ll share what I have at some time in the future. Until then someone with Python experience should have a look at hahomematic to see if my proposed architecture makes sense.