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

Apps
,
2479

Hello @Adrian_Rockall

I hope you are doing well :slight_smile:

I wanted to get your help on a similar issue with the integration of my Somfy Sunteis io sensor.

The device was successfully added to my Tahoma and then to Homey (as 2 separate sensors), but the data (temperature and luminance) is not being reported. The sensor works correctly within the TaHoma app.

I have tried the following steps:

  • Restarted the Homey app.

  • Removed and re-added the device.

  • Restarted my TaHoma box.

Despite these actions, the issue remains. I created a log report with ID#1309526624 and was wondering if you could please provide some guidance on how to resolve this?

Thank you for your precious help and don’t hesitate if you need anything else from me.

Best regards,

2480

Hello @Adrian_Rockall

my Velux io roof windows are connected to homey via the Somfy Tahoma Switch.

Things are working very fine (so thanks for that!!) except of the fact that the rain sensor is not dealt with in the homey-app at all.

  1. I’d assume that once it starts raining and the window close automatically the “when the lock state changed” would be triggered. That’s unfortunately not the case. But that might be impossible considering that not even in the Tahoma app the lock state is shown at all. As a matter of fact it still falsely shows the window to be open. A automatic refresh to correct the position feels like is happening around every 30 minutes (apparently hard coded somewhere) - then the window appears closed in Tahoma.
  2. If I try to open the window through the Tahoma app during rain it shows a error message with something like “Command couldn’t be executed due to limitations of the window”.
    If I try to open the window through the homey app during rain it triggers a “command completed” with success = true. And it also shows the window position as open. When of course in fact it’s not because the window is preventing it due to the rain.
    So then I was checking the homey apps “Event Log” and I saw something that gives me hope that theoretically it might be possible to at least trigger the “command completed” with success = false.
    Because as you can see in the following log there is a “IoCommandWhileExecDeviceLimitationError”. That sounds basically precisely like the error message in Tahoma.
    So long story short: Is it possible to implement a correct error handling and if so: Could you pleeeeaaasssee? :blush:

{
“failedCommands”: [
{
“deviceUrl”: “io://2078-7057-1460/8322516”,
“failureType”: “UNKNOWN_ERROR”,
“rank”: 0
}
],
“oldState”: “INITIALIZED”,
“execId”: “9e1502c0-aaa6-4b37-a7ef-a8db9b7334c6”,
“newState”: “FAILED”,
“rawError”: {
“result”: -254,
“detailedError”: “basicInfo=4B;detailExecStatus=00;mainInfo=C800C7E5000186FB0201**;IoCommandWhileExecDeviceLimitationError**”
},
“failureType”: “UNKNOWN_ERROR”,
“name”: “ExecutionStateChangedEvent”
}

2481

Could you send that complete log using the Send Log button so I can see the messages in context.

2482

Done. Thank you!!

2483

Hi @Adrian_Rockall, thanks for the great app.

I’ve got an issue with a dimmable light that keeps re-occurring.

I’ve got a mood which includes a Somfy dimmable light and sets its brightness level to 20%. I often find the dimmable light being set to a much brighter level than the 20% it was configured in the mood.

For example today:

  • 20:56:00 the applicable mood was activated by flow, but the dimmable light was not set to 20% but much brighter.
  • 22:07:09 I turned off the mood to test
  • 22:07:10 I manually turned on the mood again which should set the dimmable light to 20% but again it was much brighter
  • 22:07:13 I again turned off the mood, turning off the lights
  • 22:07:15 I turned on the mood again and now the dimmable light was correctly set to the 20% brightness as configured in the mood

I’ve created a report (0801cc5c-2d2f-4e18-8093-ae5bf8cb62dc), but I am not quite sure if this is an issue with moods or in the app. Any help is appreciated. Thanks!

Edit: I can reproduce it pretty easy. Just send additional logs (id 254450229) via the configuration pane where it looks like it is changing the LightIntensityState without me (consciously) giving it instructions to do so.

It looks like setIntensity to 20% command completes first, after which an additional
on command is send (with IN_PROGRESS) 1.4 seconds later. To me it seems that this is causing the override of intensity. Does that make sense?

