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

Error: getaddrinfo ENOTFOUND #6

Open
garfieldhy opened this issue Jul 23, 2020 · 13 comments
Open

Error: getaddrinfo ENOTFOUND #6

garfieldhy opened this issue Jul 23, 2020 · 13 comments
Assignees
Labels
bug Something isn't working

Comments

@garfieldhy
Copy link

Hi! I installed the plugin on both Synology Nas Docker or Windows 10, and got the same error, could you help? Thanks!

[2020-7-23 7:35:14 ├F10: AM┤] Loading 1 accessories...
[2020-7-23 7:35:14 ├F10: AM┤] [XC90] Initializing Volvo accessory...
[2020-7-23 7:35:14 ├F10: AM┤] [XC90] Starting homebridge-volvo
[2020-7-23 7:35:14 ├F10: AM┤] [XC90] Failed to start homebridge-volvo with Error: getaddrinfo ENOTFOUND vocapi.truewirelesscar.net
at extractValue (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\node_modules\sync-rpc\lib\index.js:165:19)
at C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\node_modules\sync-rpc\lib\index.js:175:12
at Object.request (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\node_modules\sync-request\lib\index.js:28:15)
at REST.GetSync (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\src\util\rest.ts:58:36)
at VolvoPlatform.GetVehicleSync (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\src\index.ts:60:34)
at new VolvoPlatform (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge-volvo\src\index.ts:36:27)
at C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge\src\server.ts:357:50
at Array.forEach ()
at Server._loadAccessories (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge\src\server.ts:330:29)
at Server.start (C:\Users\10298\AppData\Roaming\npm\node_modules\homebridge\src\server.ts:156:12)
[2020-7-23 7:35:14 ├F10: AM┤] [XC90] Shutting down homebridge-volvo.
[2020-7-23 7:35:14 ├F10: AM┤] [XC90] Accessory Volvo returned empty set of services. Won't adding it to the bridge!

@ghost
Copy link

ghost commented Jul 23, 2020

came here to post the same issue on Raspberry Pi Homebridge. Optimus is the name of my XC90.

[7/23/2020, 11:51:45 AM] [Optimus] Initializing Volvo accessory...
[7/23/2020, 11:51:45 AM] [Optimus] Starting homebridge-volvo
[7/23/2020, 11:51:45 AM] [Optimus] Shutting down homebridge-volvo.
[7/23/2020, 11:51:45 AM] [Optimus] Accessory Volvo returned empty set of services. Won't adding it to the bridge!
[7/23/2020, 11:51:45 AM] [Optimus] Failed to start homebridge-volvo with Error: getaddrinfo EAI_AGAIN vocapi.truewirelesscar.net
at extractValue (/usr/local/lib/node_modules/homebridge-volvo/node_modules/sync-rpc/lib/index.js:165:19)
at /usr/local/lib/node_modules/homebridge-volvo/node_modules/sync-rpc/lib/index.js:175:12
at Object.request (/usr/local/lib/node_modules/homebridge-volvo/node_modules/sync-request/lib/index.js:28:15)
at REST.GetSync (/usr/local/lib/node_modules/homebridge-volvo/src/util/rest.ts:58:36)
at VolvoPlatform.GetVehicleSync (/usr/local/lib/node_modules/homebridge-volvo/src/index.ts:60:34)
at new VolvoPlatform (/usr/local/lib/node_modules/homebridge-volvo/src/index.ts:36:27)
at /usr/local/lib/node_modules/homebridge/src/server.ts:357:50
at Array.forEach ()
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:330:29)
at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:156:12)

@trympet
Copy link
Owner

trympet commented Jul 24, 2020

Hi, thanks for letting me know.

It seems that the API endpoint is returning a 301 redirect when homebridge-volvo sends the initial request to the endpoint https://vocapi.wirelesscar.net/customerapi/rest/v3.0/, since there is no reference to the domain vocapi.truewirelesscar.net in the entire source code.

@trympet trympet self-assigned this Jul 24, 2020
@trympet
Copy link
Owner

trympet commented Jul 24, 2020

I presume you live in NA. If so, it should be fixed now in v1.0.5. Otherwise, please let me know :)

@trympet trympet added the bug Something isn't working label Jul 24, 2020
@garfieldhy
Copy link
Author

Yes,in NA. Thank you so much for the fix!Now all the function work except the Climate button. It shows no response in red colour.

@trympet
Copy link
Owner

trympet commented Jul 30, 2020

Okay, thanks for the feedback. I'll look into it 😊

@Dunlapjc
Copy link

Yes,in NA. Thank you so much for the fix!Now all the function work except the Climate button. It shows no response in red colour.

Yes, confirmed by a second person. All is working except for a climate tile/button which shows no response and is red in color.

@trympet
Copy link
Owner

trympet commented Aug 16, 2020

Hi. Could you turn on debug mode and post the output from Homebridge on startup?

@Dunlapjc
Copy link

Dunlapjc commented Aug 16, 2020 via email

@trympet
Copy link
Owner

trympet commented Aug 18, 2020

Hi, Jonathan. Thanks for the help! You can enable debug mode from the web interface and see the logs by:

  1. Logging into the web interface and opening Homebridge Settings
    step1

  2. Enable Homebridge Debug Mode
    step2

  3. Restart Homebridge and check the logs
    step3

  4. Post logs (vehicle attributes and vehicle state)

All sensitive information should automatically be censored, but you could also send me an email if you'd like 😊

@Dunlapjc
Copy link

Dunlapjc commented Aug 20, 2020 via email

@trympet
Copy link
Owner

trympet commented Aug 23, 2020

Thanks for your help!

Hmm, interesting. It appears that the response is missing the "heater" object and "status" property, which is used for determining if the climate is on or off. This is what it looks like on my end:

"heater": {
  "seatSelection": {
      "frontDriverSide": false,
      "frontPassengerSide": false,
      "rearDriverSide": false,
      "rearPassengerSide": false,
      "rearMid": false
  },
  "status": "off",
  "timer1": {
      "time": null,
      "state": null
  },
  "timer2": {
      "time": null,
      "state": null
  },
  "timestamp": "2020-08-10T10:50:05+0000"
}

I was not able to replicate a response without the "heater" object on my end, which could mean that the API differs between different regions (I am EU).

@Dunlapjc
Copy link

Dunlapjc commented Aug 23, 2020 via email

@trympet
Copy link
Owner

trympet commented Aug 25, 2020

Agreed. Either the API is different, and/or the the car software itself. For instance, parking climate is in the menus, but doesn’t work in this region... Thanks for your work at this, Jonathan

Sent from my iPhone
On Aug 23, 2020, at 10:13 AM, TrymPet @.***> wrote:  Thanks for your help! Hmm, interesting. It appears that the response is missing the "heater" object and "status" property, which is used for determining if the climate is on or off. This is what it looks like on my end: "heater": { "seatSelection": { "frontDriverSide": false, "frontPassengerSide": false, "rearDriverSide": false, "rearPassengerSide": false, "rearMid": false }, "status": "off", "timer1": { "time": null, "state": null }, "timer2": { "time": null, "state": null }, "timestamp": "2020-08-10T10:50:05+0000" } I was not able to replicate a response without the "heater" object on my end, which could mean that the API differs between different regions (I am EU). — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Does that apply to the official app by Volvo as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants