2007-01-30 12:47:36 +00:00
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
|
|
|
|
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
|
|
|
|
|
|
|
|
<head>
|
|
|
|
|
<title>FHEM FAQ</title>
|
|
|
|
|
</head>
|
|
|
|
|
|
|
|
|
|
<body style="background-color: white;">
|
|
|
|
|
|
|
|
|
|
<h2>FHEM FAQ</h2>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
<a href="#faq1">1. I am using fhem.pl with an fhz1000.pl config file and fhem.pl
|
2008-09-19 13:51:22 +00:00
|
|
|
won't start</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq2">2. I get "undefined" messages in the log after upgrading
|
2008-09-19 13:51:22 +00:00
|
|
|
fhem.pl</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq3">3. I switched on a FS20 device directly (without the remote),
|
2008-09-19 13:51:22 +00:00
|
|
|
but the fhem.pl did not noticed it. Is it a bug?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq4">4. I have some FS20/FHT/HMS devices. How do I know their
|
2008-09-19 13:51:22 +00:00
|
|
|
housecode?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq5">5. I have the code for my devices in the ELV notation, which
|
|
|
|
|
contains 1,2,3 and 4, but you require a hex code. How should I convert
|
2008-09-19 13:51:22 +00:00
|
|
|
it?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq6">6. I replaced my FHZ1X00PC, now the FHT80b's does not work
|
2008-09-19 13:51:22 +00:00
|
|
|
anymore. Help me!</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq7">7. I can specify an optional ml/raincounter for a KS300. Why
|
2008-09-19 13:51:22 +00:00
|
|
|
do you think that 255 should be the default?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq8">8. The time specification of the builtin at command is not very
|
2008-09-19 13:51:22 +00:00
|
|
|
flexible. Please add day/month/weekday to it.</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq9">9. I defined my FS20STR as an FHT device, but I do not get
|
2008-09-19 13:51:22 +00:00
|
|
|
any data from it.</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq10">10. How to convert the FHT8b code seen in its display to the
|
2008-09-19 13:51:22 +00:00
|
|
|
hex code needed by fhem.pl?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a href="#faq11">11. I'd like to use this sunrise/sunset stuff, can you help
|
2008-09-19 13:51:22 +00:00
|
|
|
me?</a><br>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
2008-08-04 13:47:53 +00:00
|
|
|
<a href="#faq12">12. I'd like to switch on the ventilator if the FHT tells me
|
2008-09-19 13:51:22 +00:00
|
|
|
its too hot. How to tell fhem to do that?</a><br>
|
2008-08-04 13:47:53 +00:00
|
|
|
|
|
|
|
|
<a href="#faq13">13. I'd like to see directly in the Web frontend if a window
|
2008-09-19 13:51:22 +00:00
|
|
|
is open. How to do that?</a><br>
|
2008-08-04 13:47:53 +00:00
|
|
|
|
|
|
|
|
<a href="#faq14">14. In the summer I get a lot of "actuator:lime-protection"
|
|
|
|
|
messages from my FHT80b. How to switch back to the actuator:0% messages?</a>
|
2008-09-19 13:51:22 +00:00
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<a href="#faq15">15. My notify/filelog does not work, help me!</a><br>
|
2007-05-22 07:09:07 +00:00
|
|
|
|
2008-10-02 08:05:20 +00:00
|
|
|
<a href="#faq16">16. Setting auto-mode from manual for the FHT won't change the
|
|
|
|
|
desired temperature!</a><br>
|
|
|
|
|
|
2008-10-11 08:04:22 +00:00
|
|
|
<a href="#faq17">17. I have problem receiving data, I get "Bad CRC" or "Oversized message."</a><br>
|
2008-07-24 07:39:15 +00:00
|
|
|
|
2008-07-28 12:33:29 +00:00
|
|
|
<br/>
|
|
|
|
|
<br/>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq1"></a>
|
|
|
|
|
<b>1. I am using fhem.pl with an fhz1000.pl config file and fhem.pl won't
|
|
|
|
|
start</b>
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
The syntax changed, you have to modify you config file:
|
|
|
|
|
<ul>
|
|
|
|
|
<li>logfile/modpath/pidfile/port/verbose "renamed" to "attr global xx</li>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>change logfile <xxx> to attr global logfile <xxx></li>
|
|
|
|
|
<li>change modpath <xxx> to attr global modpath <xxx></li>
|
2007-05-27 17:33:06 +00:00
|
|
|
<li>change pidfile <xxx> to attr global pidfilename <xxx></li>
|
2007-04-14 08:22:18 +00:00
|
|
|
<li>change port <xxx> to attr global port <xxx></li>
|
|
|
|
|
<li>change verbose <xxx> to attr global verbose <xxx></li>
|
|
|
|
|
</ul>
|
|
|
|
|
<li>savefile renamed to "attr global statefile" (<b>not</b> savefile)</li>
|
|
|
|
|
<li>at/notify "renamed" to "define at/notify"<br>
|
|
|
|
|
This means you have to give a name to each of your at's or
|
|
|
|
|
notify commands. E.g.:
|
|
|
|
|
<ul>
|
|
|
|
|
<li><code>at *07:00 set lamp on</code><br>
|
|
|
|
|
becomes<br>
|
|
|
|
|
<code>define wake_me at *07:00 set lamp on</code></li>
|
|
|
|
|
<li><code>notify fire:on "send_sms"</code><br>
|
|
|
|
|
becomes<br>
|
|
|
|
|
<code>define fire_alarm notify fire:on "send_sms"</code><br>
|
|
|
|
|
</ul>
|
|
|
|
|
This seems to be tedious at the beginning but you get easy
|
|
|
|
|
deletion and attribute specification for these commands.
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<a name="faq2"></a>
|
|
|
|
|
<b>2. I get "undefined" messages in the log after upgrading fhem.pl</b>
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
|
|
|
|
Stop fhem.pl, delete the previous .save file and restart fhem.pl.
|
|
|
|
|
If the problem still exists, send a bugreport.
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq3"></a>
|
|
|
|
|
<b>3. I switched on a FS20 device directly (without the remote), but
|
2007-01-30 12:47:36 +00:00
|
|
|
the fhem.pl did not noticed it.<br>Is it a bug?</b>
|
|
|
|
|
<ul>
|
|
|
|
|
The protocol used by the FS20 family is quite simple: it is </b>not</b>
|
|
|
|
|
encrypted in any way, and there is no feedback to the sender. So if you
|
|
|
|
|
push any buttons on a pure receiver, no radio waves will be sent out, and
|
|
|
|
|
the FHZ1000 won't notice anything. The FHZ1000PC does not even know if
|
|
|
|
|
somebody received its message, it simply sends it out 3 times and hopes
|
|
|
|
|
for good luck.<br>
|
|
|
|
|
To answer the question: it is not a bug :-)
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq4"></a>
|
|
|
|
|
<b>4. I have some FS20/FHT/HMS devices.<br>
|
2007-01-30 12:47:36 +00:00
|
|
|
How do I know their housecode?</b><br>
|
|
|
|
|
<ul>
|
|
|
|
|
If you already programmed some devices, then just start fhem.pl with one
|
|
|
|
|
of the example configuration files, and watch the log. When activating a
|
2007-05-24 11:30:25 +00:00
|
|
|
device (e.g. with the remote) then it will be logged as an unknown device
|
2007-01-30 12:47:36 +00:00
|
|
|
with the housecode. Note: the verbose level must be 3 or higher. KS300
|
|
|
|
|
devices do not have a proper code, so you can use anything.
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq5"></a>
|
|
|
|
|
<b>5. I have the code for my devices in the ELV notation, which contains 1,2,3
|
2008-07-28 12:33:29 +00:00
|
|
|
and 4, but fhem requires a hex code. How should I convert it?</b>
|
2007-04-14 08:22:18 +00:00
|
|
|
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
2008-07-28 12:33:29 +00:00
|
|
|
Note: current fhem versions accept FS20 codes in ELV notation.<br/><br/>
|
|
|
|
|
|
2007-01-30 12:47:36 +00:00
|
|
|
The code used by ELV is in the "quaternal" (?) system plus one added to each
|
|
|
|
|
digit, so you can even use the 4 button remote for programming. To convert,
|
|
|
|
|
you have two choices: the program four2hex in the contrib directory, or the
|
|
|
|
|
good old unix program bc.
|
|
|
|
|
<ul>
|
|
|
|
|
<li>From quaternal (ELV Remote) to hex (fhem.pl):<br>
|
|
|
|
|
<pre>
|
|
|
|
|
% bc
|
|
|
|
|
obase=16
|
|
|
|
|
ibase=4
|
|
|
|
|
<elv number></pre>
|
|
|
|
|
where <elv number> is the number used on the remote, but 1
|
|
|
|
|
substracted from every digit (so each digit is between 0 and 3).</li>
|
|
|
|
|
|
|
|
|
|
<li>From hex (fhem.pl) to quaternal (ELV Remote):<br>
|
|
|
|
|
<pre>
|
|
|
|
|
% bc
|
|
|
|
|
ibase=16
|
|
|
|
|
obase=4
|
|
|
|
|
<hex number></pre>
|
|
|
|
|
Now add 1 to each digit of the result, and prepend it with 1's if
|
|
|
|
|
it has less than 4 digits.</li> </ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq6"></a>
|
2008-07-28 12:33:29 +00:00
|
|
|
<b>6. I replaced my FHZ1X00PC, now the FHT80b's does not work anymore.
|
2007-01-30 12:47:36 +00:00
|
|
|
Help me!</b>
|
|
|
|
|
<ul>
|
|
|
|
|
The FHT80b's are talking to a single FHZ1XXX device, which has a unique
|
|
|
|
|
"FHTcode". You have two choices: if you know the old FHTcode, then you can
|
|
|
|
|
set it, or you can tell the FHT80b to forget the old FHZ, and start talking
|
|
|
|
|
with the new one.
|
|
|
|
|
<ul>
|
|
|
|
|
<li>Set the FHTcode: The problem with this method is that I don't know how
|
|
|
|
|
to read out the value, we just can change it with<br>
|
|
|
|
|
<code>set FHZ FHTcode <hex-code></code></li>
|
|
|
|
|
<li>Resync the FHT80b: Press PROG until "Sond" appears, then select "CEnt"
|
|
|
|
|
with the wheel, press PROG again, Select "nA" with the wheel, press PROG
|
|
|
|
|
again.</li>
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq7"></a>
|
2008-07-28 12:33:29 +00:00
|
|
|
<b>7. I can specify an optional ml/raincounter for a KS300. Why do you think
|
|
|
|
|
that 255 should be the default?</b>
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
|
|
|
|
The manual talks about 0.3l resolution, but I wanted to calibrate my device.
|
|
|
|
|
So I filled a plastic bottle with 0.5 liter water from the measuring cup,
|
|
|
|
|
drilled a small hole in the bottom of the bottle, let the water flow slowly
|
|
|
|
|
in the KS300 rain-cup, and looked at the counter after the bottle was empty.<br>
|
|
|
|
|
|
|
|
|
|
The raincounter was incremented by 130 ticks. The diameter of my KS300
|
|
|
|
|
rain-cup is 13.9 cm, the area ca 151.75 cm<sup>2</sup>, which
|
|
|
|
|
is ca 1/65.9 m<sup>2</sup>.
|
|
|
|
|
The 0.5 liter corresponds to 32.95 liter per m<sup>2</sup>. 130 ticks
|
|
|
|
|
correspond to 32.95 l/m<sum>2</sup> -> 1 tick is ca 253 ml. I estimate
|
|
|
|
|
the error margin to +/- 2%<br>
|
|
|
|
|
|
|
|
|
|
You are welcome to do your own experiments, I am interested in the results.
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq8"></a>
|
|
|
|
|
<b>8. The time specification of the builtin at command is not very
|
2008-07-28 12:33:29 +00:00
|
|
|
flexible. Please add day/month/weekday to it.</b>
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
|
|
|
|
I think the command is complex and flexible enough. Use a perl expression
|
|
|
|
|
for this functionality like (described in the commandref.html):
|
|
|
|
|
<pre>at *07:00:00 { fhz "set lamp on" if($we) }</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
<a name="faq9"></a>
|
|
|
|
|
<b>9. I defined my FS20STR as an FHT device, but I do not get any data from
|
|
|
|
|
it.</b>
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
|
|
|
|
The FS20STR is an FS20 device, even if it looks like an FHT80b.
|
2007-03-19 14:59:37 +00:00
|
|
|
You'll get "only" on-for-timer and off-for-timer events sent.
|
2007-01-30 12:47:36 +00:00
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq10"></a>
|
|
|
|
|
<b>10. How to convert the FHT8b code seen in its display to the hex code needed
|
|
|
|
|
by fhem.pl?</b>
|
|
|
|
|
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
|
|
|
|
Convert the first 2 digits first from decimal to hex, then the next two. Example:<br>
|
|
|
|
|
<pre>
|
|
|
|
|
% bc
|
2007-05-22 07:09:07 +00:00
|
|
|
obase=16
|
2007-01-30 12:47:36 +00:00
|
|
|
<first two digits>
|
|
|
|
|
<last two digits></pre>
|
|
|
|
|
E.g The FHT8b code 1121 is 0b15 for the fhem.pl
|
|
|
|
|
</ul>
|
|
|
|
|
|
2007-04-14 08:22:18 +00:00
|
|
|
|
|
|
|
|
<a name="faq11"></a>
|
|
|
|
|
<b>11. I'd like to use this sunrise/sunset stuff, can you help me?</b>
|
2007-01-30 12:47:36 +00:00
|
|
|
<ul>
|
2008-07-28 12:33:29 +00:00
|
|
|
Look for the geographic coordinates of your home, e.g with a GPS
|
2007-01-30 12:47:36 +00:00
|
|
|
receiver or with googleearth. Compute the latitude/longitude as needed, and
|
2007-11-26 08:27:04 +00:00
|
|
|
enter them in your lastinclude file with the command:
|
|
|
|
|
<pre>{sunrise_coord("<latitude>", "<longitude>", "") }</pre>
|
2008-07-28 12:33:29 +00:00
|
|
|
After restart, { sunrise_abs() } will return the time of the sunrise today,
|
|
|
|
|
in a HH:MM:SS format.<br><br>
|
2007-05-24 11:30:25 +00:00
|
|
|
|
2008-07-28 12:33:29 +00:00
|
|
|
Note: 99_SUNRISE_EL.pm is the ExtraLight version of the original
|
|
|
|
|
99_SUNRISE.pm, which needs the DateTime::Event::Sunrise perl module, which
|
|
|
|
|
in turn is usually difficult to install. If you still want to use the
|
|
|
|
|
original module, then the initialization string will be slightly different:
|
|
|
|
|
<pre>{sunrise_coord("<latitude>", "<longitude>", "Europe/Berlin") }</pre>
|
2007-01-30 12:47:36 +00:00
|
|
|
</ul>
|
|
|
|
|
|
2007-05-22 07:09:07 +00:00
|
|
|
<a name="faq12"></a>
|
|
|
|
|
<b>12. I'd like to switch on the ventilator if the FHT tells me its too hot. How to tell fhem to do that?</b>
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
|
|
To get used to the methods, we do it step by step. Telnet to fhem, and type
|
|
|
|
|
the following:
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
# Check simply the value. It is the same as seen in "list"
|
|
|
|
|
FHZ> {$value{myfht}}
|
|
|
|
|
measured-temp: 23.8 (Celsius)
|
|
|
|
|
|
|
|
|
|
# Get the second word, so we can compare it.
|
|
|
|
|
FHZ> { my @a = split(" ", $value{myfht});; $a[1] }
|
|
|
|
|
23.8
|
|
|
|
|
|
|
|
|
|
# Set the ventilator on now, if its too hot.
|
|
|
|
|
FHZ> { my @a = split(" ", $value{myfht});; fhem("set ventilator on") if($a[1] > 25.0) }
|
|
|
|
|
|
|
|
|
|
# Now do this regularly
|
|
|
|
|
FHZ> define chilldown at +*00:30:00 { my @a = split(" ", $value{myfht});; fhem("set ventilator on") if($a[1] > 25.0) }
|
|
|
|
|
|
|
|
|
|
# An alternative:
|
|
|
|
|
FHZ> define chilldown at +*00:30:00 { fhem("set ventilator on") if($value{myfht} gt "measured-temp: 25.0") }
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
2008-07-24 07:39:15 +00:00
|
|
|
<a name="faq13"></a>
|
|
|
|
|
<b>13. I'd like to see directly in the Web frontend if a window is open.
|
|
|
|
|
How to do that? (by fwolff)</b>
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
|
|
Just define a new (pseudo) FS20 device called "window" and use the following
|
|
|
|
|
notify settings:
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
define window_open notify bad.*warnings.*Window.*open.* set window on
|
|
|
|
|
define window_close notify bad.*warnings.*none.* set window off
|
|
|
|
|
</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
|
2008-08-04 13:47:53 +00:00
|
|
|
<a name="faq14"></a>
|
|
|
|
|
<b>14. In the summer I get a lot of "actuator:lime-protection
|
|
|
|
|
messages from my FHT80b. How to switch back to the actuator:0% messages?
|
|
|
|
|
</b>
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
|
|
(Thanks for Martin Fischer for researching)<br>
|
|
|
|
|
The problem happens if at the weekly lime-protection time (usually saturday
|
|
|
|
|
at 11:00 AM) the desired temperature is lower than the measured temperature.
|
|
|
|
|
I think this is an FHT80b firmware bug, a workaround is to set the desired
|
|
|
|
|
temperature for a short time higher than the measured temperature.
|
|
|
|
|
You can automate it with the following notify:
|
|
|
|
|
<pre>
|
|
|
|
|
define lime_reset notify .*lime-protection {\
|
|
|
|
|
$d = $defs{@}{READINGS}{"desired-temp"}{VAL};;\
|
|
|
|
|
$m = $defs{@}{READINGS}{"measured-temp"}{VAL};;\
|
2008-08-06 07:55:53 +00:00
|
|
|
if($m gt $d) {\
|
2008-08-04 13:47:53 +00:00
|
|
|
fhem("set @ desired-temp 29");;\
|
|
|
|
|
fhem("set @ desired-temp $d");;\
|
|
|
|
|
}\
|
|
|
|
|
}
|
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
2008-09-19 13:51:22 +00:00
|
|
|
<a name="faq15">
|
|
|
|
|
<b>15. My notify/filelog does not work, help me!</b>
|
|
|
|
|
<ul>
|
|
|
|
|
First learn what are the trigger messages: telnet to your fhem (e.g. telnet
|
|
|
|
|
localhost 7072) and issue the command "inform on". If there is an
|
|
|
|
|
FS20/HMS/etc event, then you'll see a line of the form
|
|
|
|
|
"TYPE DEVICENAME EVENT". Some devicetypes generate more than one trigger
|
|
|
|
|
message for one event, (E.g. HMS or KS300.<br>
|
|
|
|
|
Example: you have an FS20 device named piri, which sends a command
|
|
|
|
|
"on-for-timer 60". In this case you'll see: FS20 piri on-for-timer 60
|
|
|
|
|
<br><br>
|
|
|
|
|
|
|
|
|
|
Now define your notify/filelog. The regexp specified will be tested
|
|
|
|
|
against the DEVICENAME and against the DEVICENAME:EVENT strings. If they
|
|
|
|
|
match, then the action will be executed. For our example this would be:
|
|
|
|
|
define piri_ntfy piri:on.* some_command<br><br>
|
|
|
|
|
|
|
|
|
|
You can test the notify/filelog with the trigger command: issue "trigger
|
|
|
|
|
DEVICENAME EVENT" in the telnet prompt, and check if your notify/filelog
|
|
|
|
|
works as designed. Example: trigger piri on-for-timer 60<br><br>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</ul>
|
2008-08-04 13:47:53 +00:00
|
|
|
|
2008-10-02 08:05:20 +00:00
|
|
|
<a name="faq16">
|
|
|
|
|
<b>16. Setting auto-mode from manual for the FHT won't change the desired temperature!</b>
|
|
|
|
|
<ul>
|
|
|
|
|
Thanks to Waldemar Porsche the following notify will take care of that:<br>
|
|
|
|
|
<pre>define ExtendedAutoMode notify .*mode.*auto {\
|
|
|
|
|
$r = $defs{@}{READINGS};;\
|
|
|
|
|
return if (!defined($r));;\
|
|
|
|
|
my $olddesired = $r->{"desired-temp"}{VAL};;\
|
|
|
|
|
return if (!defined($olddesired));;\
|
2008-10-11 08:04:22 +00:00
|
|
|
my @@day = ("sun", "mon", "tue", "wed", "thu", "fri", "sat");;\
|
|
|
|
|
my $now = sprintf("%%02d:%%02d", $hour, $min);;\
|
2008-10-02 08:05:20 +00:00
|
|
|
my $wd = $day[$wday];;\
|
|
|
|
|
my $desired;;\
|
|
|
|
|
if (defined($r->{"warnings"}{VAL}) && $r->{"warnings"}{VAL} eq "Window open") {\
|
|
|
|
|
$desired = $r->{"windowopen-temp"}{VAL};;\
|
|
|
|
|
} elsif (defined($r->{"$wd-from1"}{VAL}) && $r->{"$wd-from1"}{VAL} le $now && defined($r->{"$wd-to1"}{VAL}) && $r->{"$wd-to1"}{VAL} ge $now) {\
|
|
|
|
|
$desired = $r->{"day-temp"}{VAL};;\
|
|
|
|
|
} elsif (defined($r->{"$wd-from2"}{VAL}) && $r->{"$wd-from2"}{VAL} le $now && defined($r->{"$wd-to2"}{VAL}) && $r->{"$wd-to2"}{VAL} ge $now) {\
|
|
|
|
|
$desired = $r->{"day-temp"}{VAL};;\
|
|
|
|
|
} else {\
|
|
|
|
|
$desired = $r->{"night-temp"}{VAL};;\
|
|
|
|
|
}\
|
|
|
|
|
fhem ("set @ desired-temp $desired") if (defined($desired) && $desired ne $olddesired);;\
|
|
|
|
|
}
|
|
|
|
|
attr ExtendedAutoMode comment Setzt fuer den Auto mode die desired-temp in Abhaengigkeit von Temperaturprofil und Fensterkontakt
|
|
|
|
|
</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
|
2008-10-11 08:04:22 +00:00
|
|
|
<a name="faq17">
|
|
|
|
|
<b>17. I have problem receiving data, I get "Bad CRC" or "Oversized
|
|
|
|
|
message."</b>
|
|
|
|
|
<ul>
|
|
|
|
|
Some Linux distibutions have problems with the settings of the serial USB
|
|
|
|
|
lines. Sometimes the 8.th bit is stripped, sometimes software flowcontrol
|
|
|
|
|
is enabled. Fhem tries to clear the serial line, but it is not always
|
|
|
|
|
successfull. Following command fixes the problem in some cases:
|
|
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
stty < /dev/elv_fhz1300pc\
|
|
|
|
|
-parenb -parodd cs8 hupcl -cstopb -cread clocal\
|
|
|
|
|
-crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr\
|
|
|
|
|
-igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost\
|
|
|
|
|
-olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0\
|
|
|
|
|
bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl\
|
|
|
|
|
-noflsh -xcase -tostop -echoprt -echoctl -echoke
|
|
|
|
|
</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
|
2008-10-02 08:05:20 +00:00
|
|
|
|
|
|
|
|
|
2007-01-30 12:47:36 +00:00
|
|
|
</body>
|
|
|
|
|
</html>
|
