Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. JNDMNK

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 18
    • Best 0
    • Groups 1

    JNDMNK

    @JNDMNK

    0
    Reputation
    6
    Profile views
    18
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Bayern Age 30

    JNDMNK Follow
    Starter

    Latest posts made by JNDMNK

    • DasWetter Error: Cannot check Object existence
      Systemdata Bitte Ausfüllen
      Hardwaresystem: Pi4
      Arbeitsspeicher: 4GB
      Festplattenart: SD-Karte
      Node-Version: 16.18.1
      Nodejs-Version: 16.18.1
      NPM-Version: 8.19.2
      Admin-Version: 6.2.23
      2022-12-08 06:31:23.334 - error: daswetter.0 (18562) force terminate
      2022-12-08 06:31:23.340 - warn: daswetter.0 (18562) Terminated (UNKNOWN_ERROR): Without reason
      2022-12-08 06:31:23.907 - warn: daswetter.0 (18562) get state error: Connection is closed.
      2022-12-08 06:31:23.914 - error: daswetter.0 (18562) exception in await insertIntoList [Error: DB closed]
      2022-12-08 06:31:23.960 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.day_name": Connection is closed.
      2022-12-08 06:31:23.984 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.day_name: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.day_name": Connection is closed.]
      2022-12-08 06:31:24.012 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.day_value": Connection is closed.
      2022-12-08 06:31:24.021 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.day_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.day_value": Connection is closed.]
      2022-12-08 06:31:24.027 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc2": Connection is closed.
      2022-12-08 06:31:24.035 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc2: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc2": Connection is closed.]
      2022-12-08 06:31:24.042 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value2": Connection is closed.
      2022-12-08 06:31:24.045 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value2: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value2": Connection is closed.]
      2022-12-08 06:31:24.050 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc": Connection is closed.
      2022-12-08 06:31:24.054 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_desc": Connection is closed.]
      2022-12-08 06:31:24.058 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value": Connection is closed.
      2022-12-08 06:31:24.064 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.symbol_value": Connection is closed.]
      2022-12-08 06:31:24.069 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.iconURL": Connection is closed.
      2022-12-08 06:31:24.072 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.iconURL: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.iconURL": Connection is closed.]
      2022-12-08 06:31:24.080 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmin_value": Connection is closed.
      2022-12-08 06:31:24.083 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmin_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmin_value": Connection is closed.]
      2022-12-08 06:31:24.087 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmax_value": Connection is closed.
      2022-12-08 06:31:24.091 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmax_value: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.tempmax_value": Connection is closed.]
      2022-12-08 06:31:24.095 - error: daswetter.0 (18562) Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.wind_symbolB": Connection is closed.
      2022-12-08 06:31:24.098 - error: daswetter.0 (18562) exception in await insertIntoList [Error: Could not check object existence of daswetter.0.NextDaysDetailed.Location_1.Day_5.wind_symbolB: Cannot check object existence of "daswetter.0.NextDaysDetailed.Location_1.Day_5.wind_symbolB": Connection is closed.]
      2022-12-08 06:31:24.199 - error: host.raspberrypi instance system.adapter.daswetter.0 terminated with code 15 (UNKNOWN_ERROR)
      

      DasWetter-Adapter schmeißt mir seit einiger Zeit (Es wurde nix geändert) immer wieder mal den Error rein. Im Objekt Baum bestehen die Objekte aber.

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Javascript warnt das Objekt falsche rolle hat

      @paul53 ah ok jetzt kam keine meldung mehr, danke 🙂

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Javascript warnt das Objekt falsche rolle hat

      @codierknecht Habe es auf 0 geändert und beim Speichern kom wieder die Meldung:

      admin.0 - 2022-12-07 09:57:29.161 warn This object will not be created in future versions. Please report this to the developer.
      admin.0 - 2022-12-07 09:57:29.160 warn Object 0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere is invalid: Default value has to be type "number" but received type "string"

      {
        "common": {
          "name": "Verbrauch Waschtrockner_MAX_Ampere",
          "desc": "Manuell erzeugt",
          "role": "state",
          "unit": "A",
          "type": "number",
          "read": true,
          "write": true,
          "def": "0"
        },
        "type": "state",
        "native": {},
        "_id": "0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere",
        "acl": {
          "object": 1636,
          "state": 1636,
          "owner": "system.user.admin",
          "ownerGroup": "system.group.administrator"
        },
        "from": "system.adapter.admin.0",
        "user": "system.user.admin",
        "ts": 1670403449159
      }
      
      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Javascript warnt das Objekt falsche rolle hat

      @codierknecht

      {
        "common": {
          "name": "Verbrauch Waschtrockner_MAX_Ampere",
          "desc": "Manuell erzeugt",
          "role": "state",
          "unit": "A",
          "type": "number",
          "read": true,
          "write": true,
          "def": ""
        },
        "type": "state",
        "native": {},
        "_id": "0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere",
        "acl": {
          "object": 1636,
          "state": 1636,
          "owner": "system.user.admin",
          "ownerGroup": "system.group.administrator"
        },
        "from": "system.adapter.admin.0",
        "user": "system.user.admin",
        "ts": 1670399821158
      }
      

      und

      {
        "type": "state",
        "common": {
          "name": "Current",
          "type": "number",
          "role": "value.current",
          "read": true,
          "write": false,
          "def": 0,
          "unit": "A"
        },
        "native": {},
        "from": "system.adapter.shelly.0",
        "user": "system.user.admin",
        "ts": 1670343260883,
        "_id": "shelly.0.shellyplus1pm#a8032abb9504#1.Relay0.Current",
        "acl": {
          "object": 1636,
          "state": 1636,
          "owner": "system.user.admin",
          "ownerGroup": "system.group.administrator"
        }
      }
      
      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Javascript warnt das Objekt falsche rolle hat

      @cash also wenn ich Zahl einstelle kommt einmalig dieser fehler:

      admin.0 - 2022-12-07 08:57:01.159 warn This object will not be created in future versions. Please report this to the developer.
      admin.0 - 2022-12-07 08:57:01.159 warn Object 0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere is invalid: Default value has to be type "number" but received type "string"

      aber beim aktualisieren des Objektes durch das Script wird kein Fehler im Protokoll ausgegeben.
      wenn ich es auf Zeichenkette stelle jammert er jedes mal beim aktualisieren aber der Admin schmeißt keinen Fehler 😕

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Javascript warnt das Objekt falsche rolle hat

      @cash

      Ich wüsste grad nicht wie. Vll übersehe ich es auch grad nur.
      Wenn ich das Userobject auf genau den selben wert einstelle wie das was dort reingeschrieben wird.

      Script.jpg

      Waschtrockner Power.jpg

      Object Power.jpg

      admin.0 - 2022-12-07 08:35:38.131 warn This object will not be created in future versions. Please report this to the developer.
      admin.0 - 2022-12-07 08:35:38.131 warn Object 0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere is invalid: Default value has to be type "number" but received type "string"

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • [gelöst] Javascript warnt das Objekt falsche rolle hat
      Hardwaresystem: Pi4
      Arbeitsspeicher: 4GB
      Festplattenart: SD-Karte
      Node-Version: 16.18.1
      Nodejs-Version: 16.18.1
      NPM-Version: 8.19.2
      Admin-Version: 6.2.23
      Javascript-Version: 6.0.3

      Guten Tag, aktuell werden mir Warn-Meldungen rausgegeben. Bei dem Benutzerdefinierten-Objekt Wenn ich es als Zeichenkette definiere jammert Javascript und wenn ich es wie Javascript sagt als Zahl definiere, jammert Admin.... Weiß jemand ne lösung? Es wird nur eine Zahl von einem anderen Objekt "kopiert".

      2022-12-07 06:40:16.608 - warn: javascript.0 (2169) You are assigning a number to the state "0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere" which expects a string. Please fix your code to use a string or change the state type to number. This warning might become an error in future versions.
      2022-12-07 06:40:16.610 - warn: javascript.0 (2169) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1689:20)
      2022-12-07 06:40:16.611 - warn: javascript.0 (2169) at Object. (script.js.Smart_Home.Shelly:56:5)
      2022-12-07 06:40:16.611 - warn: javascript.0 (2169) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1214:38)
      2022-12-07 06:40:16.611 - warn: javascript.0 (2169) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:596:29)
      2022-12-07 06:40:16.612 - warn: javascript.0 (2169) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:5909:56)
      2022-12-07 06:40:16.613 - warn: javascript.0 (2169) at processImmediate (node:internal/timers:466:21)

      2022-12-07 06:41:43.091 - warn: admin.0 (2081) Object 0_userdata.0.Verbrauch.Verbrauch_Waschtrockner_MAX_Ampere is invalid: Default value has to be type "number" but received type "string"
      2022-12-07 06:41:43.092 - warn: admin.0 (2081) This object will not be created in future versions. Please report this to the developer.

      Log Javascript.jpg

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Shelly über ioBroker steuern funktioniert nicht

      @mickym

      ah ok danke, damit gehts.

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • RE: [gelöst] Shelly über ioBroker steuern funktioniert nicht

      @spacerx

      Schalter Bestätigt um und im Log wird nix aufgezeichnet.

      posted in Error/Bug
      JNDMNK
      JNDMNK
    • [gelöst] Shelly über ioBroker steuern funktioniert nicht
      Hardwaresystem: Pi4
      Arbeitsspeicher: 4GB
      Festplattenart: SD-Karte
      Node-Version: 16.18.1
      Nodejs-Version: 16.18.1
      NPM-Version: 8.19.2

      Ich habe seit gestern einen Shelly Plus 1 in meinem System am laufen, über den Shelly-Adapter mit MQTT eingebunden. Daten werden alle synchronisiert aber wenn ich über den Datenpunkt Switch den Relaisausgang am Shelly schalten will, funktioniert dies nicht (Datenpunkt wird geändert überträgt es aber nicht an Shelly). Nur über Request und URL Aufruf für den Befehl (http://IP.vom.Shelly.Gerät/relay/1?turn=on). Shelly wurde 1x auf Werkseinstellungen zurückgesetzt und die Shelly Instanz einmal neu Installiert = Ergebnis das selbe.

      Node und NPM.jpg

      Shelly MQTT.jpg

      ioBroker Shelly Allgemein.jpg
      ioBroker SHelly MQTT.jpg
      ioBrokerSheller Objekte.jpg

      posted in Error/Bug
      JNDMNK
      JNDMNK
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo