-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISSUES WITH BETA RELEASE #511
Comments
Thanks a lot for your hard work @oliverrahner and @robinostlund! :) Let the party begin:
VW Touran 1.5 TSI 2021 |
Thank you for your hard work, everyone! Continuing the party - VW Passat GTE 2018 phev `This error originated from a custom integration. Logger: custom_components.volkswagencarnet Unexpected error fetching volkswagencarnet data: 'measurements' Also: Got unhandled error from server: 429 |
A HUGE THANK YOU for everyone working on this! Now my e-UP 2021 is finally showing entities and can be smart charged again. EDIT
EDIT2 |
Big Thanks to ALL for your Great Work Following Error on my Side: Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht Logger: volkswagencarnet.vw_connection User identity token could not be verified! |
Issue with parking position: Could not fetch parkingposition for vin WVG***** |
Updated to latest Beta version and tried to add integration back again... it doesn't fail now logging in anymore but I see a forever spinning 'Logging in to We Connect' window... not sure how to debug as it doesn't stop! Update: I thought nothing was to be seen in the logs but I now found it:
|
Hi Thansk alot! One issue i have on the e-golf is that it does not report remaining charge time, :) |
Just to sum up the current development status:
|
On my side the Volkswagen app also doesn't load or work, so no clue if this is related to e.g. rate limiting or if Volkswagen itself has issues (NL). Errors I see in the logging:
|
@oliverrahner unfortunately have not too much time to debug it, but it seems like for the combustion cars like Touran the "fuelLevelStatus" and in general "measurements" are different. Here the example for my Touran:
Fuel status and many other params are actually in a different path. I will try to find some time today to try to adapt it to my Touran, I will keep you posted. |
@Driekes that "HTTP status code: 429" line means "Too many requests", so it seems to be related to rate limiting. Did that happen immediately or after a certain time? |
Same here.... The logging in pop up keeps spinning |
@stickpin That is funny... for my 2023 Arteon (Diesel only), these properties are present under both nodes. I could just adapt both and check which one is available. |
Same here at the moment(DE) [v4.4.67] with e-golf. The Volkswagen App is receiving no data. |
Also my Audi Connect integration is not loading this morning after I restarted HA for the new VW integration. So could it be the issues are on the VW/Audi side and nothing to do with the integration itself... |
Good job, the integration logs in, loads the sensors of my Polo. |
Let me check the logging. It did work, because I did get results after installing yesterday evening. I also had the other component the 'id' HA component running which I disabled shortly after. That component had also recommendations to only check less than e.g. every 90 seconds, so maybe that conflicted. I will await until tomorrow to see if it resolves itself. |
Mine also did not work earlier today for about an hour or two but now it is back and data still also shows in HA - seems to me there was rather something on VW. |
@MHerweijer @menloperk I had the same problem (endless spinning) but tried some hours later again, and now it works. |
After upgrading to the beta version, I unfortunately have the same behaviour as some of the previous posters. During the login process on the integration page, the window remains permanently open with a spinning wheel. I see the following information in the log file: 2023-11-29 13:05:25.685 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
|
Most of the above issues should already be fixed (for technical details, you might look at robinostlund/volkswagencarnet#216). |
Also, the additional features now working are:
|
The same error here. I got a VW Passat Variant model 2018. |
I ended up deleting it from hacs, rebooting, installing again and then I was able to install the integration without any spinning. Keep up the good work guys! |
Everything should work now, apart from control stuff (stop/start charging, stop/start climatisation, stop/start window heating, lock/unlock car). |
Just as a reminder, should anybody feel overwhelmingly thankful :) |
@stickpin ah thanks. I might missed that. |
I just got time to do it. Actually updating the integration "requirements": [
"pytz",
"git+https://github.com/robinostlund/volkswagencarnet.git@next-stable#volkswagencarnet==4.4.65"
], Results in HA managing the installation of the dependency directly from the branch, unless there is a 4.4.65 tag already (which doesn't exist yet):
I will keep you posted with the results, with the previous (current) beta I usually get locked out by the evening hours with 1 hour refresh time set in the integration. |
Hello |
@maceace just read the whole thread. |
The new beta released: https://github.com/robinostlund/homeassistant-volkswagencarnet/releases/tag/v4.4.69-beta3 |
Awesome work guys! Little snag though, it logs on fine but reports wrong car type (Passat vs Golf, I can live with that), but the only sensors I get are these: |
I have all my sensors in the number of 37, I didn't even add all the API sensors. |
See API status. You are rate-limited. That's why you don't see the sensors. |
I might be rate limited, the app won't connect right now either - will check tomorrow. |
Thank you very much for releasing beta3. |
Thanks for reporting. |
@maceace the new beta released: https://github.com/robinostlund/homeassistant-volkswagencarnet/releases/tag/v4.4.69-beta4 vehicle_moving sensor should work now. |
Thank you very much. |
Sorry, I just noticed that I'm missing the overall average fuel economy sensor. EDIT: |
Sorry, binary.sensor.vehicle_moving and device_tracker.position still not working with eUP! from log: |
@AlexJacu I think remote controls (such as start charging, climatisation, etc.) are not implemented yet in the current beta. |
Same here, also with egolf. Thanks for making the integration work again.. |
Great work with beta4 guys! I'm sure you know most if not all of the below, but I've repeated the full list in-case it's useful... For my Golf GTE hybrid, all previous vwcarnet sensors are back and appear to be working reliably, except:
Departure schedules in configuration are all unavailable and while controls appear to reflect current state, their operation fails. |
I implemented the lock controls, which is now way easier than it was before. |
Really happy with all your work on this! Running beta-4 now, and all currently working sensors seem to be updating and the API remains up. However, since my car is quiet limited in functions, none of the interactive functions are currently working. Through the Volkswagen App (as well as WeConnect before), the following functions are available:
note: I mentioned heater and ventilation seperately, because that was the case previously in WeConnect and the integration. However, in the new Volkswagen App, they have combined the two so that I can only enable/disable climatisation. It then mentions that heating or ventilation is selected, based on the current temperature. There is no way to manually choose heating of ventilation through the app now. But in the car itself, it is a different setting on the Auxiliary heater. Another function that is available in the Volkswagen app (and also was available in the WeConnect app, but never in the integration), is setting departure times for climatisation. However, when this function is enabled, it doesn't really seem to actually work at all. So I'm not entirely sure what goes wrong here. Just want to mention that this is potentially something that you can find when investigating this. Regarding blinking and honking, I honestly can't remember if it was included in the integration before, since it is something I never used. I would love to help, but my skills are very limited in this case, compared to you guys. |
@Jaspils I have just implemented to lock/unlock scenario, because I could test that with my own car. Next might be the blink lights (and horn) scenario. |
@robinostlund @stickpin I suggest we close these very large threads once we release the next stable version to keep things well separated again |
@oliverrahner yes, I agree. :) |
@oliverrahner you can keep them good, as i will not change them, and test anytime you want or like, you really did an awsome job all of you of course! |
Hello. |
@csiemsen should be fixed once we merge this PR: robinostlund/volkswagencarnet#237 Thanks for reporting. |
PR is now merged, please close this and open separate issues for each thing that's not working. Thanks! 👌🏼✅ |
Only report issues here with the latest beta release and do not start any discussion here!
Thanks
The text was updated successfully, but these errors were encountered: