# LG acquires Athom

**URL:** <https://community.homey.app/t/lg-acquires-athom/112310>\
**Category:** Off-Topic\
**Created:** [July 3, 2024, 3:50am UTC](https://community.homey.app/t/lg-acquires-athom/112310 "2024-07-03T03:50:04Z")\
**Posts on this page:** 13\
**Page:** 16

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [January 11, 2026, 7:52pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/304 "2026-01-11T19:52:38Z")

</div>

I often like to refer back to the Homey Podcast episode I recorded together with Kyle [(Episode #9)](https://www.youtube.com/watch?v=vBY8dSdQGmM). In that episode, we had a very open conversation about LG’s plans with Homey.

Speaking as the Partnerships Manager, my job has become significantly easier with LG backing us. Partners take us more seriously, and we’re entering markets that would have been far more difficult to penetrate without LG’s support.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 11, 2026, 11:21pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/305 "2026-01-11T23:21:42Z")

</div>

> [@Pascal\_Nohl](#):
>
> What I’m actually interested in, though, are people’s thoughts going forward.  
> That’s not quite _Back to the Future_ yet 😉

I still have all trust in Athom doing a lot new nice innovations.

---

<div class="post-metadata">

**Author:** ![Vnet](https://avatars.discourse-cdn.com/v4/letter/v/d78d45/32.png) [@Vnet](https://community.homey.app/u/Vnet)\
**Post date:** [January 12, 2026, 7:29pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/306 "2026-01-12T19:29:56Z")

</div>

so when do we see the first lg tv with homey shs build in.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 12, 2026, 11:26pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/307 "2026-01-12T23:26:20Z")

</div>

> [@Vnet](#):
>
> first lg tv with homey shs build in

Homey Self-Hosted Server is ehhhh… Self-Hosted. Not Build in!  
Maybe ask a TV with a open App Platform and Linux shell where you can install own packages and docker containers…

But do you really think there is a market for that?

---

<div class="post-metadata">

**Author:** ![Vnet](https://avatars.discourse-cdn.com/v4/letter/v/d78d45/32.png) [@Vnet](https://community.homey.app/u/Vnet)\
**Post date:** [January 13, 2026, 5:17am UTC](https://community.homey.app/t/lg-acquires-athom/112310/308 "2026-01-13T05:17:14Z")

</div>

shs just a name, i can imagine that it can be ported to on board tv microcontrollers. i did port it to ms hyper-v and soon azure. after the community has ‘battle hardned shs’ by the current use/testing. then a certain range ( or all?) of tv’s is shipped with this ‘ehs’ (embedded hosted server) already available. after purchasing a key it is activated. the tv must have thread radio on board i would say, so the low cost ikea thread matter devices work. a market? well ship it with a few free apps like weather, ikea,hue. you want more, buy the key. lg does the marketing. thiscway you do not need additional hardware except maybe the bridge if you want more functionality for ‘legacy’

its more like an embedded homey mini if i think about it lol

---

<div class="post-metadata">

**Author:** ![Pascal\_Nohl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pascal_nohl/32/164446_2.png) [@Pascal\_Nohl](https://community.homey.app/u/Pascal_Nohl)\
**Post date:** [January 17, 2026, 7:50am UTC](https://community.homey.app/t/lg-acquires-athom/112310/309 "2026-01-17T07:50:16Z")

</div>

> [@Vnet](#):
>
> shs just a name, i can imagine that it can be ported to on board tv microcontrollers. i did port it to ms hyper-v and soon azure.

I agree, but I’m curious to understand more about the portability aspect. Is it built in layers? What I mean is something like a clear separation between:

- a hardware-specific layer, and
- one or more higher layers that implement the Homey logic

Similar to how macOS is structured, with an open-source UNIX/Linux-based foundation, additional open-source components, and proprietary layers on top.

I’d be interested to know whether Homey follows a comparable architectural approach.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [January 17, 2026, 8:02am UTC](https://community.homey.app/t/lg-acquires-athom/112310/310 "2026-01-17T08:02:16Z")

</div>

> [@Pascal\_Nohl](#):
>
> Similar to how macOS is structured, with an open-source UNIX/Linux-based foundation,

macOS is absolutely not based on Linux.

---

<div class="post-metadata">

**Author:** ![Pascal\_Nohl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pascal_nohl/32/164446_2.png) [@Pascal\_Nohl](https://community.homey.app/u/Pascal_Nohl)\
**Post date:** [January 17, 2026, 8:22am UTC](https://community.homey.app/t/lg-acquires-athom/112310/311 "2026-01-17T08:22:28Z")

</div>

> [@robertklep](#):
>
> macOS is absolutely not based on Linux.

Right, macOS is based on BSD Unix. The phrase _“with an open-source UNIX/Linux-based foundation”_ was meant as a **general architectural comparison** , not a statement about macOS being Linux-based. I agree that the wording can be confusing in this context — thanks for pointing it out.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 17, 2026, 1:39pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/312 "2026-01-17T13:39:09Z")

</div>

> [@Vnet](#):
>
> so when do we see the first lg tv with homey shs build in

Have you looked at the [LG ThinQ ON AI (전문기사 설치) | HMAK4W | AI Home 제품 | AI Home | 제품/소모품 | LG전자](https://www.lge.co.kr/home-iot-product/hmak4w-akori)  
It is a LG AI Smart speaker device with Homey build in. Not a shs, just Homey onboard.

---

<div class="post-metadata">

**Author:** ![Vnet](https://avatars.discourse-cdn.com/v4/letter/v/d78d45/32.png) [@Vnet](https://community.homey.app/u/Vnet)\
**Post date:** [January 17, 2026, 1:47pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/313 "2026-01-17T13:47:58Z")

</div>

there you go!. personally i would like to have it in a tv, as this is a homey mini with a speaker……

i expect more of these variants coming up.

---

<div class="post-metadata">

**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\
**Post date:** [January 17, 2026, 9:15pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/314 "2026-01-17T21:15:32Z")

</div>

“Thanks for pointing it out” is just classic ChatGPT

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [January 17, 2026, 9:16pm UTC](https://community.homey.app/t/lg-acquires-athom/112310/315 "2026-01-17T21:16:56Z")

</div>

And the “—“ as well.

---

<div class="post-metadata">

**Author:** ![Pascal\_Nohl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pascal_nohl/32/164446_2.png) [@Pascal\_Nohl](https://community.homey.app/u/Pascal_Nohl)\
**Post date:** [January 18, 2026, 7:35am UTC](https://community.homey.app/t/lg-acquires-athom/112310/316 "2026-01-18T07:35:36Z")

</div>

> [@deejayreissue](#):
>
> Thanks for pointing it out” is just classic ChatGPT

What’s wrong with using ChatGPT as a non-native English speaker? These are my own words in German, which ChatGPT simply translates and polishes into clear and polite English. While I understand English perfectly well, my written English can sometimes sound awkward or unintentionally impolite, which is not my intention.

I’m using ChatGPT in a very controlled way. It’s not allowed to change the meaning or the intent of what I write — only to improve clarity and tone. These are still my words. For example, I wrote _“Danke für die Klarstellung”_, which correctly becomes _“Thanks for pointing it out.”_ That’s both polite and more accurate than what I might have written myself, like _“Thanks for clarificating that.”_

So yes, I use ChatGPT as a writing aid — just like spell checkers or grammar tools — and I don’t see anything wrong with that.

[Previous page](https://community.homey.app/t/lg-acquires-athom/112310.md?page=15)
