search

robinostlund / homeassistant-volkswagencarnet

Volkswagen Carnet Component for home assistant
GNU General Public License v3.0
303 stars 61 forks source link

connection error #493

Closed kwithus closed 10 months ago

kwithus commented 10 months ago

Before you post a new issue - you must first check the following (and check the boxes with an "X" below)

Environment

HA core 2023.8.4 latest version of integration

Describe the bug

Integration reports need of re-configuration, which is then done and successful, however short after connection is lost again and integration asks for re-configuration. I deleted the integration and reinstalled everything, initial configuration was again successful, but again short after it was lost

I can log in with same credentials via App or Web

Steps to Reproduce

Expected behavior

Screenshots

Traceback/Error logs

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.volkswagencarnet Source: helpers/update_coordinator.py:229 Integration: Volkswagen WeConnect (documentation, issues) First occurred: 14:11:16 (2 occurrences) Last logged: 15:03:50

Error fetching volkswagencarnet data: Failed to update WeConnect. Need to accept EULA? Try logging in to the portal: https://www.portal.volkswagen-we.com/

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.volkswagencarnet Source: custom_components/volkswagencarnet/init.py:489 Integration: Volkswagen WeConnect (documentation, issues) First occurred: 14:11:16 (2 occurrences) Last logged: 15:03:50

Could not query update from volkswagen WeConnect

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: volkswagencarnet.vw_connection Source: custom_components/volkswagencarnet/init.py:541 Integration: Volkswagen WeConnect (documentation, issues) First occurred: 14:11:16 (2 occurrences) Last logged: 15:03:50

Could not update information: 'serviceInfo'-->

Additional context

Logger: volkswagencarnet.vw_connection Source: runner.py:179 First occurred: 14:05:52 (109 occurrences) Last logged: 15:03:50 Got unhandled error from server: 429 Could not fetch pre-heating, HTTP status code: 429 Could not fetch climatisation, HTTP status code: 429 Could not fetch carportData, error: 'WVWZZZAUZL8916704' Could not fetch operation list, error: 'WVWZZZAUZL8916704'
jacobgarder commented 10 months ago

I have similar error after upgrade to HA core 2023.8.4. I can login https://vwid.vwgroup.io/ (no new EULAs to accept and no messages).

Loginfo:

2023-08-25 16:28:07.738 DEBUG (MainThread) [custom_components.volkswagencarnet] Updating data from volkswagen WeConnect
2023-08-25 16:28:07.738 DEBUG (MainThread) [custom_components.volkswagencarnet] Finished fetching volkswagencarnet data in 1.455 seconds (success: False)
2023-08-25 16:28:07.738 DEBUG (MainThread) [custom_components.volkswagencarnet] Async update finished for WVWZZZ3CZKE01xxxx (volkswagencarnet). Next update in 0:05:00.
2023-08-25 16:30:20.295 WARNING (MainThread) [volkswagencarnet.vw_connection] Received "unauthorized" error while fetching data: 401, message='', url=URL('https://msg.volkswagen.de/fs-car/vehicleMgmt/vehicledata/v2/VW/SE/vehicles/WVWZZZ3CZKE01xxxx')
2023-08-25 16:30:20.296 WARNING (MainThread) [volkswagencarnet.vw_connection] Could not fetch carportdata, HTTP status code: 401
2023-08-25 16:30:29.440 ERROR (MainThread) [volkswagencarnet.vw_connection] Got unhandled error from server: 429
2023-08-25 16:30:29.442 WARNING (MainThread) [volkswagencarnet.vw_connection] Could not fetch operation list, HTTP status code: 429
2023-08-25 16:30:29.443 WARNING (MainThread) [volkswagencarnet.vw_connection] Could not update information: 'serviceInfo'
2023-08-25 16:30:29.444 WARNING (MainThread) [custom_components.volkswagencarnet] Could not query update from volkswagen WeConnect
2023-08-25 16:30:29.445 ERROR (MainThread) [custom_components.volkswagencarnet] Error fetching volkswagencarnet data: Failed to update WeConnect. Need to accept EULA? Try logging in to the portal: https://www.portal.volkswagen-we.com/
2023-08-25 16:30:29.446 DEBUG (MainThread) [custom_components.volkswagencarnet] Finished fetching volkswagencarnet data in 27.023 seconds (success: False)
janchlebek commented 10 months ago

