# Reuse "old" Homey 2018 with new Homey Pro?

**URL:** <https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [November 23, 2022, 6:35am UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531 "2022-11-23T06:35:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Homey\_User\_T](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homey_user_t/32/65605_2.png) [@Homey\_User\_T](https://community.homey.app/u/Homey_User_T)\
**Post date:** [November 23, 2022, 6:35am UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/1 "2022-11-23T06:35:59Z")

</div>

Does someone know whether it’ll be possible to reuse the “old” Homey (2018) in any way with the new Homey Pro when it arrives? I am thinking of range extending … I already saw the community effort with the “Homesh” app.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [November 23, 2022, 7:28am UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/2 "2022-11-23T07:28:19Z")

</div>

Homesh is your only option, Homey Pro (2016/2018/2019) won’t be made a (native) satellite like Homey Bridge by Athom.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 24, 2022, 11:37am UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/3 "2022-11-24T11:37:39Z")

</div>

And you can connect the Old homey as an Zwave client to the new Honey Zwave network, to also use the zwave extenions.  
I think it can already be done (but i have no way of testing it now), else i will create a device for it in Homesh to connect it as zwave.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [November 24, 2022, 2:30pm UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/4 "2022-11-24T14:30:26Z")

</div>

Yes theoretically that’s possible to include it as generic Z-Wave device so it will act as a router, though it has no functionality (the standard onoff capability won’t do anything).  
Though have never tried that 🤔

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 24, 2022, 2:34pm UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/5 "2022-11-24T14:34:01Z")

</div>

> [@Caseda](#):
>
> Yes technically that’s possible to include it as generic Z-Wave device so it will act as a router, though it has no functionality (the standard onoff capability won’t do anything).

No thought so, but i do wanna look into if i can add any functionalities.  
Do you know if, when Homey is a zwave-client/device, i can recive signals on the client in any way?

On the new Homey it’s a App device which can be programmed ofc., but on the client it’s different.  
Perhaps you (or anyone else) knows of some tricks?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [November 24, 2022, 2:41pm UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/6 "2022-11-24T14:41:42Z")

</div>

I’m actually not sure how Homey would react to such, in theorie it should show up as controller on the Z-Wave page, but not sure how you could respond to anything/send anything, outside of the raw Z-Wave flow card and raw Z-Wave commands on the Dev pages.  
But as the raw Z-Wave card is able to do it (most likely), should be possible from an app too, though that would probably will need some lower level z-waveing

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [November 24, 2022, 2:46pm UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/7 "2022-11-24T14:46:04Z")

</div>

So, i can send, but i cannot (act on ) a recieved message on the client, right?

Or can Apps also read generic (non-app-device) zwave signals?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [November 24, 2022, 3:28pm UTC](https://community.homey.app/t/reuse-old-homey-2018-with-new-homey-pro/72531/8 "2022-11-24T15:28:09Z")

</div>

That I’m definitely not sure, in apps you don’t receive any commands from other Z-Wave devices, security reasons and such, so I don’t you can 🤔.  
Gets bound to a certain driver.
