[Homematic] NPE when initiating connection to CCU2
See original GitHub issueAfter adding a CCU2 as a Homematic bridge, I found this in my log:
17:02:41.787 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing 'homematic:bridge:ccu2' has been added.
17:02:41.805 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'homematic:bridge:ccu2' changed from UNINITIALIZED to INITIALIZING
17:02:42.214 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway 'ccu2' not available, disabling support
17:02:42.231 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway 'ccu2' not available, disabling support
17:02:42.233 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway 'ccu2' not available, disabling support
17:02:42.332 [INFO ] [ternal.communicator.HomematicGateway] - HmGatewayInfo[id=CCU,type=CCU2,firmware=2.3.11,address=JEQ0739206,wired=false,hmip=false,cuxd=false]
17:02:42.333 [INFO ] [ternal.communicator.HomematicGateway] - Used Homematic transfer modes: RF:BIN_RPC
17:02:43.210 [ERROR] [very.HomematicDeviceDiscoveryService] -
java.lang.ExceptionInInitializerError
at org.openhab.binding.homematic.type.HomematicTypeGeneratorImpl.createChannelType(HomematicTypeGeneratorImpl.java:228)[230:org.openhab.binding.homematic:2.0.0.201611270958]
'org.apache.felix.eventadmin.impl.adapter.LogEventAdapter$1@3908a247' is removed as a LogListener, since it threw an exception. at org.openhab.binding.homematic.type.HomematicTypeGeneratorImpl.generate(HomematicTypeGeneratorImpl.java:128)[230:org.openhab.
binding.homematic:2.0.0.201611270958]
at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onDeviceLoaded(HomematicBridgeHandler.java:283)[230:org.openhab.binding.homematic:2.0.0.201611270958]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:400)[230:org.openhab.binding.homematic:2.0.0.201611270958]
at org.openhab.binding.homematic.discovery.HomematicDeviceDiscoveryService$1.run(HomematicDeviceDiscoveryService.java:108)[230:org.openhab.binding.homematic:2.0.0.201611270958]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_101]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
Caused by: java.lang.NullPointerException
at java.io.Reader.<init>(Reader.java:78)[:1.8.0_101]
at java.io.InputStreamReader.<init>(InputStreamReader.java:72)[:1.8.0_101]
at org.openhab.binding.homematic.type.MetadataUtils.loadStandardDatapoints(MetadataUtils.java:71)[230:org.openhab.binding.homematic:2.0.0.201611270958]
at org.openhab.binding.homematic.type.MetadataUtils.<clinit>(MetadataUtils.java:52)[230:org.openhab.binding.homematic:2.0.0.201611270958]
... 12 more
17:02:43.216 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'homematic:bridge:ccu2' changed from INITIALIZING to ONLINE
@gerrieg Is this anything known?
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (12 by maintainers)
Top Results From Across the Web
Openhabe 2 Homematic / can't find things - Bindings
Connecting Homematic CCU2 with openHAB2 Bindings. Hey, I'm totally new in openHAB and ... Homematic: Fixed NPE if datapoint name is null.
Read more >NullPointerException mit neuer CCU2 - HomeMatic-Forum
apiKeys=[] 14:20:37|INFO |Starting base services 14:20:37|INFO |Connecting to database 14:20:38|FINE |Database: Preparing table DATA_POINTS ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@ooswald In the new 2.27.7 firmware, eq-3 changed some security things. The binding can not connect to the CCU on port 8181. Check the firewall settings in the CCU and set the Remote HomeMatic-Script API and/or HomeMatic XML-RPC API to full access.
I think your problem has nothing to do with this issue. It has probably the same cause as #2543 (where you already added a comment).