Originally posted by: <email address deleted>
Fixes/reduced logging on 70_WS3600.pm
Made CUL_FHTTK work with 98_autocreate.pm, (first) GPLOT info is now used
Added sanity checking to fhem.pl, does not save undefined fields anymore
Added fht80tf.gplot, may need (re-)work
CVS: ----------------------------------------------------------------------
CVS: Enter Log. Lines beginning with `CVS:' are removed automatically
CVS:
CVS: Committing in .
CVS:
CVS: Modified Files:
CVS: fhem.pl FHEM/70_WS3600.pm FHEM/98_autocreate.pm
CVS: Added Files:
CVS: FHEM/fht80tf.gplot
CVS: ----------------------------------------------------------------------
Hopefully I didn't break anything; works for me though ;)
Working towards less perl errors, I added sanity checks to the save routine
in fhem.pl:
2010.01.04 23:57:48 3: Sanitizer: not saving READING measured-temp of FHT_0a55 due to missing VAL and/or TIME.
2010.01.04 23:57:48 3: Sanitizer: not saving READING measured-temp of FHT_3202 due to missing VAL and/or TIME.
2010.01.04 23:57:48 3: Sanitizer: not saving READING measured-temp of FHT_3315 due to missing VAL and/or TIME.
That is, malformatted data is no longer saved to the fhem.save file, thus
restarting fhem.pl frees you from this messages (and the bad data).
Long-term solution would be to make the corresponding modules not to generate
that bad data, so keep bugging the list with these messages ;)
98_autocreate.pm has been touch so that it now uses this dataset:
my %flogpar = (
"CUL_EM:.*" => { GPLOT => "cul_em:Power,", FILTER => "%NAME:CNT:.*" },
"CUL_WS:.*" => { GPLOT => "hms:Temp/Hum,", FILTER => "%NAME" },
"CUL_FHTTK:.*" => { GPLOT => "fht80tf:Window,", FILTER => "%NAME" },
"FHT:.*" => { GPLOT => "fht:Temp/Act,", FILTER => "%NAME" },
"HMS:HMS100TFK_.*" => { GPLOT => "fht80tf:Contact,", FILTER => "%NAME" },
"HMS:HMS100T._.*" => { GPLOT => "hms:Temp/Hum,", FILTER => "%NAME:T:.*" },
"KS300:.*" => { GPLOT => "ks300:Temp/Rain,ks300_2:Wind/Hum,",
FILTER => "%NAME:T:.*" },
);
CUL_WS-devices now run with humidity as well. As for CUL_FHTTK and HMS100TFK,
the gplot-stuff seems to need some work. Haven't used that yet (using rrdtool
for data storage and presentation normally) and first shoot doesn't seem to
catch; hints/help appreciated.
I'm not sure what GPLOT => "ks300:Temp/Rain,ks300_2:Wind/Hum," is supposed to
do; but as I split(/:/, $gplot) -- which yields ks300, like $lctype before --
my changes shouldn't break it, whatever this does ;)
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
> I'm not sure what GPLOT => "ks300:Temp/Rain,ks300_2:Wind/Hum," is supposed to
> do;
See my posting (2010-01-03, about 12:00) in the "S555TH plot ist leer" thread.
Thanks for the changes, they should not break anything.
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Originally posted by: <email address deleted>
Rudolf Koenig wrote:
>> I'm not sure what GPLOT => "ks300:Temp/Rain,ks300_2:Wind/Hum," is supposed to
>> do;
>
> See my posting (2010-01-03, about 12:00) in the "S555TH plot ist leer" thread.
Ah. Currently (I don't own KS300 unfortunately; it would be rather helpful to
see "list" output e. g. of WS2000 and KS300 devices, thus I could e. g. model
the WS3600 behaviour along those) it would write only one weblink fileplot
definition with "ks300"; does KS300 need more or is it purely something that
is handled via attr for weblink?
> Thanks for the changes, they should not break anything.
Uff ;)
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
> Ah. Currently (I don't own KS300 unfortunately; it would be rather helpful to
> see "list" output e. g. of WS2000 and KS300 devices,
Here is my KS300, I do not have any WSxxx
=========
Internals:
CODE 1234
CUL_MSGCNT 3313
CUL_RAWMSG K9730705600D968F7
CUL_RSSI -78.5
CUL_TIME 2010-01-05 15:32:58
DEF 1234
IODev CUL
LASTIODev CUL
MSGCNT 4871
NAME out1
NR 89
RAINUNIT 255
RFR_MSGCNT 3371
RFR_RAWMSG K9723800600D948E6
RFR_RSSI -87
RFR_TIME 2010-01-05 15:07:33
STATE T: -3 H: 67 W: 0.5 R: 577.6 IR: no
TYPE KS300
WINDUNIT 1
Readings:
2010-01-05 15:32:58 avg_day T: -9.4 H: 77 W: 0.3 R: 0.3
2010-01-05 00:00:06 avg_month T: -1.4 H: 37 W: 39.2 R: 0.2
2010-01-05 15:32:58 cum_day 2010-01-05 00:00:06 T: -526641.7 H: 4360784 W: 14385.9 R: 577.3
2010-01-05 00:00:06 cum_month 4 T: -5.5 H: 149 W: 156.8 R: 0.2
2010-01-05 15:32:58 humidity 67 (%)
2010-01-05 15:32:58 israining no (yes/no)
2010-01-05 15:32:58 rain 577.6 (l/m2)
2010-01-05 15:32:58 rain_raw 2265 (counter)
2010-01-05 15:32:58 rain_raw_adj 2265
2010-01-05 15:32:58 temperature -3 (Celsius)
2010-01-05 15:32:58 tsecs 1262701978
2010-01-05 15:32:58 unknown1 6
2010-01-05 15:32:58 unknown2 7
2010-01-05 15:32:58 unknown3 9
2010-01-05 15:32:58 wind 0.5 (km/h)
Attributes:
=========
> definition with "ks300"; does KS300 need more or is it purely something that
> is handled via attr for weblink?
In a gplot file I can only display two units (on the left and right) but the
KS300 delivers 4 (temp/hum/rain/wid).
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Am Dienstag 05 Januar 2010 schrieb Kai 'wusel' Siering:
> Ah. Currently (I don't own KS300 unfortunately; it would be rather helpful
> to see "list" output e. g. of WS2000 and KS300 devices, thus I could e. g.
> model the WS3600 behaviour along those) it would write only one weblink
ich habe eine KS-555.
fhem> list GH.ga.WE.01
Internals:
CODE 0b0b
CUL868_MSGCNT 299
CUL868_RAWMSG K97807008006FCDEE
CUL868_RSSI -83
CUL868_TIME 2010-01-05 17:23:16
DEF 0b0b 255 10
IODev CUL868
LASTIODev CUL868
MSGCNT 299
NAME GH.ga.WE.01
NR 9
RAINUNIT 255
STATE T: -8 H: 87 W: 0.0 R: 876.9 IR: no
TYPE KS300
WINDUNIT 10
Readings:
2010-01-05 17:23:16 avg_day T: -4.0 H: 81 W: 0.0 R: 0.0
2010-01-05 00:03:39 avg_month T: -4.1 H: 43 W: 44.0 R: 0.0
2010-01-05 17:23:16 cum_day 2010-01-05 00:03:39 T: -251521.6
H: 5099513 W: 0 R: 876.9
2010-01-05 00:03:39 cum_month 4 T: -16.3 H: 172 W: 176.0 R:
0.0
2010-01-05 17:23:16 humidity 87 (%)
2010-01-05 17:23:16 israining no (yes/no)
2010-01-05 17:23:16 rain 876.9 (l/m2)
2010-01-05 17:23:16 rain_raw 3439 (counter)
2010-01-05 17:23:16 rain_raw_adj 3439
2010-01-05 17:23:16 temperature -8 (Celsius)
2010-01-05 17:23:16 tsecs 1262708596
2010-01-05 17:23:16 unknown1 c
2010-01-05 17:23:16 unknown2 7
2010-01-05 17:23:16 unknown3 9
2010-01-05 17:23:16 wind 0.0 (km/h)
Attributes:
comment Wetterstation
room Garten
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Originally posted by: <email address deleted>
Moin,
Rudolf & Martin, danke für die WS300/KS555-Werte!
Fragen:
> fhem> list GH.ga.WE.01
> Internals:
> CODE 0b0b
> CUL868_MSGCNT 299
> CUL868_RAWMSG K97807008006FCDEE
> CUL868_RSSI -83
> CUL868_TIME 2010-01-05 17:23:16
> DEF 0b0b 255 10
> IODev CUL868
> LASTIODev CUL868
> MSGCNT 299
> NAME GH.ga.WE.01
> NR 9
> RAINUNIT 255
> STATE T: -8 H: 87 W: 0.0 R: 876.9 IR: no
> TYPE KS300
> WINDUNIT 10
> Readings:
> 2010-01-05 17:23:16 avg_day T: -4.0 H: 81 W: 0.0 R: 0.0
> 2010-01-05 00:03:39 avg_month T: -4.1 H: 43 W: 44.0 R: 0.0
> 2010-01-05 17:23:16 cum_day 2010-01-05 00:03:39 T: -251521.6
> H: 5099513 W: 0 R: 876.9
Bei "T:" & "H:" habt Ihr beide da ziemlich wurstige Werte ...
| 2010-01-05 15:32:58 cum_day 2010-01-05 00:00:06 T: -526641.7 H: 4360784 W: 14385.9 R: 577.3
... und bei "W:" und "R:", grade bei Schneefall, ebenfalls ziemlich
deftige Werte. Liefert das die Anlage so gruselig oder bastelt sich
FHEM das zusammen? (Und was soll bitte kumulierte Windgeschwindigkeit
sein? "Ich hatte aber mehr Wind als wie Du, ätsch bätsch!"? ;) Bei
Regen sehe ich ja noch 'nen Sinn, das aufzusummieren, aber bei Wind?!)
Wird cum_* (oder irgendwas von den READINGS) von Frontends benutzt?
> 2010-01-05 00:03:39 cum_month 4 T: -16.3 H: 172 W: 176.0 R: 0.0
| 2010-01-05 00:00:06 cum_month 4 T: -5.5 H: 149 W: 156.8 R: 0.2
Das erste Feld ist die Anzahl der Tage?
Hintergrund der Fragen: ich möchte einerseits die WS3600.pm-Ausgabe mög-
lichst nahe an der der bestehenden Wetterstationen halten (und fragte mich,
wie diese vielen Werte im "Status" wohl repräsentiert würden), ohne aber
natürlich Infos der WS3600 zu verlieren oder zu verfälschen. (Ja, use the
source ging notfalls auch, aber da Ihr wohl Ersthanderfahrungen mit diesen
Geräten habt ... ;))
Danke & Ciao,
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Hallo,
Kai 'wusel' Siering schrieb:
> Bei "T:" & "H:" habt Ihr beide da ziemlich wurstige Werte ...
>
> | 2010-01-05 15:32:58 cum_day 2010-01-05 00:00:06 T:
> -526641.7 H: 4360784 W: 14385.9 R: 577.3
>
> ... und bei "W:" und "R:", grade bei Schneefall, ebenfalls ziemlich
> deftige Werte. Liefert das die Anlage so gruselig oder bastelt sich
> FHEM das zusammen? (Und was soll bitte kumulierte Windgeschwindigkeit
> sein? "Ich hatte aber mehr Wind als wie Du, ätsch bätsch!"? ;) Bei
> Regen sehe ich ja noch 'nen Sinn, das aufzusummieren, aber bei Wind?!)
>
> Wird cum_* (oder irgendwas von den READINGS) von Frontends benutzt?
>
die kumulierten Werte werden benoetigt, um den Tages-/Monatsdurchschnitt
zu berechnen. Da wird jeweils beim ersten Datagramm nach Mitternacht
erledigt. Die Webfrontends benutzen die cum_*-Werte m.W. nicht, wohl
aber die daraus abgeleiteten avg_*-Werte.
Gruesse,
Boris
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Originally posted by: <email address deleted>
Moin,
Dr. Boris Neubert wrote:
>> Regen sehe ich ja noch 'nen Sinn, das aufzusummieren, aber bei Wind?!)
>>
>> Wird cum_* (oder irgendwas von den READINGS) von Frontends benutzt?
>>
> die kumulierten Werte werden benoetigt, um den Tages-/Monatsdurchschnitt
> zu berechnen.
Okay, das macht die WS3600 für 1h, 24h, 1W, 1M sowie absolut seit
Rain-total-Date, Rain-total-Time (18-09-2005, 03:29 bei mir) selbst;
denke, das muß man wohl nicht nachbauen.
> Da wird jeweils beim ersten Datagramm nach Mitternacht
> erledigt. Die Webfrontends benutzen die cum_*-Werte m.W. nicht, wohl
> aber die daraus abgeleiteten avg_*-Werte.
Hmm, vielleicht kann ich das basierend auf den vorhandenen Daten ja
zurechtfaken, um den Aufwand da gering zu halten. WS3600.pm gibt jetzt
'nen ähnlichen Status raus (klein-i ist der Wert für Innen, DP der
Taupunkt, WC "Wind Chill" (gefühlte Temperatur?), P der rel. Druck),
sieht zumindest in pgm2 schon mal besser aus ;)
Frage an die Frontend-Tüftler: macht das die Integration einfacher?
fhem> list WS3600
Internals:
DEF /usr/local/bin/fetch3600.real
DeviceName /usr/local/bin/fetch3600.real |
NAME WS3600
NR 4
STATE Ti: 22.2 T: -4.2 DP: -6.1 Hi: 36 H: 87 W: 0.0 Dir: W WC: -4.2 R: 0.00 P: 990.100 Tendency: Falling Forecast: Rainy
TMPSTATE
TYPE WS3600
Timer 64
pipeopentime 1262743203
Readings:
2010-01-06 03:00:21 Date 06-Jan-2010
2010-01-06 03:00:21 Dew-Point -6.1
2010-01-06 03:00:21 Dew-Point-max 20.3
2010-01-06 03:00:21 Dew-Point-min -17.2
2010-01-06 03:00:21 Dew-Point-min-Date 20-08-2009
2010-01-06 03:00:21 Dew-Point-min-Time 11:58
2010-01-06 03:00:21 Forecast Rainy
2010-01-06 03:00:21 Rain-1M 61.64
2010-01-06 03:00:21 Rain-1M-max 117.58
2010-01-06 03:00:21 Rain-1M-max-Date 01-11-2009
2010-01-06 03:00:21 Rain-1M-max-Time 00:00
2010-01-06 03:00:21 Rain-1h 0.00
2010-01-06 03:00:21 Rain-1h-hmax 24.34
2010-01-06 03:00:21 Rain-1h-hmax-Date 07-10-2009
2010-01-06 03:00:21 Rain-1h-hmax-Time 22:34
2010-01-06 03:00:21 Rain-1w 11.39
2010-01-06 03:00:21 Rain-1w-max 95.83
2010-01-06 03:00:21 Rain-1w-max-Date 12-10-2009
2010-01-06 03:00:21 Rain-1w-max-Time 00:00
2010-01-06 03:00:21 Rain-24-hmax 55.42
2010-01-06 03:00:21 Rain-24h 0.00
2010-01-06 03:00:21 Rain-24h-max-Date 08-10-2009
2010-01-06 03:00:21 Rain-24h-max-Time 07:11
2010-01-06 03:00:21 Rain-total 3133.30
2010-01-06 03:00:21 Rain-total-Date 18-09-2005
2010-01-06 03:00:21 Rain-total-Time 03:29
2010-01-06 03:00:21 Temp-inside 22.2
2010-01-06 03:00:21 Temp-inside-max 27.9
2010-01-06 03:00:21 Temp-inside-max-Date 20-08-2009
2010-01-06 03:00:21 Temp-inside-max-Time 23:31
2010-01-06 03:00:21 Temp-inside-min 19.6
2010-01-06 03:00:21 Temp-inside-min-Date 19-12-2009
2010-01-06 03:00:21 Temp-inside-min-Time 12:42
2010-01-06 03:00:21 Temp-outside -4.2
2010-01-06 03:00:21 Temp-outside-max 35.6
2010-01-06 03:00:21 Temp-outside-max-Date 20-08-2009
2010-01-06 03:00:21 Temp-outside-max-Time 16:52
2010-01-06 03:00:21 Temp-outside-min -14.7
2010-01-06 03:00:21 Temp-outside-min-Date 20-12-2009
2010-01-06 03:00:21 Temp-outside-min-Time 00:42
2010-01-06 03:00:21 Tendency Falling
2010-01-06 03:00:21 Time 03:00:08
2010-01-06 03:00:21 Wind-Chill -4.2
2010-01-06 03:00:21 Wind-Chill-max 35.6
2010-01-06 03:00:21 Wind-Chill-max-Date 20-08-2009
2010-01-06 03:00:21 Wind-Chill-max-Time 16:52
2010-01-06 03:00:21 Wind-Chill-min -14.7
2010-01-06 03:00:21 Wind-Chill-min-Date 20-12-2009
2010-01-06 03:00:21 Wind-Chill-min-Time 00:42
2010-01-06 03:00:21 Wind-DIR0 270.0
2010-01-06 03:00:21 Wind-DIR1 270.0
2010-01-06 03:00:21 Wind-DIR2 270.0
2010-01-06 03:00:21 Wind-DIR3 270.0
2010-01-06 03:00:21 Wind-DIR4 270.0
2010-01-06 03:00:21 Wind-DIR5 270.0
2010-01-06 03:00:21 Wind-Direction-Text W
2010-01-06 03:00:21 Wind-Speed 0.0
2010-01-06 03:00:21 Wind-Speed-max 25.6
2010-01-06 03:00:21 Wind-Speed-max-Date 24-09-2009
2010-01-06 03:00:21 Wind-Speed-max-Time 19:08
2010-01-06 03:00:21 Wind-Speed-min 0.0
2010-01-06 03:00:21 Wind-Speed-min-Date 02-01-2010
2010-01-06 03:00:21 Wind-Speed-min-Time 08:34
2010-01-06 03:00:21 abs-Pressure 993.800
2010-01-06 03:00:21 rel-Humidity-inside 36
2010-01-06 03:00:21 rel-Humidity-inside-max 57
2010-01-06 03:00:21 rel-Humidity-inside-max-Date 07-10-2009
2010-01-06 03:00:21 rel-Humidity-inside-max-Time 22:24
2010-01-06 03:00:21 rel-Humidity-inside-min 18
2010-01-06 03:00:21 rel-Humidity-inside-min-Date 19-12-2009
2010-01-06 03:00:21 rel-Humidity-inside-min-Time 12:37
2010-01-06 03:00:21 rel-Humidity-outside 87
2010-01-06 03:00:21 rel-Humidity-outside-max 96
2010-01-06 03:00:21 rel-Humidity-outside-max-Date 25-12-2009
2010-01-06 03:00:21 rel-Humidity-outside-max-Time 09:43
2010-01-06 03:00:21 rel-Humidity-outside-min 27
2010-01-06 03:00:21 rel-Humidity-outside-min-Date 20-08-2009
2010-01-06 03:00:21 rel-Humidity-outside-min-Time 16:41
2010-01-06 03:00:21 rel-Pressure 990.100
2010-01-06 03:00:21 rel-Pressure-max 1020.000
2010-01-06 03:00:21 rel-Pressure-max-Date 11-09-2009
2010-01-06 03:00:21 rel-Pressure-max-Time 09:19
2010-01-06 03:00:21 rel-Pressure-min 967.600
2010-01-06 03:00:21 rel-Pressure-min-Date 25-12-2009
2010-01-06 03:00:21 rel-Pressure-min-Time 06:24
Attributes:
fhem>
Ciao,
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
> Frage an die Frontend-Tüftler: macht das die Integration einfacher?
Nicht direkt.
State ist fuers uebersicht, was man beim "list" sieht, bzw. in den Fronteds auf
dem ersten Blick.
Ansonsten gibt es die triggers, die fuers Loggen sorgen. Ich wuerde bei so
einem Geraet gerne nur eine Zeile Loggen. Der KS300 triggert fuer fast jeden
seiner Readings, das ist in meinem Augen ein Dorn, da jeder der notifys fuer
jeden Reading aufgerufen werden, was CPU kostet. Andererseits macht die
Ueberwachung von einem Parameter evtl. leichter.
Btw. es muesste reichen fuer die Frontend Leute (pgm{2,3,5} entsprechende
.gplot Files zu liefern).
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Originally posted by: <email address deleted>
Rudolf Koenig wrote:
>> Frage an die Frontend-Tüftler: macht das die Integration einfacher?
>
> Nicht direkt.
> State ist fuers uebersicht, was man beim "list" sieht, bzw. in den Fronteds auf
> dem ersten Blick.
>
> Ansonsten gibt es die triggers, die fuers Loggen sorgen. Ich wuerde bei so
> einem Geraet gerne nur eine Zeile Loggen. Der KS300 triggert fuer fast jeden
> seiner Readings, das ist in meinem Augen ein Dorn, da jeder der notifys fuer
> jeden Reading aufgerufen werden, was CPU kostet. Andererseits macht die
> Ueberwachung von einem Parameter evtl. leichter.
Ich glaube, den Mechanismus verstehe ich noch nicht.
Ich habe nun
$hash->{CHANGED}[$i++] = "$reading: $val";
wieder eingefügt, am Ende des Lesens folgt ein
# $hash->{CHANGED}[$i++] = "Status: $StateString";
DoTrigger($name, undef);
-- mit "attr global verbose 5" sehe ich nur 1 Trigger durchlaufen.
Fragen:
1) Was sorgt dafür, daß -- und was -- ins Logfile geschrieben wird?
2) READINGS landen im fhem.save (wann eigentlich?), wofür ist CHANGED und wie
ist die Verbindung der beiden?
Da WS3600 (in der Theorie; das klappt noch nicht so wirklich "as expected",
aber dazu mal an anderer Stelle was) alle Daten in einem Rutsch alle ~65
Sekunden liefert, habe ich mit nur 1 Trigger erst einmal kein Problem.
> Btw. es muesste reichen fuer die Frontend Leute (pgm{2,3,5} entsprechende
> .gplot Files zu liefern).
Yuk. Ich und gplot ... Nun denn, wie ist die Namenskonvention für >2 Werte?
Effektiv interessant sind IMHO T/H innen, T/H außen, T außen/DP/WC, Rain/Wind,
Wind/Pressure, ...
kai
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.
Originally posted by: <email address deleted>
Hallo Zusammen,
Also soweit ich das verstanden habe...
Ein Device meldet sich...
Die Meldung wird per fhem.pl->Disptacher an die "zuständige" ParseFN
übergeben.
ParseFN schreibt die Werte in die READINGs und füllt das Array $hash->
{CHANGED}[]
Danach gehts weiter....an alle Module/Devices, die eine NotifyFN
haben...
Übergeben werden der Device-Name von z.B. einem Notify und der Name
des meldenden Devices...
Die NotifyFN "verarbeitet" dann $hash->{CHANGED}[]
> 1) Was sorgt daf r, da -- und was -- ins Logfile geschrieben wird?
Ein definiertes FileLog...
Das Modul FileLog hat eine NotifyFN...
> Der KS300 triggert fuer fast jeden seiner Readings,
Das doch auch nur wenn ich für jedes READING ein NOTIFY habe:
z.B. notify KS300 Temperature; notify KS300 Humidity; Notify KS300
Rain
oder ??
> wof r ist CHANGED und wie ist die Verbindung der beiden?
Dokumentation der geänderten Werte/READINGS eines Devices...
Ich denke mal, das ist einfacher als den TimeStamp der READINGs
auszuwerten ...{READINGS}{...}{TIME}
Schöne Grüße
Axel
--
You received this message because you are subscribed to the Google Groups "FHEM users" group.
To post to this group, send email to fhem-users@googlegroups.com.
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en.