# \[APP\]\[Pro&Cloud\]\[Official\] Kia and Hyundai

**URL:** <https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487>\
**Category:** Apps\
**Created:** [July 17, 2020, 6:22am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487 "2020-07-17T06:22:28Z")\
**Posts on this page:** 20\
**Page:** 25

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [July 4, 2023, 6:59am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/483 "2023-07-04T06:59:27Z")

</div>

Works with KIA Niro PHV ! 👏💪👍

---

<div class="post-metadata">

**Author:** ![cam\_neely](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cam_neely/32/30115_2.png) [@cam\_neely](https://community.homey.app/u/cam_neely)\
**Post date:** [July 4, 2023, 7:13am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/484 "2023-07-04T07:13:55Z")

</div>

It works on Kia EV6 👍👍😀

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [July 4, 2023, 7:18am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/485 "2023-07-04T07:18:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 4, 2023, 7:20am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/486 "2023-07-04T07:20:18Z")

</div>

> [@Teddy](#):
>
> Cosmetical issue

Nothing the app can control. It is a Homey issue

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [July 4, 2023, 1:50pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/487 "2023-07-04T13:50:59Z")

</div>

Ahh had to dig in the other apps to see it was more then yours that had this. Then a homey issue 😉

---

<div class="post-metadata">

**Author:** ![Torch1969](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torch1969/32/33305_2.png) [@Torch1969](https://community.homey.app/u/Torch1969)\
**Post date:** [July 15, 2023, 7:40am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/488 "2023-07-15T07:40:12Z")

</div>

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

 ![Schermafbeelding 2023-07-16 om 14.09.12](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/c/2c4bcd0f487e39760720497f13e872593b917ddf.png)

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?

---

<div class="post-metadata">

**Author:** ![Torch1969](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torch1969/32/33305_2.png) [@Torch1969](https://community.homey.app/u/Torch1969)\
**Post date:** [July 19, 2023, 6:20pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/489 "2023-07-19T18:20:56Z")

</div>

Looks I’m not the only one with this problem and error message.

> <https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/672>
>
> \*\*Region and Brand of car\*\*
> 
> Europe (UK), Kia (e-Niro)
> 
> \*\*Version of the int…egration\*\*
> 
> 2.10.4
> 
> \*\*Describe the bug\*\*
> I know there have been issues the last few days and a flurry up updates to fix it, but I'm running the latest release and still having issues.
> 
> Last night my charging automation didn't work; the start/stop charge service calls resulted in messages such as:
> \> Server returned: 'Invalid request body - Invalid deviceId. '
> 
> This morning I enabled debug logging in the integration and restarted Home Assistant, which resulted in it taking a very long time but I'm not sure if that's expected. The startup log complains about:
> 
> \> "Force update failed, falling back to cached: Request timeout. - Request timeout."
> 
> However it does manage to list the vehicles and obtain the cached data OK.
> 
> \*\*Debug logs if an error occurred\*\*
> 
> When calling the \`stop\_charge\` service:
> 
> \`\`\`
> 2023-07-04 08:53:41.986 DEBUG (SyncWorker\_22) \[hyundai\_kia\_connect\_api.KiaUvoApiEU\] hyundai\_kia\_connect\_api - Stop Charge Action Request {'action': 'stop', 'deviceId': '1591fb40-0738-4daf-8b68-b5a5bbbd9785'}
> 2023-07-04 08:53:41.986 DEBUG (SyncWorker\_22) \[hyundai\_kia\_connect\_api.KiaUvoApiEU\] hyundai\_kia\_connect\_api - get\_stamp 2023-07-04 05:02:13.150000+00:00 120000 85 998 85.74030704166667
> 2023-07-04 08:53:42.133 DEBUG (SyncWorker\_22) \[hyundai\_kia\_connect\_api.KiaUvoApiEU\] hyundai\_kia\_connect\_api - Stop Charge Action Response: {'retCode': 'F', 'resCode': '4002', 'resMsg': 'Invalid request body - Invalid deviceId. ', 'msgId': '77ce6410-6146-4b27-8bbd-9d9dafbb9952'}
> 2023-07-04 08:53:42.134 ERROR (MainThread) \[homeassistant.helpers.script.websocket\_api\_script\] websocket\_api script: Error executing script. Unexpected error for call\_service at pos 1: Server returned: 'Invalid request body - Invalid deviceId. '
> Traceback (most recent call last):
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 452, in \_async\_step
> await getattr(self, handler)()
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 685, in \_async\_call\_service\_step
> await service\_task
> File "/usr/src/homeassistant/homeassistant/core.py", line 1910, in async\_call
> task.result()
> File "/usr/src/homeassistant/homeassistant/core.py", line 1950, in \_execute\_service
> await cast(Callable\[\[ServiceCall\], Awaitable\[None\]\], handler.job.target)(
> File "/config/custom\_components/kia\_uvo/services.py", line 105, in async\_handle\_stop\_charge
> await coordinator.async\_stop\_charge(vehicle\_id)
> File "/config/custom\_components/kia\_uvo/coordinator.py", line 219, in async\_stop\_charge
> await self.hass.async\_add\_executor\_job(
> File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
> result = self.fn(\*self.args, \*\*self.kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/VehicleManager.py", line 151, in stop\_charge
> return self.api.stop\_charge(self.token, self.get\_vehicle(vehicle\_id))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/KiaUvoApiEU.py", line 854, in stop\_charge
> \_check\_response\_for\_errors(response)
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/KiaUvoApiEU.py", line 111, in \_check\_response\_for\_errors
> raise APIError(f"Server returned: '{response\['resMsg'\]}'")
> hyundai\_kia\_connect\_api.exceptions.APIError: Server returned: 'Invalid request body - Invalid deviceId. '
> 2023-07-04 08:53:42.139 ERROR (MainThread) \[homeassistant.components.websocket\_api.http.connection\] \[140567518132112\] Error handling message: Unknown error (unknown\_error) Chris Boot from 2001:67c:2e80:60:450d:474a:2a87:cf17 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36)
> Traceback (most recent call last):
> File "/usr/src/homeassistant/homeassistant/components/websocket\_api/decorators.py", line 26, in \_handle\_async\_response
> await func(hass, connection, msg)
> File "/usr/src/homeassistant/homeassistant/components/websocket\_api/commands.py", line 678, in handle\_execute\_script
> await script\_obj.async\_run(msg.get("variables"), context=context)
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1533, in async\_run
> await asyncio.shield(run.async\_run())
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 410, in async\_run
> await self.\_async\_step(log\_exceptions=False)
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 454, in \_async\_step
> self.\_handle\_exception(
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 477, in \_handle\_exception
> raise exception
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 452, in \_async\_step
> await getattr(self, handler)()
> File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 685, in \_async\_call\_service\_step
> await service\_task
> File "/usr/src/homeassistant/homeassistant/core.py", line 1910, in async\_call
> task.result()
> File "/usr/src/homeassistant/homeassistant/core.py", line 1950, in \_execute\_service
> await cast(Callable\[\[ServiceCall\], Awaitable\[None\]\], handler.job.target)(
> File "/config/custom\_components/kia\_uvo/services.py", line 105, in async\_handle\_stop\_charge
> await coordinator.async\_stop\_charge(vehicle\_id)
> File "/config/custom\_components/kia\_uvo/coordinator.py", line 219, in async\_stop\_charge
> await self.hass.async\_add\_executor\_job(
> File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
> result = self.fn(\*self.args, \*\*self.kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/VehicleManager.py", line 151, in stop\_charge
> return self.api.stop\_charge(self.token, self.get\_vehicle(vehicle\_id))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/KiaUvoApiEU.py", line 854, in stop\_charge
> \_check\_response\_for\_errors(response)
> File "/config/deps/lib/python3.11/site-packages/hyundai\_kia\_connect\_api/KiaUvoApiEU.py", line 111, in \_check\_response\_for\_errors
> raise APIError(f"Server returned: '{response\['resMsg'\]}'")
> hyundai\_kia\_connect\_api.exceptions.APIError: Server returned: 'Invalid request body - Invalid deviceId. '
> \`\`\`
> 
> \*\*To Reproduce\*\*
> Call the \`kia\_uvo.stop\_charge\` (with a valid \`device\_id\` from the web ui popup).
> 
> \*\*Expected behavior\*\*
> Car should stop charging etc...
> 
> \*\*Screenshots\*\*
> n/a
> 
> \*\*Additional context\*\*

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.

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 19, 2023, 6:51pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/490 "2023-07-19T18:51:58Z")

</div>

> [@Torch1969](#):
>
> will patiently wait for solution.

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).

---

<div class="post-metadata">

**Author:** ![Torch1969](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torch1969/32/33305_2.png) [@Torch1969](https://community.homey.app/u/Torch1969)\
**Post date:** [July 19, 2023, 7:01pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/491 "2023-07-19T19:01:51Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 19, 2023, 7:07pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/492 "2023-07-19T19:07:52Z")

</div>

> [@Torch1969](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![Torch1969](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torch1969/32/33305_2.png) [@Torch1969](https://community.homey.app/u/Torch1969)\
**Post date:** [July 19, 2023, 7:14pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/493 "2023-07-19T19:14:12Z")

</div>

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……

---

<div class="post-metadata">

**Author:** ![Torch1969](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torch1969/32/33305_2.png) [@Torch1969](https://community.homey.app/u/Torch1969)\
**Post date:** [July 29, 2023, 6:48am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/494 "2023-07-29T06:48:49Z")

</div>

@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 😬 🫰

---

<div class="post-metadata">

**Author:** ![MatsHansen](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@MatsHansen](https://community.homey.app/u/MatsHansen)\
**Post date:** [July 29, 2023, 7:15am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/495 "2023-07-29T07:15:16Z")

</div>

I’m getting a 401 error code today and nothing is working… The Bluelink app is working, so suspect something with the app.

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [July 29, 2023, 9:00am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/496 "2023-07-29T09:00:56Z")

</div>

Same here… getting invalid app id.

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [July 29, 2023, 2:05pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/497 "2023-07-29T14:05:14Z")

</div>

Same here…  
Kia seems to be tinkering with the API again.

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 29, 2023, 4:24pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/498 "2023-07-29T16:24:36Z")

</div>

Is being worked on at the moment… 🔜

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [July 30, 2023, 9:07am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/499 "2023-07-30T09:07:46Z")

</div>

Oddly it started working for me this morning by itself. Have done a couple of updates without errors in the log.

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 30, 2023, 9:13am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/500 "2023-07-30T09:13:25Z")

</div>

> [@Teddy](#):
>
> started working for me this morning by itself.

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)

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [July 30, 2023, 9:18am UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/501 "2023-07-30T09:18:52Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Gruijter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gruijter/32/1973_2.png) [@Gruijter](https://community.homey.app/u/Gruijter)\
**Post date:** [July 30, 2023, 3:31pm UTC](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487/502 "2023-07-30T15:31:41Z")

</div>

@Mark_Stevens Many thx for your kind donation! ❤

[Previous page](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487.md?page=24)

[Next page](https://community.homey.app/t/app-pro-cloud-official-kia-and-hyundai/32487.md?page=26)
