Originally posted by: <email address deleted>
Hallo all,
After a succesfull installation of FHEM on Ubuntu and basic use of
several FS20 and FHT devices I'm starting to implement some more
functionality. In doing this the following questions came up:
1) Examining the main logfile I see a large number of failures caused
by the CUL_FHTTK device (door contact). The exact line is "n_Fenster
return value: Bareword "FHTTK_status" not allowed while "strict subs"
in use at (eval 15889) line 1." I see an entry every few minutes. The
status of the door contact is registered correctly so whats causing
this error and how can I solve it.
2) I noticed that the same FHTTK devices don't immediately send a
change in their status but this can take up to 1 or 2 minutes before
it is send. I guess that's normal behaviour but can that be changed?
3) Following an example on the Wiki I decided to split my fhem.cfg in
multiple cfg files and use an include statement in fhem.cfg. Much to
my surprise I saw after a day that fhem had put them al together again
in 1 fhem.cfg. Is that normal behaviour or did I do something wrong?
4) I would like to implement a trigger to send email from within FHEM
and I tried to figure out from earlier messages how this works but my
German is not good enough. If I'm correct I have to create an
99_email.pm and put that in the modules folder. What's the correct
contents of this module (I'm using Ubuntu v11) ?
5) I'm using the FS20 ST/3 (Funk-Schaltsteckdose). I sometimes swtich
these devices on or off on the device it self. Is there a way to check
the status of these (and similair) devices so the status can be
displayed correctly?
6) I'm using FHT80b and FHT80v devices. In one room I'm using two
FHT80v and I've configured the amount of valves on the FHT80b (An A).
Furthermore I've set the offset off the second valve to -15% to
decrease the amount on that specific radiator. It doesn't seem to
work. What am I doing wrong?
7) Are there radiator valves that can be controlled directly from FHEM
instead of throught the FHT80b device?
8) Smoke detectors? I saw earlier messages about this subject but I
didn't see a solution yet. Are there smoke detectors available that I
can use in combination with my CUNO, FS20 and FHT devices or do I have
to implement a separate CUL and use the Homematic smoke detectors?
I know these are a lot of questions but I hope you can help me out
with one or more of them.
Thanks,
Alex
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
1) The perl eval function is of the opinion that the perl code belonging to
your notify named n_Fenster is not correct.
2) It is normal, and cannot be influenced. To be overly exact, you can change
the X in the formula "115+X*0.5 sec" between 0 and 7 with the last digit of the
FHT-Code.
3) It is normal if you are using autocreate, type save, or click on the save
button in the frontend. If you are sure that it is neither, then it is a bug,
please help me to pinpoint it.
4) This is not strictly necessary, just one of the possible ways. I am using a
shell-script for the same purpose. If you still want to use it: Copy
99_Utils.pm to 99_MyUtils.pm, delete everything after the initialize function,
and rename the function to MyUtils_Initialize. Any perl function created there
will be accessible from the "perl oneliners" of at/notify/etc.
5) Not with FS20. HomeMatic has such a functionality.
6) I probably cannot help anyway, but I have the feeling that "doesn't seem to
work" is not enough information.
7) The FHT8v can be controlled with the CUL, and I hope I get the EnOcean based
MD15 to work in the next weeks (it is waiting to be fixed for months now).
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Thanks Rudolf for the fast response and answers.
On 21 dec, 13:15, Rudolf Koenig wrote:
> 1) The perl eval function is of the opinion that the perl code belonging to
> your notify named n_Fenster is not correct.
Correct, I made a typo in implementing 99_marte.pm that I copied from
the wiki. Solved.
>
> 2) It is normal, and cannot be influenced. To be overly exact, you can change
> the X in the formula "115+X*0.5 sec" between 0 and 7 with the last digit of the
> FHT-Code.
ok.
>
> 3) It is normal if you are using autocreate, type save, or click on the save
> button in the frontend. If you are sure that it is neither, then it is a bug,
> please help me to pinpoint it.
I probably did something wrong because it seems to work now. Thanks.
>
> 4) This is not strictly necessary, just one of the possible ways. I am using a
> shell-script for the same purpose. If you still want to use it: Copy
> 99_Utils.pm to 99_MyUtils.pm, delete everything after the initialize function,
> and rename the function to MyUtils_Initialize. Any perl function created there
> will be accessible from the "perl oneliners" of at/notify/etc.
I'll give it a try
>
> 5) Not with FS20. HomeMatic has such a functionality.
Too bad. Maybe I'll try some of the HomeMatic devices to see the
difference but first I'll spend my time in optimizing my current
config.
>
> 6) I probably cannot help anyway, but I have the feeling that "doesn't seem to
> work" is not enough information.
You're right but that's because I didn't have spend a lot of time to
this problem yet. Although I have set the offset for the second valve
(also confirmed by the details I see in Fhem for that FHT80 device) I
see no difference in % in the readout on the valve itself. I should
think that if the first valve shows 30% opening, the second valve
should show 15% (with a offset of -15%). And at the same time I got
the impression that the heating of the second radiotor was increased
instead of decreased. I'm going to experiment a bit more with this and
let you know.
>
> 7) The FHT8v can be controlled with the CUL, and I hope I get the EnOcean based
> MD15 to work in the next weeks (it is waiting to be fixed for months now).
I'm saw the 11_FHT8V module in the contrib folder. Do I need to copy
that module to the modules folder before I can define a FHT8V valve?
Anyway, I'm going to try and se myself :)
Thanks again.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> I'm saw the 11_FHT8V module in the contrib folder. Do I need to copy
> that module to the modules folder before I can define a FHT8V valve?
Since fhem 5.1 there is a documented 11_FHT8v.pm in the FHEM directory. Since
it is not widely used, I recommend it only for experienced fhem users.
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com