This is a known problem at the moment and I’m not sure if it will be resolved. I’m hoping that Somfy will look into it, but as it’s an unsupported API I don’t know if they will.
Previously I was working with another automation app available on Android. With this I was able to connect to Somfy. I have no clue what API they are using and what relationship they might have with Somfy, but it worked.
I switched now to homey, cause I like the UI much more and it seems to me to be more flexible.
So I am bit sad that besides of somfy I also have issues to integrate hue (see my other post). At the end the integration is the main aspect to use software like homey.
Lets see and wait. Currently I am patient as I just have started with homey
I appreciate the disappointment and hope Somfy can do something.
The current issue seems to mainly affect Homey (cloud) user and my feeling is it’s caused by Athom using a small number of IP addresses, so there are many cloud users all connecting from the same ones. I think that triggers an alarm on the Somfy servers as being some sort of attack, so they block the IP’s.
But this is pure speculation so I could be completely wrong.
Also there are rumours that Somfy are stopping connections for certain devices via the login that the app uses.
The person at Somfy that normally helps me is on holiday until the end of august so hopefully he will give some answers when he gets back, but that is not guaranteed.
Homey Pro only as the bridge is just an extension to Homey cloud. If you have a Pro then you will connect to the Somfy server via your own IP address, plus the new version of the app can use the official local API if you have a Tahoma hub.
Homey, even with the bridge doesn’t have any local network access, so there will always be some apps that are Pro only. Also, as a lot of apps are made by community developers, they will not want to pay for a Homey developer account that is required to publish apps for Homey.
Regarding somfy integration i do get further as before. No 401 error, but still I get nothing connected. I tried several devices, but for each I get the response no device found.
What I have is following:
Somfy Connection Kit (Somfy Connectivity Kit) - it seems there is no device available to connect this kit in the homey app.
I have a somfy remote control. For this I see a device in the list if the Somfy app. But I can’t get this connected either. I do have a prog button on the rear side of the control, but nothing changes when I click this. The device is labelled “Situo 1 Io Pure II”
The engine for the sun shield has no clear name. It is specified as electric motor from Somfy with IO wireless technology / controllable via remote controller
That’s all I got. Hope you can help me
Thanks in advance.
It’s not quite clear to me as I go through this topic about the Somfy Connection kit.
You should be able to connect the screens (IO) to the Somfy Connection kit. But is it also possible to connect to the Homey Bridge and set schedules for the screens?
I answered your question in the other topic at the same time you posted here
But the answer is Yes.
The app uses a cloud connection to your Tahoma account, so it works with Homey (cloud) as well.
Hi @Adrian_Rockall ,
Thank you for your work on this app. It has been the reason for me to purchase a Connectivity Kit.
Unfortunately it still seems that I cannot add my screen to Homey. I tried several types, but they all report that no devices are found.
I sent you a report with id 377478c6-a83f-420d-93e7-33441c68d8e.
Appreciate the help
Quite unexpected since it’s not Velux, but it actually works! Thanks a lot!
For future enhancement; would there be a way of the app doing an discovery of all available devices, without the hit-and-miss pain of selecting device classes?
I have thought about it but haven’t found a solution yet. The majority of support request I get are from users not being able to add devices because they use a different driver to what they would expect, so I am well aware of the confusion and would love to make it easier.
The original design when I took over the app was quite simple and only supported about 10 devices / drivers, but then manufactures started to mix and match motors and devices. Also, as new motors have appeared I have been lazy and added them to existing devices that have the same capabilities. Currently the app supports over 130 products, identified by their controllable names, via 59 drivers. Generally, each device class has a specific set of capabilities mapped into a specific set of commands supported by the device.
Each driver has to have icons and images, all of which take up Homey resources. So, as I was adding more products the app size started to expand, which is why I have since combined so many that share capabilities.
At one point I asked Athom if there was a way to filter the list of devices presented during paring to only show the ones that were applicable, but sadly I haven’t got anywhere with that.