Add core:PriorityLockTimerState and core:PriorityLockOriginatorState when available

[BernoldNL]

Is it possible to add core:PriorityLockTimerState to io:WindowOpenerVeluxIOComponent? I see it online (tahomalink.com), but not in developer mode.

Also, it would be great if at developer mode could have io:PriorityLockOriginatorState added. I don't see this in Overkiz either, but the actuator has a rain sensor, so it feels like it should be possible.

[qelanhari]

For my pergola, I think the originator only is présent when there is currently a lock from the rain sensor, else it does not even appear in States list.

[flhoest]

@qelanhari talking about this, how to you read the rain sensor value ? I cannot find it. I have one and it works but I have no clue how to interact with it....

[qelanhari]

There is none,if it rains, the originator is set as "rain". There is no direct state "it is raining or not". If there is no more rain, the lock is gone.

[flhoest]

Ok, then how can I achieve this : I need to create an event based on the rain status : only do it if no rain ... I'm a bit lost

[flhoest]

Is it the place to look at ?

core:CommandLockLevelsState

[flhoest]

@qelanhari ⬆️

[qelanhari]

if core:PriorityLockTimerState has a value above 0 (as X) and the io:PriorityLockOriginatorState has rain as value, it means that it's raining or it did a few minutes ago and the lock will clear in X (don't remember if it's seconds/minute or date).

[flhoest]

Thanks a lot ! I will start some testing based on that. It really helped me a lot ;) If you are curious, I'm working on this : https://www.lets-talk-about.tech/2023/09/somfy-how-to-control-your-devices-in-php.html and another version will be released as soon as I manage the rain factor !

[flhoest]

@qelanhari can you send me a private message on tweeter ? @flhoest thanks ;)

[qelanhari]

@qelanhari can you send me a private message on tweeter ? @flhoest thanks ;)

-> @tankoo

[BernoldNL]

Not sure if a separate issue should be created, but this seems very related.

I noticed that after updating the TaHoma Switch to the latest firmware (2024.3.3-10) there are some changes to io:WindowOpenerVeluxIOComponent:

1. When closed automatically (in this case due to rain), the core:ClosureState is not updated anymore. It should go to 100%, but it stays at the value it was. Also core:OpenClosedState stays at "open", so there is no way of knowing that it actually closed.

2. Commands setClosureAndLinearSpeed and setPositionAndLinearSpeed were added, but they don't seem to be different than setClosure (I have roller shutters that also have this and will be slower and more quiet, the Velux not so much).

[fberu-somfy]

Hello @BernoldNL ,

Yes your issue is different than the PrioryLock topic.

Regarding your points:

When closed automatically (in this case due to rain), the core:ClosureState is not updated anymore. It should go to 100%, but it stays at the value it was. Also core:OpenClosedState stays at "open", so there is no way of knowing that it actually closed.

When raining the Velux window automatically closes but not at 100%. It closes until the "ventilation" position: the window is closed but not the top bar. core:OpenClosedState is 7% and so core:ClosureState is still "open"

Commands setClosureAndLinearSpeed and setPositionAndLinearSpeed were added, but they don't seem to be different than setClosure (I have roller shutters that also have this and will be slower and more quiet, the Velux not so much).

You're right this is a new feature from the last 2024.3.3-10 firmware. It allows you to control the Velux Window with a low speed, in order to reduce the motor noise. To do so you can send the command setClosureAndLinearSpeed([1-100], "lowspeed") or setPositionAndLinearSpeed([1-100], "lowspeed"). Depending on the age and the version of your Velux, this command may not be available

[BernoldNL]

Hello @BernoldNL ,

Yes your issue is different than the PrioryLock topic.

Regarding your points:

When closed automatically (in this case due to rain), the core:ClosureState is not updated anymore. It should go to 100%, but it stays at the value it was. Also core:OpenClosedState stays at "open", so there is no way of knowing that it actually closed.

When raining the Velux window automatically closes but not at 100%. It closes until the "ventilation" position: the window is closed but not the top bar. core:OpenClosedState is 7% and so core:ClosureState is still "open"

Commands setClosureAndLinearSpeed and setPositionAndLinearSpeed were added, but they don't seem to be different than setClosure (I have roller shutters that also have this and will be slower and more quiet, the Velux not so much).

You're right this is a new feature from the last 2024.3.3-10 firmware. It allows you to control the Velux Window with a low speed, in order to reduce the motor noise. To do so you can send the command setClosureAndLinearSpeed([1-100], "lowspeed") or setPositionAndLinearSpeed([1-100], "lowspeed"). Depending on the age and the version of your Velux, this command may not be available

Thanks for your reply. Well, in my case it's not a window, but a skylight. It does not have a ventilation position, so it does go to 100% closed. It's only about 2 years old. Mine is a CVU 100100 0225Q, originally powered from a power socket, but last year it got called back by Velux after a recall for grounding issues. It's now modified to be solar powered.

Edit: Created a separate issue #138