[APP][Pro] HomeyLink - Link multiple Homey Pros for unified device control

The first screenshot shows you selected the same Homey instead of the other Homey. That won’t ever work.

Because you don’t mention it: what was the result of pushing this “Repair” button?

.

In general, maybe a restart of the updated Homey solves it. Restarting after a firmware update solved the weirdest stuff.

Thanks for your reply. I’ve restarted both homeys, installed the same latest version of the app again, updated the other Homey as well, but same result. It did work flawlessly before and I have not changed anything but the firmware update of Homey1.

edit: repairing the device and selecting the other homey did the trick indeed. I think I selected Homey1 by mistake. Solved and thanks!!!

I see, thanks!

Hi

Just catching up with HomeyLink due to the launch of SHS. Coming from an existing HP2023 with 50+ z-wave devices

Request for the developer: when selecting devices in HomeyLink the existing devices show up in non-alphabetic order, please allow:

  1. Search for device name
  2. Search for a device type: z-wave, RF, etc. In the SHS use-case: this will help selecting devices on a connected Homey Pro for which SHS has no hardware

Hi all,

I have linked my Homey Pro to my Homey SHS using the Homey Link app.

I added the buttons from my Homey Pro to my Homey SHS, but I cannot use these buttons in flows on SHS. However, I can use the capabilities of my motion sensors in SHS flows without any issues.

For example:

  • When I want to create a flow in SHS like “When button is pressed → Turn on the light”, the button does not appear as an available trigger.

  • But when I create a flow like “When motion is detected → Turn on the light”, that works correctly.

Am I missing something, or are button triggers not supported through Homey Link?

Thanks in advance!

What kind of devices are your buttons? Screenshot of the device in tools would help

For example;

Property Value
ID xxx
Name Schakelaar muur kinderkamer
Class remote
Driver homey:app:com.athom.link:homey-pro
Ready Yes
Available Yes
Warning No
Custom icon Yes

Data
Key Value
homeyId “xx”
deviceId “xxx”

Settings
Key Value
homey_name “xxx”
homey_id “xxx”
device_id “xxx”

Capabilities
ID Title Type Value Set Value Last Changed
measure_battery Accuniveau number null 4 minutes ago

in t his example it its an ikea strybar remote

the same ‘issu’ with ikea rodret button / remote

// i dont have other brands of remote / buttons to try

Yup, HomeyLink doesn’t “do all”.

I’ve KaKu (ClickOnClickOff) remotes and wall mounted remotes, they’re not recognised by HomeyLink.
I reported it 3 months ago, the reply was standard: “We’re going to investigate it, but can’t make any promises”.

.

But you’d just have to turn it around:
Your remote can trigger a flow on the other Homey per HomeyLink flowcard!

Just make sure these flows on the other Homey are startable (“this flow is started” / Start button), although many flows with other kinds of triggers can be started as well.
They’ll appear in a dropdown selection list:

Hello,

I have my homey’s connected trough homeylink and for al devices it works great.

But today i tryed to ad a camera from the my other location trough homeylink and that did not work, i think because the are not on the same lokal network? Ore should i work?

If it is not posible tough homey link how can i then make i work?

Hi there,

I installed Homeylink on my new HP2026 to link to my old HP2019, which now handles a separate appartment, this works perfectly!

But can I also install Homeylink on the old HP2019 to share a few devices from my main HP2026 back to HP2019 and have them both running at the same time, basically creating a two-way link?

Any reason not to, limitations, things to be careful about?

Thanks in advance for any insight :slight_smile:

Marc

Yes, you can install and run HomeyLink on the “remote” Homey as well, and create a two-way link that way.

Of course the amount of linked devices, and the interval of the data they send (f.i. once a day, or every second) can cause performance issues at some point, but that’s dependent on several local conditions.