Navigation

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

    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

    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 12
    • Best 0
    • Groups 1

    Alkazar

    @Alkazar

    Starter

    0
    Reputation
    3
    Profile views
    12
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Alkazar Follow
    Starter

    Latest posts made by Alkazar

    • RE: Encrypted credentials not found

      @mickym
      Ja, ich habe alles gelöscht - natürlich auch den Adapter - und auch manuell den node-red Ordner.

      Nach der Neuinstallation sind da zwei Ordner und zwei Dateien drin:

      root@ioBroker:/opt/iobroker/iobroker-data/node-red# ls
      lib  node_modules  package.json  settings.js
      

      ich hab beim stöbern dies hier gefunden: https://github.com/ioBroker/ioBroker.node-red/issues/387
      Wahrscheinlich habe nicht nur ich dieses Problem.
      Aber danke für deine Hilfe.

      RALFISBORN created this issue in ioBroker/ioBroker.node-red

      closed Verschlüsselte Credentials nicht gefunden #387

      posted in Node-Red
      A
      Alkazar
    • RE: Encrypted credentials not found

      @mickym
      Klappt bei mir nicht, nochmal alles gelöscht, gleiches Bild :

      node-red.0
      2023-07-27 23:19:44.807	warn	27 Jul 23:19:44 - [warn] Encrypted credentials not found
      
      node-red.0
      2023-07-27 23:19:44.802	warn	27 Jul 23:19:44 - [warn] Projects disabled : editorTheme.projects.enabled=false
      
      node-red.0
      2023-07-27 23:19:42.175	info	Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
      
      node-red.0
      2023-07-27 23:19:41.624	info	starting. Version 4.0.3 in /opt/iobroker/node_modules/iobroker.node-red, node: v18.16.1, js-controller: 4.0.23
      
      posted in Node-Red
      A
      Alkazar
    • RE: Encrypted credentials not found

      @mickym
      Den importierten Flow habe ich jetzt ja gar nicht mehr, hab ja alles gelöscht vorher. Jungfräulicher gehts jetzt nicht mehr.
      Fehlermeldung kommt auch im Sicherheitsmodus.

      posted in Node-Red
      A
      Alkazar
    • RE: Encrypted credentials not found

      @mickym

      Ich hatte tatsächlich einen Flow importiert aber daran hat es wohl nicht gelegen.
      Ich hab mal alles neu gemacht:

      1. Instanz gelöscht
      2. Adapter gelöscht
      3. node-red Verzeichnis gelöscht
      4. Adapter und Instanz neu hinzugefügt

      Gleiches Bild wie vorher:

      node-red.0
      2023-07-27 22:58:48.232	warn	27 Jul 22:58:48 - [warn] Encrypted credentials not found
      
      node-red.0
      2023-07-27 22:58:48.228	warn	27 Jul 22:58:48 - [warn] Projects disabled : editorTheme.projects.enabled=false
      

      Und jetzt weiß ich auch nicht mehr weiter....

      posted in Node-Red
      A
      Alkazar
    • RE: Encrypted credentials not found

      @mickym
      Auch wenn ich die Authentifizierung auf "Keine" stelle, habe ich die gleiche Meldung.
      Daher habe ich mal einen Benutzer erstellt, in der Hoffnung der Adapter macht dann was nötig ist, hat aber nicht geklappt.

      Henry

      posted in Node-Red
      A
      Alkazar
    • Encrypted credentials not found

      Moin zusammen,

      ich habe noch nie mit node red gearbeitet und macher gerade hier meine ersten Schritte, daher bitte ich um Nachsicht falls ich "komische" Fragen stelle.
      Ich habe ganz frisch den Node red Adapter (V4.0.3) installiert und den ersten Flow erstellt.
      Allerdings passiert nichts, außer der Fehlermeldung im Log:

      node-red.0 2023-07-27 20:59:18.817	warn	27 Jul 20:59:18 - [warn] Encrypted credentials not found. 
      

      Muss ich, außer in den Einstellungen im Adapter/Instanz noch irgendwas beachten / einstellen?
      Hier mal meine Konfig:
      0df08c56-592b-4d41-ad10-d3bec4b3e117-image.png

      Danke schonmal für eure Tipps.

      Alkazar

      posted in Node-Red
      A
      Alkazar
    • RE: mqtt keep alive im iobroker, oder in Node red

      @steffen_dec
      Moin Steffen,

      ich bin heute Abend über das gleiche Problem gestolpert. Nach mehreren erfolglosen Versuchen habe ich jetzt eine Lösung mit einem Blockly-Skript gefunden.
      Wichtig hier der Datenpunkt muss gesteuert und nicht aktualisiert werden, so klappt es zumindest bei mir:
      Screenshot 2023-07-24 004326.jpg

      posted in ioBroker Allgemein
      A
      Alkazar
    • RE: [Vorlage] Xiaomi Airpurifier 3H u.a. inkl. Token auslesen.

      Hallo zusammen.

      Ich habs mittlerweile hinbekommen, habe den Luftreiniger nun nochmal neu mit dem Netzwerk verbunden und es funktioniert nun.

      Aber ich hab noch ne Frage:
      Wenn ich den Modus ändern will habe ich zwei Zeilen, den Werttyp und den Wert:
      5971ace7-f9a8-40b2-8629-4b87d5d70a86-image.png

      {
        "common": {
          "name": "air-purifier.mode",
          "type": "number",
          "read": true,
          "write": true,
          "min": 0,
          "max": 3,
          "states": {
            "0": "auto",
            "1": "sleep",
            "2": "favorite",
            "3": "fanset"
          },
          "role": "state"
        },
        "native": {},
        "type": "state",
        "from": "system.adapter.javascript.0",
        "user": "system.user.admin",
        "ts": 1637404094112,
        "_id": "javascript.0.MiHomeAll.394459228.air-purifier.mode",
        "acl": {
          "object": 1636,
          "state": 1636,
          "owner": "system.user.admin",
          "ownerGroup": "system.group.administrator"
        }
      }
      

      Was muss ich aus der VIS senden um diesen zu ändern, Zahl z.B. 0 geht nicht und String z.B. auto funktioniert auch nicht.
      UPDATE:
      Nachdem ich die VIS einmal neugeladen habe geht es plötzlich - mit der Zahl!

      posted in JavaScript
      A
      Alkazar
    • RE: [Vorlage] Xiaomi Airpurifier 3H u.a. inkl. Token auslesen.

      Hallo zusammen,

      ich habe zu diesem Thema auch mal eine Frage, ich habe auch den 3H Luftreiniger und das Skript installiert.
      Ich bin genau nach der Anleitung vorgegangen

      1. JS-Adapter Einstellungen vorgenommen:
        022f8be1-e916-4ae8-8f8f-59b5ed86459f-image.png
      2. Zugangsdaten im Skript hinterlegt
      3. Überprüft ob die zugehörige Datei (zhimi.airpurifier.mb3.js) im Ordner \node_modules\node-mihome\lib\devices vorhanden ist.
        Das Skript läuft auch, legt die Datenpunkte an, aber alle Werte sind leer, außer im Ordner info:
        a48904dc-c40a-4c66-aea0-6b66506047a7-image.png
        9c3a5cc0-2a45-45ce-a327-65e19b0be2b5-image.png
        Hier das Log:
      2021-11-20 11:49:00.285 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Retrieving your in de registered MiHome Devices
      2021-11-20 11:49:00.663 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Found 1 MiHome Devices, those are:
      2021-11-20 11:49:00.664 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Mi Air Purifier 3/3H
      2021-11-20 11:49:00.666 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Now searching for supported Devices...
      2021-11-20 11:49:00.667 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Device Mi Air Purifier 3/3H is supported, creating DataPoints
      2021-11-20 11:49:00.669 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching PrepareDeviceDps, did=394459228 model=zhimi.airpurifier.mb3
      2021-11-20 11:49:00.671 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching CreateStates()
      2021-11-20 11:49:00.689 - info: javascript.0 (3248) script.js.Luftreiniger_3H: 24 States created, now setting up channels!
      2021-11-20 11:49:00.692 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching main
      2021-11-20 11:49:00.693 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching WriteGenericDpValues()
      2021-11-20 11:49:00.695 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching CreateDevices
      2021-11-20 11:49:00.696 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Now creating device for zhimi.airpurifier.mb3 / 394459228 / 192.168.179.5 / 1c3730d1b8b95ab38a8d5cf3be192b5a / 10000
      2021-11-20 11:49:00.699 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Created device {"_events":{},"_eventsCount":0,"_maxListeners":100,"id":"394459228","address":"192.168.179.5","token":"1c3730d1b8b95ab38a8d5cf3bxxxxxxxa","protocol":"local","refresh":10000,"_properties":{},"_propertiesToMonitor":["air-purifier:fault","air-purifier:on","air-purifier:fan-level","air-purifier:mode","environment:pm2.5-density","environment:relative-humidity","environment:temperature","filter:filter-life-level","filter:filter-used-time","alarm:alarm","indicator-light:brightness","indicator-light:on","physical-controls-locked:physical-controls-locked"],"_miotSpec":null,"_miotSpecType":"urn:miot-spec-v2:device:air-purifier:0000A007:zhimi-mb3:2","model":"zhimi.airpurifier.mb3","setter":{},"definition":{"info":[{"id":"localip","initial":"","forceCreation":false,"common":{"read":true,"write":true,"name":"Ip Adress","type":"string","role":"value","def":""}},{"id":"token","initial":"","forceCreation":false,"common":{"read":true,"write":true,"name":"Token","type":"string","role":"value","def":""}},{"id":"did","initial":"","forceCreation":false,"common":{"read":true,"write":true,"name":"Device Id","type":"string","role":"value","def":""}},{"id":"model","initial":"","forceCreation":false,"common":{"read":true,"write":true,"name":"Model","type":"string","role":"value","def":""}},{"id":"rssi","initial":0,"forceCreation":false,"common":{"read":true,"write":false,"name":"rssi","type":"number","role":"value.rssi","def":0}},{"id":"name","initial":"","forceCreation":false,"common":{"read":true,"write":true,"name":"Name","type":"string","role":"value","def":""}},{"id":"isOnline","initial":false,"forceCreation":false,"common":{"read":true,"write":true,"name":"Is online","type":"boolean","role":"value","def":false}}],"model":"zhimi.airpurifier.mb3","description":"Purifier 3H","setter":{},"common":[{"name":"air-purifier.on","type":"boolean","role":"switch","read":true,"write":true,"min":false,"max":true},{"name":"air-purifier.fault","type":"number","read":true,"write":false,"min":0,"max":5,"states":{"0":"No faults","1":"m1_run","2":"m1_stuck","3":"no_sensor","4":"error_hum","5":"error_temp","6":"timer_error1","7":"timer_error2"},"role":"state"},{"name":"air-purifier.mode","type":"number","read":true,"write":true,"min":0,"max":3,"states":{"0":"auto","1":"sleep","2":"favorite","3":"fanset"},"role":"state"},{"name":"air-purifier.fan-level","type":"number","read":true,"write":true,"min":1,"max":3,"role":"state"},{"name":"alarm.alarm","type":"boolean","read":true,"write":true,"role":"state"},{"name":"indicator-light.brightness","type":"number","read":true,"write":true,"min":0,"max":2,"role":"state"},{"name":"indicator-light.on","type":"boolean","role":"switch","read":true,"write":true,"min":false,"max":true},{"name":"environment.temperature","type":"number","role":"value.temperature","read":true,"write":false,"min":-40,"max":125,"unit":"°C"},{"name":"motor-speed.motor-speed","type":"number","read":true,"write":false,"min":0,"max":3000,"unit":"rpm","role":"state"},{"name":"motor-speed.motor-set-speed","type":"number","read":true,"write":false,"min":0,"max":3000,"unit":"rpm","role":"state"},{"name":"motor-speed.favorite-fan-level","type":"number","read":true,"write":true,"min":0,"max":14,"role":"state"},{"name":"use-time.use-time","type":"number","read":true,"write":false,"role":"state"},{"name":"environment.relative-humidity","type":"number","role":"value.humidity","read":true,"write":false,"min":0,"max":100,"unit":"%"},{"name":"environment.pm2_5-density","type":"number","read":true,"write":false,"min":0,"max":600,"unit":"μg/m³","role":"state"},{"name":"filter.filter-life-level","type":"number","read":true,"write":false,"min":0,"max":100,"unit":"%","role":"state"},{"name":"filter.filter-used-time","type":"number","read":true,"write":false,"unit":"h","role":"state"},{"name":"physical-controls-locked.physical-controls-locked","type":"boolean","role":"switch","read":true,"write":true,"min":false,"max":true}]},"firstrun":true,"rssi":0,"isOnline":true} now fetching data
      2021-11-20 11:49:02.604 - info: influxdb.0 (8536) Store 11 buffered influxDB history points
      2021-11-20 11:49:04.851 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Init Device# 0 - device="zhimi.airpurifier.mb3"
      2021-11-20 11:49:04.852 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting trigger #0 for zhimi.airpurifier.mb3
      2021-11-20 11:49:04.854 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Reaching CreateDpTrigger
      2021-11-20 11:49:04.854 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting DataPointTrigger #0 for zhimi.airpurifier.mb3
      2021-11-20 11:49:04.855 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.air-purifier.on / read=true write=true
      2021-11-20 11:49:04.856 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for air-purifier.fault because its readonly.
      2021-11-20 11:49:04.856 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.air-purifier.mode / read=true write=true
      2021-11-20 11:49:04.856 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.air-purifier.fan-level / read=true write=true
      2021-11-20 11:49:04.857 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.alarm.alarm / read=true write=true
      2021-11-20 11:49:04.857 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.indicator-light.brightness / read=true write=true
      2021-11-20 11:49:04.858 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.indicator-light.on / read=true write=true
      2021-11-20 11:49:04.858 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for environment.temperature because its readonly.
      2021-11-20 11:49:04.858 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for motor-speed.motor-speed because its readonly.
      2021-11-20 11:49:04.859 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for motor-speed.motor-set-speed because its readonly.
      2021-11-20 11:49:04.859 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.motor-speed.favorite-fan-level / read=true write=true
      2021-11-20 11:49:04.860 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for use-time.use-time because its readonly.
      2021-11-20 11:49:04.860 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for environment.relative-humidity because its readonly.
      2021-11-20 11:49:04.860 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for environment.pm2_5-density because its readonly.
      2021-11-20 11:49:04.861 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for filter.filter-life-level because its readonly.
      2021-11-20 11:49:04.861 - info: javascript.0 (3248) script.js.Luftreiniger_3H: No Datapoint Trigger set for filter.filter-used-time because its readonly.
      2021-11-20 11:49:04.861 - info: javascript.0 (3248) script.js.Luftreiniger_3H: Setting Datapoint Trigger for javascript.0.MiHomeAll.394459228.physical-controls-locked.physical-controls-locked / read=true write=true
      

      JS_Adapter ist Version v5.2.13 / SkriptVersion = "0.2.25"; //vom 23.08.2021

      Habt ihr noch Ideen was ich anders machen muss?

      posted in JavaScript
      A
      Alkazar
    • RE: influxdb -Doppelte Werte bei Anzeige mit Grafana

      @crunchip
      Ja, ich vermute das lässt sich irgendwie hinbiegen, ich bin jetzt einen Schritt weiter:
      Die Tageserträge bekomme ich hin, indem ich im SELECT das Argument first() verwende, also immer nur den ersten Eintrag pro Tag:
      68022b46-fa23-4437-bcdb-9507b116c309-image.png
      Bei der Ansicht "last 7 days" müsste die Summe aus den folgenden Einzelwerten 6,221 ergeben und nicht 8,084.
      1,498
      1,618
      0,791
      0,34
      0,131
      0,071
      1,772

      cff9fefa-25d9-470e-b48d-5df085233b3d-image.png
      Bei "last 2 dys" sieht es änlich aus 1,498+1,618 sind bei mir 3,116 :
      c2754468-73b3-44ef-b7f2-fb51c1b968e3-image.png

      Ich werde mal testweise einen neuen Datenpunkt erschaffen in den genau 1x pro Tag der letzte wert geschrieben wird und den dann in die Datenbank schieben, mal sehen wie das wird...

      posted in ioBroker Allgemein
      A
      Alkazar
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo