Open JarlMorgennebel opened 1 year ago
got the same error also on v1.7:
State "wolf.0.bm1_t.194" has no existing object, this might lead to an error in future versions
Thx for the great work btw!!
Gleicher Fehler bei mir nach Update von Version 1.50 auf V1.70 Bei 1.50 ist der DP im Objektbaum an einer anderen Stelle. Nach Löschen des DP und Neustart des Adapters wurde DP neu angelegt. Fehler tritt nicht mehr auf.
Habe jetzt aber einen anderen Fehler: info For datapoint 362 no device defined. info For datapoint 363 no device defined.
Steht alle 30 Min je 6 mal im Log
2023-02-06 16:11:17.715 info For datapoint 363 no device defined. 2023-02-06 16:11:17.712 info For datapoint 362 no device defined. 2023-02-06 16:11:17.615 info For datapoint 363 no device defined. 2023-02-06 16:11:17.611 info For datapoint 362 no device defined. 2023-02-06 16:11:17.512 info For datapoint 363 no device defined. 2023-02-06 16:11:17.508 info For datapoint 362 no device defined. 2023-02-06 16:11:17.409 info For datapoint 363 no device defined. 2023-02-06 16:11:17.407 info For datapoint 362 no device defined. 2023-02-06 16:11:17.309 info For datapoint 363 no device defined. 2023-02-06 16:11:17.305 info For datapoint 362 no device defined. 2023-02-06 16:11:17.207 info For datapoint 363 no device defined. 2023-02-06 16:11:17.205 info For datapoint 362 no device defined. 2023-02-06 16:10:58.479 info Invalid polling interval. Disable polling. 2023-02-06 16:10:58.443 info starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.wolf, node: v16.17.0, js-controller: 4.0.23 2023-02-06 16:10:56.489 info instance system.adapter.wolf.0 started with pid 6964
it is correct the 363 and 362 are not yet defined. Do you know the definition? @fred0815 any idea maybe?
Both are defined by Wolf as internal DPs. I ignored them cause i got only zeros the hole time.
Maybe we should simply add themm also when it is just 0? ;-)
I have added both DPs. 362 and 363 main.js.txt datapoints.json.txt
@Apollon77 any propose to update the adapter?
I have one milestone left on my "Matter list" for now, then I do an other Adapter break and check that
Fehler tritt bei mir auch auf: iobroker.Wolf._LOG.2023-11-06.log
Nabend, ich habe die beiden Dateien runtergeladen und ersetzt from issue https://github.com/ioBroker/ioBroker.wolf/issues/96 "datapoints,json" to "/opt/iobroker/node_modules/iobroker.wolf/js" "main.js" to "/opt/iobroker/node_modules/iobroker.wolf"
leider immer noch viele Fehler:
Der Adapter hat sich beendet:
wolf.0 | 2023-11-06 18:30:31.544 | info | terminating
wolf.0 | 2023-11-06 18:30:31.044 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
wolf.0 | 2023-11-06 18:30:31.044 | info | terminating
wolf.0 | 2023-11-06 18:30:31.036 | error | undefined is not a valid state value
wolf.0 | 2023-11-06 18:30:31.036 | error | Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21) at setState (/opt/iobroker/node_modules/iobroker.wolf/main.js:899:17) at Socket.
ich habe die Änderung der 2 Dateien wieder rückgängig gemacht.
Ich prüfe es nochmal..
Hej,
Adapter 1.7.0.
Thanks, JMN