13.01.2023, 18:52
(12.01.2023, 14:34)admin Wrote: Can you enable object logs for pir output, lamp control and status? Then provide object log CSV where the issue is visible. It's hard to replicate this without exact commands and timings between them.
Dear Admin,
Thank you for the reaction!
This is what I did in chronological order (see the attached CSV log):
On Jan 12, 2023:
I first set the timeout to 60 seconds and the high setting to 88% and I deleted the old logs.
Then I set the brightness manually (via the visualization) to 30%.
The script went wrong immediately. I manually reset to 30% at 7:31:30 PM.
The script went wrong again. I reset to 30% at 8:16:45 PM, after which the script failed again.
On Jan 13, 2023 another script started the lamp at 30% around 4pm.
With movement around 4:30 PM, the lamp went to 88%, but before the timeout was over, there was movement again. The lamp then remained at 88%.
Around 6:50 PM I set timeout to 4 seconds and a restart was performed. Several PIR movements detected and lamp did not hang at 88%. But 4 seconds is far to short.
Around 7:05 PM I set the timeout to 15 seconds and a restart was performed. Already after the first single movement, the lamp remains at 88%.
In between, of course, much more movement has been detected from my family.
In the attachment you will find the csv.
I have re-read our entire correspondence. Maybe I'm doing something wrong with the status. I have the return object of the dimmer there (brightness value feedback). Am I doing that wrong?
This is what I have in the table:
input = '9/0/1', -- binary PIR status
enable = '3/0/7', -- enable timer on/off
output = '1/1/7', -- dimmer control (0..100%)
status = '3/2/7', -- dimmer status (0..100%)
onvaluehigh = 88, -- high output value in %
onvaluelow = 10, -- low output value in %
timeout = 15, -- in seconds
If you need more information, I am very happy to send everything you need to solve this.
Thank you,
Dirk