In the App settings page - Settings tab, can you delete the Username and Password and then Save credentials. If the button at the bottom says Log out then click on that.
Next, try to add a device and it should prompt for you details again.
I (with A LOT of help from ChatGPT) started adding a device, selected USA as the server region, then returned to the app Settings and saved my Somfy username/password, newly generated local token, and Region: USA together. The app then logged in successfully.
After that, Device Log and Driver Support populated correctly. Driver Support identified all of the coverings as Blind or Shutter (RTS) rather than IO. I added them using that driver and have confirmed that they respond correctly from Homey.
For anyone else using a TaHoma Beecon in the USA, the key steps were:
Enable Developer Mode and generate a local token.
Save the complete credentials, token, and USA region in the Homey app Settings.
Begin adding a device to create the session.
Use Driver Support to identify the correct device driver.
I understand that Somfy Tahoma has a local mode (3s vs. 30s). This seems to work fine for me as the system is responsive, everything is working fine while I am online.
As my internet was down last week for about one and a half day I’ve encountered that local mode seems not to be a true offline mode. I was able to confirm that today. As soon as I’ve disconnected my router from the internet Homey was not able to control Somfy devices anymore.
Is there any way to set up a true offline mode for Somfy devices for Homey?
the last few days i noticed my wakingup-scenario didnt do anything anymore (worked fine for over a year). I tried the secenario dicrectly on my phone on the tahoma-app and it worked. single devices work directly from homey.
i saw my local token had no longer connection, so i deleted it, made a new one and reconected. it was fine, but same result with the scenario. this morning i checked, and local token is disconected again.
when i try to remove and re-add the scenario i get this error.
I am getting lots of reports from Homey (cloud) users about this issue, but as it is the server rejecting the login there is nothing I can do about it.
Obviously, double check the credentials are entered correct and note that user names are case sensitive.
Also make sure you have selected the correct region as each one maintains it’s own user list.
You can connect your Somfy TaHoma box locally to Homey Pro by enabling Developer Mode in your online Somfy account and installing the official Somfy TaHoma & Connexoon app
Developer mode is activated and the local token is used, automatically by the app once dev mode is activated btw. The local token is not delivering a true offline mode. It seems that Tahoma is rejecting the local connection once Tahoma itself is loosing internet connectivity.
I have 3 RTS operated vertical blinds (tilt-capable, with tiltPositive/tiltNegative commands) connected to my TaHoma box. They show up fine in the TaHoma app itself, but they don’t appear as addable devices in the Homey app.
Looking at my device log, they report as:
controllableName: rts:SheerBlindRTSComponent
widgetName: UpDownSheerScreen
uiClass: VenetianBlind
My 2 regular RTS roller blinds (rts:BlindRTSComponent / UpDownScreen) work fine and show up as expected, so it looks like SheerBlindRTSComponent specifically isn’t supported yet.
I’ve sent you the device log showing both the working blind type and the ones that don’t appear, in case that helps add support for this device type.
Is this something that could be added? Happy to provide more info/testing if needed.
tested it again today after restarting homey and loging out and in on the homeyapp.
on my phone i still cant add a scenario, but on my desktop it works, so i’m good at the moment, i just post it here if anyone else expreiences the same they can try this as a workaround.
I have a problem controlling our roller shutters. When I command a shutter to move up or down, I see the windowcoverings_state capability change to ‘up’ or ‘down’. The status remains for a few seconds but then automatically changes to null. As a result, I can no longer determine within a flow whether the status is ‘up’, ‘idle’, or ‘down’. I also tested using version 4.0.149, but the issue persists there as well.
Hmm, I need to look in to that as the buttons are set to null so the middle button can be used to stop movement. If it were to remain active, Homey ignores any taps / clicks on it.
I probably need to make sure the Flow treats null as idle the idle status.