Homey Pro 2023 + Somfy TaHoma & Connexoon v4.0.124 + Somfy Connectivity Kit (Switzerland/Europe)
I can log into my Somfy account successfully, but Homey always reports “The app has no devices.”
Using the Homey device diagnostics, my blinds are returned by the Somfy API as:
These are Griesser io exterior venetian blinds (lift + tilt) and they work correctly in the TaHoma app.
Is DynamicVenetianBlind currently supported by the Homey app, or could this be a missing device mapping?
Can you install the test version (4.0.142).
Hi Adrian. Thx for your fast reply. I’m new to all this. Where can I find the version 4.0.142? in the App store the latest version is 4.0.124. However, I reinstalled the app and now all my blinds are suddenly visible! the only thing not working is the “my” position. When i push it I get the message " Request failed with status code 400" Is there a fix for that?
You just need to add test to the end of the url.
Hello Adrian
I use your app for my blind and Velux windows. Last time I asked this question, the answer was no, but I hope you don’t mind me asking again, in case there is an update.
Is there anyway to allow Homey to see if the velux windows are actually open or not. When it rains, my windows close but Homey thinks they are still open. That is the use case I am trying to resolve.
Thanks
Matt
I think I remember this and we found that Tahoma wasn’t sending any notifications when the window was closed by the rain sensor.
To be sure, can you enable the event log and then try to trigger the windows to close or wait for it to rain and once they have closed, send the log.
Hi Adrian
Thanks and yes, I will have to wait for the rain. Log is enabled.
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.
Is there any way we can fix this, do you want me to provide info to get this going?
Many many thanks!
ADDED:
Both tahoma’s are NOT in develop mode for local api yet
Have you tried the test version 4.0.142?
Just 15 min ago I installed the testversion, when add devices, no different results.
I one of the logs I do see the NL local ip address, but the tahoma ES is not present or not mentioned.
Do you wish me to reboot the homey?
This is what the log shows on the tahoma ES, the local ip is the tahoma NL.
{
“time”: “2026-07-04T19:30:01.215Z”,
“elapsed”: 0.08,
“source”: “mDNS Found a local bridge”,
“data”: “{
“pin”: “####-####-####”,
“address”: “192.168.9.121”,
“port”: 8443,
“api_version”: “1”,
“fw_version”: “2026.1.3-4”
}”
}
]
log-ID: 161036663
There is a device mentioned as NON compatible 'INTERNAL (wifi/0)
That is just one of the Tahoma internal devices, so of no use to Homey.
The mDNS will only find a Tahoma that is on the same network as Homey.
But, my mistake, with the new version, when you add a device it should show which gateway it is on. At least it would if I had remember to publish it, but I left it on my Homey for testing and then forgot about it. A new test version (4.0.143) is now available.
Hi Adrian,
Just tested v 4.0.143, results unchanged; in the log only one gateway is mentioned, the tahoma in NL. The corresponding NL devices are all mentioned as well. so somehow during init of the app, the local tahoma itself is not detected.
The mDNS finding the NL Tahoma on a different sub without VPN or anything is odd.
I suppose that IF (I asked the user a minute ago, not sure) the Tahoma ES has been connected earlier in NL and transported as is, should not make any difference to the facts we know now?
EDIT : Rebooting the homey to make sure the mDNS inits clean.
EDIT: After reboot, the log shows the app found 2 local bridges, but the subnet is equal (NL) and the devices found are still only NL.
[
{
“time”: “2026-07-05T06:54:55.590Z”,
“elapsed”: 506.604,
“source”: “mDNS Found a local bridge”,
“data”: “{
“pin”: “####-####-####”,
“address”: “192.168.9.121”,
“port”: 8443,
“api_version”: “1”,
“fw_version”: “2026.1.3-4”
}”
},
{
“time”: “2026-07-05T06:54:55.594Z”,
“elapsed”: 0.004,
“source”: “mDNS Found a local bridge”,
“data”: “{
“pin”: “####-####-####”,
“address”: “192.168.9.121”,
“port”: 8443,
“api_version”: “1”,
“fw_version”: “2026.1.3-4”
}”
}
]
The mDNS is strange as that is a broadcast from the Tahoma gateway that is picked up by Homey and should only be visible on the same network.
Have you tried using the normal add devices procedure to see if it now detects devices from both Tahoma’s?
Unfortunately, the multiple Tahoma feature is untested as I only have one, so I have just had to go by limited information that I can find on the internet.
I understand, I do not expect it to work instantly, just helping you. Yes I tried adding devices, ony the NL devices are available.
So the mDNS info is faulty. Let me investigate this evening/tomorrow what might be the root cause of that and report back.
To be honest, my guess is that Tahoma does not handle the 2 devices correctly, assuming that the first found gateway based on cloud info is the only one. Finding the second and using the first found data is faulty 4sure.
If you want to open the app settings - Device log tab and tap on Get Log and then Send Log, I can look at the information to see if it sheds any light things.
log-ID: 161036663
If it makes any difference to restart the app and then do something with logs, let me know!
