2023-01-05 18:03:55.947	error	API err => [object Object]

fritzdect.1
2023-01-05 18:03:55.946	error	no response part in returned message

fritzdect.1
2023-01-05 18:03:55.946	error	API funct => executeCommand2

fritzdect.1
2023-01-05 18:03:55.946	error	API msg => relogin failed

fritzdect.1
2023-01-05 18:03:55.946	error	--------------- error calling the fritzbox -----------

zigbee.0
2023-01-05 18:03:53.650	error	Send command to 0x84fd27fffece6f70 failed with no error code (undefined)

fritzdect.1
2023-01-05 17:40:01.715	error	API err => [object Object]

fritzdect.1
2023-01-05 17:40:01.715	error	no response part in returned message

fritzdect.1
2023-01-05 17:40:01.715	error	API funct => executeCommand2

fritzdect.1
2023-01-05 17:40:01.715	error	API msg => relogin failed

fritzdect.1
2023-01-05 17:40:01.715	error	--------------- error calling the fritzbox -----------

@michael_4358 sagte in Fritz DECT API Err:

fritzdect uses USER: root

Ich kenne den Adapter zwar nicht, solltest du da auf dem System aber als root herumkaspern: Lass es sein!

Ne das is kein Root im Sinne des Admin rechte System.

fritzdect uses USER: root

Ich kenne den Adapter zwar nicht, solltest du da auf dem System aber als root herumkaspern: Lass es sein!

Fehler gefunden❗️ das war es❗️
habe den broker mal neugestartet.
irgendwo muss es geklemmt haben.

nun is alles wie es soll.

fritzdect.1
2023-01-03 20:10:59.898	info	setting up levelcontrol

fritzdect.1
2023-01-03 20:10:59.855	info	setting up alert

fritzdect.1
2023-01-03 20:10:59.855	info	setting up alert

fritzdect.1
2023-01-03 20:10:59.854	info	setting up levelcontrol

fritzdect.1
2023-01-03 20:10:59.854	info	setting up blind

fritzdect.1
2023-01-03 20:10:59.809	info	setting up blind

fritzdect.1
2023-01-03 20:10:59.809	info	setting up alert

fritzdect.1
2023-01-03 20:10:59.808	info	setting up alert

fritzdect.1
2023-01-03 20:10:59.746	info	setting up temperature

fritzdect.1
2023-01-03 20:10:59.731	info	CREATE Devices 9

fritzdect.1
2023-01-03 20:10:59.113	info	start creating devices/groups

fritzdect.1
2023-01-03 20:10:59.113	info	the rights are : {"Rights":{"Name":["Dial","App","HomeAuto","BoxAdmin","Phone","NAS"],"Access":["2","2","2","2","2","2"]}}

fritzdect.1
2023-01-03 20:10:59.112	info	raw perm =>[object Object]

fritzdect.1
2023-01-03 20:10:58.762	info	checking user permissions

fritzdect.1
2023-01-03 20:10:57.674	info	fritzdect uses USER: root

fritzdect.1
2023-01-03 20:10:57.661	info	fritzdect entered ready

fritzdect.1
2023-01-03 20:10:57.650	info	starting. Version 2.2.6 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v16.19.0, js-controller: 4.0.23


fritzdect.0
2023-01-03 20:10:57.262	info	fritzdect uses USER: root

fritzdect.0
2023-01-03 20:10:57.249	info	fritzdect entered ready

fritzdect.0
2023-01-03 20:10:57.238	info	starting. Version 2.2.6 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v16.19.0, js-controller: 4.0.23

Das kann nicht sein, ein vollständiger Neustart sieht gemeinhin anders aus.

Neustart habe ich gemacht. nun kommt erstmal nur eine Meldung...

2023-01-03 19:26:14.065	error	try/catch error in onReady [object Object]

Adapter Neustart sieht wie aus?

Bitte den vollen TEXT aus dem Log in CodeTags eingebettet posten.