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
I used to use the remote lock/unlock and the start/stop heater functionality for quite a long time, but recently I noticed that it didn't function any more.
A more detailed search with the original VoC app gave me the following information:
Lock
Your Volvo has not been in use for
a while and is offline to not drain
battery. The Volvo on Call service
is waiting for your Volvo to come
back online, which normally happens
within an hour.
Do you still want to continue?
Obviously the car was in standby.
Further information gave:
Your Volvo may have difficulty
communicating if it has no mobile
coverage or is in power save mode.
Indeed I had not used my car for 6 days and that it went into power save mode is fully
acceptable, but if you send a command with the VoC python script, you don't get information that the script is not giving the desired result.
The question.
Are you aware of any command that monitors the connection between the car and the VoC server?
A way to solve it could be to monitor this sensor:
"timeFullyAccessible": 7200,
"timeFullyAccessibleUntil": "2019-06-25T14:12:06+00:00",
"timePartiallyAccessible": 31680,
"timePartiallyAccessibleUntil": "2019-07-12T14:12:06+00:00",
It turns out that after 7200 minutes (= 5 days) the car goes in power save mode
Something else will happen after 22 days (31680) minutes, but I have no idea, what will happen on July 12, if I don"t use the car before that date.
Is it possible to implement a function that a warning is generated if the current date/time exceeds the date/time in timeFullyAccessible?
Or is there a better solution?
Regards,
Herman
The text was updated successfully, but these errors were encountered:
While capturing the VoC communication from the VoC app, I discovered that beside the VoC server, other URL were polled for information, among them Amazon (don't know why), Google (yes, for the map and Time Zone), Here (for the weather/temperature) and Microsoft.
The last one is used to monitor the availability of the VoC server.
Some developers claim to monitor the availability.
Question.
Is that something to implement in VoC in order to increase the functionality?
See below:
//Send from the VoC application to the Microsoft server
Hello Erik,
I used to use the remote lock/unlock and the start/stop heater functionality for quite a long time, but recently I noticed that it didn't function any more.
A more detailed search with the original VoC app gave me the following information:
Lock
Your Volvo has not been in use for
a while and is offline to not drain
battery. The Volvo on Call service
is waiting for your Volvo to come
back online, which normally happens
within an hour.
Do you still want to continue?
Obviously the car was in standby.
Further information gave:
Your Volvo may have difficulty
communicating if it has no mobile
coverage or is in power save mode.
Indeed I had not used my car for 6 days and that it went into power save mode is fully
acceptable, but if you send a command with the VoC python script, you don't get information that the script is not giving the desired result.
The question.
Are you aware of any command that monitors the connection between the car and the VoC server?
A way to solve it could be to monitor this sensor:
"timeFullyAccessible": 7200,
"timeFullyAccessibleUntil": "2019-06-25T14:12:06+00:00",
"timePartiallyAccessible": 31680,
"timePartiallyAccessibleUntil": "2019-07-12T14:12:06+00:00",
It turns out that after 7200 minutes (= 5 days) the car goes in power save mode
Something else will happen after 22 days (31680) minutes, but I have no idea, what will happen on July 12, if I don"t use the car before that date.
Is it possible to implement a function that a warning is generated if the current date/time exceeds the date/time in timeFullyAccessible?
Or is there a better solution?
Regards,
Herman
The text was updated successfully, but these errors were encountered: