I can implement things, but only if they are supported by the API. Remember that the guys from Home Assistant developed the MySkoda API, which I’m using, but this is a reverse engineered API. So we have no support at all on it.
To comment on the items you mention here:
Start/stop of charging, that should be available already. The session ID is not available in the API, so I cannot expose it.
Charged energy is not available in the API. I would recommend you to use the API of your charging point instead for this (I’m using that).
Charging power in real time can be added. This info is available.
This should already be available right now.
Sadly this support is currently broken in the API. There is some kind of MQTT available, but the developers of the library told me it is broken. As long as that is broken, I cannot enable it and we are stuck with 5 minute refresh intervals. Anything faster will trigger API limitations.
Battery capacity is available, I can add that one.
I don’t know what causes this, this is very specific towards the Homey SHS (which I don’t have). I’ve seen other uses comment in the past in this topic, and they referred to checking your Homey version. You need at least v13.0.0.
First of all, thank you for your work on this app, it’s really useful and I appreciate the effort, especially knowing that the API is reverse engineered and limited.
I’ve been testing the charging-related flows and I’d like to share some feedback and small feature requests that could improve reliability:
Charging start/stop detection works well, but due to the 5-minute refresh delay, location can sometimes be outdated. I worked around this by combining the car’s charging state with a power threshold from my P1 meter (e.g. >9000W) to ensure it’s actually charging at home.
It would be very helpful to have:
• Real-time charging power exposed (since you mentioned it’s available in the API)
• Battery capacity (also mentioned as available)
I understand that charged energy (kWh per session) and session ID are not available via the API, so I’m handling energy tracking externally via my meter.
Faster updates or push-based updates (MQTT) would obviously be ideal, but I understand this is currently not possible due to API limitations.
Overall the app already works well as a trigger source, and with the above additions it would be even more powerful for automation and energy tracking.
The app works on the SHS too. The problem was that I hadn’t updated the Homey’s firmware to the latest version (>13) yet.
Perhaps with the next updates you could also display the status of the air conditioning, i.e. true/false. And also the event/feedback indicating whether it has been switched on or off, for querying an event. That would be great.
Hi, I would like to try this app but when installing I receive a big URL message after entering my vwgroup username and password. Did I miss something?
It works, thanks! Great work with this app!! I’ll use the experimental app .
It would be fantastic to be able to see the current battery percentage so I can use that in my smart charging schedules at home for optimum price and solar usage. Now I predict how long I need to charge at night or during the day at the lowest rates (ex. always charge for 4 hours) but if I know the battery percentage of the Enyaq, I can use the cheapest 2 hours
how did you get it running on SHS. I also tried to install/use the app on my SHS (today patched from 13.1.0 to 13.1.5) but the app still shows “could not mount /dev/random : 32” at start.
@KennyMoens maybe the error from the docker container log will help you:
The app has crashed.
Error: Could not mount /dev/random : 32
at file:///app/packages/homey-local/lib/AppLocal.mts:1112:25
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async AppLocal.executeStart (file:///app/packages/homey-local/lib/AppLocal.mts:1295:7)
at async AppLocal.start (file:///app/packages/homey-local/lib/AppLocal.mts:979:7)
Homey [log][ManagerAppsLocal][AppLocal:be.functor.skoda] Automatically restarting in 50 seconds…
@Steggi - I fear I cannot help you out here. This is something very specific for the Homey SHS which occurs before my application triggers. I don’t know what causes it, I would suggest to reach out to Homey support for it.
@Hesse-MTK - the battery measure is a standard capability of Homey, I want to avoid modifying it, and stick to the standard way of working in Homey.
I will look at the docker Container how it runs on my side. I just followed the instructions for SHS on proxmox, maybe I need to change to the native docker version.
The host mode could be the point. I will give you feedback.
The problem with /dev/random was the proxmox lxc container, which is usually created as “Unprivileged container”. In this state (more security of course) there is no access possible to /dev/random.
I created a snapshot backup of my lxc vm and restored it as privileged container, then the app does not crash anymore. I know it is less secure but in my home environment it’s fine for me.
.
The app has crashed.