search

tillsteinbach / WeConnect-cli

Commandline Interface to interact with the Volkswagen WeConnect Services
MIT License
61 stars 3 forks source link

Temporarily no response from command line #72

Closed gerhard1951 closed 1 year ago

gerhard1951 commented 2 years ago

I really appreciate your work. Unfortunately there is strange problem with WeConnect-cli: It works fine from morning to afternoon and informs about battery status, range, odometer, door status and lock status as expected, every 5 minutes. In the afternoon of the day, only battery status and range is reported correctly, all other commands do not give back the expected value, but (for odometer for instance) "id /vehicles/WVWXXXXXXXXXX/domains/measurements/odometerStatus/odometer not found". This continues until the next morning, then the correct value ist shown again (till afternoon) What could be the reason for this strange behaviour? Thanks for your reply Gerhard

tillsteinbach commented 2 years ago

Hello Gerhard, what kind of car is it, and do you get correct values in the App at the same time?

gerhard1951 commented 2 years ago

Hi Till,

my car is an ID.3, model 2022. I get always (all the day long) correct values for “…charging/batteryStatus/currentSOC_pct”and “… charging/batteryStatus/cruisingRangeElectric_km”, but for “…/measurements/odometerStatus/odometer” and others correct values in the morning, but no response from afternoon on. The command line is always the same.

Von: Till Steinbach @.> Gesendet: Donnerstag, 7. Juli 2022 17:30 An: tillsteinbach/WeConnect-cli @.> Cc: gerhard1951 @.>; Author @.> Betreff: Re: [tillsteinbach/WeConnect-cli] Temporarily no response from command line (Issue #72)

Hello Gerhard, what kind of car is it, and do you get correct values in the App at the same time?

— Reply to this email directly, view it on GitHub https://github.com/tillsteinbach/WeConnect-cli/issues/72#issuecomment-1177796755 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL435QWHAK3SU4T53WPC7Y3VS3ZY5ANCNFSM525ZFC2A . You are receiving this because you authored the thread.Message ID: @.***>

tillsteinbach commented 2 years ago

Hmmm, you are one of the lucky ones that already have a car with 3.0 software. Unfortunately I have some more weeks to wait for my update. So it is hard for me to tell what might be the problem and if it is common. My stomach feeling is that it is a problem on VW side but I‘m of course not sure. Is the data coming back when you drive the car? I‘m afraid that we need to wait for some other user to check if it is a common problem.

gerhard1951 commented 2 years ago

After driving a few kilometers nothing changed – unfortunately. Let´s wait if this is a common problem. To get the problem solved is nice to me, but not of highest importance, because the relevant parameters for me – battery status and range – do always work,

Von: Till Steinbach @.> Gesendet: Donnerstag, 7. Juli 2022 17:55 An: tillsteinbach/WeConnect-cli @.> Cc: gerhard1951 @.>; Author @.> Betreff: Re: [tillsteinbach/WeConnect-cli] Temporarily no response from command line (Issue #72)

Hmmm, you are one of the lucky ones that already have a car with 3.0 software. Unfortunately I have some more weeks to wait for my update. So it is hard for me to tell what might be the problem and if it is common. My stomach feeling is that it is a problem on VW side but I‘m of course not sure. Is the data coming back when you drive the car? I‘m afraid that we need to wait for some other user to check if it is a common problem.

— Reply to this email directly, view it on GitHub https://github.com/tillsteinbach/WeConnect-cli/issues/72#issuecomment-1177839020 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL435QUAJOTHFGNMTCS4XWDVS34XBANCNFSM525ZFC2A . You are receiving this because you authored the thread.Message ID: @.***>

gerhard1951 commented 2 years ago

One more information:

Normally I run weconnet-cli on my Raspbian system. Now I tried out to run it on my Windows system. It worked, but the result is the same: Some commands deliver the right value, on some commands not answer follows.

Von: Till Steinbach @.> Gesendet: Donnerstag, 7. Juli 2022 17:55 An: tillsteinbach/WeConnect-cli @.> Cc: gerhard1951 @.>; Author @.> Betreff: Re: [tillsteinbach/WeConnect-cli] Temporarily no response from command line (Issue #72)

Hmmm, you are one of the lucky ones that already have a car with 3.0 software. Unfortunately I have some more weeks to wait for my update. So it is hard for me to tell what might be the problem and if it is common. My stomach feeling is that it is a problem on VW side but I‘m of course not sure. Is the data coming back when you drive the car? I‘m afraid that we need to wait for some other user to check if it is a common problem.

— Reply to this email directly, view it on GitHub https://github.com/tillsteinbach/WeConnect-cli/issues/72#issuecomment-1177839020 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL435QUAJOTHFGNMTCS4XWDVS34XBANCNFSM525ZFC2A . You are receiving this because you authored the thread.Message ID: @.***>

gerhard1951 commented 2 years ago

Mwanwhile I found out, that

tillsteinbach commented 2 years ago

Thank you for the update. Regarding contacting the Volkswagen support: I don’t believe that Volkswagen is interested in helping making third party software that uses their API work, but if you experience the same behavior on the official WeConnect ID app (it should behave the same) then of course you can report it there. If they fix it for the official app it will be fixed for WeConnect-cli too.

gerhard1951 commented 1 year ago

Unfortunately, last year my ID.3 had to spend nearly four months in the garage because of software and hardware problems. Therefore I could not follow up the above mentioned problem. Meanwhile it seems to be solved.