Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 3.2 jetzt im Latest!

    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

    js-controller 3.2 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • apollon77
      apollon77 @JayR last edited by

      @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

      Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

      JayR 1 Reply Last reply Reply Quote 0
      • Master67
        Master67 @JayR last edited by

        Läuft bei mir nicht... bekomme X-Fehlermeldungen (leider konnte ich die nicht speichern, lade eine Sicherung und dann habe ich die Meldungen), nur soviel, die Vis ging noch ein Einlogen per IP und Port ging nicht mehr!

        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @Master67 last edited by

          @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

          Master67 2 Replies Last reply Reply Quote 0
          • JayR
            JayR @apollon77 last edited by

            @apollon77 said in js-controller 3.2 jetzt im Latest!:

            @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

            Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

            Kam aus dem CLI Kommand. Mehr wurde nicht angezeigt. Welches Log brauchst du genau?

            Der Controller lief noch bin nur nicht mehr auf de WebUi gekommen.

            apollon77 1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @JayR last edited by

              @jayr Restarte mal controller sodass wieder alles geht. und dann versuch später ob es mit der 3.2.8 noch passiert

              1 Reply Last reply Reply Quote 0
              • Master67
                Master67 @apollon77 last edited by

                @apollon77 sagte in js-controller 3.2 jetzt im Latest!:

                @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                Mache ich wenn der ioBroker wieder läuft... spiele doch grade eine Sicherung ein 😉

                1 Reply Last reply Reply Quote 0
                • Master67
                  Master67 @apollon77 last edited by

                  @apollon77 so hier mal die Fehlermeldung die ich erhalte 🙂

                  Update js-controller from @3.1.6 to @3.2.7
                  NPM version: 6.14.10
                  npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                  In file included from ../authenticate_pam.cc:23:
                  ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                  ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                   2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                        |                                                              ^
                  ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
                  ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                    107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                        |                                                                                       ^
                  In file included from ../authenticate_pam.cc:23:
                  ../../nan/nan.h:1026:46: note: declared here
                   1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                        |                                              ^~~~~~~~~~~~
                  ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                    107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                        |                                                                                       ^
                  In file included from ../authenticate_pam.cc:23:
                  ../../nan/nan.h:1026:46: note: declared here
                   1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                        |                                              ^~~~~~~~~~~~
                  ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
                  ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                    147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                        |                                                                                   ^
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                   from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                   from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                   3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                        |                                                   ^~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                    328 |   declarator __attribute__((deprecated(message)))
                        |   ^~~~~~~~~~
                  ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
                    150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                        |                           ~~~^~~~~~~~~~~
                        |                              |
                        |                              char [128]
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                   2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                        |                 ~~~~~~~~~^~~~~~~
                  ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                    152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                        |                                                                     ^
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                   from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                   from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                   3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                        |                                                   ^~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                    328 |   declarator __attribute__((deprecated(message)))
                        |   ^~~~~~~~~~
                  ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
                    155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                        |                          ~~~^~~~~~~~~~
                        |                             |
                        |                             char [128]
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                   2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                        |                 ~~~~~~~~~^~~~~~~
                  ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                    160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                        |                      ~~~^~~~~~~~
                        |                         |
                        |                         char [128]
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                   2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                        |                 ~~~~~~~~~^~~~~~~
                  ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                    161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                        |                      ~~~^~~~~~~~
                        |                         |
                        |                         char [128]
                  In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                   from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                   2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                        |                 ~~~~~~~~~^~~~~~~
                  ../authenticate_pam.cc: At global scope:
                  ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
                    170 | void init(Handle<Object> exports) {
                        |           ^~~~~~
                  ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
                  ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
                    170 | void init(Handle<Object> exports) {
                        |                        ^
                  ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
                    170 | void init(Handle<Object> exports) {
                        |                          ^~~~~~~
                  In file included from ../../nan/nan.h:56,
                                   from ../authenticate_pam.cc:23:
                  ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
                    175 | NODE_MODULE(authenticate_pam, init);
                        |                               ^~~~
                  /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
                    737 |       (node::addon_register_func) (regfunc),                          \
                        |                                    ^~~~~~~
                  ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
                    175 | NODE_MODULE(authenticate_pam, init);
                        | ^~~~~~~~~~~
                  make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1
                  gyp ERR! build error 
                  gyp ERR! stack Error: `make` failed with exit code: 2
                  gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                  gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
                  gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                  gyp ERR! System Linux 5.4.78-2-pve
                  gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                  gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                  gyp ERR! node -v v12.20.1
                  gyp ERR! node-gyp -v v5.1.0
                  gyp ERR! not ok 
                  Starting node restart.js
                  
                  apollon77 1 Reply Last reply Reply Quote 0
                  • apollon77
                    apollon77 @Master67 last edited by

                    @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

                    Das sind faktisch nur warnungen von einem optionalen Paket

                    Master67 1 Reply Last reply Reply Quote 0
                    • Master67
                      Master67 @apollon77 last edited by

                      @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf 😉

                      Thomas Braun apollon77 2 Replies Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Master67 last edited by Thomas Braun

                        @master67
                        Ist libpam0g-dev auf deinem System installiert?

                        [Edit:] Das ist wieder so'n Container-Gesumsel, oder?

                        Master67 1 Reply Last reply Reply Quote 0
                        • Master67
                          Master67 @Thomas Braun last edited by Master67

                          @thomas-braun .... keine Ahnung!
                          Da läuft nur der ioBroker unter Ubuntu 20.04.1

                          Edit: japp Proxmox 🙂

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Master67 last edited by

                            @master67

                            apt policy libpam0g-dev
                            
                            Master67 1 Reply Last reply Reply Quote 0
                            • Master67
                              Master67 @Thomas Braun last edited by

                              @thomas-braun sagte in js-controller 3.2 jetzt im Latest!:

                              apt policy libpam0g-dev

                              Ja läuft....

                              libpam0g-dev:
                                Installed: 1.3.1-5ubuntu4.1
                                Candidate: 1.3.1-5ubuntu4.1
                                Version table:
                               *** 1.3.1-5ubuntu4.1 500
                                      500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
                                      100 /var/lib/dpkg/status
                                   1.3.1-5ubuntu4 500
                                      500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
                              
                              1 Reply Last reply Reply Quote 0
                              • H
                                homecineplexx last edited by

                                also mit dem js-controller 3.2.7 hab ich leuter Fehlermeldungen:

                                2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                2021-01-18 19:37:16.508  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                2021-01-18 19:37:16.509  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                2021-01-18 19:37:16.510  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]: TypeError: Cannot read property 'stateValue' of undefined
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at VirtualDevice.<anonymous> (script.js.VirtuelleDevices.ESP.watermeter:297:72)
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at runCallback (timers.js:706:11)
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at tryOnImmediate (timers.js:676:5)
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at processImmediate (timers.js:658:5)
                                2021-01-18 19:37:16.511  - ESC[31merrorESC[39m: host.IoBrokerSmartHome Caught by controller[0]:     at process.topLevelDomainCallback (domain.js:126:23)
                                

                                hab auch schon geschaut, aber wonach bitte zählt der denn die Line 297? nicht so, wie sie im JavaScript ist denke ich.

                                apollon77 1 Reply Last reply Reply Quote 0
                                • omega235
                                  omega235 Developer last edited by omega235

                                  Die Installation von Branches über Github funktioniert nicht mehr korrekt.

                                  js-controller: 3.2.7
                                  os: Linux / Docker / buanet 5.1
                                  architektur: x64
                                  nodejs: v12.20.0
                                  NPM: 6.14.8

                                  über den bisher funktionierenden Link (https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0) kommt es zu einer Fehlermeldung (wird aber installiert, man muss aber manuell upload und neu starten):

                                  $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                                  install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                                  NPM version: 6.14.8
                                  npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                                  + iobroker.virtualpowermeter@1.3.0
                                  updated 1 package in 43.181s
                                  23 packages are looking for funding  run `npm fund` for details
                                  ERROR: host.IoBrokerTestSystem1 Cannot install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0: 0
                                  ERROR: process exited with code 25
                                  

                                  Wenn man den Link von github nimmt (https://github.com/Omega236/ioBroker.virtualpowermeter/tree/1.3.0) dann installiert er die Version aus dem Master branch.

                                  edit:
                                  im stable (3.1.6) sieht der log gut aus:

                                  $ ./iobroker url "https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0" --debug
                                  install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0
                                  NPM version: 6.14.8
                                  npm install https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0 --loglevel error --prefix "/opt/iobroker" (System call)
                                  + iobroker.virtualpowermeter@1.3.0updated 1 package in 16.663s
                                  25 packages are looking for funding  run `npm fund` for details
                                  upload [8] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/words.js words.js application/javascript
                                  upload [7] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/virtualpowermeter.png virtualpowermeter.png image/png
                                  upload [6] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/tsconfig.json tsconfig.json application/json
                                  upload [5] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/style.css style.css text/css
                                  upload [4] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/index_m.html index_m.html text/html
                                  upload [3] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/custom_m.html custom_m.html text/html
                                  upload [2] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/admin.d.ts admin.d.ts video/mp2t
                                  upload [1] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/InstanceSettings.PNG InstanceSettings.PNG image/png
                                  upload [0] virtualpowermeter.admin /opt/iobroker/node_modules/iobroker.virtualpowermeter/admin/DatapointSample.PNG DatapointSample.PNG image/png
                                  process exited with code 0
                                  
                                  apollon77 2 Replies Last reply Reply Quote 0
                                  • Feuersturm
                                    Feuersturm @apollon77 last edited by

                                    @apollon77 sagte in js-controller 3.2 jetzt im Latest!:

                                    @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

                                    @apollon77 Bisher verhält sich mein DWD Adapter von Github unauffällig. 🙂

                                    1 Reply Last reply Reply Quote 1
                                    • apollon77
                                      apollon77 @Master67 last edited by

                                      @master67 Dann muss es aber Fehler im Log geben wenn du startest ... schau mal ins Logfile

                                      Master67 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @homecineplexx last edited by

                                        @homecineplexx Falls du globale Scripts hast werden die ja davorgehängt. du versuchst auf irgendetwas zuzugreifen was falsch ist. von solchen Javascripts hab ich auch einiges im Sentry wo versucht wird ein state zuzugreifen mit nem "." am ende - das ist jetzt verboten. Muss im javascript adapter wohl noch abgefangen werden

                                        H 2 Replies Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @omega235 last edited by

                                          @omega235 Ok, checke

                                          Chaot 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @omega235 last edited by

                                            @omega235 sagte in js-controller 3.2 jetzt im Latest!:

                                            https://github.com/Omega236/ioBroker.virtualpowermeter/tarball/1.3.0

                                            BTW: in js.controller 3.2 geht das viel einfacher :-))

                                            "iobroker url Omega236/ioBroker.virtualpowermeter#1.3.0"

                                            besser als das alte?

                                            ioBrokerChecker created this issue in Omega236/ioBroker.virtualpowermeter

                                            closed Think about to fix the issues found by adapter checker #1

                                            omega235 UncleSam 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            837
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            575
                                            108480
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo