Describe the bug
Today I updated the Tahoma box to the lastet version. Now the Tohama adapter is throwing a package of 4 warnings to the protocoll.
Current version of tahoma adapter:
adapter tahoma v0.7.2.3
Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v14.19.1, js-controller: 4.0.23
2022-07-12 13:24:10.059 | warn | Failed getting execution state for 9233ad1d-0b97-4944-b19b-d2004f234b31
Describe the bug
Today I updated the Tahoma box to the lastet version. Now the Tohama adapter is throwing a package of 4 warnings to the protocoll. Current version of tahoma adapter: adapter tahoma v0.7.2.3 Version 0.7.2 (non-npm: Excodibur/ioBroker.tahoma) in /opt/iobroker/node_modules/iobroker.tahoma, node: v14.19.1, js-controller: 4.0.23
2022-07-12 13:24:10.059 | warn | Failed getting execution state for 9233ad1d-0b97-4944-b19b-d2004f234b31
tahoma.0 | 2022-07-12 13:24:10.058 | warn | Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
tahoma.0 | 2022-07-12 13:24:10.057 | warn | Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Tue, 12 Jul 2022 11:24:10 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"----deleted-------
2022-07-12 13:24:10.056 | warn | error during request: null, request path: history/executions/9233ad1d-0b97-4944-b19b-d2004f234b31 with payload:{}
I guess the long warning contains some access data. I delete this to publish the warning here.
Access via direct API.
Regards Andreas