[velux] New OpenHAB2 binding - feedback welcome!

Tags: #<Tag:0x00007f5c9f944618> #<Tag:0x00007f5c9f944460>

Weird if you ask me… But it may be on purpose (for some reason) when using PaperUI things. I did try a scan in PaperUI which found all my devices. But I dont recall ever having seen that one.

I´m using manual things file, in which I believe this will not be possible.
Interesting to know to reason though :smiley:

did I miss something? Normally changing of the preferences within the section user interface should lead to the proper messages…

Oh, I was not complaining, I use german for myself, but for the forum I added a translation.

1 Like

Hi, I just upgraded from an older OH1 version (march 2019) to the latest OH2 version and must say that I am very impressed :slight_smile:
I was having issues that any klf action was veryyyy slow, like reacting only after around 20s of triggering it.

With the latest version it is instantaneous!
Thank you!

In case this is not normal, I am getting these lines on every item update:

10:34:09.609 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:rollershutter:home:blinds_velux_xxx:limitation,REFRESH): updating of item velux:rollershutter:home:blinds_velux_xxx
:limitation (type velux:rollershutter/limitation) failed

While debugging some issues I had I also saw a lot of

2019-11-10T11:07:24+01:00 homectrl karaf[19828]: 11:07:24.356 [DEBUG] [g.velux.bridge.slip.SCgetHouseStatus] - getRequestCommand() returns GW_OPENHAB_RECEIVEONLY (0xfffffffd).
2019-11-10T11:07:24+01:00 homectrl karaf[19828]: 11:07:24.358 [DEBUG] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(GW_OPENHAB_RECEIVEONLY,authenticated) called.
2019-11-10T11:07:24+01:00 homectrl karaf[19828]: 11:07:24.359 [DEBUG] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(GW_OPENHAB_RECEIVEONLY) returns failure.
2019-11-10T11:07:24+01:00 homectrl karaf[19828]: 11:07:24.361 [DEBUG] [lux.bridge.VeluxBridgeGetHouseStatus] - evaluateState() finished with failure.

Not sure they are really of any problem as the binding is working fine it seems.

cheers

Hello Georges,

thanks for the feedback.

The debug messages regarding GW_OPENHAB_RECEIVEONLY tell you, that the binding is querying the i/o layer for any message coming from the gateway (which normally contain some status information about externally initiated actuator changes) … this is normal and does not matter.

The retrieval of the limitation settings is disabled, now, as the Velux gateway seems to have a faulty protocol implementation (or a typo within the API documentation). Without a proper feedback from Velux, the binding will just ignore this set of commands.

Best regards, Guenther

Hi Guenther,

Thank you for the explanations!

I have a strange problem when using the binding with a Velux window actuator:
When e.g. opening the window, the corresponding item at fist correctly switches from 0 to 100. However, then it osciallates several times back and forth between 100 and 0, and only about one minute after the window has opened it settles for the correct “100”.

This is the result of one “open window” command - the only active operation on my side is to toggle the window to “open”, all other events are happening automatically. The window behaves as expected, it is only the item in OpenHAB which behaves erratically:

2019-11-26 15:07:33.224 [ome.event.ItemCommandEvent] - Item ‘velux_skylight_B’ received command 100
2019-11-26 15:07:33.235 [nt.ItemStatePredictedEvent] - velux_skylight_B predicted to become 100
2019-11-26 15:07:33.259 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 100
2019-11-26 15:07:40.633 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 100 to 0
2019-11-26 15:08:49.954 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 100
2019-11-26 15:08:50.146 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 100 to 0
2019-11-26 15:09:59.452 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 100

I try to use the current state of the window for a rule, but this is basically impossible with this problem, as the rule keeps on starting and stopping.

What can I do about this problem?

I havn´t got this problem… (just tried).
Are you using the latest binding?

I use org.openhab.binding.velux-2.5.0.201911042102.jar on the latest OH milestone.

For me it’s completely reproducable:

2019-11-26 20:09:28.076 [ome.event.ItemCommandEvent] - Item 'velux_skylight_B' received command 60
2019-11-26 20:09:28.095 [nt.ItemStatePredictedEvent] - velux_skylight_B predicted to become 60
2019-11-26 20:09:28.116 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 60
2019-11-26 20:09:30.194 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 60 to 0
2019-11-26 20:10:39.590 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 60
2019-11-26 20:10:39.678 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 60 to 0
2019-11-26 20:11:48.942 [vent.ItemStateChangedEvent] - velux_skylight_B changed from 0 to 60

I´m using org.openhab.binding.velux-2.5.0.201911012210.jar
Perhaps there is a mistake in the one you´re using?

Might be - however I vaguely remember that I noticed the behaviour already in previous versions. As long as you don’t need the item state for rules it is only a optical (logfile spamming, UI redrawing) problem, so I did not really look deeper into it.

The problem only occurs when switching the item with OH (postCommand). Using the Velux remote control only toggles the item state once (however, with quite some delay after the window has reached its position).

BTW, the problem for me occurs for all my devices paired to the Velux KLF. I attach an example when closing one of my rollershutters from 50 to 100% close. As you see, it jumps 50 - 100 - 0 - 100. That means the item does not jump between previous state and new state, but 0 and new state, if that is of relevance.

The various “thing has been updated” log entries also keep spamming my logs, I don’t know what they mean.

There are differences how often the item state oscillates between 0 and the new state, however. It might be connected with the time the real action takes, as I have the feeling that the longer the device takes to reach its intended position, the more often the item state changes in between.

velux.log (2.5 KB)

Does it happen if you use a slider in a sitemap?

Well, yes. Doesn’t a slider in the sidemap do exactly that? Whatever, it doesn’t matter, sendCommand in a rule or a switch in a sitemap, as soon as I use the binding, the problem occurs.

Could be please share the value of the property bundleVersion of the Thing Velux Binding Information?

I just wanted to make sure I tested the same, cause I used a slider in a sitemap :slight_smile:

I don’t have that thing. It isn’t autodiscovered and adding it manually does not give meaningful information :frowning: . I did, however, not yet really play around with this stuff, as I not really had the need yet. I’ll look into it this evening.

Hello @Nosepull

unfortunatelly, I cannot reproduce your issue…

in my cases there is a continuous change from closed to open, i.e. taking a look onto the last two weeks:

2019-11-18 22:29:44.325 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-18 22:29:47.433 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-19 06:32:12.306 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-19 06:32:15.433 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-19 06:59:07.958 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-19 07:04:46.586 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-19 07:31:39.912 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-19 07:34:00.734 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-19 07:35:03.893 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-19 07:35:08.050 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-19 23:02:54.269 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-19 23:02:57.395 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-20 06:44:01.266 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-20 06:44:04.394 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-20 07:03:05.674 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-20 07:04:15.077 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-20 18:45:29.445 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-20 18:45:32.562 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-21 06:29:56.953 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-21 06:30:00.089 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-21 06:42:17.683 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-21 06:48:00.514 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-21 06:49:03.681 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-21 06:49:07.830 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-21 06:51:16.296 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-21 06:53:32.982 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-21 19:59:00.376 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-21 19:59:03.493 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-22 06:40:43.648 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-22 15:11:16.040 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-22 23:03:41.304 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-22 23:03:44.438 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-23 07:56:46.216 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-23 07:57:50.419 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-23 07:58:54.610 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-23 07:58:54.627 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-23 07:59:00.875 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-23 08:00:01.947 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-23 21:08:54.391 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-23 21:14:37.176 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-23 21:15:40.343 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-23 21:15:44.482 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-23 22:13:58.303 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-23 22:15:07.691 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-23 22:38:39.162 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-23 22:38:42.283 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-24 07:28:27.811 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-24 07:28:30.924 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-24 07:29:32.011 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-24 07:29:32.030 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-24 07:29:38.234 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-24 07:30:39.329 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-24 08:30:10.379 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-24 08:32:23.958 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-24 17:45:30.942 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-24 17:45:34.059 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-25 06:20:46.014 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-25 06:26:24.685 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-25 06:46:34.417 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-25 06:46:37.539 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-25 07:03:24.181 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-25 07:05:38.841 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-25 20:26:15.388 [ome.event.ItemCommandEvent] - Item 'velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position' received command DOWN
2019-11-25 20:26:15.410 [nt.ItemStatePredictedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position predicted to become DOWN
2019-11-25 20:26:15.414 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-25 20:26:51.440 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-25 20:26:57.692 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-25 20:28:01.970 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-25 20:28:05.091 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-25 20:50:25.727 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-26 06:34:04.265 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-26 06:35:08.470 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-26 06:36:12.659 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-26 06:36:12.675 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-26 06:36:18.870 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-26 06:37:19.948 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-26 07:02:00.903 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-26 07:05:29.046 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/GW_SS_IDLE to GW_S_GWM/UNDEFTYPE
2019-11-26 07:06:32.221 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-26 07:06:36.383 [vent.ItemStateChangedEvent] - velux_klf200_cfd1ce5b_status changed from GW_S_GWM/UNDEFTYPE to GW_S_GWM/GW_SS_IDLE
2019-11-26 21:19:09.535 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 12
2019-11-26 21:19:09.556 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 12 to 0
2019-11-26 21:20:16.842 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 12
2019-11-26 21:21:24.160 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 12 to 100
2019-11-26 21:21:24.177 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-26 21:21:27.275 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-26 21:22:31.460 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-27 06:05:22.905 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 100 to 0
2019-11-27 06:05:26.021 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 100 to 0
2019-11-27 06:37:55.975 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 100
2019-11-27 06:40:12.673 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 100 to 0
2019-11-27 07:22:48.510 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 11
2019-11-27 17:41:03.414 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_O_Rollershutter_position changed from 0 to 100
2019-11-27 17:41:06.535 [vent.ItemStateChangedEvent] - velux_rollershutter_cfd1ce5b_DG_W_Rollershutter_position changed from 0 to 100
2019-11-27 18:03:35.036 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 11 to 0
2019-11-27 18:37:12.881 [ome.event.ItemCommandEvent] - Item 'velux_window_cfd1ce5b_DG_M_Window_position' received command 25
2019-11-27 18:37:12.887 [nt.ItemStatePredictedEvent] - velux_window_cfd1ce5b_DG_M_Window_position predicted to become 25
2019-11-27 18:37:12.889 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 0 to 25
2019-11-27 18:37:37.547 [ome.event.ItemCommandEvent] - Item 'velux_window_cfd1ce5b_DG_M_Window_position' received command 0
2019-11-27 18:37:37.551 [nt.ItemStatePredictedEvent] - velux_window_cfd1ce5b_DG_M_Window_position predicted to become 0
2019-11-27 18:37:37.558 [vent.ItemStateChangedEvent] - velux_window_cfd1ce5b_DG_M_Window_position changed from 25 to 0

Please verify that you are using the latest binding.

openHAB console says:

204 │ Active │ 80 │ 2.5.0.201911042102 │ openHAB Add-ons :: Bundles :: Velux Binding

What about the continuous updates of the Velux thing in my logs? Is it possible that these updates during an active operation lead to wrong values for the items?

I defined a “status” item for the bridge, as

Notes: (***) The existence of this item triggers the continuous realtime status updates of any Velux item like shutters even if they are manually controlled by other controllers.

Reason: Most of the time in real life the Velux items are controlled by the Velux remotes.

Is it possible that this causes the Velux thing updates?

Edit: Removal of the status item does not change anything :-/