Did you draw a line from the card with tags to the card you wish to use the tags in?
After reboot the old homey still only find itself,
And the new one gets timeout when searching for sattelites, so now it doesnt even find it self 
Have tried multiple reboots, but its the same now 
I also tried re-installing the apps
I’ll spend time on it next week.
Can you send me a diagnostic?
Which version of Homey are you running?
The old Pro is on 8.1.3
And the new one on 10.0.0-rc.61
Diagnostics from the new one d44153fa-9dd1-4103-b45b-b76c44924e47
And from the old one that cant find the other
5fa32033-e375-415a-8934-59d3431549ac
1 Like
homey basics….indeed no line between the cards. Works perfect now….
As long as not all devices and apps are supported by the Pro 2023, I will leave unsupported stuff on the old Pro 2019 and because of Homesh, everything is working again here…
Thanks !
Eric
2 Likes
Success! I have installed both Controller and Satellite on both my Early 2016 and Early 2023. I have been able to send commands forward and backward between both Homeys.
Issue:
I noticed that Satellite can not handle spaces in the Triggername.
1 Like
Okay, please create a ticket for it, htne i can pick it up when i have a Homesh moment 
Your Bitbucket seems not to be open for creating Issues (I have a Bitbucket account).
1 Like
Which one? Homesh are both open.
I just even put it on anonymous.
If I click on “Create Issue” when not logged in I am asked to log in.
If I click on “Create Issue” when logged in I get a message
1 Like
Am I the only who can not create a ticket? Your link give same result:
Asks for login
After login and Create Issue - We can’t let you see this page
Ah, just checked, i think there is an issue with BitBucket, in private, it ask me to login too.
I installed and connected Homesh on my Homey2023 (controller) and Homey2016 (slave).
In Homey2016 I created a flow triggered by Adv trigger (1 text) and configured a trigger name (selected create).
Then I tried to call that flow from the Homey2023 but the trigger name never shows up.
Am I doing something wrong?
Using the set screensaver card all my configured screensavers is shown, so connection works.
1 Like
For the moment Homesh cannot handle spaces in the trigger name. Maybe other special characters also.
2 Likes
Noticed that before, I used “Homesh” as trigger name so should be ok. 
Does it work for you?
1 Like
Will it be a problem if I have other triggers with a space in the name, will they make all trigger names not to show up?
1 Like
Note sure.
But there still seems to be an issue with the names, i’ll fix it asap, but currently don’t have the time.
Ill fix Homesh as soon as i can.
1 Like
