Originally posted by: <email address deleted>
FYI, as discussed: 14_CUL_WS.pm has been updated to write the
received values into READINGS as well. Please check -- and speak
up if it breaks anything.
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.
On 25 Jan., 20:59, "Kai 'wusel' Siering"
wrote:
> FYI, as discussed: 14_CUL_WS.pm has been updated to write the
> received values into READINGS as well. Please check -- and speak
> up if it breaks anything.
> kai
Everything fine. Readings are shown.
Thx a lot! ;-)
--
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.
Hello Kai,
is it possible to get a separate output for temperature and humidity
at the READINGS?
--
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>
Gerhard Pfeffer wrote:
> Hello Kai,
>
> is it possible to get a separate output for temperature and humidity
> at the READINGS?
Hu?
list Bad_TH
Internals:
CODE 7
CUL_MSGCNT 22
CUL_RAWMSG K61041242EA
CUL_RSSI -85
CUL_TIME 2010-01-26 16:20:25
DEF 7
IODev CUL
LASTIODev CUL
MSGCNT 22
NAME Bad_TH
NR 34
STATE T: 20.4 H: 42.1
TYPE CUL_WS
corr1 0
corr2 0
corr3 0
corr4 0
Readings:
2010-01-26 16:20:25 DEVFAMILY WS300
2010-01-26 16:20:25 DEVTYPE S300TH
2010-01-26 16:20:25 humidity 42.1
2010-01-26 16:20:25 state T: 20.4 H: 42.1
2010-01-26 16:20:25 temperature 20.4
Attributes:
room Bad
Which device are you using? SxxxTH should work (see above). Or do
I get you wrong?
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>
Hi,
wie waers denn wenn DEVFAMILY und DEVTYPE aus:
Readings:
2010-01-26 16:20:25 DEVFAMILY WS300
2010-01-26 16:20:25 DEVTYPE S300TH
nach $attr wandert ?
wegen der einheitlichen READINGs und so ;-))
Schoene Gruesse
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.
Ok, my fault. I thought, a reload of the module is enough - but it
displayed not before a restart of fhem. :-/
On 26 Jan., 17:12, "Kai 'wusel' Siering"
wrote:
> Gerhard Pfeffer wrote:
> > Hello Kai,
>
> > is it possible to get a separate output for temperature and humidity
> > at the READINGS?
>
> Hu?
>
> list Bad_TH
> Internals:
> CODE 7
> CUL_MSGCNT 22
> CUL_RAWMSG K61041242EA
> CUL_RSSI -85
> CUL_TIME 2010-01-26 16:20:25
> DEF 7
> IODev CUL
> LASTIODev CUL
> MSGCNT 22
> NAME Bad_TH
> NR 34
> STATE T: 20.4 H: 42.1
> TYPE CUL_WS
> corr1 0
> corr2 0
> corr3 0
> corr4 0
> Readings:
> 2010-01-26 16:20:25 DEVFAMILY WS300
> 2010-01-26 16:20:25 DEVTYPE S300TH
> 2010-01-26 16:20:25 humidity 42.1
> 2010-01-26 16:20:25 state T: 20.4 H: 42.1
> 2010-01-26 16:20:25 temperature 20.4
> Attributes:
> room Bad
>
> Which device are you using? SxxxTH should work (see above). Or do
> I get you wrong?
> 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>
Gerhard Pfeffer wrote:
> Ok, my fault. I thought, a reload of the module is enough - but it
> displayed not before a restart of fhem. :-/
Reloading the module should have worked in my opinion, but, well, I
usually just restart FHEM after changes; I rather prefer to have seen
a correct start, just in case there is a power outage or something,
dying with an error than would be undesirable.
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.
> wie waers denn wenn DEVFAMILY und DEVTYPE aus:
> Readings:
> 2010-01-26 16:20:25 DEVFAMILY WS300
> 2010-01-26 16:20:25 DEVTYPE S300TH
> nach $attr wandert ?
Dies sind beim Empfang der Daten festgestellte Eigenschaften, und koennen nicht
vom Benutzer gesetzt werden. Insofern gehoeren sie m.A.n. zu Readings.
Fuer FS20 haben wir zwar das model Attribut, aber da kann das Modul nicht aus
dem RF-Nachricht das Geraetetyp rauslesen -> Der Benutzer muss es setzen.
Architektonisch sauberer waere CUL_WS in 11 Module aufzuteilen (CUL_WS_TH,
CUL_WS_PS50, CUL_WS_WIND, etc). Ich glaube nicht, dass es die Muehe Wert ist.
Manchmal ist is besser mit einer nicht ganz perfekten Loesung zu leben.
--
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.