Does not seem to be related to 2023.8.4 as I am still on 2023.8.3 where it worked just fine until today. In my case the issue started after HA OS update so I think the trigger is just any kind of restart.

kwithus commented 10 months ago

thanks for adding, so its at least most likely not a problem on our side, but either the integration needs to be updated to 2023.8.4 (or a bug in .4) or (although not so likely) VW has changed something in regards to the api Lets hope the developer finds time to look into it asap, thanks for that in advance

janchlebek commented 10 months ago

Again, 2023.8.4 or bug in it is not the point here as I am on older core. My feeling is that this is something on VW side, hopefully not breaking change for the integration (can be only some kind of temporary outage - would not be the first one).

danielszilagyi commented 10 months ago

Same here without any updates to HA since yesterday night Europe time.

App didn’t work even in the morning hours. App is now OK, integration fails to setup after reauthentication.

kwithus commented 10 months ago

Last time I had connection issues it was always also an issue to connect via the app. This time it’s only the integration.

vdleun commented 10 months ago

Same issue here. App and website are working, integration is not. For what it's worth, still on 2023.8.3 here.

janchlebek commented 10 months ago

Last time I had connection issues it was always also an issue to connect via the app. This time it’s only the integration.

I recall situations that the app worked but HA integration not.

andlo commented 10 months ago

VW confirms that they earlier had a system down Wich resulted in no login from app. Now it is up and working, but can't login whit ha integration :( I suspect that vw have made changes and the downtime were when they implemented such changes...

CZaMOR commented 10 months ago

I have the same problem. I called Car-Net support this morning and they said they have been registering server failures in Europe since 3:00 CET. Around 11:00 CET the app came back up. The mobile app and the browser page works now. HA does not work.

chrisandsally commented 10 months ago

4 Hours on. App working but HA not. Hope it is not a breaking change.

danielszilagyi commented 10 months ago

here's some debug log if you could take a look, @robinostlund I think it would be much appreciated.

weconnect.log

Phoenix-DH commented 10 months ago

Exactly same behaviour here.

Thanks for working on a fix.

hanjuq commented 10 months ago

Same for me: web login works, official VW app (android) works but no chance to re-add (after deletion) the HA integration. Maybe this hint could help to fix: https://github.com/tillsteinbach/WeConnect-mqtt actually does a successful login.

mava75 commented 10 months ago

Also have the same problem with login in the integration after uppdatering to 8.4 from 8.3. Then rolling back to 8.3 it works again.

janchlebek commented 10 months ago

As I said before - this has nothing to do with HA core version, it is/was a problem at VW side. I reauthenticated now successfully without making any changes on HA, seems they fixed it.

chrisandsally commented 10 months ago

@janchlebek Re-authenticated (get message saying successful) but fails to load entities. So something is still not right. On 2023.8.4.

omaba1 commented 10 months ago

Same with me @chrisandsally

janchlebek commented 10 months ago

I'd say - keep trying, maybe you are hitting different servers. For me it stopped working on 2023.8.3, in the meantime I updated to 8.4 and it works for me now.

hanjuq commented 10 months ago

