Lösung für Türklingel

surfer09

@bahnuhr sagte in Lösung für Türklingel:

LEQ0533995

Das ist eine Funksteckdose, die aber aktuell Werte liefert...

bahnuhr

@surfer09 sagte in Lösung für Türklingel:

Das ist eine Funksteckdose

und warum meckert iob dann im log.

surfer09

Ich habe gerade nochmal alles neu gestartet. Es taucht immer dann ".. no matching device" auf

2024-04-01 10:17:36.654 - info: host.IOBroker-Server iobroker.js-controller version 5.0.19 js-controller starting
2024-04-01 10:17:36.657 - info: host.IOBroker-Server Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-04-01 10:17:36.658 - info: host.IOBroker-Server hostname: IOBroker-Server, node: v18.20.0
2024-04-01 10:17:36.658 - info: host.IOBroker-Server ip addresses: 192.168.1.25
2024-04-01 10:17:36.666 - warn: host.IOBroker-Server-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
2024-04-01 10:17:38.430 - warn: host.IOBroker-Server-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
2024-04-01 10:17:38.625 - info: host.IOBroker-Server connected to Objects and States
2024-04-01 10:17:38.651 - info: host.IOBroker-Server added notifications configuration of host
2024-04-01 10:17:39.041 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.nodeCurrent"
2024-04-01 10:17:39.043 - info: host.IOBroker-Server 40 instances found
2024-04-01 10:17:39.077 - info: host.IOBroker-Server starting 29 instances
2024-04-01 10:17:39.180 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.nodeNewest"
2024-04-01 10:17:39.182 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.nodeNewestNext"
2024-04-01 10:17:39.194 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.npmCurrent"
2024-04-01 10:17:39.207 - info: host.IOBroker-Server instance system.adapter.admin.0 started with pid 7328
2024-04-01 10:17:39.211 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.npmNewest"
2024-04-01 10:17:39.215 - info: host.IOBroker-Server Delete state "system.host.IOBroker-Server.versions.npmNewestNext"
2024-04-01 10:17:39.218 - info: host.IOBroker-Server Some obsolete host states deleted.
2024-04-01 10:17:41.458 - error: admin.0 (7328) admin.0 already running
2024-04-01 10:17:41.459 - warn: admin.0 (7328) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:17:42.024 - error: host.IOBroker-Server instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:17:42.024 - info: host.IOBroker-Server Restart adapter system.adapter.admin.0 because enabled
2024-04-01 10:17:43.709 - info: host.IOBroker-Server instance system.adapter.javascript.0 started with pid 7444
2024-04-01 10:17:45.116 - error: javascript.0 (7444) javascript.0 already running
2024-04-01 10:17:45.117 - warn: javascript.0 (7444) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:17:45.685 - error: host.IOBroker-Server instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:17:45.685 - info: host.IOBroker-Server Restart adapter system.adapter.javascript.0 because enabled
2024-04-01 10:17:47.127 - info: host.IOBroker-Server instance system.adapter.node-red.0 started with pid 7492
2024-04-01 10:17:47.717 - error: node-red.0 (7492) node-red.0 already running
2024-04-01 10:17:47.718 - warn: node-red.0 (7492) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:17:48.266 - error: host.IOBroker-Server instance system.adapter.node-red.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:17:48.266 - info: host.IOBroker-Server Restart adapter system.adapter.node-red.0 because enabled
2024-04-01 10:17:51.138 - info: host.IOBroker-Server instance system.adapter.sql.0 started with pid 8340
2024-04-01 10:17:51.786 - error: sql.0 (8340) sql.0 already running
2024-04-01 10:17:51.787 - warn: sql.0 (8340) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:17:52.345 - error: host.IOBroker-Server instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:17:52.345 - info: host.IOBroker-Server Restart adapter system.adapter.sql.0 because enabled
2024-04-01 10:17:55.139 - info: host.IOBroker-Server instance system.adapter.telegram.2 started with pid 9264
2024-04-01 10:17:56.368 - error: telegram.2 (9264) telegram.2 already running
2024-04-01 10:17:56.369 - warn: telegram.2 (9264) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:17:56.939 - error: host.IOBroker-Server instance system.adapter.telegram.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:17:56.939 - info: host.IOBroker-Server Restart adapter system.adapter.telegram.2 because enabled
2024-04-01 10:17:59.136 - info: host.IOBroker-Server instance system.adapter.hm-rega.0 started with pid 9512
2024-04-01 10:17:59.950 - error: hm-rega.0 (9512) hm-rega.0 already running
2024-04-01 10:17:59.951 - warn: hm-rega.0 (9512) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:00.514 - error: host.IOBroker-Server instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:00.514 - info: host.IOBroker-Server Restart adapter system.adapter.hm-rega.0 because enabled
2024-04-01 10:18:03.178 - info: host.IOBroker-Server instance system.adapter.hm-rpc.0 started with pid 9744
2024-04-01 10:18:03.919 - debug: hm-rpc.0 (9744) Redis Objects: Use Redis connection: 0.0.0.0:9001
2024-04-01 10:18:03.936 - debug: hm-rpc.0 (9744) Objects client ready ... initialize now
2024-04-01 10:18:03.937 - debug: hm-rpc.0 (9744) Objects create System PubSub Client
2024-04-01 10:18:03.937 - debug: hm-rpc.0 (9744) Objects create User PubSub Client
2024-04-01 10:18:03.958 - debug: hm-rpc.0 (9744) Objects client initialize lua scripts
2024-04-01 10:18:03.961 - debug: hm-rpc.0 (9744) Objects connected to redis: 0.0.0.0:9001
2024-04-01 10:18:03.984 - debug: hm-rpc.0 (9744) Redis States: Use Redis connection: 0.0.0.0:9000
2024-04-01 10:18:03.992 - debug: hm-rpc.0 (9744) States create System PubSub Client
2024-04-01 10:18:03.992 - debug: hm-rpc.0 (9744) States create User PubSub Client
2024-04-01 10:18:04.007 - debug: hm-rpc.0 (9744) States connected to redis: 0.0.0.0:9000
2024-04-01 10:18:04.011 - error: hm-rpc.0 (9744) hm-rpc.0 already running
2024-04-01 10:18:04.012 - debug: hm-rpc.0 (9744) Plugin sentry destroyed
2024-04-01 10:18:04.012 - warn: hm-rpc.0 (9744) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:04.565 - error: host.IOBroker-Server instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:04.565 - info: host.IOBroker-Server Restart adapter system.adapter.hm-rpc.0 because enabled
2024-04-01 10:18:07.124 - info: host.IOBroker-Server instance system.adapter.hm-rpc.1 started with pid 10088
2024-04-01 10:18:07.764 - error: hm-rpc.1 (10088) hm-rpc.1 already running
2024-04-01 10:18:07.765 - warn: hm-rpc.1 (10088) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:08.329 - error: host.IOBroker-Server instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:08.330 - info: host.IOBroker-Server Restart adapter system.adapter.hm-rpc.1 because enabled
2024-04-01 10:18:11.150 - info: host.IOBroker-Server instance scheduled system.adapter.ical.0 */25 * * * *
2024-04-01 10:18:11.153 - info: host.IOBroker-Server instance system.adapter.ical.0 started with pid 9604
2024-04-01 10:18:12.054 - info: host.IOBroker-Server instance system.adapter.admin.0 started with pid 9044
2024-04-01 10:18:12.981 - info: admin.0 (9044) starting. Version 6.13.16 in I:/ioBroker/node_modules/iobroker.admin, node: v18.20.0, js-controller: 5.0.19
2024-04-01 10:18:12.990 - info: admin.0 (9044) requesting all objects
2024-04-01 10:18:13.613 - info: admin.0 (9044) received all objects
2024-04-01 10:18:13.779 - info: admin.0 (9044) Request actual repository...
2024-04-01 10:18:13.787 - info: admin.0 (9044) socket.io server listening on port 8081
2024-04-01 10:18:13.789 - info: admin.0 (9044) http server listening on port 8081
2024-04-01 10:18:13.789 - info: admin.0 (9044) Use link "http://127.0.0.1:8081" to configure.
2024-04-01 10:18:13.863 - error: host.IOBroker-Server cannot call visUtils: Not exists
2024-04-01 10:18:14.048 - info: host.IOBroker-Server Updating repository "Stable" under "http://iobroker.live/repo/sources-dist.json"
2024-04-01 10:18:14.731 - info: admin.0 (9044) Repository received successfully.
2024-04-01 10:18:15.066 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:15.069 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:15.103 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:15.115 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:15.137 - info: host.IOBroker-Server instance system.adapter.mielecloudservice.0 started with pid 10216
2024-04-01 10:18:15.476 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:16.098 - info: host.IOBroker-Server instance system.adapter.javascript.0 started with pid 10140
2024-04-01 10:18:16.108 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:16.108 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:16.110 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:16.111 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:16.206 - warn: host.IOBroker-Server "system.host.IOBROKER-SLAVE-WINDOWS" is offline
2024-04-01 10:18:16.210 - error: mielecloudservice.0 (10216) mielecloudservice.0 already running
2024-04-01 10:18:16.211 - warn: mielecloudservice.0 (10216) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:16.803 - error: host.IOBroker-Server instance system.adapter.mielecloudservice.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:16.804 - info: host.IOBroker-Server Restart adapter system.adapter.mielecloudservice.0 because enabled
2024-04-01 10:18:17.059 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:17.062 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:17.839 - info: host.IOBroker-Server instance system.adapter.mielecloudservice.0 started with pid 1508
2024-04-01 10:18:18.312 - info: host.IOBroker-Server instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2024-04-01 10:18:18.333 - info: host.IOBroker-Server instance system.adapter.node-red.0 started with pid 2988
2024-04-01 10:18:19.124 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:19.205 - info: host.IOBroker-Server instance system.adapter.synology.0 started with pid 6324
2024-04-01 10:18:20.066 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:20.068 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:20.097 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:20.098 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:20.339 - error: synology.0 (6324) synology.0 already running
2024-04-01 10:18:20.341 - warn: synology.0 (6324) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:20.896 - error: host.IOBroker-Server instance system.adapter.synology.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:20.896 - info: host.IOBroker-Server Restart adapter system.adapter.synology.0 because enabled
2024-04-01 10:18:21.063 - info: admin.0 (9044) ==> Connected system.user.admin from ::ffff:192.168.1.4
2024-04-01 10:18:21.066 - info: admin.0 (9044) <== Disconnect system.user.admin from ::ffff:192.168.1.4 admin
2024-04-01 10:18:21.276 - error: javascript.0 (10140) npm
2024-04-01 10:18:21.277 - error: javascript.0 (10140) WARN deprecated har-validator@5.1.5: this library is no longer supported
2024-04-01 10:18:21.352 - error: host.IOBroker-Server cannot call visUtils: Not exists
2024-04-01 10:18:21.432 - error: javascript.0 (10140) npm
2024-04-01 10:18:21.433 - error: javascript.0 (10140) WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
2024-04-01 10:18:21.601 - error: javascript.0 (10140) npm
2024-04-01 10:18:21.602 - error: javascript.0 (10140) WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
2024-04-01 10:18:21.612 - error: javascript.0 (10140) npm
2024-04-01 10:18:21.613 - error: javascript.0 (10140)
2024-04-01 10:18:21.613 - error: javascript.0 (10140) WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
2024-04-01 10:18:22.440 - info: host.IOBroker-Server instance system.adapter.sql.0 started with pid 7900
2024-04-01 10:18:23.143 - info: host.IOBroker-Server instance system.adapter.alexa2.0 started with pid 608
2024-04-01 10:18:24.405 - error: alexa2.0 (608) alexa2.0 already running
2024-04-01 10:18:24.407 - warn: alexa2.0 (608) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:24.978 - error: host.IOBroker-Server instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:24.979 - info: host.IOBroker-Server Restart adapter system.adapter.alexa2.0 because enabled
2024-04-01 10:18:25.114 - warn: node-red.0 (2988) Node-RED: 1 Apr 10:18:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
2024-04-01 10:18:25.124 - warn: node-red.0 (2988) Node-RED: 1 Apr 10:18:25 - [warn] Encrypted credentials not found
2024-04-01 10:18:26.993 - info: host.IOBroker-Server instance system.adapter.telegram.2 started with pid 9196
2024-04-01 10:18:27.135 - info: host.IOBroker-Server instance system.adapter.sonos.0 started with pid 9292
2024-04-01 10:18:28.148 - error: sonos.0 (9292) sonos.0 already running
2024-04-01 10:18:28.150 - warn: sonos.0 (9292) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:28.705 - error: host.IOBroker-Server instance system.adapter.sonos.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:28.705 - info: host.IOBroker-Server Restart adapter system.adapter.sonos.0 because enabled
2024-04-01 10:18:30.558 - info: host.IOBroker-Server instance system.adapter.hm-rega.0 started with pid 8108
2024-04-01 10:18:31.121 - info: host.IOBroker-Server instance system.adapter.sun2000.0 started with pid 9608
2024-04-01 10:18:31.512 - info: hm-rega.0 (8108) starting. Version 4.0.0 in I:/ioBroker/node_modules/iobroker.hm-rega, node: v18.20.0, js-controller: 5.0.19
2024-04-01 10:18:31.574 - info: hm-rega.0 (8108) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2024-04-01 10:18:31.622 - info: hm-rega.0 (8108) ReGaHSS 192.168.1.100 up
2024-04-01 10:18:31.651 - info: hm-rega.0 (8108) time difference local-ccu 1s
2024-04-01 10:18:31.785 - info: hm-rega.0 (8108) request state values
2024-04-01 10:18:32.158 - error: sun2000.0 (9608) sun2000.0 already running
2024-04-01 10:18:32.159 - warn: sun2000.0 (9608) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:32.626 - info: hm-rega.0 (8108) Updated all datapoints
2024-04-01 10:18:32.720 - error: host.IOBroker-Server instance system.adapter.sun2000.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:32.720 - info: host.IOBroker-Server Restart adapter system.adapter.sun2000.0 because enabled
2024-04-01 10:18:32.767 - info: hm-rega.0 (8108) added/updated 1 objects
2024-04-01 10:18:32.779 - info: hm-rega.0 (8108) update rooms to enum.rooms
2024-04-01 10:18:34.609 - info: host.IOBroker-Server instance system.adapter.hm-rpc.0 started with pid 10168
2024-04-01 10:18:35.139 - info: host.IOBroker-Server instance system.adapter.zigbee.0 started with pid 8968
2024-04-01 10:18:35.319 - debug: hm-rpc.0 (10168) Redis Objects: Use Redis connection: 0.0.0.0:9001
2024-04-01 10:18:35.338 - debug: hm-rpc.0 (10168) Objects client ready ... initialize now
2024-04-01 10:18:35.339 - debug: hm-rpc.0 (10168) Objects create System PubSub Client
2024-04-01 10:18:35.339 - debug: hm-rpc.0 (10168) Objects create User PubSub Client
2024-04-01 10:18:35.361 - debug: hm-rpc.0 (10168) Objects client initialize lua scripts
2024-04-01 10:18:35.365 - debug: hm-rpc.0 (10168) Objects connected to redis: 0.0.0.0:9001
2024-04-01 10:18:35.382 - debug: hm-rpc.0 (10168) Redis States: Use Redis connection: 0.0.0.0:9000
2024-04-01 10:18:35.389 - debug: hm-rpc.0 (10168) States create System PubSub Client
2024-04-01 10:18:35.390 - debug: hm-rpc.0 (10168) States create User PubSub Client
2024-04-01 10:18:35.406 - debug: hm-rpc.0 (10168) States connected to redis: 0.0.0.0:9000
2024-04-01 10:18:35.425 - debug: hm-rpc.0 (10168) Plugin sentry Initialize Plugin (enabled=true)
2024-04-01 10:18:35.559 - info: hm-rpc.0 (10168) starting. Version 1.16.0 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v18.20.0, js-controller: 5.0.19
2024-04-01 10:18:35.613 - info: hm-rpc.0 (10168) xmlrpc server is trying to listen on 192.168.1.25:2001
2024-04-01 10:18:35.613 - info: hm-rpc.0 (10168) xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:18:35.614 - debug: hm-rpc.0 (10168) Connect...
2024-04-01 10:18:35.614 - debug: hm-rpc.0 (10168) xmlrpc -> 192.168.1.100:2001/ init ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:18:35.619 - debug: hm-rpc.0 (10168) start connecting interval
2024-04-01 10:18:35.631 - info: hm-rpc.0 (10168) xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:18:35.636 - info: hm-rpc.0 (10168) xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:18:35.637 - debug: hm-rpc.0 (10168) No suitable Lua script, fallback to keys!: function(doc) {
if (doc._id.match(/^hm-rpc\.[0-9]+\.\*?[A-Za-z0-9_-]+(\.[0-9]+)?$/)) {
emit(doc._id, {ADDRESS:(doc.native?doc.native.ADDRESS:''),VERSION:(doc.native?doc.native.VERSION:'')});
}
}
2024-04-01 10:18:35.654 - info: hm-rpc.0 (10168) xmlrpc -> 94 devices
2024-04-01 10:18:35.681 - info: hm-rpc.0 (10168) Connected
2024-04-01 10:18:35.682 - debug: hm-rpc.0 (10168) clear connecting interval
2024-04-01 10:18:35.682 - debug: hm-rpc.0 (10168) start ping interval
2024-04-01 10:18:35.682 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,LEQ0568108:0,STICKY_UNREACH,true
2024-04-01 10:18:35.682 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","LEQ0568108:0","STICKY_UNREACH",true]
2024-04-01 10:18:35.682 - debug: hm-rpc.0 (10168) hm-rpc.0.LEQ0568108.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,LEQ0796944:0,CONFIG_PENDING,true
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","LEQ0796944:0","CONFIG_PENDING",true]
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) hm-rpc.0.LEQ0796944.0.CONFIG_PENDING ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,LEQ1003243:0,STICKY_UNREACH,true
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","LEQ1003243:0","STICKY_UNREACH",true]
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) hm-rpc.0.LEQ1003243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:35.683 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,MEQ0641207:0,CONFIG_PENDING,true
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","MEQ0641207:0","CONFIG_PENDING",true]
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) hm-rpc.0.MEQ0641207.0.CONFIG_PENDING ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,OEQ0015243:0,STICKY_UNREACH,true
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","OEQ0015243:0","STICKY_UNREACH",true]
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) hm-rpc.0.OEQ0015243.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103,QEQ2009724:0,STICKY_UNREACH,true
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103","QEQ2009724:0","STICKY_UNREACH",true]
2024-04-01 10:18:35.684 - debug: hm-rpc.0 (10168) hm-rpc.0.QEQ2009724.0.STICKY_UNREACH ==> UNIT: "" (min: undefined, max: undefined) From "true" => "true"
2024-04-01 10:18:37.053 - error: zigbee.0 (8968) zigbee.0 already running
2024-04-01 10:18:37.055 - warn: zigbee.0 (8968) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:37.619 - error: host.IOBroker-Server instance system.adapter.zigbee.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:37.619 - info: host.IOBroker-Server Restart adapter system.adapter.zigbee.0 because enabled
2024-04-01 10:18:37.663 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,BOOT,true
2024-04-01 10:18:37.663 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","BOOT",true]
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.BOOT:true discarded, no matching device
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,ENERGY_COUNTER,91511.6
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","ENERGY_COUNTER",91511.6]
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.ENERGY_COUNTER:91511.6 discarded, no matching device
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,POWER,68.1
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","POWER",68.1]
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.POWER:68.1 discarded, no matching device
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,CURRENT,535
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","CURRENT",535]
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.CURRENT:535 discarded, no matching device
2024-04-01 10:18:37.664 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,VOLTAGE,226.1
2024-04-01 10:18:37.665 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","VOLTAGE",226.1]
2024-04-01 10:18:37.665 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.VOLTAGE:226.1 discarded, no matching device
2024-04-01 10:18:37.665 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0533995:2,FREQUENCY,49.97
2024-04-01 10:18:37.665 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0533995:2","FREQUENCY",49.97]
2024-04-01 10:18:37.665 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0533995.2.FREQUENCY:49.97 discarded, no matching device
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0568108:1,TEMPERATURE,9.7
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0568108:1","TEMPERATURE",9.7]
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0568108.1.TEMPERATURE:9.7 discarded, no matching device
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,LEQ0568108:1,HUMIDITY,89
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","LEQ0568108:1","HUMIDITY",89]
2024-04-01 10:18:37.669 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.LEQ0568108.1.HUMIDITY:89 discarded, no matching device
2024-04-01 10:18:38.385 - info: host.IOBroker-Server instance system.adapter.hm-rpc.1 started with pid 9832
2024-04-01 10:18:39.110 - info: host.IOBroker-Server instance system.adapter.discovery.0 started with pid 9932
2024-04-01 10:18:39.921 - error: discovery.0 (9932) discovery.0 already running
2024-04-01 10:18:39.922 - warn: discovery.0 (9932) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:40.479 - error: host.IOBroker-Server instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:40.479 - info: host.IOBroker-Server Restart adapter system.adapter.discovery.0 because enabled
2024-04-01 10:18:43.769 - info: host.IOBroker-Server instance system.adapter.info.0 started with pid 5448
2024-04-01 10:18:45.203 - error: info.0 (5448) info.0 already running
2024-04-01 10:18:45.204 - warn: info.0 (5448) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:45.763 - error: host.IOBroker-Server instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:45.763 - info: host.IOBroker-Server Restart adapter system.adapter.info.0 because enabled
2024-04-01 10:18:47.134 - info: host.IOBroker-Server instance system.adapter.simple-api.0 started with pid 1712
2024-04-01 10:18:48.103 - error: simple-api.0 (1712) simple-api.0 already running
2024-04-01 10:18:48.105 - warn: simple-api.0 (1712) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:48.664 - error: host.IOBroker-Server instance system.adapter.simple-api.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:48.664 - info: host.IOBroker-Server Restart adapter system.adapter.simple-api.0 because enabled
2024-04-01 10:18:49.723 - info: host.IOBroker-Server instance system.adapter.simple-api.0 started with pid 3944
2024-04-01 10:18:50.658 - warn: simple-api.0 (3944) Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
2024-04-01 10:18:50.692 - debug: hm-rpc.0 (10168) [KEEPALIVE] Check if connection is alive
2024-04-01 10:18:50.693 - debug: hm-rpc.0 (10168) Send PING...
2024-04-01 10:18:50.700 - debug: hm-rpc.0 (10168) PING ok
2024-04-01 10:18:50.702 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,CENTRAL,PONG,IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103
2024-04-01 10:18:50.702 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","CENTRAL","PONG","IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:18:50.702 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.CENTRAL.PONG:IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103 discarded, no matching device
2024-04-01 10:18:50.935 - info: host.IOBroker-Server instance system.adapter.synology.0 started with pid 7464
2024-04-01 10:18:51.122 - info: host.IOBroker-Server instance system.adapter.web.0 started with pid 3472
2024-04-01 10:18:52.126 - error: web.0 (3472) web.0 already running
2024-04-01 10:18:52.127 - warn: web.0 (3472) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:52.675 - error: host.IOBroker-Server instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:52.675 - info: host.IOBroker-Server Restart adapter system.adapter.web.0 because enabled
2024-04-01 10:18:55.017 - info: host.IOBroker-Server instance system.adapter.alexa2.0 started with pid 1060
2024-04-01 10:18:55.094 - info: host.IOBroker-Server instance system.adapter.yahka.2 started with pid 7880
2024-04-01 10:18:56.492 - error: yahka.2 (7880) yahka.2 already running
2024-04-01 10:18:56.494 - warn: yahka.2 (7880) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:18:57.065 - error: host.IOBroker-Server instance system.adapter.yahka.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:18:57.065 - info: host.IOBroker-Server Restart adapter system.adapter.yahka.2 because enabled
2024-04-01 10:18:58.745 - info: host.IOBroker-Server instance system.adapter.sonos.0 started with pid 8608
2024-04-01 10:18:59.140 - info: host.IOBroker-Server instance system.adapter.jarvis.0 started with pid 6704
2024-04-01 10:19:00.611 - error: jarvis.0 (6704) jarvis.0 already running
2024-04-01 10:19:00.611 - warn: jarvis.0 (6704) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:19:01.161 - error: host.IOBroker-Server instance system.adapter.jarvis.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:19:01.161 - info: host.IOBroker-Server Restart adapter system.adapter.jarvis.0 because enabled
2024-04-01 10:19:02.763 - info: host.IOBroker-Server instance system.adapter.sun2000.0 started with pid 9364
2024-04-01 10:19:03.111 - info: host.IOBroker-Server instance system.adapter.socketio.0 started with pid 8308
2024-04-01 10:19:04.146 - error: socketio.0 (8308) socketio.0 already running
2024-04-01 10:19:04.148 - warn: socketio.0 (8308) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:19:04.682 - error: host.IOBroker-Server instance system.adapter.socketio.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:19:04.682 - info: host.IOBroker-Server Restart adapter system.adapter.socketio.0 because enabled
2024-04-01 10:19:05.692 - debug: hm-rpc.0 (10168) [KEEPALIVE] Check if connection is alive
2024-04-01 10:19:05.692 - debug: hm-rpc.0 (10168) Send PING...
2024-04-01 10:19:05.700 - debug: hm-rpc.0 (10168) PING ok
2024-04-01 10:19:05.702 - debug: hm-rpc.0 (10168) xml multicall : IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67,CENTRAL,PONG,IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103
2024-04-01 10:19:05.702 - debug: hm-rpc.0 (10168) xmlrpc <- event ["IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67","CENTRAL","PONG","IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103"]
2024-04-01 10:19:05.702 - debug: hm-rpc.0 (10168) xmlrpc <- event: IOBroker-Server:hm-rpc.0:7cec1d0f2b415e054a707b064790aa67.CENTRAL.PONG:IOBroker-Server:hm-rpc.0:27432cc944a84b163a8c42e6a2ea8103 discarded, no matching device
2024-04-01 10:19:07.126 - info: host.IOBroker-Server instance system.adapter.ws.0 started with pid 9612
2024-04-01 10:19:07.675 - info: host.IOBroker-Server instance system.adapter.zigbee.0 started with pid 3680
2024-04-01 10:19:08.106 - error: ws.0 (9612) ws.0 already running
2024-04-01 10:19:08.108 - warn: ws.0 (9612) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:19:08.756 - error: host.IOBroker-Server instance system.adapter.ws.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:19:08.756 - info: host.IOBroker-Server Restart adapter system.adapter.ws.0 because enabled
2024-04-01 10:19:10.524 - info: host.IOBroker-Server instance system.adapter.discovery.0 started with pid 3152
2024-04-01 10:19:11.080 - info: host.IOBroker-Server instance system.adapter.echarts.0 started with pid 9748
2024-04-01 10:19:11.993 - error: echarts.0 (9748) echarts.0 already running
2024-04-01 10:19:11.994 - warn: echarts.0 (9748) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:19:12.556 - error: host.IOBroker-Server instance system.adapter.echarts.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:19:12.557 - info: host.IOBroker-Server Restart adapter system.adapter.echarts.0 because enabled
2024-04-01 10:19:13.069 - warn: zigbee.0 (3680) DeviceConfigure: 0x680ae2fffe121dcf TRADFRI on/off switch Failed to configure. When device works is all fine when not wake up the device and check again
2024-04-01 10:19:15.126 - info: host.IOBroker-Server instance system.adapter.windows-control.0 started with pid 2144
2024-04-01 10:19:15.823 - info: host.IOBroker-Server instance system.adapter.info.0 started with pid 2644
2024-04-01 10:19:15.836 - error: windows-control.0 (2144) windows-control.0 already running
2024-04-01 10:19:15.837 - warn: windows-control.0 (2144) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:19:16.446 - error: host.IOBroker-Server instance system.adapter.windows-control.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:19:16.446 - info: host.IOBroker-Server Restart adapter system.adapter.windows-control.0 because enabled

