You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Currently, for individual _writetopic instructions for air conditioning, the complete body is transferred to the VW server, if my wife now makes settings for temperature / windows and seat heating ect on the wall tablet in quick succession, the MQTT queue request gets muddled, in the worst case nothing happens and the container needs to be restarted.
I think it would be more stable to be able to transmit a complete json structure of the desired values "at the same time",
I agree, I JSON based format would be preferrable. At the moment, to consume MQTT messages for the parkingPosition, multiple topics need to be consumed:
latitude
longitude
carCapturedTimestamp
A single JSON-based payload with all three values would greatly simplify further processing.
Hi,
Currently, for individual _writetopic instructions for air conditioning, the complete body is transferred to the VW server, if my wife now makes settings for temperature / windows and seat heating ect on the wall tablet in quick succession, the MQTT queue request gets muddled, in the worst case nothing happens and the container needs to be restarted.
I think it would be more stable to be able to transmit a complete json structure of the desired values "at the same time",
{'windowHeatingEnabled': True, 'zoneFrontLeftEnabled': True, 'zoneFrontRightEnabled': True, 'targetTemperature_K': 295.15, 'climatisationWithoutExternalPower': True, 'targetTemperature_C': 22, 'targetTemperature_F': 72, 'climatizationAtUnlock': False}
maybe also implementable with weconnect-cli, currently the _writetopic instructions do not run reliably after a longer runtime (see other issue)
The text was updated successfully, but these errors were encountered: