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

**URL:** https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206
**Category:** Apps
**Tags:** official, homey-pro
**Created:** [September 29, 2020, 3:01pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206 "2020-09-29T15:01:37Z")
**Posts on this page:** 20
**Page:** 39

<div class="post-metadata">

### Author: ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)
#### Post date: [June 6, 2021, 10:39am UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/765 "2021-06-06T10:39:47Z")

</div>

It might be a quite easy solution to not immediately send the position update but to use the timer/timeout function to schedule it in a second. Each time one comes in you cancel the existing timer and create a new one. that way there is at least one sec between updates (or any other delay you choose) and the last will always fire, albeit the timeout later. I use those constructs myself in the Motion app (curtains), so I know how tricky it can be.

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 6, 2021, 1:42pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/766 "2021-06-06T13:42:31Z")

</div>

That’s certainly another option. I will look to see what is easier to implement given the existing structure.

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 8:13am UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/767 "2021-06-18T08:13:51Z")

</div>

Hi Adrian

I noticed the Somfy Tahoma app has been updated. Now I have a major issue - my velux windows appear to now ignore the rain sensor - I have two rooms where flows open the windows if the temp is too high. This has worked perfectly, with the windows self closing in rain. However, since the update, the windows keep opening , even when raining. It cannot be a rain sensor issue as it is affecting all windows.

Any ideas?

Thanks

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 9:12am UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/768 "2021-06-18T09:12:08Z")

</div>

That’s strange. My app is not able to influence the rain sensors as they are exclusive to the windows.  
I have added a check to try and detect the state of the lock imposed by the rain sensors but that is just reading the status. Also the rain sensor should override any command to open the windows as far as I know.  
Could you enable the Information log (blue tick) in the Apps - Configure app section of Homey. When the window opens while it is raining, wait about 30 seconds and then send the log. Hopefully it will show me what commands the app is sending so i can try and work out what is happening.

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 9:49am UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/769 "2021-06-18T09:49:16Z")

</div>

Great, thank you. I think I have sent the log correctly

There is def something odd going on – not all windows opened this time. Everything was fine until today. I will also try and clean all the rain sensors when the rain stops.

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 12:50pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/770 "2021-06-18T12:50:52Z")

</div>

I can’t see anything ‘unusual’ in the log. It does show it is sending open to 50% commands and one to 47%, but they appear to be normal requests.  
If you disable the temperature flow that close the windows does it behave then (as in doesn’t try to open them when it’s raining)?

When I was debugging with another user, trying to get the priorityLockStatus, it appears the velux windows don’t change the state, so maybe they the rain sensors just send a close command and don’t set the lock out like the wind sensor does on the canopies. When the windows have been closed by the rain sensors, can you still open them with Tahoma / Connexoon while it is still raining?

If that is the case and your temperature flow is constantly sending close commands then they will open again. Unfortunately, I don’t know enough about the way the Velux windows work

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 1:32pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/771 "2021-06-18T13:32:57Z")

</div>

Hi Adrian

Yes, if flows disabled and I try to open via the app, they will still open – I have done more investigating now and tested with just the Tahoma app. It appears all windows, except two are showing a “A sensor has detected a risk to your device. It has been placed in safety mode and its movement is restricted” – which is what I would expect but that is not visible in Homey unfortunately.

I have booked a velux engineer to visit 12th July who will be able to test the sensors.

Is it possible to show the sensor status in Homey – that way we could use it to prevent flows from trying to open when raining?

Thanks for the prompt help again

Tahoma UI screen shot below

 ![image001.jpg](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/0/a0ad89a9810a7887afaacc0f7f9ad697aed02eb3.jpeg)

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 2:17pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/772 "2021-06-18T14:17:07Z")

</div>

I have been trying to get the sensor information but so far no luck.  
While Tahoma shows that status could you send be a device log from the Configure App screen. So tap on Get Log then when the list populates tap on Send Log.  
For sun screens with wind detection there is a status that comes back to say they are locked but that didn’t seem to be present with another users rain sensor on his Velux windows.

---

<div class="post-metadata">

### Author: ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)
#### Post date: [June 18, 2021, 2:52pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/773 "2021-06-18T14:52:32Z")

</div>

Hi @Adrian_Rockall . Since the last update, I have noticed a potential bug. Not sure if it has already been adressed in this thread, if so, disregard.  
The screens have a boolean tag “Open” to indicate open or closed status. However, I noticed that in several instances, the “open” tag of my awning remained on “true” after it was fully closed. Restarting the app sets the tag to the correct “false” value again. I have, besides the awning, also 2 roller shutters screens. On those I have not yet seen the same issue.  
This issue has not occurred before the last update. I would have noticed, since a number of flows rely on this tag status to execute.

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 3:25pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/774 "2021-06-18T15:25:07Z")

</div>

How was the awning close?  
What is your polling interval?

One change I have made is to filter multiple events that come in for each device so it only uses the last event. This was to prevent the app from producing a burst of flow triggers that could have accumulated between checking the events. In theory this only applies if the device is operated externally to Homey as the automatic boost should kick in when Homey operates the device.  
So basically when the awning is moved externally it will produce a stream of new positions. If the interval is set to say 1 minute then Homey will get all those position events in one go. Previously each one would be processed and that would trigger the position change trigger multiple times in a few milliseconds which could disable the flow. Now when it gets an event it searches forward to see if another event for the same device and action exists. If another one doesn’t exist then it processes it else it discards it in preference for the newer one.

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 3:25pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/775 "2021-06-18T15:25:34Z")

</div>

I couldn’t see a “get log” option but have sent the log from the “information log” tab page

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 3:27pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/776 "2021-06-18T15:27:12Z")

</div>

It on the Device log tab

 ![Screenshot_20210618-162637_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/d/2dc742757c062fbf8c68b2951224a4c20d558bf6.jpeg)

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 3:38pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/777 "2021-06-18T15:38:00Z")

</div>

done

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 3:41pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/778 "2021-06-18T15:41:45Z")

</div>

For ref these are windows , not awning if that makes any real difference

Poll interval is set at 3000

---

<div class="post-metadata">

### Author: ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)
#### Post date: [June 18, 2021, 3:59pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/779 "2021-06-18T15:59:49Z")

</div>

The awning is operated exclusively by Homey. The polling interval is set to 30sec

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 4:17pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/780 "2021-06-18T16:17:39Z")

</div>

The reference to awnings was for Bas, the joys of multiple queries in a single thread 😉

As for the other user with Velux windows, there is nothing appearing for the “io:PriorityLockOriginatorState” apart from the definition and the “core:PriorityLockTimerState” is zero.  
Can you confirm that Tahoma still had the warnings when you tapped on the Get Log button?  
As you have given me your Interval setting, it might be worth dropping that down to 30 as your windows can close by themselves when it rains. That way Homey will be notified much sooner.

---

<div class="post-metadata">

### Author: ![MBSHomey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbshomey/32/16579_2.png) [@MBSHomey](https://community.homey.app/u/MBSHomey)
#### Post date: [June 18, 2021, 4:40pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/781 "2021-06-18T16:40:44Z")

</div>

Ok,thanks

Poll dropped to 30

I think the warnings were still active as it was def still raining at the time.

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 18, 2021, 5:19pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/782 "2021-06-18T17:19:33Z")

</div>

Ok, I will ask my contact at Somfy but I’m not sure what help I will get as one of the understandings of allowing us to use the private API is that they don’t provide support.

---

<div class="post-metadata">

### Author: ![Bas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bas/32/12539_2.png) [@Bas](https://community.homey.app/u/Bas)
#### Post date: [June 20, 2021, 12:36pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/783 "2021-06-20T12:36:43Z")

</div>

I now also have a case where “open” state remained on False when the awning was opened. So somhow, the state change update can be missed in both directions.  
It does seem that the “position” indicator is updated correctly, so for now I think I can fix my flows by replacing any “open=true”-conditions with a “position is not 0”-condition.

---

<div class="post-metadata">

### Author: ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)
#### Post date: [June 20, 2021, 2:51pm UTC](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206/784 "2021-06-20T14:51:52Z")

</div>

Could you send me the information log just after the awning is open or closed.  
I wonder if the filtering is too general so it’s filtering out the open/close events with the position events. If I can see what events are coming through I can check the conditions I check are different.

[Previous page](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206.md?page=38)

[Next page](https://community.homey.app/t/app-cloud-pro-somfy-tahoma-connexoon-v4-0-124-test-v4-0-152/35206.md?page=40)
