FAQ - tillsteinbach/VWsFriend GitHub Wiki

Why can't I make changes to the dashboards in Grafana? Why do I get the error: "Cannot save provisioned dashboard"

The dashboards are updated with every update of VWsFriend. To not loose your changes the appropriate way to adapt VWsFriend is to use "Save dashboard as..." and safe a copy of the dashboard. This way your changes will persist on your copy while VWsFriend dashboards are evolving.

I get "Fatal Python error: init_interp_main: can't initialize time"

You are probably running a Raspberry PI. This error only affects 32 bit installs of distributions based on Debian Buster. This is due to a bug in the libseccomp2 library (dependency of Docker itself), which is fixed. However it's not included in all recent images yet. You can fix this problem by updating libseccomp2. The easiest way is through the backports repo for Debian Buster:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC 648ACFD622F3D138
echo "deb http://deb.debian.org/debian buster-backports main" | sudo tee -a /etc/apt/sources.list.d/buster-backports.list
sudo apt update
sudo apt install -t buster-backports libseccomp2

VWsFriend is unable to connect to WeConnect, complains that "No user id provided"

Errors like this on container startup:

vwsfriend_1   | 2023-03-01T10:35:05+0000:CRITICAL:vwsfriend_base:There was a problem when communicating with WeConnect. If this problem persists please open a bug report: No user id provided
vwsfriend_vwsfriend_1 exited with code 0

...may be due expiry of your acceptance of the terms and conditions on myvolkswagen.net. This seems to happen occasionally for some users. Log in to MyVolkswagen, go to Settings, then hit the Edit data button in the Volkswagen ID section. This should bring up a request for you to (re-)accept the terms and conditions.

Your are not able to connect to the Webfrontend http://ip-address:4000/ and the Grafana Statistics on http://ip-address:4000/. Answer is always "webpage not found"

Try to access the Front end on the engine where the container is running on http://0.0.0.0:4000/
Check IP-Adress of your Raspi/Synology and check if your can get access to the frontend with the IP-Adress of your server. e.g. http://192.168.178.150:4000