On 8.4 just in this moment (didn't try a rollback): Zwischenablage01

Weconnect-Android works, https://identity.vwgroup.io works!

My region: Germany/Augsburg(close to Munich)

danielszilagyi commented 10 months ago

It still doesn't work for me either. Probably depends on region.

Removed the integration and added again with debug logging on setup. Hope it helps on resolving the issue.

2023-08-26 12:07:35.665 DEBUG (MainThread) [custom_components.volkswagencarnet.config_flow] Creating connection to volkswagen weconnect
2023-08-26 12:07:35.666 DEBUG (MainThread) [volkswagencarnet.vw_connection] Using service https://msg.volkswagen.de
2023-08-26 12:07:35.692 DEBUG (MainThread) [volkswagencarnet.vw_connection] Initiating new login
2023-08-26 12:07:35.693 DEBUG (MainThread) [volkswagencarnet.vw_connection] Requesting openid config
2023-08-26 12:07:35.888 DEBUG (MainThread) [volkswagencarnet.vw_connection] Get authorization page from "https://identity.vwgroup.io/oidc/v1/authorize"
2023-08-26 12:07:35.889 DEBUG (MainThread) [volkswagencarnet.vw_connection] Request headers: "{'Connection': 'keep-alive', 'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9', 'Accept-Encoding': 'gzip, deflate', 'Content-Type': 'application/x-www-form-urlencoded', 'x-requested-with': 'We Connect', 'User-Agent': 'okhttp/3.14.7', 'X-App-Name': 'We Connect'}"
2023-08-26 12:07:35.985 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got redirect to "https://identity.vwgroup.io/signin-service/v1/signin/9496332b-ea03-4091-a224-8c746b885068@apps_vw-dilab_com?relayState=216079d5711cd9352d5754e62400227b419e5d1e"
2023-08-26 12:07:36.114 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got authorization endpoint
2023-08-26 12:07:36.366 DEBUG (MainThread) [volkswagencarnet.vw_connection] Authenticating with email and password.
2023-08-26 12:07:36.366 DEBUG (MainThread) [volkswagencarnet.vw_connection] Using login action url: "https://identity.vwgroup.io/signin-service/v1/9496332b-ea03-4091-a224-8c746b885068@apps_vw-dilab_com/login/authenticate"
2023-08-26 12:07:36.838 DEBUG (MainThread) [volkswagencarnet.vw_connection] Parsing login response.
2023-08-26 12:07:36.838 DEBUG (MainThread) [volkswagencarnet.vw_connection] Following redirect to "https://identity.vwgroup.io/oidc/v1/oauth/sso?clientId=9496332b-ea03-4091-a224-8c746b885068@apps_vw-dilab_com&relayState=216079d5711cd9352d5754e62400227b419e5d1e&userId=26e933df-ff39-469d-aac8-4357df530430&HMAC=64354f0cce9bf11986bf5449cd70d9bd9c979b2391eb9e48491e871b210a800d"
2023-08-26 12:07:36.921 DEBUG (MainThread) [volkswagencarnet.vw_connection] Following redirect to "https://identity.vwgroup.io/signin-service/v1/consent/users/26e933df-ff39-469d-aac8-4357df530430/9496332b-ea03-4091-a224-8c746b885068@apps_vw-dilab_com?scopes=openid%20mbb%20profile%20cars%20address%20email%20birthdate%20nickname%20phone&relayState=216079d5711cd9352d5754e62400227b419e5d1e&callback=https://identity.vwgroup.io/oidc/v1/oauth/client/callback&hmac=5d1bbb6b77acfce40356e14584b12f1dc2dfbd96f04fe14aa2f50376c1a50abc"
2023-08-26 12:07:37.055 DEBUG (MainThread) [volkswagencarnet.vw_connection] Following redirect to "https://identity.vwgroup.io/oidc/v1/oauth/client/callback/success?user_id=26e933df-ff39-469d-aac8-4357df530430&client_id=9496332b-ea03-4091-a224-8c746b885068@apps_vw-dilab_com&scopes=openid%20mbb%20profile%20cars%20address%20email%20birthdate%20nickname%20phone&consentedScopes=openid%20mbb%20profile%20cars%20address%20email%20birthdate%20nickname%20phone&relayState=216079d5711cd9352d5754e62400227b419e5d1e&hmac=8c41f7b1f5f28bf7f8ce603edadd0936a2008f726db157ce521f132b7facbc4b"
2023-08-26 12:07:37.196 DEBUG (MainThread) [volkswagencarnet.vw_connection] Login successful, received authorization code.
2023-08-26 12:07:37.197 DEBUG (MainThread) [volkswagencarnet.vw_connection] Trying to fetch user identity tokens.
2023-08-26 12:07:37.702 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token access_token
2023-08-26 12:07:37.702 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token expires_in
2023-08-26 12:07:37.703 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token id_token
2023-08-26 12:07:37.703 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token refresh_token
2023-08-26 12:07:37.703 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token token_type
2023-08-26 12:07:37.910 DEBUG (MainThread) [volkswagencarnet.vw_connection] User identity token verified OK.
2023-08-26 12:07:37.911 INFO (MainThread) [volkswagencarnet.vw_connection] Successfully logged in
2023-08-26 12:07:37.911 DEBUG (MainThread) [volkswagencarnet.vw_connection] Trying to fetch api tokens.
2023-08-26 12:07:38.145 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token access_token
2023-08-26 12:07:38.146 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token token_type
2023-08-26 12:07:38.146 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token refresh_token
2023-08-26 12:07:38.146 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token expires_in
2023-08-26 12:07:38.147 DEBUG (MainThread) [volkswagencarnet.vw_connection] Got token scope
2023-08-26 12:07:38.233 DEBUG (MainThread) [volkswagencarnet.vw_connection] VW-Group API token verified OK.
2023-08-26 12:07:38.233 DEBUG (MainThread) [volkswagencarnet.vw_connection] Fetching vehicles associated with account
2023-08-26 12:07:38.233 DEBUG (MainThread) [volkswagencarnet.vw_connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/HU/vehicles"
2023-08-26 12:07:38.564 DEBUG (MainThread) [volkswagencarnet.vw_connection] Server side throttled. Waiting 1, try 1
2023-08-26 12:07:39.565 DEBUG (MainThread) [volkswagencarnet.vw_connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/HU/vehicles"
2023-08-26 12:07:39.775 DEBUG (MainThread) [volkswagencarnet.vw_connection] Server side throttled. Waiting 4, try 2
2023-08-26 12:07:43.799 DEBUG (MainThread) [volkswagencarnet.vw_connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/HU/vehicles"
2023-08-26 12:07:44.030 DEBUG (MainThread) [volkswagencarnet.vw_connection] Server side throttled. Waiting 4, try 3
2023-08-26 12:07:48.183 DEBUG (MainThread) [volkswagencarnet.vw_connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/HU/vehicles"
2023-08-26 12:07:48.324 ERROR (MainThread) [volkswagencarnet.vw_connection] Got unhandled error from server: 429
2023-08-26 12:07:48.331 WARNING (MainThread) [volkswagencarnet.vw_connection] Failed to login to We Connect API.

The app/webpage works, no EULA changes visible anywhere. Tried even signing out and in of the We Connect app, doesn't make any difference.

A quick google search on http 429 reveals that this might be some kind of throttling on the API side, based on the request or user-agent...

chrisandsally commented 10 months ago

Interesting @janchlebek please could you let us know what country you have specified as I have DE even though in UK.

andlo commented 10 months ago

I can't get it working :( keeps trying same result. App on mobile is working.

stepir commented 10 months ago

same here - will try updating HA

m-art-in-hof commented 10 months ago

same here - will try updating HA

Let us know what the result is

janchlebek commented 10 months ago

Interesting @janchlebek please could you let us know what country you have specified as I have DE even though in UK.

I'm in CZ and have also CZ set as region.

RegularAdrian commented 10 months ago

I had this issue too - HA not signing in even though Weconnect App on iOS signing in fine without it bringing up any requests or agreements.

However, this morning I went to https://vwid.vwgroup.io/ just to check, and was presented with another terms and conditions agreement. Agreed to it and HA started working again.

Don’t know whether whatever VW did triggered this, but thought I’d share.

Edit: Also am on latest HA Core 2023.8.4

Edit 2: Day 2 - stopped working again...

stepir commented 10 months ago

Updated to 8.34

now this is what I get as soon as I reconfigure and the wizard report ‘reauthentication successful’

image

CZaMOR commented 10 months ago

For me, it still doesn't work. I am also from CZ, I bought my car from NL, I tried to select NL, CZ, DE when registering and the same problem that I could not login to Volkswagen We Connect. I tried logging in at https://vwid.vwgroup.io and no new license terms there.

raresv commented 10 months ago

429

The "429" HTTP Error code (assuming that is what error code is being logged) is about "rate limiting". It's possible that VW changed something on their side to limit the number of API requests which can be done for each account.

hanjuq commented 10 months ago

Rate limiting cannot explain my problem. My temporarily used alternative https://github.com/tillsteinbach/WeConnect-mqtt get's a bunch of data the whole day all 300 seconds for 280 different mqtt topics!

nmsoares commented 10 months ago

Hi. I suffer from the same. I noticed that it stooped working since I updated to 2023.8. Could be a coincidence and API change/servers down.

These are the errors I get on from the log:

This error originated from a custom integration.

Logger: homeassistant.config_entries Source: custom_components/volkswagencarnet/init.py:527 Integration: Volkswagen We Connect (documentation, issues) First occurred: 4:30:22 PM (1 occurrences) Last logged: 4:30:22 PM

Error setting up entry myCar for volkswagencarnet Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/volkswagencarnet/init.py", line 125, in async_setup_entry if not await coordinator.async_login(): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/volkswagencarnet/init.py", line 527, in async_login await self.connection.doLogin(3) File "/usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py", line 117, in doLogin loaded_vehicles = await self.get( ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py", line 504, in get response = await self._request(METH_GET, self._make_url(url, vin)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py", line 463, in _request async with self._session.request( File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 1141, in aenter self._resp = await self._coro ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 560, in _request await resp.start(conn) File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 899, in start message, payload = await protocol.read() # type: ignore[union-attr] ^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 616, in read await self._waiter aiohttp.client_exceptions.ClientOSError: [Errno 104] Connection reset by peer

Any fixes / workarrounds ?

danielszilagyi commented 10 months ago

Rate limiting cannot explain my problem. My temporarily used alternative https://github.com/tillsteinbach/WeConnect-mqtt get's a bunch of data the whole day all 300 seconds for 280 different mqtt topics!

I can confirm this tool is able to fetch data properly. However I hope the integration will also get a fix.

GroundAttack commented 10 months ago

Daniel, I would love to try WeConnect-mqtt but I have a HAOS install. Is it possible to install it on my system? Any tips on how to do that appreciated.

mrandt commented 10 months ago

Same issue here.

Appeared out of the blue, not sure when it had last worked.

I have deleted and re-added the integration, enabled debug logs.

Error seems to be here:

2023-08-26 18:48:02.938 DEBUG (MainThread) [volkswagencarnet.vw_connection] HTTP GET "https://msg.volkswagen.de/fs-car/usermanagement/users/v1/VW/DE/vehicles"
2023-08-26 18:48:03.174 ERROR (MainThread) [volkswagencarnet.vw_connection] Got unhandled error from server: 429
2023-08-26 18:48:03.180 WARNING (MainThread) [volkswagencarnet.vw_connection] Failed to login to We Connect API.

HTTP 429 indicates too many requests, so I'll retry tomorrow and report back.

andlo commented 10 months ago

Daniel, I would love to try WeConnect-mqtt but I have a HAOS install. Is it possible to install it on my system? Any tips on how to do that appreciated.

Yah it s posible and quite easy. But not relevant on this issue though.

Make a folder /addons/weconnect-mqtt add a file named Dockerfile whith this content:

`FROM python:3.11.0-alpine as base RUN apk add --update tzdata

FROM python:3.11.0-alpine ARG VERSION ENV USER="XXXXXXXXXXXX" ENV PASSWORD="XXXXXXXXXX" ENV BROKER_ADDRESS=XXX.XXX.XXX.XXX ENV ADDITIONAL_PARAMETERS="--mqtt-username XXXXXX --mqtt-password XXXXX--prefix weconnect" ENV TZ= ENV MUSL_LOCPATH="/usr/share/i18n/locales/musl"

COPY --from=base /usr/share/zoneinfo /usr/share/zoneinfo

RUN apk --no-cache add --virtual build-dependencies build-base \ && apk --no-cache add jpeg-dev \ zlib-dev \ freetype-dev \ lcms2-dev \ openjpeg-dev \ tiff-dev \ tk-dev \ tcl-dev \ musl-locales \ musl-locales-lang \ && pip install weconnect-mqtt \ && apk del build-dependencies

CMD weconnect-mqtt --username ${USER} --password ${PASSWORD} --mqttbroker ${BROKER_ADDRESS} ${ADDITIONAL_PARAMETERS}`

Replase XXXXX whith correct information like username and psswords etc.

Make another file named config.yaml with this content:

`name: "WeConnect-MQTT" description: "My first real add-on!" version: "0.0.1" slug: "weconnect" init: false arch:

GroundAttack commented 10 months ago

Wow, that's great. I don't mind where I get the data from as I use it in HA to regulate my solar dump to EV. It's pretty essential for me.

thank you for taking the time to put this together, much appreciated.

megabyte0469 commented 10 months ago

I have the same problem.

I can log on to the Volkswagen website with the ID. The Volkswagen app works with the ID. EVCC uses the same credentials and still works. I have deleted the integration and added it again. Without success. Again and again the same. Entering the login data works and it reports that it was done correctly. After initialisation, however, the error occurs again.

Logging on to the WeConnect page works perfectly. No problems here. No new guidelines are reported here to confirm, as some had already reported.

The error started with the update of the HomeAssistant to version 8.4. With 8.3 everything still worked.

stepir commented 10 months ago

No I was running 6.3 and still got the error - updated to 8.4 and nothing changed

it has to do with some changes made on the portal

P356c commented 10 months ago

Same probleem here and still using a previous HA version 2023.7.3. Thanx for looking in to it!

shiraz-b commented 10 months ago

+1 on this issue. I'm happy to help testing any solution/provide logs as required.

jurrianv commented 10 months ago

I have the same problem. I'm running HA version 2023.8.4. It did work on this version.

janchlebek commented 10 months ago

I have the same problem. I'm running HA version 2023.8.4. It did work on this version.

I can confirm it works on this one, it does not depend on HA at all. It is for sure something on VW side.

I had the problem too but then simply out of nothing yesterday it just started to work. Reauthenticated, all entities appeared in HA and the warning does not come back (I did not even remove/add the integration).

megabyte0469 commented 10 months ago

@jurrianv ok it works for you under 8.4. Which location did you use for WE Connect? I'm starting to think this is a location problem with WeConnect. Because for some it still works under 8.4 and for others (like me) it doesn't.

shiraz-b commented 10 months ago

Ok - I'm on 2023.5.2 - So I'll up to latest and report back... thanks... (FYI - I'm in the UK, so I use GB for my WeConnect Location)

saikimecky commented 10 months ago

I'm connected in Germany. Still doesn't work. 🤷‍♂️

GroundAttack commented 10 months ago

Andreas, (andlo) when installing WeConnect-mqtt I get this Error: dockerfile parse error on line 22: unknown instruction: &&

here is the error message: 400 Client Error for http+docker://localhost/v1.42/build?t=local%2Faarch64-addon-weconnect%3A0.0.1&q=False&nocache=False&rm=False&forcerm=True&pull=True&dockerfile=Dockerfile&buildargs=%7B%22BUILD_FROM%22%3A+%22ghcr.io%2Fhome-assistant%2Faarch64-base%3Alatest%22%2C+%22BUILD_VERSION%22%3A+%220.0.1%22%2C+%22BUILD_ARCH%22%3A+%22aarch64%22%7D&labels=%7B%22io.hass.version%22%3A+%220.0.1%22%2C+%22io.hass.arch%22%3A+%22aarch64%22%2C+%22io.hass.type%22%3A+%22addon%22%2C+%22io.hass.name%22%3A+%22WeConnect-MQTT%22%2C+%22io.hass.description%22%3A+%22My+first+real+add-on%21%22%7D&platform=linux%2Farm64: Bad Request ("dockerfile parse error on line 22: unknown instruction: &&")

megabyte0469 commented 10 months ago

@saikimecky same here from Germany

CZaMOR commented 10 months ago

Andreas, (andlo) when installing WeConnect-mqtt I get this Error: dockerfile parse error on line 22: unknown instruction: &&

here is the error message: 400 Client Error for http+docker://localhost/v1.42/build?t=local%2Faarch64-addon-weconnect%3A0.0.1&q=False&nocache=False&rm=False&forcerm=True&pull=True&dockerfile=Dockerfile&buildargs=%7B%22BUILD_FROM%22%3A+%22ghcr.io%2Fhome-assistant%2Faarch64-base%3Alatest%22%2C+%22BUILD_VERSION%22%3A+%220.0.1%22%2C+%22BUILD_ARCH%22%3A+%22aarch64%22%7D&labels=%7B%22io.hass.version%22%3A+%220.0.1%22%2C+%22io.hass.arch%22%3A+%22aarch64%22%2C+%22io.hass.type%22%3A+%22addon%22%2C+%22io.hass.name%22%3A+%22WeConnect-MQTT%22%2C+%22io.hass.description%22%3A+%22My+first+real+add-on%21%22%7D&platform=linux%2Farm64: Bad Request ("dockerfile parse error on line 22: unknown instruction: &&")

here is the corrected code that should work, however, even after installing the plugin, it does not connect to the volkswagen servers in my case Dockerfile.zip

danielszilagyi commented 10 months ago

Daniel, I would love to try WeConnect-mqtt but I have a HAOS install. Is it possible to install it on my system? Any tips on how to do that appreciated.

Go to Settings/Add-ons and add your new add-on. Maybe you have to restart HASOS first to get it to se the new addon. Start the addon, and now it should publish on your MQTT under weconnect

I wanted to say Thank you for the input on how to create a simple addon, since I was tagged on this question by someone. Actually there is also a docker image referred on the project page, could use it also for a simpler Dockerfile.

https://hub.docker.com/r/tillsteinbach/weconnect-mqtt

But firing up it only one part and I for example did not yet have time to implement mqtt sensor configs for HA while this issue is present with the weconnect integration. Since this is offtopic here, I'd suggest to move any further discussion to the project repo and open issue/PR there for example mqtt sensors or other input - I will do the same once I have time to contribute.