Hallo zusammen,
parallel zu meiner Homematic Classic Welt möchte ich mit HMCCU + Debmatic + HB-RF-ETH den Einstieg in die HMIP Welt wagen.
Nach einigen Stolpersteinen zu beginn bzgl. Einrichtung habe ich nun mein HMIP Device in FHEM angelegt bekommen.
Allerdings wird der Status bei Schaltvorgängen am Gerät und auch durch FHEM nicht aktualisiert, das Schalten funktioniert aber einwandfrei.
Ich vermute mal, dass ich noch ein Problem beim RPC Server habe und die Rückmeldungen vom Debmatic einfach nicht auftauchen.
List der CCU:
Alles unter ADR habe ich mal weggelassen zwecks der Übersicht.
Internals:
CCUNum 1
Clients :HMCCUDEV:HMCCUCHN:HMCCURPCPROC:
DEF 192.168.200.31
FUUID 62869319-f33f-98e1-91b5-f422a9b94fdd43b8
NAME d_ccu
NOTIFYDEV global
NR 888
NTFY_ORDER 50-d_ccu
RPCState running
STATE running/OK
TYPE HMCCU
ccuaddr BidCoS-RF
ccuchannels 144
ccudevices 3
ccuif BidCos-RF
ccuinterfaces BidCos-RF,VirtualDevices,HmIP-RF
ccuip 192.168.200.31
ccuname HM-RCV-50 BidCoS-RF
ccustate active
ccutype CCU2/3
config 5.0
host 192.168.200.31
prot http
version 5.0 220431743
READINGS:
2022-06-07 14:19:07 PLATFORM amd64
2022-06-07 14:19:07 PRODUCT debmatic
2022-06-07 14:19:07 VERSION 3.63.9.93
2022-06-07 14:19:07 count_channels 144
2022-06-07 14:19:07 count_devices 3
2022-06-07 14:19:07 count_groups 0
2022-06-07 14:19:07 count_interfaces 3
2022-06-07 14:19:07 count_programs 0
2022-06-07 14:43:11 rpcstate running
2022-06-07 14:43:11 state OK
hmccu:
ccuDevList "HmIP-RCV-50#HmIP-RCV-1",HmIP_Gartenbewaesserung
ccuSuppDevList HmIP_Gartenbewaesserung
defaults 0
evtime 0
evtimeout 0
postInit 0
rpccount 0
rpcports 9292,2010,2001
updatetime 0
adr:
Attributes:
ccuflags procrpc
cmdIcon on:general_an off:general_aus
room 00_System
rpcinterfaces HmIP-RF
rpcserver on
stateFormat rpcstate/state
List HMCCURPCPROC Device:
Internals:
CCUNum 1
DEF http://192.168.200.31 HmIP-RF
FD 21
FUUID 628693c6-f33f-98e1-3013-630e156456e38bb1
IODev d_ccu
NAME d_rpc200031HmIP_RF
NR 889
RPCPID 1794
RPCState running
STATE running/OK
TYPE HMCCURPCPROC
ccuip 192.168.200.31
ccustate active
ccutype CCU2/3
host 192.168.200.31
prot http
rpcid 200010200031
rpcinterface HmIP-RF
rpcip 192.168.200.31
rpcport 2010
version 5.0 220431743
READINGS:
2022-06-07 14:43:11 rpcstate running
2022-06-07 14:43:11 state OK
hmccu:
defaultaddr 192.168.200.10
devspec HmIP-RF
evtime 0
localaddr 192.168.200.31
rpcstarttime 1654605791.27297
rpc:
cbport 4030
cburl http://192.168.200.31:4030/fh2010
clkey CB2010200010200031
clurl http://192.168.200.31:2010
evtime 1654605791.25564
methods getLinkPeers,restoreConfigToDevice,getParamset,getDeviceDescription,replaceDevice,listReplaceableDevices,activateLinkParamset,setTeam,getKeyMismatchDevice,getParamsetDescription,installFirmware,init,getMetadata,deleteDevice,putParamset,reportValueUsage,changeKey,setBidcosInterface,setTempKey,abortDeleteDevice,addLink,getLinkInfo,getInstallMode,system.methodHelp,getLinks,ping,setInterfaceClock,listDevices,clearConfigCache,listTeams,setInstallModeWithWhitelist,determineParameter,logLevel,getServiceMessages,setInstallMode,getVersion,system.multicall,searchDevices,updateFirmware,removeLink,refreshDeployedDeviceFirmwareList,getParamsetId,setMetadata,getValue,setLinkInfo,addDevice,setValue,system.listMethods,listBidcosInterfaces,rssiInfo
pid 1794
port 2010
requests 557
state running
sumdelay 0
rec:
DD 0
EV 0
EX 0
IN 0
ND 0
RA 0
RD 0
SL 1
TO 0
UD 0
snd:
DD 0
EV 0
EX 0
IN 0
ND 0
RA 0
RD 0
SL 0
TO 0
UD 0
Attributes:
alias CCU RPC HmIP-RF
eventMap /rpcserver on:on/rpcserver off:off/
room 00_System
rpcServerAddr 192.168.200.31
rpcServerPort 2010
stateFormat rpcstate/state
List eines Kanals vom Device (wurde angelegt mit CreateDEV):
Internals:
DEF 000D1D89A09B87 sd=9.STATE cd=10.STATE
FUUID 629f40b7-f33f-98e1-6d75-9cce2a82a6062283
IODev d_ccu
NAME HmIP_MOD_OC8_000D1D89A09B87_9
NR 890
STATE off
TYPE HMCCUDEV
ccuaddr 000D1D89A09B87
ccudevstate active
ccuif HmIP-RF
ccuname HmIP_Gartenbewaesserung
ccurolectrl SWITCH_VIRTUAL_RECEIVER
ccurolestate SWITCH_TRANSMITTER
ccusubtype MOD-OC8
ccutype HmIP-MOD-OC8
firmware 1.8.12
readonly no
READINGS:
2022-06-07 14:43:11 10.PROCESS STABLE
2022-06-07 14:43:11 10.SECTION 0
2022-06-07 14:43:11 10.SECTION_STATUS NORMAL
2022-06-07 14:43:11 10.STATE off
2022-06-07 14:43:11 9.PROCESS STABLE
2022-06-07 14:43:11 9.SECTION 0
2022-06-07 14:43:11 9.SECTION_STATUS NORMAL
2022-06-07 14:43:11 9.STATE off
2022-06-07 14:19:07 IODev d_ccu
2022-06-07 14:43:11 activity alive
2022-06-07 14:43:11 control off
2022-06-07 14:43:11 devstate ok
2022-06-07 14:43:11 hmstate off
2022-06-07 14:43:11 rssidevice -30
2022-06-07 14:43:11 rssipeer -40
2022-06-07 14:43:11 state off
2022-06-07 14:43:11 voltage 0.0
hmccu:
channels 42
defCDP 10.STATE
defSDP 9.STATE
detect 5
devspec 000D1D89A09B87
forcedev 0
nodefaults 1
role 0:MAINTENANCE,1:KEY_TRANSCEIVER,2:KEY_TRANSCEIVER,3:KEY_TRANSCEIVER,4:KEY_TRANSCEIVER,5:KEY_TRANSCEIVER,6:KEY_TRANSCEIVER,7:KEY_TRANSCEIVER,8:KEY_TRANSCEIVER,9:SWITCH_TRANSMITTER,10:SWITCH_VIRTUAL_RECEIVER,11:SWITCH_VIRTUAL_RECEIVER,12:SWITCH_VIRTUAL_RECEIVER,13:SWITCH_TRANSMITTER,14:SWITCH_VIRTUAL_RECEIVER,15:SWITCH_VIRTUAL_RECEIVER,16:SWITCH_VIRTUAL_RECEIVER,17:SWITCH_TRANSMITTER,18:SWITCH_VIRTUAL_RECEIVER,19:SWITCH_VIRTUAL_RECEIVER,20:SWITCH_VIRTUAL_RECEIVER,21:SWITCH_TRANSMITTER,22:SWITCH_VIRTUAL_RECEIVER,23:SWITCH_VIRTUAL_RECEIVER,24:SWITCH_VIRTUAL_RECEIVER,25:SWITCH_TRANSMITTER,26:SWITCH_VIRTUAL_RECEIVER,27:SWITCH_VIRTUAL_RECEIVER,28:SWITCH_VIRTUAL_RECEIVER,29:SWITCH_TRANSMITTER,30:SWITCH_VIRTUAL_RECEIVER,31:SWITCH_VIRTUAL_RECEIVER,32:SWITCH_VIRTUAL_RECEIVER,33:SWITCH_TRANSMITTER,34:SWITCH_VIRTUAL_RECEIVER,35:SWITCH_VIRTUAL_RECEIVER,36:SWITCH_VIRTUAL_RECEIVER,37:SWITCH_TRANSMITTER,38:SWITCH_VIRTUAL_RECEIVER,39:SWITCH_VIRTUAL_RECEIVER,40:SWITCH_VIRTUAL_RECEIVER,41:SWITCH_WEEK_PROFILE
setDefaults 0
cmdlist:
get
set on:noArg on-till on-for-timer off:noArg toggle:noArg
control:
chn 10
dpt STATE
dp:
CLEARED - TO LONG
Attributes:
ccureadingfilter 1,10,2,3,4,5,6,7,8,9..*
cmdIcon on:general_an off:general_aus
group HmIP_Gartenbewaesserung
Wenn ich mit <get HmIP_MOD_OC8_000D1D89A09B87_9 update> manuell aktualisiere erhalte ich den aktuellen Status.
Irgendwo habe ich bei der Einrichtung sicherlich noch einen Fehler gemacht und brauche daher eure Hilfe.
Entlangehangelt habe ich mich am Wiki Artikel https://wiki.fhem.de/wiki/HMCCU
Vielen Dank für eure Hilfe !
Auf welcher Soft/Hardwarebasis läuft Dein FHEM?
Fhem und Debmatic laufen in je einer Ubuntu VM auf einem ESXi.
Firewall auf beiden Systemen sind offen. (Iptables sowie UFW habe ich gecheckt)
Im Wiki Artikel steht noch was von der Firewall in der CCU an sich, allerdings ist diese in den neueren Debmatic Versionen soweit ich es gelesen habe nicht mehr enthalten und es wird auf die ,,Systemfirewalls" des Hosts verwiesen.
Hat Dein System, auf dem FHEM läuft, mehrere IP Adressen? Wenn ja, solltest Du entweder im I/O Device (HMCCU) oder in den HMCCURPCPROC Devices mit dem Attribut rpcServerAddr die richtige IP-Adresse setzen.
Danach müssen die RPC-Server neu gestartet werden. Ggf. findest Du auch im FHEM Log beim Starten der RPC-Server Meldungen mit der verwendeten IP-Adresse.
Im CCU Systemlog (/var/log/messages) sollten außerdem Fehlermeldungen stehen, wenn die CCU keine Events an FHEM schicken kann.
Ja der FHEM Server hat mehrere IPs.
Im HMCCURPCPROC Device habe ich IP/Port gesetzt.
Ist die RPC Verbindung eine stehende Verbindung? In einem netstat kann ich keine entsprechende Verbindung sehen.
Unter /var/log/hmserver.log konnte ich jetzt folgende Einträge finden:
Jun 7 20:58:09 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.200.31:7420/fh2010
Jun 7 20:58:09 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO [CB2010200010200031_WorkerPool-1] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started
Jun 7 20:58:09 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [CB2010200010200031_WorkerPool-1] init finished
Jun 7 20:58:09 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-0] Added InterfaceId: CB2010200010200031
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Connection refused (Connection refused)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:110)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at com.sun.proxy.$Proxy22.listDevices(Unknown Source)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:139)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:158)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:109)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.lang.Thread.run(Thread.java:748)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] Caused by: java.net.ConnectException: Connection refused (Connection refused)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.PlainSocketImpl.socketConnect(Native Method)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at java.net.Socket.connect(Socket.java:607)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:106)
Jun 7 20:58:09 de.eq3.cbcs.util.EQ3LoggerOutputStream ERROR [vert.x-worker-thread-0] ... 15 more
Jun 7 20:58:09 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer ERROR [vert.x-worker-thread-0] IO Exception: Could not add interface: CB2010200010200031
de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Connection refused (Connection refused)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:110)
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.$Proxy22.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:158)
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.impl.AbstractContext.dispatch(AbstractContext.java:100)
at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59)
at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104)
at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:106)
... 15 more
Hat jemand auf CCU Seite diese Meldungen schon mal gesehen ?
"Connection refused" klingt nicht gut.
Wie sieht es denn auf dem FHEM System aus bei
netstat -alp | grep fhem
Es war einfach ein Config Fehler.... Aber vielleicht ist ja jemand genauso verpeilt wie ich.
rpcServerAddr 192.168.200.31
rpcServerPort 2010
Hier darf natürlich NICHT die IP der CCU drinstehen sondern es muss die FHEM IP drinstehen.
So hat er versucht an der CCU einen CALLBACK Register auf die CCU IP zu machen....
Vielleicht kann man das ganze noch irgendwie in der Doku hinterlegen.
Dokumentiert ist es schon (Commandref)
rpcserveraddr <ip-or-name>
Specify network interface by IP address or DNS name where RPC server should listen on. By default HMCCU automatically detects the IP address. This attribute should be used if the FHEM server has more than one network interface.
rpcserverport <base-port>
Specify base port for RPC server. The real listening port of an RPC server is calculated by the formula: base-port + rpc-port + (10 * ccu-number). Default value for base-port is 5400.
The value ccu-number is only relevant if more than one CCU is connected to FHEM. Example: If base-port is 5000, protocol is BidCos (rpc-port 2001) and only one CCU is connected the resulting RPC server port is 5000+2001+(10*1) = 7010.
Das Attribut rpcserverport würde ich nur im Notfall setzen. Die 2010 bei Dir deutet an, dass Du das für den HmIP Port hältst. Dem ist nicht so. Das ist der Basisport, auf dem die RPC-Server auf FHEM lauschen. Daraus ergeben sich die endgültigen Ports wie oben beschrieben.
2010 ist sehr niedrig und Du läufst in Gefahr, dass die RPC-Server versuchen, sich an bereits anderweitig verwendete Ports zu binden.
Dann hatte ich es einfach nur falsch verstanden.
Port hatte ich inzwischen schon wieder gelöscht, der war nur im initialen List noch gesetzt.