Adrian,
isnt it just possible to show all available devices and let the user decide. There is still something different between your device count and the app results on my screen, if all devices are available, we simply make a choice and test the screens corresponding..
Hello i wonder do i need Somfy TaHoma® switch to connect to Homey?, my blindfolds are work with ziggbe, i cant get it to work direkt to homey, and if i dont need the swich then att dont now how connect direkt to homey, i have install the app **Somfy TaHoma & Connexoon, but it dont work, and i have even install the test version 4.0.142 and that doesent work, so if you have any tips so please lett me now.
I think there’s a misunderstanding as all the usable devices are visible, about 9. The 9 entries that are not visible are internal components, such as bridges, etc.
What I have been trying to do it get the device that are in the other location, as the locations are listed, but both locations returned the exact same list.
I have looked at other integrations, such as Home Assistant, but they have the same limitations. The reason I asked if you were the owner is I wonder if that’s why you can’t see the device from the other location. I wasn’t questioning your integrity.
So the limitation is purely that I can’t seem to get the Somfy account to disclose the devices.
Ok, I get it. We are seeing the devices located in NL on the homey in ES, all thanks to the local mDNS local ip of the NL tahoma. This is the point my understanding stops.
I do understand some kind of mixture as a result of tahoma cloud facts, but as you wrote earlier, the mDNS should detect the tahoma on site, not the remote tahoma without any connection (no vpn nothing).
I asked the owner if he configged the tahoma in NL and took it to ES, clearly no, out the box in ES, new. He just did his thing with installation procedures etc. and thats it.
EDIT:
The project is very big, each time new devices of all brands etc are added. That came to an hold (all installed, from that point I started configging it all, starting with tahoma.
The local mDNS is just that, local. It will only work when Homey and Tahoma are on the same network.
The app originally, and still does work via the cloud, talking to the Somfy servers. That’s the way it has always worked before Somfy introduced the local mode. So if the Homey in ES is seeing the device in NL, that’s via the cloud.
I must admit I am a bit confused now about the setup. Is there a Homey and a Tahoma in both locations?
Yes there is. Tahoma NL, no homey → Operating all the devices as listed in the ES!
and Tahoma in ES, operating all somfy devices locally, but the homey app does not show them at all.
As the topic started 
Hi Adrian,
So I have a situ with 2 tahoma’s, used at different locations but with the same account. The Tahoma’s are operating perfect, the tahoma app shows both locations etc.
Tahoma 1 is in NL, does the job, no homey there.
Tahoma 2 is in ES, connected to homey. When adding devices it sees the devices in NL but nothing of the Tahoma 2.
Yes, this app communicates using Cloud so there always needs to be some kind of gateway for that communication, in this case the TaHoma Switch
All I can suggest is to split the Tahoma’s into two separate accounts as I have no other ideas.
I seem to be having an issue with this app, which worked perfectly before. I have a sunscreen + volant (screen). The sunscreen is listed as a Pergola and the volant as an interior blind. I had both configured and working in Homey.
Since a few weeks (don’t exactly know when), the sunscreen is no longer working. Controls are not responding and in the Homey webapp I’m seeing a 400 error when trying to control it. I’ve already tried to update the app to the most recent test version and I’ve removed and re-added the device itself. That unfortunately didn’t make any difference (and forced me to redo all of my flows).
No idea what might have changed. Control via the Somfy app itself works fine for everything. Apart from the sunscreen we also have two rolling shutters which also work fine from Homey. So it’s only this one specific device which seems to be having issues.
Any ideas?
Thanks for your answer
Kind regards
Did the problem start before updating to the latest test version?
Do have a Homey Pro or Homey (cloud)?
Yes I only updated to the test version to see whether that would solve it. I had the same issue on the normal version as well. Homey Pro.
Could open the app settings and select the information Log tab, Enable the log and then when you get the error Send the log.
I will have a look at the errors, but the problem could be with Somfy. I have had quite a lot of users reporting they are unable to connect which make me think there is an issue with the servers. Thankfully, I haven’t seen any problems, so I’m not sure if it is down to a specific region / server or even account.
Ok Adrian, we tried everything possible. I informed the owner, he has to split the tahoma’s if he wants the homey to work.
Many thanks!
