Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapter 1.7.0: missing datapoint #96

Open
JarlMorgennebel opened this issue Jan 29, 2023 · 12 comments
Open

Adapter 1.7.0: missing datapoint #96

JarlMorgennebel opened this issue Jan 29, 2023 · 12 comments

Comments

@JarlMorgennebel
Copy link

Hej,

wolf.0 | 2023-01-29 17:05:39.169 | warn | State "wolf.0.bm1_t.194" has no existing object, this might lead to an error in future versions
-- | -- | -- | --
wolf.0 | 2023-01-29 16:33:49.940 | warn | State "wolf.0.bm1_t.194" has no existing object, this might lead to an error in future versions
wolf.0 | 2023-01-29 16:02:31.063 | warn | State "wolf.0.bm1_t.194" has no existing object, this might lead to an error in future versions
wolf.0 | 2023-01-29 15:31:32.069 | warn | State "wolf.0.bm1_t.194" has no existing object, this might lead to an error in future versions

Adapter 1.7.0.

Thanks, JMN

@Claus1985
Copy link

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!!

@tobi119
Copy link

tobi119 commented Feb 6, 2023

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

@Apollon77
Copy link
Contributor

it is correct the 363 and 362 are not yet defined. Do you know the definition? @fred0815 any idea maybe?

@fred0815
Copy link

fred0815 commented Feb 6, 2023

Both are defined by Wolf as internal DPs. I ignored them cause i got only zeros the hole time.

@Apollon77
Copy link
Contributor

Maybe we should simply add themm also when it is just 0? ;-)

@fred0815
Copy link

fred0815 commented Feb 8, 2023

I have added both DPs. 362 and 363
main.js.txt
datapoints.json.txt

@fred0815
Copy link

@Apollon77 any propose to update the adapter?

@Apollon77
Copy link
Contributor

I have one milestone left on my "Matter list" for now, then I do an other Adapter break and check that

@franks06347
Copy link

Fehler tritt bei mir auch auf:
iobroker.Wolf._LOG.2023-11-06.log

@franks06347
Copy link

Nabend,
ich habe die beiden Dateien runtergeladen und ersetzt
from issue #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:

wolf_log_20231106_1830.log

@franks06347
Copy link

franks06347 commented Nov 6, 2023

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. (/opt/iobroker/node_modules/iobroker.wolf/main.js:949:31) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at addChunk (node:internal/streams/readable:335:12) at readableAddChunk (node:internal/streams/readable:308:9) at Socket.Readable.push (node:internal/streams/readable:245:10)
wolf.0 | 2023-11-06 18:30:30.941 | error | unhandled promise rejection: undefined is not a valid state value

ich habe die Änderung der 2 Dateien wieder rückgängig gemacht.

@fred0815
Copy link

fred0815 commented Nov 6, 2023

Ich prüfe es nochmal..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants