Closed james5294 closed 2 years ago
nothing?
@james5294 have you tried to reproduce in bluelinky without using HomeKit?
Sharing the debug logs from that could help move this ticket in a forward direction.
@Hacksore not sure how to use it other than this? this is my only use. any ideas?
@james5294 you'd need to clone this repo and follow this https://github.com/Hacksore/bluelinky#debug-locally
I'd say before we visit anything here we have homebridge-hyundai-bluelink updated to use bluelinky v7.6.2
.
However, it looks like @athal7 is in the same boat as I am, we no longer own Hyundai vehicles đŸ˜….
@james5294 I'll close this issue for now but if you can get this tested on the latest bluelinky please raise a new issue.
Describe the bug The engine of my Hyundai does not successfully start. (via homebridge bluelink plugin which uses BlueLinky)
Useful info(please complete the following information):
OS: Homebridge (Linux) Version: BlueLinky 7.6.2 Region: US Vehicle: 2021 Palisade
Additional context When trying to start the engine through Apple HomeKit the command gets sent however the command doesn't seem to get executed. To elaborate, the command to start the ignition IS in fact going through however it seems like the command that's being sent is incorrect as the BlueLink app DOES in fact register that there is a command being sent however the command seems to have no action. When I try to toggle the Ignition from HomeKit if i go right to the BlueLink app and trying to execute any remote action it says "We are currently processing an earlier inquiry for your vehicle please wait 90 seconds..." So it received the ignition start command its just failing to execute.
The developer of the Homebridge plugin thinks its an issue with BlueLinky. Please let me know if theres anything i can try to help further debug this issue.