Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter VW Connect für VW, ID, Audi, Seat, Skoda

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    Test Adapter VW Connect für VW, ID, Audi, Seat, Skoda

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tf @tombox last edited by

      @tombox Im "info" modus das Folgende:

      vw-connect.0 2020-03-15 21:50:12.778 error (6729) 406
      vw-connect.0 2020-03-15 21:50:08.700 info (6729) starting. Version 0.0.11 in /opt/iobroker/node_modules/iobroker.vw-connect, node: v10.19.0

      Im "debug" Modus wie in meiner vorletzten Mail:

      vw-connect.0 2020-03-15 21:16:52.321 debug (6455) 400
      vw-connect.0 2020-03-15 21:16:52.319 debug (6455) error while getting https://msg.volkswagen.de/fs-car/bs/rs/v1/$type/$country/vehicles/$vin/status
      vw-connect.0 2020-03-15 21:16:52.318 debug (6455) 502
      vw-connect.0 2020-03-15 21:16:51.973 debug (6455) {"CurrentVehicleDataResponse":{"requestId":"57619337","vin":"TMBxxxx"}}
      vw-connect.0 2020-03-15 21:16:51.072 error (6455) 406
      vw-connect.0 2020-03-15 21:16:50.785 debug (6455) {"userVehicles":{"vehicle":["TMBxxxxxx"]}}
      vw-connect.0 2020-03-15 21:16:50.502 debug (6455) {"firstName":"xx","lastName":"xx","salutation":"SALUTATION:MR","dateOfBirth":"xx","nickname":"xx","businessIdentifierType":"BUSINESS_IDENTIFIER_TYPE:MBB_ID","businessIdentifier
      vw-connect.0 2020-03-15 21:16:50.269 debug (6455) getData
      vw-connect.0 2020-03-15 21:16:50.267 debug (6455) Login successful
      vw-connect.0 2020-03-15 21:16:49.531 debug (6455) Error: Invalid protocol: skodaconnect:
      vw-connect.0 2020-03-15 21:16:48.792 debug (6455) {"date":"Sun, 15 Mar 2020 20:16:48 GMT","content-length":"0","connection":"close","cache-control":"no-cache, no-store, max-age=0, must-revalidate","content-language":"en","expires":"0","locatio
      vw-connect.0 2020-03-15 21:16:48.791 debug (6455) ""
      vw-connect.0 2020-03-15 21:16:48.396 debug (6455) parsePasswordForm
      vw-connect.0 2020-03-15 21:16:47.923 debug (6455) parseEmailForm

      1 Reply Last reply Reply Quote 0
      • Wszene
        Wszene @opossum last edited by

        @opossum
        Hallo opossum,
        ich bin jetzt auch im Besitz eines Fahrzeugs welches die Funktion hat.
        Darf ich dich mal Fragen ob du mir evtl. zur Anregung und zur Funktionserkennung deine Vis zur verfügung stellen kannst.

        Ich wäre dir sehr Dankbar.

        Gruß
        Marcel

        1 Reply Last reply Reply Quote 0
        • F
          fuchs1978 last edited by

          Wir es in absehbarer Zeit auch die Unterstützung für Seat Connect geben? Die App und Webseite sind jetzt ja online.

          T 1 Reply Last reply Reply Quote 0
          • T
            tombox @fuchs1978 last edited by

            @fuchs1978 bräuchte ich kurzzeitig Zugang zu einem Account um das aufzunehmen

            F 1 Reply Last reply Reply Quote 0
            • F
              fuchs1978 @tombox last edited by

              @tombox said in Test Adapter VW Connect v0.0.x:

              @fuchs1978 bräuchte ich kurzzeitig Zugang zu einem Account um das aufzunehmen

              Ich habe leider noch kein Auto, daher kann ich nicht helfen 😭

              1 Reply Last reply Reply Quote 0
              • Wszene
                Wszene last edited by

                Ich habe im Log immer folgende Fehler

                vw-connect.0	2020-03-25 21:50:25.707	error	(1740) 400
                vw-connect.0	2020-03-25 21:50:25.706	error	(1740) Failing to refresh token.
                

                Hat jemand eine Idee wie ich diese wegbekomme?

                Danke im Voraus

                Gruß
                Marcel

                T 1 Reply Last reply Reply Quote 0
                • T
                  tombox @Wszene last edited by

                  @Wszene sollte nicht passieren du kannst den Adapter mal im debug setzen und mir den log im den Fehler herum per PN zusenden bzw sagen wie oft es passiert. unter Instanzen Experten Modus einstellen und dann log Level auf debug setzen.

                  Wszene 1 Reply Last reply Reply Quote 0
                  • Wszene
                    Wszene @tombox last edited by

                    @tombox
                    Ich finde leider nicht wo ich das debugen einschalten kann

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tombox @Wszene last edited by

                      @Wszene Auf das rote Symbol klicken und dann unter log level einstellen
                      2462799a-77a7-4f5e-9587-60696d3f3bd8-image.png

                      Wszene 1 Reply Last reply Reply Quote 0
                      • Wszene
                        Wszene @tombox last edited by Wszene

                        @tombox
                        OK habe ich gefunden
                        Werde dir heute Abend das Log zukommen lassen

                        EDIT:
                        Log via PN

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          tombox @Wszene last edited by

                          @Wszene Bitte lösche den Log und schicke mir logs nur per pn

                          ich brauch den log wenn der 400 error mit dem refresh token kommt

                          1 Reply Last reply Reply Quote 0
                          • B
                            Bourne @opossum last edited by

                            @opossum wie hast du es bei den Türen umgesetzt, das statt 1, 2 oder 3 dann z.B. geschlossen, offen oder verriegelt ausgegeben wird?

                            1 Reply Last reply Reply Quote 0
                            • opossum
                              opossum last edited by

                              Hallo, @Bourne ,

                              anbei mal dazu ein Screenshot:

                              303f6788-e8e2-4ab9-82a3-324e0c29451d-image.png
                              5f186dce-68fd-4de3-bf37-25a2c3ff96ce-image.png

                              B 2 Replies Last reply Reply Quote 0
                              • B
                                Bourne @opossum last edited by Bourne

                                @opossum ok, danke, hab es mal so übernommen. mein Problem ist jetzt, dass der Text nicht angezeigt wird 😞

                                Edit: Text wird jetzt angezeigt, ohne das ich was geändert habe, komisch.

                                1 Reply Last reply Reply Quote 0
                                • B
                                  Bourne @opossum last edited by

                                  @opossum said in Test Adapter VW Connect v0.0.x:

                                  Hallo, @Bourne ,

                                  anbei mal dazu ein Screenshot:

                                  303f6788-e8e2-4ab9-82a3-324e0c29451d-image.png
                                  5f186dce-68fd-4de3-bf37-25a2c3ff96ce-image.png

                                  Nun habe ich ein weiteres Problem mit der Map-Anzeige.
                                  Bekomme immer die Fehlermeldung im widget:

                                  "Google Maps kann auf dieser Seite nicht richtig geladen werden."

                                  Habe Api-Schlüssel erstellt und eingetragen wo es erforderlich ist.
                                  Muss ich jetzt noch irgendwas anderes bei google oder im iobroker einstellen?

                                  1 Reply Last reply Reply Quote 0
                                  • cvidal
                                    cvidal Forum Testing last edited by

                                    Hi, ich habe vorhin mein System auf NodeJS 12 geupdatet, leider läuft der Adapter damit noch nicht.
                                    Ist es in nächster Zeit geplant das der Adapter mit NodeJS 12 läuft oder sollte ich erst wieder auf Version 10 gehen?
                                    Folgendes sagt mein Log:

                                    host.IoBroker	2020-04-14 14:15:58.343	info	Restart adapter system.adapter.vw-connect.0 because enabled
                                    host.IoBroker	2020-04-14 14:15:58.343	error	instance system.adapter.vw-connect.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                    host.IoBroker	2020-04-14 14:15:58.343	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:899:14)
                                    host.IoBroker	2020-04-14 14:15:58.343	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:1000:32)
                                    host.IoBroker	2020-04-14 14:15:58.343	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1156:30)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/canvas/lib/bindings.js:3:18)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:77:18)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1042:19)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:899:14)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:1000:32)
                                    host.IoBroker	2020-04-14 14:15:58.342	error	Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1206:18)
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: NODE_MODULE_VERSION 64. This version of Node.js requires
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: was compiled against a different Node.js version using
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/canvas/build/Release/canvas.node'
                                    host.IoBroker	2020-04-14 14:15:58.341	error	Caught by controller[0]: ^
                                    host.IoBroker	2020-04-14 14:15:58.340	error	Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename));
                                    host.IoBroker	2020-04-14 14:15:58.340	error	Caught by controller[0]: internal/modules/cjs/loader.js:1206
                                    host.IoBroker	2020-04-14 14:15:57.905	info	instance system.adapter.vw-connect.0 started with pid 18419
                                    host.IoBroker	2020-04-14 14:15:57.883	info	"system.adapter.vw-connect.0" enabled
                                    
                                    T 1 Reply Last reply Reply Quote 0
                                    • T
                                      tombox @cvidal last edited by

                                      @cvidal Hast du auch rebuild ausgeführt? es scheint so als müsste etwas neugebaut werden für den Adapter. Neuinstallation könnte vielleicht auch schon helfen?

                                      cvidal 1 Reply Last reply Reply Quote 0
                                      • cvidal
                                        cvidal Forum Testing @tombox last edited by

                                        @tombox Neuinstallation hilft hier nicht bei npm rebuild bekomme ich Errors mit denen ich nicht weiterkomme.


                                        root@IoBroker:/home/christian# cd /opt/iobroker
                                        root@IoBroker:/opt/iobroker# npm rebuild

                                        iobroker.js-controller@2.2.9 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                                        node lib/preinstallCheck.js

                                        NPM version: 6.14.4

                                        iobroker.js-controller@2.2.9 install /opt/iobroker/node_modules/iobroker.js-controller
                                        node iobroker.js setup first

                                        acme-v2@1.8.6 postinstall /opt/iobroker/node_modules/acme-v2
                                        node scripts/postinstall

                                        Greenlock and ACME.js v3 are on the way!
                                        Watch for updates at https://indiegogo.com/at/greenlock

                                        authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
                                        node-gyp rebuild

                                        make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
                                        CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
                                        ../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:
                                        ../authenticate_pam.cc:107:87: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value*)’ is deprecated [-Wdeprecated-declarations]
                                        keCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                        ^
                                        In file included from ../authenticate_pam.cc:23:0:
                                        ../../nan/nan.h:1024:46: note: declared here
                                        NAN_DEPRECATED inline v8::Localv8::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::Localv8::Value v8::Object::Get(v8::Localv8::Value)’ is deprecated: Use maybe version [-Wdeprecated-declaration ]
                                        al<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8-internal.h:14:0,
                                        from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
                                        from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:3553:51: note: declared here
                                        V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                        ^
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
                                        declarator attribute((deprecated(message)))
                                        ^~~~~~~~~~
                                        ../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
                                        serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
                                        int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                        ^~~~~~~~~
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                                        ../authenticate_pam.cc:152:69: warning: ‘v8::Localv8::Value v8::Object::Get(v8::Localv8::Value)’ is deprecated: Use maybe version [-Wdeprecated-declaration ]
                                        res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8-internal.h:14:0,
                                        from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
                                        from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:3553:51: note: declared here
                                        V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                        ^
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
                                        declarator attribute((deprecated(message)))
                                        ^~~~~~~~~~
                                        ../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
                                        remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
                                        int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                        ^~~~~~~~~
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                                        ../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
                                        username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
                                        int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                        ^~~~~~~~~
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                                        ../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
                                        password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                        ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
                                        from ../../nan/nan.h:54,
                                        from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
                                        int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                        ^~~~~~~~~
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                                        ../authenticate_pam.cc: At global scope:
                                        ../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void
                                        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
                                        void init(Handle<Object> exports) {
                                        ^
                                        ../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope
                                        void init(Handle<Object> exports) {
                                        ^~~~~~~
                                        In file included from ../../nan/nan.h:54:0,
                                        from ../authenticate_pam.cc:23:
                                        ../authenticate_pam.cc:175:31: error: ‘init’ was not declared in this scope
                                        NODE_MODULE(authenticate_pam, init);
                                        ^
                                        /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’
                                        (node::addon_register_func) (regfunc),
                                        ^~~~~~~
                                        ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
                                        NODE_MODULE(authenticate_pam, init);
                                        ^~~~~~~~~~~
                                        authenticate_pam.target.mk:111: die Regel für Ziel „Release/obj.target/authenticate_pam/authenticate_pam.o“ scheiterte
                                        make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                                        make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
                                        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:310:20)
                                        gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                                        gyp ERR! System Linux 4.9.0-11-amd64
                                        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.16.2
                                        gyp ERR! node-gyp -v v5.1.0
                                        gyp ERR! not ok
                                        npm ERR! code ELIFECYCLE
                                        npm ERR! errno 1
                                        npm ERR! authenticate-pam@1.0.2 install: node-gyp rebuild
                                        npm ERR! Exit status 1
                                        npm ERR!
                                        npm ERR! Failed at the authenticate-pam@1.0.2 install script.
                                        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

                                        npm ERR! A complete log of this run can be found in:
                                        npm ERR! /home/iobroker/.npm/_logs/2020-04-14T20_19_29_910Z-debug.log
                                        root@IoBroker:/opt/iobroker#

                                        1 Reply Last reply Reply Quote 0
                                        • Wszene
                                          Wszene last edited by

                                          Hallo Zusammen,

                                          Ich bekomme seid dem 24.04 keine Daten mehr
                                          Das heist in der App wird alles aktualisiert aber im ioBroker nicht

                                          Gruß
                                          Marcel

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            Scooty last edited by Scooty

                                            Hier leider auch (Skoda), Auszug aus dem Log:

                                            vw-connect.0	2020-04-30 17:31:00.777	error	(1538) 400
                                            vw-connect.0	2020-04-30 17:31:00.776	error	(1538) Failing to refresh token.
                                            vw-connect.0	2020-04-30 17:31:00.353	debug	(1538) refreshToken
                                            vw-connect.0	2020-04-30 17:07:25.361	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/dwap/v1/$type/$country/vehicles/$vin/history
                                            vw-connect.0	2020-04-30 17:07:25.360	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:25.353	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/rs/v1/$type/$country/vehicles/$vin/status
                                            vw-connect.0	2020-04-30 17:07:25.352	debug	(1538) 502
                                            vw-connect.0	2020-04-30 17:07:25.322	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/cf/v1/$type/$country/vehicles/$vin/position
                                            vw-connect.0	2020-04-30 17:07:25.321	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:25.287	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/batterycharge/v1/$type/$country/vehicles/$vin/charger
                                            vw-connect.0	2020-04-30 17:07:25.287	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:25.185	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/departuretimer/v1/$type/$country/vehicles/$vin/timer
                                            vw-connect.0	2020-04-30 17:07:25.184	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:24.808	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/vsr/v1/$type/$country/vehicles/$vin/status
                                            vw-connect.0	2020-04-30 17:07:24.807	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:24.796	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/climatisation/v1/$type/$country/vehicles/$vin/climater
                                            vw-connect.0	2020-04-30 17:07:24.795	debug	(1538) 403
                                            vw-connect.0	2020-04-30 17:07:23.662	debug	(1538) {"destinations":[]}
                                            vw-connect.0	2020-04-30 17:07:23.416	debug	(1538) error while getting https://msg.volkswagen.de/fs-car/bs/tripstatistics/v1/$type/$country/vehicles/$vin/tripdata/$tripType?type=list
                                            vw-connect.0	2020-04-30 17:07:23.415	debug	(1538) 400
                                            vw-connect.0	2020-04-30 16:43:13.279	debug	(1538) {"access_token":"xxxx
                                            vw-connect.0	2020-04-30 16:43:13.108	debug	(1538) refreshToken
                                            vw-connect.0	2020-04-30 16:37:00.846	error	(1538) 400
                                            vw-connect.0	2020-04-30 16:37:00.845	error	(1538) Failing to refresh token.
                                            vw-connect.0	2020-04-30 16:37:00.352	debug	(1538) refreshToken
                                            

                                            Access Token habe ich unkenntlich gemacht.
                                            Fehler mit "Failing to refresh token" war weiter oben schon ´mal erwähnt, leider ohne Lösung, die ich nachvollziehen könnte.

                                            Viele Grüße,
                                            Andreas

                                            T 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            577
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            audi id.3 myaudi seat skoda skoda connect volkswagen vw id we connect wecharge
                                            386
                                            3014
                                            1118726
                                            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