i start dim-up and dim-down sequenze on presence-detektion. but the dim-down sequenze starts endless-looping if it reaches zero. ist this a bug? or am i missing some importiant trigger-statements? if the dim-down stops at 1 (not zero), it stays there as exptected (but light is still on). anybody can give a helping-hand to me (i am no programmer)?
Using "if-true" your action list executes every time when bm1 is validated, this means also when it was off before. So depending what triggers bm1 this actionlist can get executed repeatedly.
You may change the type to "on-true" or you may add another condition which checks of dim1 or another GA for the light is On at all.
Regards, Othmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, as I have never used type "dim-up" before I made some test of my own. And now I can confirm your problem. It's not related to the condition, it's part of the decrease function within "dim-up". According to my log the counter underflows at 0:
….
….
20120818 17:29:23,229 INFO Object : New value 2 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,275 INFO Object : New value 3 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,329 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,330 INFO Object : New value 1 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,430 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,431 INFO Object : New value 0 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,531 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,532 INFO Object : New value 4294967295 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,535 INFO Object : New value 0 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,537 INFO Object : New value 255 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,632 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,633 INFO Object : New value 4294967294 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,642 INFO Object : New value 254 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,699 INFO Object : New value 255 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,733 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,734 INFO Object : New value 4294967293 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,775 INFO Object : New value 253 for object dimmwert_licht_n (type: 5.xxx)
…
…
So I guess it's some bug indeed.
Workaround: decrease to some value above 0 and switch it off with a second action
Regards, Othmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-08-18
yes,
thats what i considered to test next. do you inform me, if the bug is fixed (next release?). What about to give an alias "dim-down", or name the function in general only "dim/dimming"?
anyway, lot of thanks for testing and confirming. gives realy a goog feeling about not being nuts,
and knowing some serias responsible professional on the source …
ozett
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, I'm just an exited user of this marvelous code myself for some years now and always happy in supporting other users. You better place a bug report in the Tracker. I'm sure Jef2000 or zikibe will take care of it.
Regards, Othmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i start dim-up and dim-down sequenze on presence-detektion. but the dim-down sequenze starts endless-looping if it reaches zero. ist this a bug? or am i missing some importiant trigger-statements? if the dim-down stops at 1 (not zero), it stays there as exptected (but light is still on). anybody can give a helping-hand to me (i am no programmer)?
<!- BM EG Gaeste->
<object id="bm1" gad="4/3/71">BM eg gaeste</object>
<object id="dim1" gad="1/6/103" type="5.xxx">dimm.eg.gaeste</object>
</objects>
<rules>
<rule id="bm-on">
<condition type="object" id="bm1" value="on" trigger="true"/>
<actionlist>
<action type="dim-up" id="dim1" start="51" stop="102" duration="10" />
</actionlist>
</rule>
<rule>
<condition type="object" id="bm1" value="off" trigger="true"/>
<actionlist type="if-true">
<action type="dim-up" id="dim1" start="102" stop="0" duration="10" />
</actionlist>
</rule>
</rules>
Using "if-true" your action list executes every time when bm1 is validated, this means also when it was off before. So depending what triggers bm1 this actionlist can get executed repeatedly.
You may change the type to "on-true" or you may add another condition which checks of dim1 or another GA for the light is On at all.
Regards, Othmar
OK, as I have never used type "dim-up" before I made some test of my own. And now I can confirm your problem. It's not related to the condition, it's part of the decrease function within "dim-up". According to my log the counter underflows at 0:
….
….
20120818 17:29:23,229 INFO Object : New value 2 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,275 INFO Object : New value 3 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,329 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,330 INFO Object : New value 1 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,430 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,431 INFO Object : New value 0 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,531 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,532 INFO Object : New value 4294967295 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,535 INFO Object : New value 0 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,537 INFO Object : New value 255 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,632 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,633 INFO Object : New value 4294967294 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,642 INFO Object : New value 254 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,699 INFO Object : New value 255 for object dimmzustand_licht_n (type: 5.xxx)
20120818 17:29:23,733 INFO KnxConnection : write(gad=1/2/41, buf, len=3)
20120818 17:29:23,734 INFO Object : New value 4294967293 for object dimmwert_licht_n (type: 5.xxx)
20120818 17:29:23,775 INFO Object : New value 253 for object dimmwert_licht_n (type: 5.xxx)
…
…
So I guess it's some bug indeed.
Workaround: decrease to some value above 0 and switch it off with a second action
Regards, Othmar
yes,
thats what i considered to test next. do you inform me, if the bug is fixed (next release?). What about to give an alias "dim-down", or name the function in general only "dim/dimming"?
anyway, lot of thanks for testing and confirming. gives realy a goog feeling about not being nuts,
and knowing some serias responsible professional on the source …
ozett
Sorry, I'm just an exited user of this marvelous code myself for some years now and always happy in supporting other users. You better place a bug report in the Tracker. I'm sure Jef2000 or zikibe will take care of it.
Regards, Othmar