# \[Homey Pro (Early 2023)\] App unsupported list

**URL:** <https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324>\
**Category:** Apps\
**Tags:** homey-pro, homey-pro-2023\
**Created:** [October 12, 2022, 8:44pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324 "2022-10-12T20:44:01Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 16, 2022, 10:04am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/63 "2022-10-16T10:04:11Z")

</div>

Homey Heating Scheduler will be upgraded by Markus. Source: [Github](https://github.com/mskg/homey-heating/issues/171)

---

<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:** [October 16, 2022, 10:47am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/64 "2022-10-16T10:47:44Z")

</div>

I just migrated plugwise2py to sdk3. So once Athom approves it it will be ready for 2023 and the new Homey Pro.

> **[Plugwise2py](https://homey.app/en-us/app/com.gruijter.plugwise2py/Plugwise2py/)**
>
> monitor and control plugwise circles via Plugwise2py

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 16, 2022, 5:56pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/65 "2022-10-16T17:56:27Z")

</div>

> [@Caseda](#):
>
> Though installing apps won’t be possible from January 1st, that includes restoring backups.

A little sigh of relief: 💙

> [@The new Homey Pro — Ask Me Anything](https://community.homey.app/t/the-new-homey-pro-ask-me-anything/70378/88):
>
> SDKv2 apps won’t stop working on Homey Pro (Early 2019) or earlier. Even when restoring a backup they will be restored.

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [October 16, 2022, 6:24pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/66 "2022-10-16T18:24:53Z")

</div>

> [@Peter\_Kawa](#):
>
> A little sigh of relief

It sure is!

Although this makes it less urgent for developers to update their apps to SDK 3 perhaps… 😉

(Devils advocate; I hugely appreciate all the work developers do!)

---

<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:** [October 17, 2022, 7:57am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/67 "2022-10-17T07:57:15Z")

</div>

I am curious about @Arie_J_Godschalk 's new app, which connects the new Homey with the old. The development of his apps is rapid and something really big is coming. He will certainly not only develop this app so that the LED ring and the loudspeaker remain usable with the old Homey.  
I am so excited…

---

<div class="post-metadata">

**Author:** ![JB2K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb2k/32/134070_2.png) [@JB2K](https://community.homey.app/u/JB2K)\
**Post date:** [October 17, 2022, 9:35am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/68 "2022-10-17T09:35:00Z")

</div>

Are there developers willing to update apps for a fee? perhaps it’s an idea to open up contribution / donation based upgrades. personally i would love to see the home-assistant github app to be upgraded to sdk3 because i use the scripts / scenes that are not available to the official app unfortunately i’m not a coder but i wouldn’t mind to pay someone to help me/us to upgrade it

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 17, 2022, 9:51am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/69 "2022-10-17T09:51:09Z")

</div>

You can’t update an app in the official store if you are not the owner. So developers not maintaining their apps have to transfer the ownership to another dev. But if the old dev is not answering on forum posts or other contact data is not known or devs don’t want to, it’s not possible.

---

<div class="post-metadata">

**Author:** ![JB2K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb2k/32/134070_2.png) [@JB2K](https://community.homey.app/u/JB2K)\
**Post date:** [October 17, 2022, 9:57am UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/70 "2022-10-17T09:57:51Z")

</div>

in my case the app is on a github not touched for 4 years

> **[GitHub - rogro82/io.homeassistant: Home-assistant integration for Homey](https://github.com/rogro82/io.homeassistant/)**
>
> Home-assistant integration for Homey. Contribute to rogro82/io.homeassistant development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 17, 2022, 12:59pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/71 "2022-10-17T12:59:23Z")

</div>

> [@RonnyW](#):
>
> But if the old dev is not answering on forum posts or other contact data is not known or devs don’t want to, it’s not possible.

Afaik Athom can ‘force’ the transfer, _for apps in their appstore_, if a dev does not respond to anything in x days.  
(Yea ofcourse there has to be a new dev for it)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 17, 2022, 1:04pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/72 "2022-10-17T13:04:42Z")

</div>

On your case Athom also released an HA app recently, and it’s SDK3. But it differs from the github / [store.homey.community](https://store.homey.community/app/io.home-assistant) version.

---

<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:** [October 17, 2022, 1:08pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/73 "2022-10-17T13:08:56Z")

</div>

> [@Peter\_Kawa](#):
>
> Afaik Athom can ‘force’ the transfer, _for apps in their appstore_, if a dev does not respond to anything in x days.

That’s not how copyrights work.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 17, 2022, 1:10pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/74 "2022-10-17T13:10:45Z")

</div>

Good point, that’s why I used ‘afaik’

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 17, 2022, 1:12pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/75 "2022-10-17T13:12:54Z")

</div>

No. The only thing Athom would do is to allow a second (new) app for the brand - what is not allowed else.  
But as you don’t own the code, you need to write a new app from scratch.

---

<div class="post-metadata">

**Author:** ![JB2K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb2k/32/134070_2.png) [@JB2K](https://community.homey.app/u/JB2K)\
**Post date:** [October 17, 2022, 1:14pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/76 "2022-10-17T13:14:30Z")

</div>

as is said … scene and scripts Athom version doesnt support that… at the moment i use both of them

---

<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:** [October 17, 2022, 1:15pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/77 "2022-10-17T13:15:16Z")

</div>

> [@RonnyW](#):
>
> The only thing Athom would do is to allow a second (new) app for the brand - what is not allowed else.

Have you counted the number of Yale apps in the store? 😂

---

<div class="post-metadata">

**Author:** ![JB2K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb2k/32/134070_2.png) [@JB2K](https://community.homey.app/u/JB2K)\
**Post date:** [October 17, 2022, 1:15pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/78 "2022-10-17T13:15:31Z")

</div>

honest question. how does it work? in the example that the code is on GitHub so freely available aren’t you aloud to fork it and use it ?

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [October 17, 2022, 1:17pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/79 "2022-10-17T13:17:24Z")

</div>

No. But the one brand - one app rule ist still alive. Only for different standards (cloud/wifi) this should not matter?

---

<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:** [October 17, 2022, 1:18pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/80 "2022-10-17T13:18:50Z")

</div>

> [@JB2K](#):
>
> honest question. how does it work? in the example that the code is on GitHub so freely available aren’t you aloud to fork it and use it ?

It depends if the license of the code explicitly allows it. If not, then no, you’re not allowed to fork it and use it (even if it’s posted online and forking isn’t expressly prohibited).

If the code has no license, strict copyright applies.

---

<div class="post-metadata">

**Author:** ![JB2K](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb2k/32/134070_2.png) [@JB2K](https://community.homey.app/u/JB2K)\
**Post date:** [October 17, 2022, 1:20pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/81 "2022-10-17T13:20:15Z")

</div>

Understand. Thanks

---

<div class="post-metadata">

**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\
**Post date:** [October 17, 2022, 2:23pm UTC](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/82 "2022-10-17T14:23:36Z")

</div>

> [@JB2K](#):
>
> open up contribution / donation

Most pages in the app store have a donation button.

[Previous page](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324.md?page=3)

[Next page](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324.md?page=5)
