Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring Communication #51

Open
FireWizard52 opened this issue Jun 20, 2019 · 1 comment
Open

Monitoring Communication #51

FireWizard52 opened this issue Jun 20, 2019 · 1 comment

Comments

@FireWizard52
Copy link

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

@FireWizard52
Copy link
Author

FireWizard52 commented Aug 1, 2019

Hello Erik,

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

GET /voc/disturbances/products/VolvoOnCall?region=Europe HTTP/1.1
Vcc-api-uuid: 059900BCBB2FBCDC1A003E3C351D6D7EF09A0A98A5D2B6CC9D5CC8CED48D9D8C
VCC-Api-Key: 855fec8628e14ba69b0bd8d6a71af78c
Accept: application/vnd.volvocars.api.disturbance.disturbancestatus.v1+json
Accept-Language: en-US
User-Agent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; MotoG3 Build/MPIS24.107-55-2-17)
Host: gw.consumer.api.volvocars.com
Connection: Keep-Alive
Accept-Encoding: gzip

//Received from the Microsoft server to the VoC application

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Content-Type: application/vnd.volvocars.api.disturbance.disturbancestatus.v1+json; charset=utf-8
VCC-Api-Region: East US
Strict-Transport-Security: max-age=0; includeSubDomains
VCC-Api-OperationId: dd321ead-21f1-4f67-9280-252c308661d8
Request-Context: appId=cid-v1:0e583c32-03e4-43cb-9fe7-b660476f31b5
Date: Thu, 01 Aug 2019 14:07:08 GMT

{"online":true}

Regards,

Herman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant