Scene 1 doesn't work, Scene 2 works. Why?

[Riki 1]

Môže mi niekto vysvetliť, prečo scéna 1 nefunguje a scéna 2 funguje? Nemala by byť funkčná aj scéna 1? Ďakujem.

Please login or register to see this attachment.

 

 

Edited January 7, 2024 by Riki
the picture did not match the description

[Martin_N 148]

@Riki

The context is not clear to me, you probably control the disconnection by the charger.

However, check that scene 1 is set to automatic mode.

I'm a bit puzzled by the idea of scene 2. Shouldn't there be an AND operator and All conditions are true?

[Riki 1]

1 hour ago, Martin_N said:

@Riki

Yes in scene 2 the operator should be "AND" and not "OR".  Somehow I accidentally flipped it while taking a screenshot.

 

Scene 1: there, the Fibaro socket (connected mobile) immediately turns off after switching on.  It will not wait for a time interval. And I don't understand why he ignores that time.  The scene is in AUTO mode.

Edited January 7, 2024 by Riki

[Brors94 51]

ah, the delay you are setting in the condtion is not a delay one the actions side. It is just a check that it have been under 9W usage for 2mins and then sends a trigger. 

 

so if it never triggers, have u checked in the general tab on the device that it is under 9W consumpotion for more then 2min? (the energy graphs)

 

and to set delay on the action side use this tool: 

Please login or register to see this image.

/monthly_2024_01/image.png.a7059237f7939ea1a7cbe46cad81c9f1.png" />

 

 

 

[Martin_N 148]

@Riki Unfortunately, due to the older (yet stable) FW, I don't have this time item available in the scenes, so I can't verify it.
The only thing I can think of is that the consumption report is for a longer time than your 2 minutes and the condition thus does not receive the relevant data. Maybe it calculates in the sense of "no data" = "none, i.e. zero consumption" = 0<9W applies.
Why this works in scene 2 will be because of the compound AND condition, so the scene has time to wait for the consumption information to be delivered.
But as I say, I can't verify it, so I'm just speculating.
Personally, I like the second scene better (with the AND), there wouldn't be as many cycles (unintentionally shutting down)

[Martin_N 148]

I understood it (probably correctly) that it monitors the charge level of the phone and if it is sufficiently charged, the consumption drops below 9W. And to prevent this from happening due to pulse charging, when the consumption fluctuates, a timeout of 2 minutes is included in the condition. Personally, this seems like a short amount of time, the 9W size could probably be smaller, but I think Riki has done some measurements and research where these values worked for him.

 

Riki, I assume that you turn on the charger with the button on the outlet, or with the application when you reconnect the phone to the charger.

[Riki 1]

@Martin_N yes my phone will turn off when the consumption drops below 9W for 2 minutes. I have experienced that this way my specific phone is charged to about 75-85%. I'm saving battery :). The fibaro socket is usually turned on by the scena at 2:00 a.m. at night. But sometimes, even during the day, I turn on the Fibaro socket when I need to charge my phone. Scene 2 works reliably. Scene 1 immediately turns off the socket immediately after turning it on. He ignores the 2 minutes.

Edited January 7, 2024 by Riki