[APP][Cloud & Pro] Somfy Tahoma & Connexoon (v4.0.106, test v4.0.122)

[smarthomesven]

Please report the issue here:

[APP][Cloud & Pro] Somfy Tahoma & Connexoon (v4.0.106, test v4.0.122)

First, I would like to thank Lennart Kuijs for making this app many years ago. I have found it extremely useful and it inspired me to write some of my own apps. However, Lennart no longer has the spare time to maintain the app, so he has handed the reins over to me. Local Access Tahoma and Connexoon now support local access when using a Homey Pro. To enable this you need to switch on the Developer mode in you Somfy account: First connect to the Somfy website and navigate to the My Accou…

[Peter_Kawa]

@Hans_Wurst

It seems that an update has broken everything. I keep getting Error 400

I’d disable auto updates right away.
You’re not the first and not the last to get such a “surprise”, for apps and firmwares in general.
(don’t fix things that ain’t broken)

@Hans_Wurst

Is there perhaps an older app version that still works? If so, how can I install it?

This way bugs can’t get resolved, just report your findings to the dev.

To revert:
In case you create offline backups before each update, it’s possible to revert to a previous app version, albeit your complete Homey gets set back in time like that.
There’s no way to install previous app versions per homey.app store.

[Adrian_Rockall]

It looks like Homey is using the setTilt command, which should be correct for a pergola as far as I can remember, but Tahoma is using setClosure.

Could you open the app setting page and Device Log tab, then tap on Get Log and then on Send Log. That information will show me which driver is required and what the valid command set is. I can then check to see what I need to change to make it work.

[Mike1233]

@Hans_Wurst Can you put your code between these brackets, they are under the + menu.

Thanks.
That will hide the long list of code.

[JW77]

Hi Adrian, referring to this post:

[APP][Cloud & Pro] Somfy Tahoma & Connexoon (v4.0.106, test v4.0.122)

It wouldn’t make any difference as the app connects via the cloud, so adding a bridge will not help. The issue is with the structure of the app as it only allows one login. Also the API doesn’t provide data from more than one Tahoma connected to an account, even though it’s possible to have more than one.

Is there any update since this post almost a year ago? I had to buy the Tahoma Switch (v3 box) since I have two new external blinds that don’t work with my Tahoma classic (v2 box). But when Homey Pro 2023 is still not able to handle devices from two different Tahoma boxes (is that still the case?), I cannot use my two new external blinds in Homey.
Note: I do have a second Homey: Homey premium (cloud service), but even the Tahoma classic needs to be connected to Homey Pro 2023 for all (RTS) devices to work with Homey. So I don’t see a solution with using two Homeys.
Note 2: I have maybe hundred flows that contain one or two cards using Somfy products. Therefore I am reluctant to move all my devices to the new Tahoma box, but prefer to keep using both.

[Adrian_Rockall]

@JW77

Is there any update since this post almost a year ago?

I haven’t added support for multiple accounts. I would need to buy another Tahoma to test that properly as it requires quite a big reorganisation of the app. That is a big expense considering I don’t need one.

@JW77

Note: I do have a second Homey: Homey premium (cloud service), but even the Tahoma classic needs to be connected to Homey Pro 2023 for all (RTS) devices to work with Homey.

I’m not sure why you think that Tahoma needs to be connected to the Homey Pro for RTS. A Homey cloud account should be able to control them via the Tahoma box as well.

[Dracoignis]

Hi Adrian, is happened again, here is the code i should give you for the log 2d1ea1d2-e67c-4d96-8a7b-5ea1c72d0fa0

[JW77]

@Adrian_Rockall

That is a big expense considering I don’t need one.

But one day, people will need to migrate from an older Tahoma box (maybe because it’s broken, or absolete) to a new one. So all Homey users that have quite some flows using somfy (Tahoma) products, would be very glad with an easy option to migrate their Somfy products in Homey, instead of fixing many broken links, right?

[smarthomesven]

@JW77

would be very glad with an easy option to migrate their Somfy products in Homey, instead of fixing many broken links, right

There is a tool for fixing your Flows:

[HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices

Use at own risk! If you have a broken device which you want to replace or you have to fix flows for your device I made a script which can help with this. Instructions: Device ID you would like to update - - Go to the Homey web app - Devices - Right click on the device to show context menu - Hold down Alt / option key on keyboard - Select “Copy ID”. Write down the Device ID Remove the Device Re-add the Device Get the Device ID of…

[Paul_Scholte]

I would like to group my Somfy-vertical suncreens using the native Homey-grouping for lights and window coverings.

But in the Homey-device settings the grouping-button does not appear. Apparently they are not recognized as window coverings.

my configuration:

• vertical Somfy IO- sunscreens.
• Connexoon-box with latest update
• Somfy-app 4.0.124

Any help would be appreciated.

Kind regards

Paul

[Adrian_Rockall]

Could you open the app setting and send the Device log so I can see which driver is being used

[Paul_Scholte]

Thank you for your quick response. As requested I have sent you the device log with ID 104155771 as requested.

kind regards,

Paul

[nmeden]

I have a Velux window that is dead, don’t maneuver. Not the remote nor Tahoma is able to control it, and Tahoma reports it as “dead”. However, I have a flow setup to notify me when “The lock state has changed” for the device, and it triggers regularly. Oddly enough, when going to the device, it says the Lock state hasn’t changed for six months.
Can I see what is going on here in some sort of log? Is my window dead..?

[Adrian_Rockall]

@Paul_Scholte

Thank you for your quick response. As requested I have sent you the device log with ID 104155771 as requested.

The devices you have use the “sunshade” class and I guess Athom don’t consider those to be window covers. I will see what Athom recommends.

[Adrian_Rockall]

@nmeden

I have a Velux window that is dead, don’t maneuver. Not the remote nor Tahoma is able to control it,

It does sound like they are dead. The app does have a log in the app settings page, but I’m not sure what that will show.

[Paul_Scholte]

Ok. Thank you.

Kind regards,

Paul

[Adrian_Rockall]

Just out of interest, are all the sunscreen in the same zone?

Are you selecting a capability that is common among all the devices?

[Paul_Scholte]

I Have 7 sunscreens in 3 zones: 5 in the livingroom and 2 in 2 bedrooms.

I group them in 4 groups: east, south_upstairs, south_downstairs and west. The group south_upstairs contains screens in two different zones, all the other groups have all screens in the same zone

I Use only one capability: open/close depending on the position of the sun.

kind regards,

Paul

[Kaspar_1]

@Adrian_Rockall , thank you for making all this!

log id 1208571386

can’t add any devices. the logging is showing everything is fine, but no devices found…

What am i doing wrong??

thanks.

[Adrian_Rockall]

The device you have will use either the “Blind or Shutter (RTS)” or “Awning (RTS)”.