[APP][Cloud & Pro] Somfy Tahoma & Connexoon (v4.0.124, test v4.0.140)

Bingo! Blind or Shutter did the trick. THank you so much!

Hello, I just replaced the Tahoma switch by a new one. All devices are working fine with the tahoma app.
I now get this error message in Homey: Error: Request failed with status code 400
It’s probably because the new token is not fetched. I generated one manually in the app and entered it in the credentials in homey (under username and password) but still the same problem. What do I need to do?
Thanks in advance!

If you go to the Local Tokens tab in the all settings page, do you see any tokens there?

You might need to delete them to force the app to fetch new ones.

Also you could send the Information Log so I can check where it is failing.

I send you the logs now. I just saw in the logs that he’s still referring to the old PIN number of the switch.
This is what I see on the local token page:

Did you delete all the old Somfy devices in Homey and re-add them?

When you add a Somfy device to Homey, it has the Tahoma pin in the device URL, which is required to fetch details and send commands. If you still have the device from the old tahoma in Homey it will try to use the old url’s

I am working on adding multiple Tahoma accounts to the app so you can add devices from different locations. The local connection will only work if all the Tahoma bridges are on the same network.

If anyone is interested (and trust me enough) to provide their Somfy Tahoma login credentials so I can test this works then PM me. If no one is willing (and I don’t blame you), I will chance publishing a test version with the feature. I have made sure the app still works with a single account, so it should be ‘safe’ but I can’t guarantee the multiple account sistuation.

Hi Adrian,

I am interested by your development because I have 2 Tahoma hubs on the same network but they don’t use a unique Somfy App. One is driven by Tahoma Classic and the other one by Tahoma (the most recent one). Is this an issue? Otherwise, no problem for me to share my credentials.

Cheers

Do you have separate login details for each box, e.g. two accounts?

So far I haven’t found a way to get information from two bridges with one account as the account login only shows one bridge.

Yes, I have 2 separate accounts and each of them has its own login details.

Ok, so that’s exactly what the update is targeting. If you are happy to share login details, I will add them to one of my spare Homey’s to make sure it can successfully login to both. I will add devices from both accounts, but I won’t control anything and once I have proven it works / fixed any issues, I will delete everything from Homey. Obviously, once the test is complete, I won’t use those details again and you can change your password.

If you can send the details via a PM that would be great.

It worked when reinstalling all devices but this is what I wanted to avoid as I had to renew all cards in the flows. Anyway, it’s done now and working, thank you!

Hey Adrian, can you help out. I can log in into the Somfy app. The same credentials I am using in the homey app to add my devices again because I received error message from one day to the other.

I get request failed with status code 401.

The error I got before this was:

Failed to send command, no valid connections.

The thing I changed recently was the internet connection to 2.4 ghz in stead of 2.4 and 5 ghz because this crashed the connection box of Somfy and I lost connection to the devices in both apps

I’m not sure if you are the user sending the Diagnostics reports, if so then the login has had too many failed attempts and has been blocked for 24 hours. I had to implement that for Homey (cloud) users else Somfy blocks the IP address and then every user hosted on the same server is blocked.

According to the log the app will be allowed to try and login again after 21:19 UTC.

Homey Pro users are not governed by the same restrictions as they will each have a unique IP address, so can’t block other users.

I have published a new test version. This version fixes a few errors but also has a new tab in the app settings pages that show the list of your devices under three categories, Supported but not added to Homey, Supported and already added to Homey, Unsupported devices.

The Bold text and the icon shows the driver name in the Add device procedure, This will hopefully help users that can’t find the correct driver to select.

The unsupported items show the device that have been detected in your Somfy account that have no driver in the Homey app. If you click on he panel you will be asked if you want to send the details to me so I can try to add support for them. the information that is sent has no identifiable details, so if you want me to keep you informed, post on here to let me know you have sent it.

I am blocked after one attempt. And the credentials are correct thats strange.

My user name is robin_tro**** if you can see something.

Hi @Adrian_Rockall appreciate your efforts in Somfy infegration. I was unsuccessful to solve automation in Tahoma itself. It has automation scenario called Temperature comfort. However one can not configure time windows to activete or deactivate the scenario. Only one start and one end time slot during the day. Is there a way to add this scenario to Homey app and resolve the activation/deactivation of the flow here? So far this scenario does not appear in your app. Many thanks again

You should be able to start a scenario via a Flow, but it just runs it. So you will need to create scenario to activate whatever you want and another scenario to deactivate them.

In my test case, I setup a scenario to open all my covers and another to open them. I haven’t used it in a long to as I use Homey to do it all from the individual devices now so I have more control.

Hi Adrian,

Something I noticed after making the switch from Pro2019 to Pro2026, Each morning (without automated scenario’s for your app) the screens wont go up, or go up after mentioning delay (error) of timeouts and enormous delay for the screen to react.

Tried to solve with a Tahoma reboot, nothing.
Tried to solve with a fresh app install, nothing.
Only solution is reboot your app.

What shall I contribute to figure this out?

After the failure, go to the app settings page and select the Diagnostics Log tab then tap on Send Log.

The app settings startpage shows 'create diagnostics report,

Within the App settings (one step further) I have;

Information log, Device log, State log, Event log. All except the state log show ‘Send log’

Which one, not sure.