search

tillsteinbach / VWsFriend

VW WeConnect visualization and control
MIT License
238 stars 18 forks source link

Failure to retrieve Car Image #661

Open zaphod-pab opened 1 week ago

zaphod-pab commented 1 week ago

Wanted to report this in quite a while. While everything else works perfectly normal, I continuously get this log output:

2024-09-10T06:49:54+0000:INFO:_internal:192.168.178.78 - - [10/Sep/2024 06:49:54] "GET /status/vehicles/WV2ZZZEBXPHXXXXXX-status_or_car-badge.png HTTP/1.1" 404 -

followed by

2024-09-10T06:51:32+0000:INFO:vehicle:Could not update status picture as birdview image could not be retrieved

The result is a missing picture in the "Car Overview" and also in the "Live View" Dashboards and the following error message:

<!doctype html> <html lang=en> <title>404 Not Found</title> <h1>Not Found</h1> <p>Status picture doesn&#39;t exist.</p>
Object
status:404
statusText:"Not Found"
data:Object
message:"<!doctype html>
<html lang=en>
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>Status picture doesn&#39;t exist.</p>
"
error:"Not Found"
response:"<!doctype html>
<html lang=en>
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>Status picture doesn&#39;t exist.</p>
"
config:Object
url:"api/datasources/proxy/uid/P36D08C1A0297C737/status/vehicles/WV2ZZZEBXPHXXXXXX-status_or_car-badge.png.json"
method:"GET"
headers:Object
retry:0
hideFromInspector:false
traceId:undefined
message:"<!doctype html>
<html lang=en>
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>Status picture doesn&#39;t exist.</p>
"

My car is VW ID.Buzz with SW3.2 and I am using the latest versions of VWsFriend (0.24.5)

tillsteinbach commented 1 week ago

I have seen this before with ID buzz, looks like not all pictures are available for the car.

MatzeG commented 4 days ago

Same here with my Buzz - any chance to get a fix or workaround?

tillsteinbach commented 3 days ago

Can you try to give me logs with higher log level (something like -vvvv), my suspicion is that for the buzz the image is not called birdview. If we can find out how it is called instead we have a chance to fix that. Worst case I would need an account of someone with a Buzz for testing.