-
Notifications
You must be signed in to change notification settings - Fork 13
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
Client Error GotError #353
Comments
Steps already taken:
|
Same here |
Same issue here. Sometimes when I restart the plug in I don't have the error but now it has been a day and still not working. |
Please see this post from the Bluelinky Github: Hacksore/bluelinky#254. Kind regards, |
I couldn't find that thread, but I figured I'd at least try downgrading to Node v16. I tried to check my current Node version to no luck, the Raspberry Pi I'm running on seems to think it isn't installed - unless it isn't installed? I just reinstalled the OS fresh and am rebuilding my Homebridge setup. Maybe Node wasn't installed along the way with Homebridge or the system? Here are my logs, if anybody can look through to see if I'm getting something different from OP --
|
That did the trick! I only edited your code slightly to get the updated 16.20.1 like in your screenshot instead of 16.13.0, and it worked perfectly. So excited to try this out now that the accessory is showing up in the Home app! |
Do we really have to down grade to an, as of this month am I supported version of node? |
Unfortunately, the issue is with one of the dependencies of the plug-in. The people that made Bluelinky are fine with the workaround and are not in a hurry to fix it any time soon. You can find more information here: Hacksore/bluelinky#254 Having an unsupported version of node is not necessarily bad u less other Homebridge have issues with it |
No longer able to downgrade below 16.18.2 and still getting the same error. @drumstix1020 What code did you edit and how please help!! |
@shpress, you can use this command in Terminal to install a working node.js version: sudo hb-service update-node 16.20.2 If id does not want to install the version check what hombridge version you have. I think the Homebridge 1.7 requieres node.js 18 at the least |
@carlosgamezvillegas So I was able t get to 16.20.2 but still getting this error homebridge-hyundai-bluelink] Status fetch error Cannot read properties of undefined (reading 'result') |
I just restated my hombridge to de if I got the same error but it loads just fine. Did you update anything else? Hombridge? |
So I try running a command from my Apple Home App and this is what happens: But nothing actually happens with the car. Sorry im somewhat technical but just so lost with this one. |
What Version of Hombridge are you using? |
1.7.0 OS: Ubuntu Focal Fossa (20.04.5 LTS) |
Probably that is the issue. Hombridge 1.7 does not support node.js 16. Try to downgrade Homebridge |
Just tried that on 1.6.1 still having the same issue. |
I am out of ideas. The only thing left is to do a fresh installation of Homebridge 1.6 in a different device to check if that fixes the issue. |
I am surprised the big brains around here haven’t taken control and fixed this looks like Bluetooth k has a new interface maybe someone can attach this and fix it ty let me k ow if I can help |
@fratinize, like it was mentioned before, the issue is not with this plugin it is with one of the dependencies. We need that to be fix first before this plugin can be fix. The dependency is Bluelinky l, and when I reached out to them about this issue they mentioned that one of their dependencies was causing the issue. |
Ty for that info Much appreciatedSent from my iPhoneOn Dec 2, 2023, at 3:18 PM, carlosgamezvillegas ***@***.***> wrote:
@fratinize, like it was mantiene before, the issue is not with this plugin it is with one of the dependencies. We need that to be fix first before this plugin can be fix. The dependency is Bluelinky l, and when I reached out to them about this issue they mentioned that one of their dependencies was causing the issue.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Describe The Bug:
Unable to connect to Hyundai Telematics API
To Reproduce:
I tried using the same login on the Hyundai app and myhyundai website, both worked as expected.
Expected behavior:
The Dashboard should show its able to connect to Hyundai Telematics API and be able to perform various Vehicle tasks such as to lock and unlock
Logs:
Plugin Config:
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: