Hallo zusammen,
ich habe Probleme mit dem fritz.dect-Adapter.
Bis vorgestern lief das Teil einwandfrei. Dann gab es plötzlich das Problem, dass die Werte nicht mehr an die Fritzbox weitergeleitet wurden. Also Beispiel: Es soll ein Sollwert auf ein Thermostat geschrieben werden. Im Objektbaum wird dann für den Sollwert eines Thermostats der Wert 20° eingetragen, aber am Thermostat kommt dieser nie an.
Beim Lesen von Werten das umgekehrte Problem: Was im Objektbaum stand, stimmte nicht mit den Werten aus der FB überein. Die Instanz wurde "grün" angezeigt, lief also. Laut Protokoll konnte sie sich aber an der FB nicht anmelden:
2023-12-26 06:04:43.352 - error: fritzdect.0 (598) --------------- error calling the fritzbox -----------
2023-12-26 06:04:43.353 - error: fritzdect.0 (598) API msg => error calling executeCommand
2023-12-26 06:04:43.354 - error: fritzdect.0 (598) API funct => login_SID
2023-12-26 06:04:43.354 - error: fritzdect.0 (598) no response part in returned error message
2023-12-26 06:04:43.355 - error: fritzdect.0 (598) 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"}}}
2023-12-26 06:04:43.355 - error: fritzdect.0 (598) login not possible, check user and permissions
- Lösungsansatz: Neustart Fritzbox, ioBroker, etc. Keine Verbesserung
- Lösungsansatz: Adapter deinstallieren und neuinstallieren: Verschlechterung. Die Instanz startet kurz, stürzt dann ab und wiederholt den Start und den Absturz bis ioBroker das unterbindet.
- Lösungsansatz: fritz.dect deinstallieren, aus dem Objektbaum löschen und auch alle Verzeichnisse des Adapters von der Festplatte löschen. Dann neu installieren: Keine Verbesserung. Die neu installierte Instanz startet nicht mehr.
Das Protokoll des fritz.dect seit der jüngsten Neuinstallation (alle Prozesse, die auf den Adapter schreiben oder von ihm lesen waren deaktiviert):
2023-12-26 12:02:21.851 - info: fritzdect.0 (891) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v19.6.1, js-controller: 5.0.17
2023-12-26 12:02:21.877 - info: fritzdect.0 (891) fritzdect entered ready
2023-12-26 12:02:21.905 - info: fritzdect.0 (891) fritzdect uses USER: boxcommander
2023-12-26 12:02:22.566 - info: fritzdect.0 (891) checking user permissions
2023-12-26 12:02:22.811 - info: fritzdect.0 (891) the rights are : {"Rights":{"Name":["Dial","App","HomeAuto","BoxAdmin","Phone","NAS"],"Access":["2","2","2","2","2","2"]}}
2023-12-26 12:02:22.812 - info: fritzdect.0 (891) start creating global values
2023-12-26 12:02:22.813 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:22.813 - info: fritzdect.0 (891) create Main object global channel list
2023-12-26 12:02:22.830 - info: fritzdect.0 (891) finished creating global values
2023-12-26 12:02:22.830 - info: fritzdect.0 (891) start creating devices/groups
2023-12-26 12:02:23.180 - info: fritzdect.0 (891) CREATE Devices 8
2023-12-26 12:02:23.183 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:23.184 - info: fritzdect.0 (891) create Main object DECT_ 116570178743 Fühler Zimmer I thermo
2023-12-26 12:02:23.280 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:23.281 - info: fritzdect.0 (891) create Main object DECT_ 119590554264 Heizung Zimmer I thermo.heat
2023-12-26 12:02:23.579 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:23.580 - info: fritzdect.0 (891) create Main object DECT_ 117950306504 Heizung Zimmer II thermo.heat
2023-12-26 12:02:23.873 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:23.873 - info: fritzdect.0 (891) create Main object DECT_ 117950143992 Heizung Zimmer III thermo.heat
2023-12-26 12:02:24.161 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:24.162 - info: fritzdect.0 (891) create Main object DECT_ 109711045416 Heizung Zimmer IV thermo.heat
2023-12-26 12:02:24.444 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:24.445 - info: fritzdect.0 (891) create Main object DECT_ 117950393480 Heizung Zimmer V thermo.heat
2023-12-26 12:02:24.731 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:24.732 - info: fritzdect.0 (891) create Main object DECT_ 139790522368 Heizung Zimmer VI thermo.heat
2023-12-26 12:02:25.010 - info: fritzdect.0 (891) ____________________________________________
2023-12-26 12:02:25.010 - info: fritzdect.0 (891) create Main object DECT_ 139790552260 Heizung Zimmer VII thermo.heat
2023-12-26 12:02:25.318 - info: fritzdect.0 (891) finished creating devices/groups (if any)
2023-12-26 12:02:25.319 - info: fritzdect.0 (891) templates are used(false)
2023-12-26 12:02:25.319 - info: fritzdect.0 (891) start creating templates
2023-12-26 12:02:25.635 - info: fritzdect.0 (891) CREATE Templates 1
2023-12-26 12:02:25.654 - info: fritzdect.0 (891) finished creating templates (if any)
2023-12-26 12:02:25.654 - info: fritzdect.0 (891) routines are used(false)
2023-12-26 12:02:25.655 - info: fritzdect.0 (891) start creating routines
2023-12-26 12:02:26.066 - info: fritzdect.0 (891) finished creating routines (if any)
2023-12-26 12:02:26.066 - info: fritzdect.0 (891) start initial updating devices/groups
2023-12-26 12:02:26.648 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:26.649 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:26.649 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:26.652 - info: fritzdect.0 (891) cleaned everything up...
2023-12-26 12:02:26.652 - info: fritzdect.0 (891) terminating
2023-12-26 12:02:26.653 - warn: fritzdect.0 (891) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-12-26 12:02:26.761 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:26.762 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:26.762 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:26.881 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:26.881 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:26.881 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:26.997 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:26.997 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:26.997 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:27.157 - info: fritzdect.0 (891) terminating
2023-12-26 12:02:27.165 - error: fritzdect.0 (891) try/catch issue updating device in updateDevices Error: DB closed
2023-12-26 12:02:27.168 - info: fritzdect.0 (891) finished initial updating devices/groups
2023-12-26 12:02:27.168 - info: fritzdect.0 (891) going over to cyclic polling, messages to poll activity only in debug-mode
2023-12-26 12:02:27.169 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:27.169 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:27.169 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:27.170 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:27.170 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:27.170 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:27.171 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:27.171 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:27.171 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:27.172 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:27.172 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:27.172 - error: fritzdect.0 (891) undefined
2023-12-26 12:02:27.175 - warn: fritzdect.0 (891) get state error: Connection is closed.
2023-12-26 12:02:27.177 - error: fritzdect.0 (891) 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().
2023-12-26 12:02:27.177 - error: fritzdect.0 (891) unhandled promise rejection: undefined
2023-12-26 12:02:27.177 - error: fritzdect.0 (891) undefined
ioBroker v6.12.0
js-Controller Version 5.0.17
fritz.dect Version 2.5.9
ioBroker läuft in einem Docker (Buanet) auf einer Synology DS918+ mit DSM DSM 7.1.1-42962 Update 6
Vielleicht hat jemand eine Idee. Ich hoffe, dass es nicht an der Fritzbox liegt.