Error Entity unknown when executing Volkswagen WeConnect: Set the maximum charging current

[Thomk-63]

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

• [ X] 1.) Can you login using the smartphone app We Connect (not We Connect ID or We Connect GO) and interact with your car?
• [ X] 2.) Please make sure that you can login into https://vwid.vwgroup.io/ and make sure that any "Terms and Conditions" are all checked
• [ X] 3.) I do not have MFA enabled.

Environment

• Volkswagencarnet release with the issue: v4.4.65
• Last working homeassistant-volkswagencarnet release (if known): before volkswagen updating its interface (some weeks ago)
• Home Assistant Core release with the issue: Home Assistant 2023.9.2 (all available updates done) Supervisor 2023.09.2 Operating System 10.5
• Operating environment (Home Assistant OS/Supervised/Container/Core/venv):
• Car model and year: E-Up 2021
• Country where the car was bought: Germany
• Valid We Connect subscription: Yes
• Have you verified that the We Connect service works via VW´s portal?: Yes, it works!

Describe the bug

I have an automation, which is automatically starting charging the car, if there is enough solar power available. In this automatisch I am using the service Volkswagen WeConnect: Set the maximum charging current. When I was tracking the execution of the automation, I got an error after trying to execute this service. The error says "Entity unknown". The automation was running perfectly before volkswagen was changing their interface recently. Other functions of the integration are working. I can start and stop charging manually and all sensors are displayed properly.

Steps to Reproduce

Screenshots

Traceback/Error logs

How can I get these?

## Debug information - all JSON responses from logfile
<!--
  Turn on debug and post the results here: Paste in you link with all debug information, save to text file or use https://www.pastebin.org/
-->

## Additional context
<!--
  Add any other context about the problem here.
-->

[Thomk-63]

Sorry, but without any change, the service is working again. No idea what might have caused this yesterday. I will monitor this service closely over the next days.