Open fursov opened 7 hours ago
To confirm, these are mqtt events the MySkoda app receives ?
I want to make sure I understand what this is going to be used for.
The way the lib uses these MQTT events is just to detect when something happened, including when a certain operation initiated by the lib itself (over the HTTP API) starts and when it completes.
However for auxiliary-heating, which is being implemented in #175, it looks like the MQTT events aren't always being received so the code (in that PR) is currently not watching for those events and instead just fires and forgets the request.
actually I can see the difference - our lib is subscribed to "air-conditioning/start-stop-auxiliary-heating" but probably it should be "auxiliary-heating/start-stop-auxiliary-heating". I will test it tomorrow
Hi,
I decided to collect some mqtt communication logs from the application. Here I put some filtered content (basically what mqtt_message.py script prints) for SUBSCRIBE messages:
There are two differences to what library sends (besides that a lot of messages are missing for Superb iV):
start-stop-auxiliary-heating
is done forauxiliary-heating
operation, the library does it forair-conditioning
service-event/departure
request in the libraryPlease, let me know if more data is needed, I can also send/attach full logs from my mitmproxy run.