2484

Hello Adrian,

We have the sunpowered Altea Solar IO exterior blinds but I am not able to connect it to Homey. I have added it to the Tahoma App on my phone.

In Homey I see our sunscreen and two other screens. I tried catogories Interior Blind IO, Buitenjaloezien IO, Verticale buitenzonwering IO and even Zonsensor IO but none of them work.

Do you have any suggestions to pair?

Thank you for your help.

Device log id, 880407835

2485

Have you tried “Buitenzonwering / Pergola (io)”, “Rolluik (io)”, “Verticale buitenzonwering (io)” as they are the devices in the log.

2486

The second message is normal as that is Tahoma reporting the progress of the request, in fact there are several stages of reporting, with the final one being COMPLETED. The only message that relate to Homey sending are the ones with “Send command” in them.

The log shows that Homey is always sending 20%.

However, the log is showing reports of other intensity states being reported that aren’t initiated by Homey, so I don’t know where they are being triggered from. Do you have any other automations setup in the Tahoma Box?

1 Like
2487

Sorry for the delay, but I’m not seeing any logs with the “DeviceLimitationError” text in them. What was the log ID reported when you clicked on the Send Log button?

2488

In the log I am seeing:

"message": "Sun sensor",
                "stack": {
                  "errorCode": "NO_SUCH_DEVICE",

and

"message": "Temperature sensor",
                "stack": {
                  "errorCode": "NO_SUCH_DEVICE",

But there isn’t much else in the log to go on. Could you make sure the log is enabled and then restart the app. Once it has finished the initialising (probable a couple of minutes), could you send the log again.

2489

Hi Adrian,

Thanks for your message. All automations are in Homey only. There’s not a single automation in the Tahoma box or any other system. The logs in Tahoma sometimes show a duplicate event when the mood is switched on; this is only happening on the moments of the incorrect brightness.

1000065057
10000650571080×572 44 KB

A couple of quick tests seem to indicate this is not happening when the device is manually controlled via Homey.

This makes me believe that Homey may be inconsistently sending some weird signals to the device as part of activating a Mood, but this contradicts with your finding regarding something else controlling the device and not Homey.

On top of that, this is only happening when activating the Mood. I’ll do some more tests later this week. Please let me know if you have some additional suggestions for me to look into.

Thanks!

2490

No, unfortunately not.

The first two you mentioned are existing sunscreen and roller shutter. But the “Verticale buitenzonwering” didn’t add the device.

2491

no problem, thanks for coming back! Sorry, but I did not write down any log ID and obviously I don’t remember. Next time there will be rain and I’m available I will check it and report back in a more clear way.

1 Like
2492

Can you make sure you are using the test version as it was a recent addition.

2493

Hi @Adrian_Rockall,

Thank you very much for your reply.

I’ve restarted the app and sent a new log report. ID is #1309526624.

This new report contains more details. I can see that the “Sun sensor” and “Temperature sensor” are both reporting the same error: “No such device : io://2301-6804-8656/16316524#2”

Does this information help you to identify the problem? Please let me know if you need anything else.

Thank you for your precious help.

Best regards,

2494

Thanks for your reply and effort to help.

No, I do not have the test version and don’t know how to get that. The recent version is v4.0.106.

In the meantime I made Scenarios in the Tahoma app which I can trigger in Homey. Unfortunetaly I cannot see the status of the screen in this way.

2495

To get the test version, find the app in the store and then add test to the end of the url. Then you can install it over the top of your existing app and it will keep your settings.

2496

Thank you very much. It worked immediately!

1 Like
2497

Hi Adrian, since this morning i’m unable to control my roller shutters through my connexoon box. The app log is showing “login 0Auth” “far Too many login attempts failed blocked for 15 minutes” which seems self explanatory but i am able to login to the box from the the Somfy Android app and their website with the same credentials. Did anything change to the login procedure for Connexoon on the Somfy end? Using app version 4.0.106 and Homey v12.6.1.

2498

I’m not aware of any changes. It could just be a temporary issue with their servers as that’s happened before.

1 Like