Domoticz

Lately i noticed that my qubino module switches on after dusk(like it should) and instantly switches off.
e.g. the light never goes on.
i can switch it on manually without any problems but scheduled it sometimes does this

anybody has the same problems

this is what it looks like from the log

Have you checked the settings of the module?
There is a setting to switch of the module after x time. Also check the input 1 type setting.(push button or not)

Greetz YcKe

1: input switch is set to push type
11:automatic turning off =0
12:automatic turning on=0

i do not use any physical switches in the module so setting 1 should not matter.

are you telling me that with the pushtype it might be sensitive to false switching?

the problem only occurs once in a while and it is not because the module did not receive the switch on command because looking at the log it did

i have thise module scheduled to switch on 20 minutes after sun set

Can you post a screenshot of your scene/timer?

Greetz YcKe

here it is
nothing complex

Mmmm, indeed. I have something similar except the 20 minutes delay, can you remove the 20 minutes delay and see if the problem still occurs?

Greetz YcKe

i will
i also changed the everyday in ma,di,wo,th,fr,sat,sun in case there is a bug in that setting

Gravityz wrote:i will
i also changed the everyday in ma,di,wo,th,fr,sat,sun in case there is a bug in that setting

I'm using the latest beta with the everyday setting so I don't see a problem occurring there.

Keep us posted how it goes!

Greetz YcKe

Gravityz wrote:i will
i also changed the everyday in ma,di,wo,th,fr,sat,sun in case there is a bug in that setting

Or a bug in the device firmware, as the relay control side of another qubino product: The smart-meter?

http://www.domoticz.com/forum/viewtopic ... 79#p130079

The Lua device script at the end handles an automatic command that reverse last one if 2 commands follows each others with close timings.

So when you get an ON (you required) immediately followed by a OFF (unwanted), the scrip sends another ON a few seconds (configurable) later in order to get a stable ON state.

It makes the smart-meter relay control work despite of it's crappy firmware.

Mmm,

might be a bug in the module.
the thing is this module performed flawless for 1 year now.

Yesterday i noticed that it did not switch off on a scheduled time.
the same off command, this time send from a scene did the job.
i am golinfg to delete and make the timer settings again to make sure they are not corrupted somehow

checked my log yesterday and indeed it looks like the module switches itself back on

it was supposed to switch off at 23:40:00 but this is what happened.

Did you check if there might be an unwanted openzwave association somewhere with the device?

how can i check that?

i haver the switch with its timing settings
besides that it is only mentioned in an all off scene which works at a certain time.
that scene turns all modules off in case some are left on(if the faiul to switch off

never experiened that this functionality is needed because normally all modules doo exactly like the are supposed to do.

Also if the firmware in the Qubino is buggy why did it function perfect for almost a year, never one failure.

Gravityz wrote: ... tuinlampen.jpg

Is that configuration really meant to scheduled to switch on 20 minutes after sun set?
Since the value description of time means value (time) between 00:01 and 23.59 ...

Would be great if this is the way to delay action after sunrise or sunset.

Kind regards
matty

Yes it is

time is indeed from 00:00-23:59
Type however describes the contect of that time

on time means: switch on exactly on the time specified
after sunset means: use the time specified as a delay after sunset

You have lot of other types
like
before sunset
after sunset
before dunrise
after sunrise
fixed date/time
odd week number
etc etc

Gravityz wrote:... Yes it is

time is indeed from 00:00-23:59
Type however describes the contect of that time

on time means: switch on exactly on the time specified
after sunset means: use the time specified as a delay after sunset

...

Confirmed. Yes it is working pretty good for me. And finally I have got e quite simple blockly to move my shutter up and down on a certain time after sunset and sunrise. Needed to use a virtual day/night switch with time functionality, a user variable and a group with open/close percentage for my shutter ...

Thanks all 4 sharing your ideas in the forum.
matty