neue Version Linknx erschienen

[hdehne]

Hallo LINKNX-Gemeinde:
Jeff hat eine neue Version veröffentlicht (linknx-0.0.1.26)

Gruss,

Hans

[davall]

Fehler in linknx sunset sunrise???

Kann jemand dieses Verhalten mit der neuen Version nachvollziehen?
Ist das ein Bug?

Viele Grüße, davall
------------------------
Rule in linknx.xml
<rules>
<rule id="sunset Licht ein">
<condition type="timer" trigger="true">
<at type="sunset" wdays="1234567"/>
</condition>
<actionlist>
<action type="set-value" id="l_wind" value="1"/>
</actionlist>
</rule>
</rules>
Ausgabe von linknx Version 026

2009-03-19 10:09:35 [ INFO] PeriodicTask: Rescheduled at 2009-3-19 10:9:35 (1237453775)
2009-03-19 10:09:35 [ INFO] TimerManager: TimerTask execution. 1237453775
2009-03-19 10:09:35 [ INFO] Condition: TimerCondition evaluated as '1'
2009-03-19 10:09:35 [ INFO] Condition: TimerCondition evaluated as '0'
2009-03-19 10:09:35 [ INFO] SolarTimeSpec: sun_rise_set date 2009-3-19
2009-03-19 10:09:35 [ INFO] SolarTimeSpec: sun_rise_set returned 18:36
2009-03-19 10:09:35 [ INFO] SolarTimeSpec: adjustTime date 2009-3-19
2009-03-19 10:09:35 [ INFO] SolarTimeSpec: adjustTime returned 10:9
2009-03-19 10:09:35 [ INFO] PeriodicTask: Rescheduled at 2009-3-19 10:9:35 (1237453775)
2009-03-19 10:09:35 [ INFO] TimerManager: TimerTask execution. 1237453775
2009-03-19 10:09:35 [ INFO] Condition: TimerCondition evaluated as '1'
2009-03-19 10:09:35 [ INFO] Condition: TimerCondition evaluated as '0'
2009-03-19 10:09:35 [ INFO] SolarTimeSpec: sun_rise_set date 2009-3-19
Killed

ÄNDERUNG DER RULE (Erweiterung um until...)
Rule in linknx.xml
<rules>
<rule id="sunset Licht ein">
<condition type="timer" trigger="true">
<at type="sunset" wdays="1234567"/>
<until hour="23" min="30" exception="no" wdays="1234567"/>
</condition>
<actionlist>
<action type="set-value" id="l_wind" value="1"/>
</actionlist>
</rule>
</rules>

Ausgabe von linknx Version 026

2009-03-19 10:03:39 [ INFO] Rule: Rule: Configuring sunset Licht ein (active=1)
2009-03-19 10:03:39 [ INFO] TimeSpec: 1899-0--1 -1:-1:0 (wdays=127; exception=2)
2009-03-19 10:03:39 [ INFO] TimeSpec: 1899-0--1 23:30:0 (wdays=127; exception=0)
2009-03-19 10:03:39 [ INFO] SolarTimeSpec: sun_rise_set date 2009-3-19
2009-03-19 10:03:39 [ INFO] SolarTimeSpec: sun_rise_set returned 18:36
2009-03-19 10:03:39 [ INFO] SolarTimeSpec: adjustTime date 2009-3-19
2009-03-19 10:03:39 [ INFO] SolarTimeSpec: adjustTime returned 10:3
2009-03-19 10:03:39 [ INFO] PeriodicTask: Rescheduled at 2009-3-19 10:3:39 (1237453419)
2009-03-19 10:03:39 [ INFO] Rule: ActionList: Configuring
2009-03-19 10:03:39 [ INFO] Action: SetValueAction: Configured for object l_wind with value on
2009-03-19 10:03:39 [ INFO] Rule: Rule: Configuration done
2009-03-19 10:03:39 [ INFO] main: Config file loaded: ../linknx-test.xml
2009-03-19 10:03:39 [ INFO] TimerManager: TimerTask execution. 1237453419
2009-03-19 10:03:39 [ INFO] Condition: TimerCondition evaluated as '1'
2009-03-19 10:03:39 [ INFO] PeriodicTask: Rescheduled at 2009-3-19 10:3:39 (1237501800)
2009-03-19 10:03:39 [ INFO] Action: Execute SetValueAction with value on
2009-03-19 10:03:39 [ INFO] KnxConnection: write(gad=4362, buf, len=2):
2009-03-19 10:03:39 [ INFO] KnxConnection: KnxConnection: Group socket opened. Waiting for messages.

Jetzt ist linknx nicht mehr in einer Endlosschleife, jedoch wertet linknx die Regel falsch, also als true aus!!!

[jef2000]

Hi,

You discovered a bug in version 0.0.1.26. In fact, it's an interaction between the timestamps of the new logging functionality and the time computation of some rules. Could you add the following line to your config file to see if the problem disappear?
<logging format="simple"/>This line must be added at the same level as the <services> <objects> and <rules> section. This will disable the timestamp on every log line.

Regards,

Jean-François

[davall]

Hi Jeff,

thanks for your reply. You got it!
With the line <logging format="simple"/> in my linknx.xml file everything seems to work. I forgot to mention that i run linknx on an asus500 gpV2 router with latest oleg firmware on it. Maybe this problem doesn't exist on other platforms.

The new output looks like this:

[ INFO] Rule: Rule: Configuring sunset Licht ein (active=1)
[ INFO] TimeSpec: 1899-0--1 -1:-1:0 (wdays=127; exception=2)
[ INFO] SolarTimeSpec: sun_rise_set date 2009-3-22
[ INFO] SolarTimeSpec: sun_rise_set returned 18:41
[ INFO] SolarTimeSpec: adjustTime date 2009-3-23
[ INFO] SolarTimeSpec: adjustTime returned 18:43
[ INFO] PeriodicTask: Rescheduled at 2009-3-23 18:43:0 (1237830180)
[ INFO] Rule: ActionList: Configuring
[ INFO] Action: SetValueAction: Configured for object l_wind with value off
[ INFO] Rule: Rule: Configuration done
[ INFO] main: Config file loaded: linknx-test.xml
[ INFO] KnxConnection: KnxConnection: Group socket opened. Waiting for messages.
------------------

Best regards, davall

[jef2000]

Hi,

No the bug is not specific to your platform. But after looking at the source code, I see that the only wrong behavior is when you use sunrise-sunset. For other timer types, some log messages are wrong but the system is working correctly.
I fixed the issue in CVS repository, it will be part of the next release.
Or you can use the following patch on file timermanager.cpp:
http://linknx.cvs.sourceforge.net/vi...1.9&view=patch

Regards,

Jean-François

[davall]

Hello Jean-François,

dowloaded and installed the patch. Now everything seems to run fine with 0.0.1.26. Thanks for your support. Great piece of software!

Regards, davall