dzVents device open() command results in "Set Level:" and "Open" in device log

[scsc3]

Hello,

I am looking for some advice or some guidelines to detect the cause for the following problem:

Recently, I noticed the following problem when sending timely scheduled commands to some Fibaro FGR223 Roller Shutters:

The dzVents script that I am using contains the following commands (the whole script is in the attachment):

Code: Select all

domoticz.devices('1.OG Ostseite/Gartenblick').open().afterSec(tostring(randomsec1))
domoticz.devices('1.OG Schlafzimmer Gartenblick').open().afterSec(tostring(randomsec1 + 4))

The commands are properly scheduled but the device log in the GUI shows that not only an Open command is executed but also a Set Level: and both of these commands for the same device are executed at the same time as shown in the following:

'1.OG Ostseite/Gartenblick' - device activity text log from GUI (Fibaro FGR223 Roller Shutter Controller 3+)
Date Data User
2025-07-13 17:22:30 Open EventSystem//home/pi/domoticz/dzVents/runtime/dzVents.lua
2025-07-13 17:22:30 Set Level: 3 % Aeotec Stick
2025-07-13 09:33:00 Set Level: 3 % EventSystem//home/pi/domoticz/dzVents/runtime/dzVents.lua
2025-07-13 09:32:00 Close EventSystem//home/pi/domoticz/dzVents/runtime/dzVents.lua

'1.OG Schlafzimmer Gartenblick' - activity text log from GUI (Fibaro FGR223 Roller Shutter Controller 3+)
Date Data User
2025-07-13 17:22:34 Open EventSystem//home/pi/domoticz/dzVents/runtime/dzVents.lua
2025-07-13 17:22:34 Set Level: 1 % Aeotec Stick
2025-07-13 12:05:46 Set Level: 1 % Aeotec Stick
2025-07-13 10:55:59 Close Aeotec Stick

As a result the two blinds (controlled by the two FGR223 devices) are not moved at all (remain at level 3 as they set hours before by a different dzVents script).
Also if 3% or 1% for the Set Level command is used could depend on the previous command that was sent to the device.
I calibrated both devices various times and in a different context (script) the command (open()) seems to work fine. Also a restart of Domoticz did not change that behavior.
Has someone seen such a behavior before or are there suggestions on how to further investigate this behavior in this context?