Transition time ignored while switching per WLAN

[TubeHead]

Hello community

I thought at first that I was too stupid for this, but this seems to be a BUG...

I have several Dimmer2 in use here without a cloud (firmware: v1.14.1-rc1), which are controlled by FHEM. One dimmer is controlled by a wired button, all the others exclusively via WLAN via FHEM.

The "transition time" is set to 3000ms everywhere.

If I switch the dimmer with the wired button, it works wonderfully: a short press of the button and the dimmer gently moves to the previously set brightness, then gently back to OFF after another press of the button.

But if I send an ON or OFF command to the dimmer via HTTP, the "transition time" is completely ignored! Then the full brightness is available immediately and when it is OFF it also immediately goes dark! Transition time is fully ignored 🤬

That somehow doesn't make any sense to me and I currently consider it a BUG.

Can anyone confirm this?
Does anyone have a workaround?

 

Greetz

Micha

Edited October 30, 2024 by TubeHead

[Heinz]

just to make sure we cover all basis here with regards to transition time and ms response time. 

what is the signal strength of your device when connected to the network? 
There is also an option in the settings that you can enable or disable to control the devices via local network control or over the cloud. 

 

[TubeHead]

8 minutes ago, Heinz said:

what is the signal strength of your device when connected to the network? 

On average, the "worst" Dimmer2 is -55db, the "best" is -40db.
What this has to do with the response to a -wired- on/off command as opposed to a -hook- on/off command is beyond me. May you like to explain...

8 minutes ago, Heinz said:

There is also an option in the settings that you can enable or disable to control the devices via local network control or over the cloud. 

On 30.10.2024 at 10:23, TubeHead said:

I have several Dimmer2 in use here without a cloud

 

[Heinz]

Just to clear the air and to make sure we are both on the same page. 

when I see ms and HTTP commands I automatically think Network as I face a lot of network-related issues.  Thus I wanted to confirm signal that the device had a good connection.

What I would like to understand to make sure we are on the same page as I am not familiar with the FHEM system there could be many parts to this. 

when you turn on the dimmer2 from the light switch it goes from 0 to X brightness in a smooth transition. 

when you turn on the dimmer2 from the FHEM system of goes 0 to X right away with no "Fade" effect. If just goes from X  brightness to off instantly. 

am I correct in my understanding? 

[TubeHead]

53 minutes ago, Heinz said:

am I correct in my understanding? 

Yapp. You are on my path right now 👌

I don't know exactly what FHEM sends. I would have to ask the maintainer of the "Shelly.pm" module. But as far as I can tell, an ON or OFF is simply sent to :state via WebHook, as described in the API documentation.
Here is an overview of the readings read by FHEM from the Shelly Dimmer2:

 

(ignore reading "error". Comes from my try&error tests)

Edited October 31, 2024 by TubeHead

[Heinz]

Ok perfect now that i fully understand the issue I can double check some items and the API documents 

[TubeHead]

Another tip; I hadn't thought of it before:
If I operate the dimmer via the built-in GUI and click the on/off button there, it will slowly dim up and down correctly.
The command sent via API obviously does not intervene in the function at the same point as the GUI button, but bypasses the implemented functions.

[dewaldo]

If you send a command via http twice, before the first command was fully executed, e.g. transition time not passed, the dimmer2 will then execute the next command immediately resulting in a final brightness instantly.
Maybe FHEM sends the "ON/OFF" command AND in a brightess command. This way, transition time will also be ignored.

You can open a browser (PC, smartphone) and try to send the http request manually and you will see that the dimmer2 will behave normally.

In the browser, enter the following adress:
http://IPShelly/light/0?turn=on

You need to substitute "IPShelly" with the correct IP address of you dimmer2. And to turn the light off, type "off" instead of "on".
You will notice that the light will go on and off using transition time.

As an experiment, send the "on" URL and as soon as light starts to dimm up, press F5 (or on smartphone refresh page) to send the command a second time. You will see that light will be instantly switch to the final brightness value.

So you need to find out how FHEM sends a command to the shelly to change this behaviour 

[TubeHead]

... japp, that's right. Many thx for the hint.

That seems to be the problem. I will try to sniff the commands FHEM send to the Shelly's. Maybe I can see what's going on and find a fix or walk around for that.