bahnuhr

@surfer09
wie gesagt; diesen Fehler hatte ich noch nie.

Er wird aber offensichtlich nur bei debug ausgewiesen.
Was kommt denn, wenn du auf Info gehst.

surfer09

@bahnuhr Mit Info sieht das so aus nach Neustart

024-04-01 10:35:21.039 - info: hm-rega.0 (9240) starting. Version 4.0.0 in I:/ioBroker/node_modules/iobroker.hm-rega, node: v18.20.0, js-controller: 5.0.19
2024-04-01 10:35:21.096 - info: hm-rega.0 (9240) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2024-04-01 10:35:21.147 - info: hm-rega.0 (9240) ReGaHSS 192.168.1.100 up
2024-04-01 10:35:21.178 - info: hm-rega.0 (9240) time difference local-ccu 0s
2024-04-01 10:35:21.315 - info: hm-rega.0 (9240) request state values
2024-04-01 10:35:21.384 - error: host.IOBroker-Server cannot call visUtils: Not exists
2024-04-01 10:35:21.894 - error: sun2000.0 (6404) sun2000.0 already running
2024-04-01 10:35:21.895 - warn: sun2000.0 (6404) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-04-01 10:35:22.152 - info: hm-rega.0 (9240) Updated all datapoints
2024-04-01 10:35:22.264 - info: hm-rega.0 (9240) added/updated 1 objects
2024-04-01 10:35:22.275 - info: hm-rega.0 (9240) update rooms to enum.rooms
2024-04-01 10:35:22.440 - error: host.IOBroker-Server instance system.adapter.sun2000.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-04-01 10:35:22.441 - info: host.IOBroker-Server Restart adapter system.adapter.sun2000.0 because enabled
2024-04-01 10:35:24.195 - info: host.IOBroker-Server instance system.adapter.hm-rpc.0 started with pid 9280
2024-04-01 10:35:24.764 - info: host.IOBroker-Server instance system.adapter.zigbee.0 started with pid 3708
2024-04-01 10:35:25.055 - info: hm-rpc.0 (9280) starting. Version 1.16.0 in I:/ioBroker/node_modules/iobroker.hm-rpc, node: v18.20.0, js-controller: 5.0.19
2024-04-01 10:35:25.118 - info: hm-rpc.0 (9280) xmlrpc server is trying to listen on 192.168.1.25:2001
2024-04-01 10:35:25.119 - info: hm-rpc.0 (9280) xmlrpc client is trying to connect to 192.168.1.100:2001/ with ["http://192.168.1.25:2001","IOBroker-Server:hm-rpc.0:7b460713fdc3b2fbb893549b6d0365ac"]
2024-04-01 10:35:25.135 - info: hm-rpc.0 (9280) xmlrpc <- system.listMethods ["IOBroker-Server:hm-rpc.0:7b460713fdc3b2fbb893549b6d0365ac"]
2024-04-01 10:35:25.140 - info: hm-rpc.0 (9280) xmlrpc <- listDevices ["IOBroker-Server:hm-rpc.0:7b460713fdc3b2fbb893549b6d0365ac"]
2024-04-01 10:35:25.159 - info: hm-rpc.0 (9280) xmlrpc -> 94 devices
2024-04-01 10:35:25.187 - info: hm-rpc.0 (9280) Connected

bahnuhr

@surfer09
zumindest ist das "no matching" weg.

Kann dir nicht sagen, was das ist.
Hatte meine HM Adapter noch nie (glaub ich) auf debug.

mfg

surfer09

@bahnuhr OKay ich denke, ich tausche dann im ersten Schott mal die Funkschnittstelle aus gegen die Tasterschnittstelle. Mal sehen, ob das damit besser wird.

bahnuhr

@surfer09
Ja, mach das.
Bei mir keine Probleme damit.

haselchen

@surfer09 sagte in Lösung für Türklingel:

@bahnuhr OKay ich denke, ich tausche dann im ersten Schott mal die Funkschnittstelle aus gegen die Tasterschnittstelle. Mal sehen, ob das damit besser wird.

Zusätzlich, einfach nur um mal alles beleuchtet zu haben,
hast Du im HM-Rega Polling aktiviert?
Wenn ja, wieviel Sekunden?
Dann im HM-RPC :

Habe ich die Standardintervalle gelassen.
Kann ja evtl. sein, dass deine gewählte Zeit zu Problemen führt.

Das sind so die Unterschiede, die ich zu meinen Einstellungen feststellen konnte.

Marc Berg

@surfer09

Da es sich um eine Art von Timing Problem zu handeln scheint, wenn die Fehler nach einem Adapter-Neustart nicht mehr auftreten, hätte ich noch die Idee, an der Startreihenfolge des Adapters zu schrauben. Standardmäßig wird der hm-rpc Adapter als "Data Provider" eingestuft. Wenn du das auf 3 (Other) änderst, startet der Adapter später in der Reihenfolge. Vielleicht bringt das was?

EDIT: falsch referenziert

haselchen

@marc-berg

Ich bin nicht derjenige mit dem Problem ;)

surfer09

@marc-berg Ich teste das mal aus! Danke für den Tipp!

haselchen

@surfer09

Ja ,ne, ich hab einfach aus Langeweile geschrieben 😂
Vielleicht probierst Du es auch mal aus oder antwortest zumindest 😉

surfer09

@haselchen Dickes Sorry, hatte deine Antwort überlesen. Aber jetzt!

Wo kann ich das Polling im HM-Rega aktivieren/prüfen?
Die Anpassung vom Interval unter RM-RPC ändert nichts an dem Verhalten. Das habe ich gerade getestet.

surfer09

@marc-berg Habe ich auch gerade getestet. Das bringt leider auch keinen Erfolg. Nach Neustart immer noch das gleiche Problem.

emil70

@surfer09

in der Instanzeinstellungen: hm-rega.0 ganz unten

Screenshot 2024-04-02 at 18-56-42 instances - f7c478effa45.png

surfer09

Ich habe mir jetzt eine Tasterschnittstelle besorgt, ich bin mir jetzt aber nicht sicher, wie das Ganze zu verkabeln ist. Die Bilder der Türklingel hatte ich ja schon gepostet. Kann mir da vielleicht nochmal jemand helfen?

bahnuhr

@surfer09
Ei, du hast doch als Klingel einen normalen Taster

Also:
Taster Klingel Abgang A -> HM Com
Taster Klingel Abgang B -> HM E1

Und dann mit Multimeter prüfen ob dies klappt.
Alternativ in der ccu schauen ob dies funktioniert.

surfer09

@bahnuhr: Ja, das sind Taster.
Also würde ich jetzt grün/weiß auf COM und braun/weiß auf E1 setzen und orange/weiß auch auf COM und blau/weiß auf E2? Sorry, ich muss das für Doofe erklärt haben, bin kein Elektriker :face_with_rolling_eyes:

bahnuhr

@surfer09 sagte in Lösung für Türklingel:

bin kein Elektriker

ich auch nicht. Also keine Gewähr.

Erklär doch mal warum an jedem Anschluss 2 Kabel sind.
Wurde ja schon einmal gefragt (glaub ich).

Community Forum

NEWS

Lösung für Türklingel

Support us

601

32.6k

82.3k

1.3m