Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Homoran]

@searcher57 sagte in FritzBox Zigbee Antenne in ioBroker einbinden?:

Bitte erkläre das!

Jetzt bin ich überfordert, was genau bedarf zusätzlicher Erklärung?

[searcher57]

@searcher57 said in FritzBox Zigbee Antenne in ioBroker einbinden?:

@homoran said in FritzBox Zigbee Antenne in ioBroker einbinden?:

@searcher57 sagte in FritzBox Zigbee Antenne in ioBroker einbinden?:

Hier das Protokoll:

bitte keinen Screenshot!
als Text in code-tags posten.

Bitte erkläre das!

v7.6.3
233

Log-Größe: 439.1 KB
Zeit
	
smartmeter.0
	2025-05-07 18:18:49.740	info	Received 13 values, 8 updated
host.Raspi58GB
	2025-05-07 18:16:52.611	info	instance system.adapter.openweathermap.0 having pid 2720211 terminated with code 0 (NO_ERROR)
openweathermap.0
	2025-05-07 18:16:52.102	info	Terminated (NO_ERROR): Without reason
openweathermap.0
	2025-05-07 18:16:43.181	info	starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 18:16:42.020	info	instance system.adapter.openweathermap.0 in version "1.1.2" started with pid 2720211
awtrix-light.0
	2025-05-07 18:15:45.576	info	error ECONNABORTED from stats: timeout of 3000ms exceeded
smartmeter.0
	2025-05-07 18:13:46.108	info	Received 13 values, 8 updated
smartmeter.0
	2025-05-07 18:08:42.387	info	Received 13 values, 8 updated
smartmeter.0
	2025-05-07 18:03:38.767	info	Received 13 values, 6 updated
smartmeter.0
	2025-05-07 17:58:37.701	info	Received 13 values, 6 updated
smartmeter.0
	2025-05-07 17:53:36.342	info	Received 13 values, 6 updated
zigbee.0
	2025-05-07 17:50:17.995	info	Starting Zigbee-Herdsman
zigbee.0
	2025-05-07 17:50:17.994	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
zigbee.0
	2025-05-07 17:50:17.978	info	Starting Adapter npm ...
zigbee.0
	2025-05-07 17:50:17.977	info	--- creating device debug ---
zigbee.0
	2025-05-07 17:50:17.972	info	--> transmitPower : normal
zigbee.0
	2025-05-07 17:50:17.969	info	init localConfig
zigbee.0
	2025-05-07 17:50:17.959	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:50:16.818	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2716727
host.Raspi58GB
	2025-05-07 17:50:13.485	info	instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
zigbee.0
	2025-05-07 17:50:13.441	info	terminating
host.Raspi58GB
	2025-05-07 17:50:13.008	info	stopInstance system.adapter.zigbee.0 send kill signal
zigbee.0
	2025-05-07 17:50:12.988	info	terminating
zigbee.0
	2025-05-07 17:50:12.988	warn	Failed to stop zigbee during startup
zigbee.0
	2025-05-07 17:50:12.987	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
zigbee.0
	2025-05-07 17:50:12.940	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
zigbee.0
	2025-05-07 17:50:12.939	info	terminating
zigbee.0
	2025-05-07 17:50:12.938	info	Saved local configuration data
zigbee.0
	2025-05-07 17:50:12.937	info	local config saved
zigbee.0
	2025-05-07 17:50:12.936	info	cleaned everything up...
zigbee.0
	2025-05-07 17:50:12.935	info	Got terminate signal TERMINATE_YOURSELF
host.Raspi58GB
	2025-05-07 17:50:12.932	info	stopInstance system.adapter.zigbee.0 (force=false, process=true)
zigbee.0
	2025-05-07 17:50:07.445	info	Starting Zigbee-Herdsman
zigbee.0
	2025-05-07 17:50:07.444	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
zigbee.0
	2025-05-07 17:50:07.428	info	Starting Adapter npm ...
zigbee.0
	2025-05-07 17:50:07.427	info	--- creating device debug ---
zigbee.0
	2025-05-07 17:50:07.422	info	--> transmitPower : normal
zigbee.0
	2025-05-07 17:50:07.419	info	init localConfig
zigbee.0
	2025-05-07 17:50:07.409	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:50:06.159	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2716711
admin.0
	2025-05-07 17:49:59.324	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120
host.Raspi58GB
	2025-05-07 17:49:35.710	info	Restart adapter system.adapter.zigbee.0 because enabled
host.Raspi58GB
	2025-05-07 17:49:35.710	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at processImmediate (node:internal/timers:483:21)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at Zigbee.emit (node:domain:489:12)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at Zigbee.emit (node:events:536:35)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97)
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'CleanupRequired')
host.Raspi58GB
	2025-05-07 17:49:35.710	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
zigbee.0
	2025-05-07 17:49:35.667	info	terminating
zigbee.0
	2025-05-07 17:49:35.191	info	terminating
zigbee.0
	2025-05-07 17:49:35.191	warn	Failed to stop zigbee during startup
zigbee.0
	2025-05-07 17:49:35.187	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
zigbee.0
	2025-05-07 17:49:35.167	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0
	2025-05-07 17:49:35.167	info	terminating
zigbee.0
	2025-05-07 17:49:35.166	info	Saved local configuration data
zigbee.0
	2025-05-07 17:49:35.165	info	local config saved
zigbee.0
	2025-05-07 17:49:35.165	info	cleaned everything up...
zigbee.0
	2025-05-07 17:49:35.151	error	Cannot read properties of undefined (reading 'CleanupRequired')
zigbee.0
	2025-05-07 17:49:35.150	error	TypeError: Cannot read properties of undefined (reading 'CleanupRequired') at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:155:97) at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:20:48) at Zigbee.emit (node:events:536:35) at Zigbee.emit (node:domain:489:12) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10953:34) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:368:37) at processImmediate (node:internal/timers:483:21)
zigbee.0
	2025-05-07 17:49:35.031	error	unhandled promise rejection: Cannot read properties of undefined (reading 'CleanupRequired')
zigbee.0
	2025-05-07 17:49:35.031	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
admin.0
	2025-05-07 17:49:34.977	info	==> Connected system.user.admin from ::ffff:192.168.178.120
web.0
	2025-05-07 17:49:29.651	info	socket.io server listening on port 8082
web.0
	2025-05-07 17:49:29.562	info	http server listening on port 8082
web.0
	2025-05-07 17:49:29.444	info	starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:49:28.305	info	instance system.adapter.web.0 in version "7.0.8" started with pid 2716693
vis-2.0
	2025-05-07 17:49:25.387	info	vis-2 license is OK.
vis-2.0
	2025-05-07 17:49:25.212	info	starting. Version 2.9.64 in /opt/iobroker/node_modules/iobroker.vis-2, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:49:24.266	info	instance system.adapter.vis-2.0 in version "2.9.64" started with pid 2716678
text2command.0
	2025-05-07 17:49:21.593	info	starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.text2command, node: v20.19.1, js-controller: 7.0.6
tankerkoenig.0
	2025-05-07 17:49:20.815	info	Start first request
host.Raspi58GB
	2025-05-07 17:49:20.263	info	instance system.adapter.text2command.0 in version "3.0.3" started with pid 2716641
shelly.1
	2025-05-07 17:49:19.622	info	[MQTT] Device with client id "shellyplusplugs-b0b21c0ec52c" connected from 192.168.178.100!
tankerkoenig.0
	2025-05-07 17:49:17.228	info	Sync time set to 30 minutes or 1800000 ms
tankerkoenig.0
	2025-05-07 17:49:17.228	info	Adapter is already in daemon mode
tankerkoenig.0
	2025-05-07 17:49:17.209	info	starting. Version 3.4.0 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:49:16.258	info	instance system.adapter.tankerkoenig.0 in version "3.4.0" started with pid 2716626
simple-api.0
	2025-05-07 17:49:13.410	info	http server listening on port 8087
simple-api.0
	2025-05-07 17:49:13.403	info	Allow states only when user is owner: false
simple-api.0
	2025-05-07 17:49:13.402	info	simpleAPI server listening on port 8087
simple-api.0
	2025-05-07 17:49:13.391	info	starting. Version 2.8.0 in /opt/iobroker/node_modules/iobroker.simple-api, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:49:12.374	info	instance system.adapter.simple-api.0 in version "2.8.0" started with pid 2716611
host.Raspi58GB
	2025-05-07 17:49:12.321	info	instance system.adapter.yr.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
yr.0
	2025-05-07 17:49:11.492	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
yr.0
	2025-05-07 17:49:11.492	info	Data updated.
iot.0
	2025-05-07 17:49:10.166	info	Connection changed: connect "wolff_netphen_web_de"
iot.0
	2025-05-07 17:49:09.557	info	Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
iot.0
	2025-05-07 17:49:09.511	info	starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.iot, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:49:08.279	info	instance system.adapter.iot.0 in version "3.3.0" started with pid 2716594
fritzdect.0
	2025-05-07 17:49:08.240	error	login not possible, check user and permissions
fritzdect.0
	2025-05-07 17:49:08.239	error	API err => {"msg":"failed to get challenge","function":"get_sid","error":{"msg":"failed to login","function":"send_response","error":{"msg":"failed to login, wrong user name or password","function":"send_response","error":"0000000000000000"}}}
fritzdect.0
	2025-05-07 17:49:08.239	error	no response part in returned error message
fritzdect.0
	2025-05-07 17:49:08.239	error	API funct => login_SID
fritzdect.0
	2025-05-07 17:49:08.238	error	API msg => error calling executeCommand
fritzdect.0
	2025-05-07 17:49:08.237	error	--------------- error calling the fritzbox -----------
fritzdect.0
	2025-05-07 17:49:06.316	info	fritzdect uses USER: admin
fritzdect.0
	2025-05-07 17:49:06.300	info	fritzdect entered ready
fritzdect.0
	2025-05-07 17:49:06.286	info	starting. Version 2.6.1 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v20.19.1, js-controller: 7.0.6
shelly.1
	2025-05-07 17:49:05.550	info	[MQTT] Device with client id "shellyplusplugs-d48afc7b9540" connected from 192.168.178.96!
shelly.1
	2025-05-07 17:49:05.278	info	[MQTT] Device with client id "shellyplusplugs-e465b8b302bc" connected from 192.168.178.95!
host.Raspi58GB
	2025-05-07 17:49:05.003	info	instance system.adapter.fritzdect.0 in version "2.6.1" started with pid 2716579
followthesun.0
	2025-05-07 17:49:03.027	info	Daily sun parameter calculation scheduled for 00:00:36
followthesun.0
	2025-05-07 17:49:03.026	info	Sun position calculation will be done every 60 seconds
followthesun.0
	2025-05-07 17:49:03.025	info	Started with JSON-Explorer version 0.1.16
followthesun.0
	2025-05-07 17:49:03.014	info	starting. Version 0.5.2 in /opt/iobroker/node_modules/iobroker.followthesun, node: v20.19.1, js-controller: 7.0.6
shelly.1
	2025-05-07 17:49:01.927	info	[MQTT] Device with client id "shellyplusplugs-e465b8456ff4" connected from 192.168.178.98!
host.Raspi58GB
	2025-05-07 17:49:01.537	info	instance system.adapter.followthesun.0 in version "0.5.2" started with pid 2716564
shelly.1
	2025-05-07 17:49:00.901	info	[MQTT] Device with client id "shellyplusplugs-b0b21c1243bc" connected from 192.168.178.102!
shelly.1
	2025-05-07 17:48:56.540	info	[MQTT] Device with client id "shellyplusplugs-d48afc7a4830" connected from 192.168.178.97!
echarts.0
	2025-05-07 17:48:54.613	info	starting. Version 1.9.2 in /opt/iobroker/node_modules/iobroker.echarts, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:53.726	info	instance system.adapter.echarts.0 in version "1.9.2" started with pid 2716549
doorbird.0
	2025-05-07 17:48:51.398	info	starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.doorbird, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:50.532	info	instance system.adapter.doorbird.0 in version "3.0.0" started with pid 2716534
discovery.0
	2025-05-07 17:48:47.316	info	starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.19.1, js-controller: 7.0.6
shelly.1
	2025-05-07 17:48:46.772	info	[MQTT] Device with client id "shellyplus1pm-d48afc598e4c" connected from 192.168.178.94!
host.Raspi58GB
	2025-05-07 17:48:46.199	info	instance system.adapter.discovery.0 in version "5.0.0" started with pid 2716519
zigbee.0
	2025-05-07 17:48:45.452	info	Starting Zigbee-Herdsman
zigbee.0
	2025-05-07 17:48:45.451	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
zigbee.0
	2025-05-07 17:48:45.436	info	Starting Adapter npm ...
zigbee.0
	2025-05-07 17:48:45.435	info	--- creating device debug ---
zigbee.0
	2025-05-07 17:48:45.430	info	--> transmitPower : normal
zigbee.0
	2025-05-07 17:48:45.427	info	init localConfig
zigbee.0
	2025-05-07 17:48:45.418	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:44.243	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2716503
awtrix-light.0
	2025-05-07 17:48:42.443	info	Starting - connecting to http://192.168.178.83:80/
awtrix-light.0
	2025-05-07 17:48:42.348	info	starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.awtrix-light, node: v20.19.1, js-controller: 7.0.6
yr.0
	2025-05-07 17:48:41.778	info	longitude/longitude will be set by self-Config - longitude: 7.0362624235667255 latitude: 50.622376836807405
yr.0
	2025-05-07 17:48:41.757	info	starting. Version 5.3.0 in /opt/iobroker/node_modules/iobroker.yr, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:40.856	info	instance system.adapter.awtrix-light.0 in version "1.7.0" started with pid 2716484
shelly.0
	2025-05-07 17:48:40.312	info	[CoAP] Device 192.168.178.45 (shelly1pm / shelly1pm-E09806A9FFDF / SHSW-PM#E09806A9FFDF#1) connected! Polltime set to 15 sec.
host.Raspi58GB
	2025-05-07 17:48:40.264	info	instance system.adapter.yr.0 in version "5.3.0" started with pid 2716473
host.Raspi58GB
	2025-05-07 17:48:40.260	info	instance scheduled system.adapter.yr.0 40 * * * *
shelly.0
	2025-05-07 17:48:38.797	info	[CoAP] Device 192.168.178.88 (shelly1pm / shelly1pm-C45BBE6A38D2 / SHSW-PM#C45BBE6A38D2#1) connected! Polltime set to 15 sec.
tr-064.0
	2025-05-07 17:48:37.888	info	starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.tr-064, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:37.165	info	instance system.adapter.openweathermap.0 terminated with code 0 (NO_ERROR)
openweathermap.0
	2025-05-07 17:48:36.607	info	Terminated (NO_ERROR): Without reason
host.Raspi58GB
	2025-05-07 17:48:36.367	info	instance system.adapter.tr-064.0 in version "4.3.0" started with pid 2716458
shelly.0
	2025-05-07 17:48:36.162	info	[CoAP] Device 192.168.178.43 (shellyplug-s / shellyplug-s-B52D91 / SHPLG-S#B52D91#1) connected! Polltime set to 15 sec.
shelly.0
	2025-05-07 17:48:36.059	info	[CoAP] Device 192.168.178.60 (shelly1pm / shelly1pm-349454783D53 / SHSW-PM#349454783D53#1) connected! Polltime set to 15 sec.
smartmeter.0
	2025-05-07 17:48:35.723	info	Received 13 values, 13 updated
smartmeter.0
	2025-05-07 17:48:34.915	info	starting. Version 3.4.0 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:32.604	info	instance system.adapter.smartmeter.0 in version "3.4.0" started with pid 2716443
host.Raspi58GB
	2025-05-07 17:48:31.167	error	cannot call visUtils: Not exists
shelly.0
	2025-05-07 17:48:30.940	info	[CoAP] Device 192.168.178.37 (shellyem3 / shellyem3-E89F6D84ABB5 / SHEM-3#E89F6D84ABB5#1) connected! Polltime set to 15 sec.
admin.0
	2025-05-07 17:48:30.856	info	==> Connected system.user.admin from ::ffff:192.168.178.120
shelly.0
	2025-05-07 17:48:30.001	info	[CoAP] Device 192.168.178.61 (shelly1pm / shelly1pm-34945475C0D4 / SHSW-PM#34945475C0D4#1) connected! Polltime set to 15 sec.
shelly.0
	2025-05-07 17:48:29.875	info	[CoAP] Device 192.168.178.27 (shellyplug-s / shellyplug-s-B4BD04 / SHPLG-S#B4BD04#1) connected! Polltime set to 15 sec.
shelly.1
	2025-05-07 17:48:29.832	info	Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
shelly.0
	2025-05-07 17:48:29.687	info	[CoAP] Device 192.168.178.59 (shelly1pm / shelly1pm-349454783F33 / SHSW-PM#349454783F33#1) connected! Polltime set to 15 sec.
shelly.1
	2025-05-07 17:48:29.372	info	starting. Version 9.2.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.19.1, js-controller: 7.0.6
shelly.0
	2025-05-07 17:48:29.178	info	[CoAP] Device 192.168.178.73 (shellygas / shellygas-3C6105F68FE8 / SHGS-1#3C6105F68FE8#1) connected! Polltime set to 3600 sec.
host.Raspi58GB
	2025-05-07 17:48:28.258	info	instance system.adapter.shelly.1 in version "9.2.0" started with pid 2716414
shelly.0
	2025-05-07 17:48:25.830	info	[CoAP Server] Listening for packets in the network
shelly.0
	2025-05-07 17:48:25.805	info	Starting in CoAP mode. Listening on 192.168.178.57:5683
shelly.0
	2025-05-07 17:48:25.601	info	starting. Version 9.2.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:24.254	info	instance system.adapter.shelly.0 in version "9.2.0" started with pid 2716395
rpi2.0
	2025-05-07 17:48:21.210	info	starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:20.281	info	instance system.adapter.rpi2.0 in version "2.4.0" started with pid 2716354
openweathermap.0
	2025-05-07 17:48:17.307	info	starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 17:48:16.284	info	instance system.adapter.openweathermap.0 in version "1.1.2" started with pid 2716339
host.Raspi58GB
	2025-05-07 17:48:16.280	info	instance scheduled system.adapter.openweathermap.0 16 * * * *
mqtt.0
	2025-05-07 17:48:14.052	info	All states published
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.ws
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.sys
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.plugs_ui
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.ffs
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.ble
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.events.rpc
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.ws
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.online
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.cloud
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.mqtt
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.switch:0
mqtt.0
	2025-05-07 17:48:13.444	info	Publishing state mqtt.0.shellyplusplugs-e465b8b302bc.status.wifi
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.sys
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.plugs_ui
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.ffs
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.ble
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.events.rpc
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.wifi
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.switch:0
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.plugs_ui
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.sys
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.ws
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.online
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.cloud
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.mqtt
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.switch:0
mqtt.0
	2025-05-07 17:48:13.443	info	Publishing state mqtt.0.shellyplusplugs-e465b8456ff4.status.wifi
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.ffs
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.ble
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.shellyplus1pm-d48afc598e4c.status
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.events.rpc
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.wifi
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.switch:0
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.mqtt
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.ffs
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.plugs_ui
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.sys
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.ws
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.online
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.shellyplus1pm-d48afc598e4c.status.on
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.cloud
mqtt.0
	2025-05-07 17:48:13.442	info	Publishing state mqtt.0.shellyplusplugs-d48afc7b9540.status.mqtt
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.ble
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.events.rpc
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.wifi
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.switch:0
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.mqtt
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.ffs
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.plugs_ui
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.sys
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-b0b21c1243bc.status.ws
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.online
mqtt.0
	2025-05-07 17:48:13.441	info	Publishing state mqtt.0.shellyplusplugs-d48afc7a4830.status.cloud

[Asgothian]

@searcher57 Dein Log zeigt das du den Adapter angehalten hast bevor das Zigbee-Subsystem vollständig gestartet war. Besagter Start kann insbesondere bei einem ersten Start mit 'neuer' Konifiguration bis zu 5 Minuten dauern.

Bitte folgendes machen:

• Zigbee Adapter anhalten.
• 60 s Warten
• Log löschen
• Zigbee Adapter starten
• Umschalten auf die Log-Ansicht
• Abwarten bis einer von 2 Events eintritt:
  -- Fehlermeldung das der Adapter nicht gestartet werden kann
  -- Meldung das der Adapter erfolgreich gestartet wurde.

Besagte Meldungen dann hier posten.

A.

[searcher57]

@asgothian said in FritzBox Zigbee Antenne in ioBroker einbinden?:

@searcher57 Dein Log zeigt das du den Adapter angehalten hast bevor das Zigbee-Subsystem vollständig gestartet war. Besagter Start kann insbesondere bei einem ersten Start mit 'neuer' Konifiguration bis zu 5 Minuten dauern.

Bitte folgendes machen:

• Zigbee Adapter anhalten.
• 60 s Warten
• Log löschen
• Zigbee Adapter starten
• Umschalten auf die Log-Ansicht
• Abwarten bis einer von 2 Events eintritt:
  -- Fehlermeldung das der Adapter nicht gestartet werden kann
  -- Meldung das der Adapter erfolgreich gestartet wurde.

Besagte Meldungen dann hier posten.

A.

Ich hoffe, dass ich nicht wieder zu ungeduldig war!

admin.0
	2025-05-07 19:33:41.984	info	==> Connected system.user.admin from ::ffff:192.168.178.120
admin.0
	2025-05-07 19:33:41.530	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120 admin
admin.0
	2025-05-07 19:33:41.525	info	==> Connected system.user.admin from ::ffff:192.168.178.120
admin.0
	2025-05-07 19:33:41.483	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120 admin
smartmeter.0
	2025-05-07 19:29:29.882	info	Received 13 values, 4 updated
smartmeter.0
	2025-05-07 19:24:25.886	info	Received 13 values, 6 updated
host.Raspi58GB
	2025-05-07 19:22:42.280	error	cannot call visUtils: Not exists
admin.0
	2025-05-07 19:22:42.049	info	==> Connected system.user.admin from ::ffff:192.168.178.120
admin.0
	2025-05-07 19:22:41.610	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120 admin
admin.0
	2025-05-07 19:22:41.602	info	==> Connected system.user.admin from ::ffff:192.168.178.120
admin.0
	2025-05-07 19:22:41.549	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120 admin
smartmeter.0
	2025-05-07 19:19:25.076	info	Received 13 values, 6 updated
admin.0
	2025-05-07 19:18:55.025	info	<== Disconnect system.user.admin from ::ffff:192.168.178.120 javascript
admin.0
	2025-05-07 19:18:53.355	info	==> Connected system.user.admin from ::ffff:192.168.178.120
host.Raspi58GB
	2025-05-07 19:16:51.969	info	instance system.adapter.openweathermap.0 having pid 2721694 terminated with code 0 (NO_ERROR)
openweathermap.0
	2025-05-07 19:16:51.460	info	Terminated (NO_ERROR): Without reason
openweathermap.0
	2025-05-07 19:16:43.034	info	starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 19:16:42.019	info	instance system.adapter.openweathermap.0 in version "1.1.2" started with pid 2721694
smartmeter.0
	2025-05-07 19:14:21.120	info	Received 13 values, 4 updated
zigbee.0
	2025-05-07 19:12:59.441	info	Starting Zigbee-Herdsman
zigbee.0
	2025-05-07 19:12:59.440	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
zigbee.0
	2025-05-07 19:12:59.424	info	Starting Adapter npm ...
zigbee.0
	2025-05-07 19:12:59.423	info	--- creating device debug ---
zigbee.0
	2025-05-07 19:12:59.418	info	--> transmitPower : normal
zigbee.0
	2025-05-07 19:12:59.415	info	init localConfig
zigbee.0
	2025-05-07 19:12:59.405	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
host.Raspi58GB
	2025-05-07 19:12:58.274	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2721587

[Asgothian]

@searcher57 Im Log steht nichts drin. Bitte mal die Einstellungen des Zigbee Adapters zeigen.

Anscheinend wird versucht den Herdsman zu starten, aber der kommt nicht zurück.

A.

[searcher57]

@asgothian said in FritzBox Zigbee Antenne in ioBroker einbinden?:

@searcher57 Im Log steht nichts drin. Bitte mal die Einstellungen des Zigbee Adapters zeigen.

Anscheinend wird versucht den Herdsman zu starten, aber der kommt nicht zurück.

A.

Zigbee-Adapter

    Einstellungen
    Local Overrides
    Geräte
    Entwickler

COM-Anschlussname
arrow_drop_down
Typ
Baudate Deconz/Conbee
Countdown zwischen 10 und 240 Sek während der Kopplung
Network
Erweiterte Pan ID

Die erweiterte PAN-ID ist die Hauptnetzwerk-ID, vergleichbar mit der SSID von WLAN-Netzwerken. Diese ID darf sich für vorhandene Netzwerke niemals ändern, da Sie sonst deine Geräte zurücksetzen und Sie neu koppeln müssen. Wenn Sie mehrere ZigBee-Adapter verwenden, müssen Sie sicherstellen, dass diese eindeutige ExtPanIDs verwenden. Geben Sie einfach 16 zufällige Hex-Zeichen ein (a-f und 0-9).
Pan ID

Pan ID ist eine vereinfachte ID (wird von Zigbee anstelle von ExtPanID verwendet, wo immer dies möglich ist). Dies sollte auch einzigartig sein. Hinweis: Das ZigBee-Netzwerk wählt möglicherweise eine andere Pan-ID als die hier angegebene, falls ID-Konflikte erkannt werden.
Kanal
graphic_eq

Kanal stellt die verwendete Funkfrequenz ein. Es kann geändert werden, um Konflikte mit vorhandenen WLAN-Netzwerken zu vermeiden. Alle Geräte müssen beim Wechsel neu gelernt werden!
Transportschlüssel
CC1352P and CC26X2R1 Sendeleistung
andere Einstellungen
External converters
Paths to files, semicolon (;) splitted
save
Speichern
save
close
Speichern und schließen
close
Schließen

[searcher57]

@asgothian said in FritzBox Zigbee Antenne in ioBroker einbinden?:

@searcher57 Im Log steht nichts drin. Bitte mal die Einstellungen des Zigbee Adapters zeigen.

Anscheinend wird versucht den Herdsman zu starten, aber der kommt nicht zurück.

A.

Also ich habe alles wieder in den Alt-Zustand gebracht. Ich werde mir dann doch das FRITZ!Smart Gateway bestellen und versuche damit die drei Zigbee Komponenten in den IO Broker zu bringen. Wenn's nicht funktioniert, sende ich es zurück.
Danke für Eure Hilfe!