Works with KIA Niro PHV ! 
1 Like
It works on Kia EV6 
1 Like
Works for me also again on both my Niro PHEV and Niro EV 2023.
I do have a minor thing for you to fix for the future thow 
If you have dark mode active in the homey app the select list menu pages for region and app language in the device settings is displayed with black text instead of beeing white text. Cosmetical issue
// Ted
1 Like
Nothing the app can control. It is a Homey issue
1 Like
Ahh had to dig in the other apps to see it was more then yours that had this. Then a homey issue
1 Like
Two nights in row the car didnāt start charging. I see al lot of errorās in the log about āinvalid device-idā. Any idea what could be the cause or how to solve this from my side?
@Gruijter debug report: e5ae21e4-7b90-4880-ad33-23630f72b232
After this tried start charging from Kia connect app, doesnāt work either. Disconnected cable and reconnected again, charging starts. Stop charging from homey app doesnāt work (same error in log). Stop charging from Kia Connect app does work. Start charging again from Kia connect app doesnāt work.
Are Kia servers buggy at the moment?
Edit 16-07-23 14:13. I keep getting these errors on every poll. What does āinvalid deviceId mean?
03464d6d-0231-483f-8b7a-b5644ed05847
Edit 18-07-23 12:38. @Gruijter can you find some time to look into this? I keep getting these errors when I stop or start charging via flow. After a while the app restarts itself (watchdog triggers, restart) and polling works ok, but as soon as i start (or stop) charging from flow, this error occurs on every poll attempt. Result is I cannot start charging from my flow anymore (has worked for weeks until this weekend)ā¦ do you need anything from me (besides a beer as thanks) to debug this?
Looks Iām not the only one with this problem and error message.
I will patiently wait for solution.
For now the only dirty work-around is to restart the app after every start and stop charging command.
1 Like
I have no issue with the latest version myself. The Github link you posted is for the HA integration, which is using python, and is not the same as Bluelinky that Iām using for Homey. On the Bluelinky discord I also see no recent reports of your issue.
Maybe you could try changing your password in Kia Connect (and Homey).
1 Like
I suspect the problem is not with login in. That works fine. All communication with servers is fine. Until i start or stop charging from device (with button) or from flow. After that the errors occur, until restart of app (after some hours from watchdog, or manual restart).
This is exactly the same as described in that HA GitHub issue. I was thinking of deleting the device and re-adding it again, maybe that generates a new deviceid?
No that wont do it. Resetting your password might. Kia/Hyundai are definitely messing with their API. The reverse engineering team has already discovered upcoming (big) changes in the API. So your issues could definitely be related to that. If a new Bluelinky version is releasd I will implement it in Homey off course. Untill that time not much I can do to help you Iām affraid.
Yep, in that GitHub issue they talk about a change in the API regarding deviceid. I understand you depend on bluelinky code and changes on this integration. Letās wait patiently. I will keep an eye on those GitHub repositories with you .
Maybe I will give reset password a tryā¦ā¦
1 Like
@Gruijter i made new diagnostic report (b8d08c08-dfa5-4c1c-9f7e-146411fb81e8)
Since 2:00 this morning my app is restarting every 5 minutes after getting error message with āinvalid application-idā. Information about the car isnāt updated anymore and device is not responding āunavailable, restartingā.
I hope Iām not the only one with this problem and you can look into this 
1 Like
Iām getting a 401 error code today and nothing is workingā¦ The Bluelink app is working, so suspect something with the app.
Same hereā¦ getting invalid app id.
Same hereā¦
Kia seems to be tinkering with the API again.
Is being worked on at the momentā¦ 
6 Likes
Oddly it started working for me this morning by itself. Have done a couple of updates without errors in the log.
There is an online component to Bluelinky that got updated. So that is why it was fixed āby itselfā. (But in reality some people have been working hard to create this fix, although I expect more isues coming up from Hyundai/Kia)
2 Likes
I can confirm that. At 10:42, the app started working again. I didnāt notice it at first. The app works for me on early 2019 and the individual entities are transferred via Home Assistant back to early 2023. On the new Homey, there is a virtual device with device capabilities, where the data and switches of the app are replicated 1:1.
Of course, this virtual device does not show an exclamation mark, as it is only fed with data externally.
1 Like
@Mark_Stevens Many thx for your kind donation! 
1 Like
