My current car has only the possibility to remotely lock and unlock the tailgate. If you press the button underneath the tailgate, it will unlock all other doors. Remember, you will not see any flashing lights, when you use remote unlock and you have to press the button underneath the tailgate within 2 minutes, otherwise it will automatically lock again. My previous car had the possibility to control the heater, but as this is no longer the case, I had to remove this button (switch). The possibility to start/stop the engine has never been available to me.
You wrote:
The thoughts behind it are as follows:1- you have both the lock,heater and engine in a text information box and actual switch status? What is the thinking behind that?
1. Volvo on call publishes the following topics:
volvo/abc123/lock/lock/state : msg.payload : string[4]: "lock"
volvo/abc123/binary_sensor/is_locked/state : msg.payload : string[2]: "on"
You can check this by connecting a debug node to the MQTT input node, called MQTT-VoC Out.
Beside that you can issue from the command line, the command: $ voc dashboard
It will give you the following information about the lock/unlock state:
ABC123 Door lock : Unlocked
AND
ABC123 Door lock : Off
A little strange. For the heater and the engine you have only one line ABC123 Door lock : Off and ABC123 Door lock : Off.
However, you are able to lock/unlock your car in various ways:
1. Use your car keys
2. Use your car remote
3. If you have so called "Key less entry", you can approach your door lock.
4. Use the lock/unlock of your Volvo on Call app
5. This Domoticz solution
The first topic (volvo/abc123/lock/lock/state) is published to the text sensor. The second topic (volvo/abc123/binary_sensor/is_locked/state) is published to the switch. The idea behind it is, that the indication of the switch (On/Off) is also synchronized if one one of the other methods for lock/unlock has been used.
For the heater, only volvo/abc123/switch/heater/state : msg.payload : string[3]: "off", is available. As I do not own a car with a heater, that can be activated remotely, I send only a message to a Text sensor. In my old car I could activate the switch, but in the document it is commented. This topic has also been used in order to synchronize the heater switch, if the heater had been activated by the Volvo on Call app.
The same applies for the engine. Only volvo/abc123/binary_sensor/is_engine_running/state : msg.payload : string[3]: "off",is available. Itś sending a message to a Text sensor.
The reason that I did not describe that topic, is that it has never been available to me.2- There is mention to add the engine start command in the document but the mqtt topic is not mentioned. Would you be able to share
But if you can support me with that, I can include it in the document.
You can do it as follows:
1. Go to the command line and issue the command: $ voc print|grep engineStart
You will get the following reply: "engineStartSupported": false, It shall be either true or false. If it is false, remote engine start is not supported. If the reply is "engineStartSupported": true, can you check with a MQTT client, such as MQTTfx, which topics are published to the MQTT server.
You can download MQTTfx at: https://mqttfx.jensd.de/, and look what is published regarding engine, if you subscribe to: volvo/abc123/#.
At least you should see:
volvo/abc123/binary_sensor/is_engine_running/avail and volvo/abc123/binary_sensor/is_engine_running/state.
If there is more, please publish this topic.
Regards
, I now notice the Volvo mentioned is not an EV, but a petrol car API. That will not fit the EV framework (for starting/stopping charging).