Great work - worked on first try (and some suggestions)

[riesi77]

My Skoda Enyaq arrived last week. I prepared the MySkoda account ahead, also the installation and configuration of docker (https://github.com/tillsteinbach/CarConnectivity-plugin-mqtt/tree/main/docker) and mqtt, web, home assistant plugins.
After I had added the car into my account, everything worked like a charm. The car appeared, the Home Assistant entities - and quite easily, I could also get the SOC to my OpenWB wallbox using MQTT.
Thanks for this great work!

There are a few things that I would like to mention as feature requests or optimizations:

1. When writing data - at least for locking/unlocking - the S-PIN is needed to authorize. It would be great if this support could be added - for instance by configuring the S-PIN in the settings json.
2. It would be great, if the connection status is more transparent. For instance:

• Are the servers reachable and what is the error if not?
• When was the last time the servers were reachable?
• When was the last time data was received?

3. Create an adjustable polling interval for instance to adjust retrieving SOC and location more frequently during driving and charging? Or is this already happening? How often?

[tillsteinbach]

On 1: config can take spin, see here: https://github.com/tillsteinbach/CarConnectivity-connector-skoda/blob/main/doc/Config.md
On 2: the data for last update is available through MQTT. I believe errors should be also available through MQTT
On 3: fetching locations during driving does not make sense, because the car only provides a location during parking. Dynamic polling intervals is also something I‘m thinking of, but did not come to a good solution yet. What you can do today is change the interval yourself through MQTT. The nice thing for the skoda is that it is not only using polling but also can update on some events, like connecting the charger or locking/unlocking.