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

[Bug]: Ungerechtfertigte Warnung: "has no existing object, this might lead to an error in future versions" #1791

Open
3 tasks done
uwe72 opened this issue Jan 1, 2025 · 1 comment
Labels

Comments

@uwe72
Copy link

uwe72 commented Jan 1, 2025

I'm sure that

  • This issue is still present in the current beta version of this adapter
  • There is no other (open) issue with the same topic (use the search!)
  • This issue is not described in the adapter documentation / FAQ (read the docs!)

Script type

TypeScript, (vermutlich auch) JavaScript

The problem

Die Warning "has no existing object, this might lead to an error in future versions" wird zu unrecht ausgegeben nach dem ein neues Script erstellt wird.

Vorab:

  1. Habe 2 JavaScript-Adapter Instanzen
  2. Ich verwende nur TypeScript

Den Fehler kannst Du einfach reproduzieren:

  1. Anlage mit Instanz 0 eines Scriptes z.B. "Testa" mit einem kurzen Log-Statement, z.B.
  2. image

--> Führt zur Logausgabe:

State "javascript.1.scriptEnabled.Testa" has no existing object, this might lead to an error in future versions

Auffälligkeit:

  1. Script wurde mit Instanz 0 erzeugt
  2. Fehlermeldung (Warnung) kommt von Instanz 1

iobroker.current.log (in debug mode!)

No response

Version of nodejs

v20.18.1

Version of ioBroker js-controller

7.0.6

Version of adapter

8.8.3

@uwe72 uwe72 changed the title [Bug]: Fehlerhafte Warnung: "has no existing object, this might lead to an error in future versions" [Bug]: Ungerechtfertigte Warnung: "has no existing object, this might lead to an error in future versions" Jan 1, 2025
@mcm1957
Copy link
Contributor

mcm1957 commented Jan 2, 2025

@klein0r klein0r added the bug label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants