FHEM Forum

Originally posted by: <email address deleted>

Hi, hopefully somebody can help me with this:

trying to set up a M232 device connected to the internal serial port
of the NLSU. Always get read errors when using set or get.

The serial port works fine, could log on to Linux with a PC as
terminal.

Tested the M232 with self-made adapter cable and the software that
came with it at a PC, worked fine (only when booted to DOS prompt,
though)

Also tested the port with FHEM with the PC terminal. Could receive the
commands sent, but got the same read error from FHEM.

Any ideas what could be the cause for this?

Thanks

LB_ORL

I
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

                                             

Hi,

LB_ORL schrieb:
> Any ideas what could be the cause for this?
>
>  
could you please start fhem with a minimal configuration and maximum
verbosity on the NSLU and post the logs?

Regards,
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>

On 3 Nov., 16:57, "Dr. Boris Neubert" wrote:
> Hi,
>
> LB_ORL schrieb:> Any ideas what could be the cause for this?
>
> could you please start fhem with a minimal configuration and maximum
> verbosity on the NSLU and post the logs?
>
> Regards,
> Boris

Thanks for the response. Here is the my last telnet session including
the log:

www-data@fhz:/usr/local/bin$ telnet localhost 7072
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

FHZ> get m232 octet
Read error
FHZ> quit
Bye...
Connection closed by foreign host.
www-data@fhz:/usr/local/bin$ cat /tmp/fhem.log
2009.11.03 23:43:52 5: Cmd: >define m232 M232 /dev/COM1<
2009.11.03 23:43:52 5: Loading /usr/local/lib/FHEM/80_M232.pm, order
80
2009.11.03 23:43:52 3: M232 opening device /dev/COM1
2009.11.03 23:43:53 3: M232 opened device /dev/COM1
2009.11.03 23:43:53 0: Server started (version =VERS= from =DATE=
($Id:
fhem.pl,
v 1.80 2009/09/11 07:34:12 rudolfkoenig Exp $), pid 13533)
2009.11.03 23:44:04 4: Connection accepted from 127.0.0.1:3661
2009.11.03 23:44:17 4: Connection accepted from 127.0.0.1:3662
2009.11.03 23:44:17 5: Cmd: >xmllist<
2009.11.03 23:44:17 5: Cmd: ><
2009.11.03 23:44:18 5: Cmd: >quit<
2009.11.03 23:44:18 4: Connection closed for 127.0.0.1:3662
2009.11.03 23:45:20 5: Cmd: >set m232 io1 1<
2009.11.03 23:45:20 4: M232: Sending D11
2009.11.03 23:45:22 4: M232: ?
2009.11.03 23:45:26 5: Cmd: >quit<
2009.11.03 23:45:26 4: Connection closed for 127.0.0.1:3661
2009.11.03 23:46:28 4: Connection accepted from 127.0.0.1:3985
2009.11.03 23:46:28 5: Cmd: >xmllist<
2009.11.03 23:46:28 5: Cmd: ><
2009.11.03 23:46:28 5: Cmd: >quit<
2009.11.03 23:46:28 4: Connection closed for 127.0.0.1:3985
2009.11.03 23:49:33 4: Connection accepted from 127.0.0.1:3986
2009.11.03 23:49:33 5: Cmd: >xmllist<
2009.11.03 23:49:33 5: Cmd: ><
2009.11.03 23:49:33 5: Cmd: >quit<
2009.11.03 23:49:33 4: Connection closed for 127.0.0.1:3986
2009.11.03 23:52:39 4: Connection accepted from 127.0.0.1:4087
2009.11.03 23:52:39 5: Cmd: >xmllist<
2009.11.03 23:52:39 5: Cmd: ><
2009.11.03 23:52:39 5: Cmd: >quit<
2009.11.03 23:52:39 4: Connection closed for 127.0.0.1:4087
2009.11.03 23:53:08 4: Connection accepted from 127.0.0.1:4088
2009.11.03 23:53:54 5: Cmd: >set m232<
2009.11.03 23:54:00 5: Cmd: >get m232 octet<
2009.11.03 23:54:00 4: M232: Sending w
2009.11.03 23:54:02 4: M232: ?
2009.11.03 23:54:06 5: Cmd: >quit<
2009.11.03 23:54:06 4: Connection closed for 127.0.0.1:4088
2009.11.03 23:55:44 4: Connection accepted from 127.0.0.1:4089
2009.11.03 23:55:44 5: Cmd: >xmllist<
2009.11.03 23:55:44 5: Cmd: ><
2009.11.03 23:55:44 5: Cmd: >quit<
2009.11.03 23:55:44 4: Connection closed for 127.0.0.1:4089
2009.11.03 23:58:22 4: Connection accepted from 127.0.0.1:4742
2009.11.03 23:58:29 5: Cmd: >get m232 octet<
2009.11.03 23:58:29 4: M232: Sending w
2009.11.03 23:58:31 4: M232: ?
2009.11.03 23:58:35 5: Cmd: >quit<
2009.11.03 23:58:35 4: Connection closed for 127.0.0.1:4742
www-data@fhz:/usr/local/bin$

Regards,

LB_ORL

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

                                             

Hi,

LB_ORL schrieb:
> 2009.11.03 23:45:20 5: Cmd: >set m232 io1 1<
> 2009.11.03 23:45:20 4: M232: Sending D11
> 2009.11.03 23:45:22 4: M232: ?
>  
this occurs at FHEM/80_M232.pm in sub M232GetData(). The return value is
the default value set in line 289. I cannot see from the code how this
might happen. Could you please add additional Log commands in the
mentioned module to see where and why the subroutine bails out?

Regards,
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>

Hi,

yesterday evening, FHEM (4.7) lost my CUN:

[...]
2009.11.03 19:36:06 2: FHZ get FHZ1 serial
[...]
2009.11.03 19:36:06 3: FHZ1 serial => ********
2009.11.03 19:36:06 5: redefine at command at_get_serial as +*00:05 { \
2009.11.03 19:36:06 5: exec at command at_get_CUN_version
2009.11.03 19:36:06 5: Cmd: >{ \
2009.11.03 19:36:06 5: Cmd: >get CUL2 version<
2009.11.03 19:36:06 3: CUL2 version => No answer
2009.11.03 19:36:06 5: redefine at command at_get_CUN_version as +*00:01 { \
2009.11.03 19:38:03 5: Cmd: >define CUL2 CUL 000.00.000.00:2323 3e06<
2009.11.03 19:38:03 5: Loading /usr/local/lib/FHEM/00_CUL.pm, order 00
2009.11.03 19:38:03 3: CUL opening CUL device 000.00.000.00:2323
2009.11.03 19:38:04 3: CUL opened 000.00.000.00:2323 for CUL2
2009.11.03 19:38:07 1: Cannot init 000.00.000.00:2323, ignoring it
2009.11.03 19:38:07 3: CUL2: Timeout reading answer for get Version
2009.11.03 19:38:07 5: Cmd: >attr CUL2 loglevel 3<
2009.11.03 19:38:07 3: Please define CUL2 first
2009.11.03 19:38:07 5: Cmd: >attr CUL2 model CUL<
2009.11.03 19:38:07 3: Please define CUL2 first
2009.11.03 19:38:07 3: CUL opening CUL device /dev/busware_cul
2009.11.03 19:38:07 3: CUL opened /dev/busware_cul for CUL1
2009.11.03 19:38:07 5: CUL/RAW: K1133524707
2009.11.03 19:38:07 5: CUL/RAW: V 1.30 CUL868
2009.11.03 19:38:07 5: CUL/RAW: 3E06
2009.11.03 19:38:07 5: GOT CUL fhtid: 3E06
2009.11.03 19:38:07 5: Cmd: >attr CUL1 loglevel 3<
2009.11.03 19:38:07 5: Cmd: >attr CUL1 model CUL<
[...]

I'm not sure why there was a problem talking to the CUN nor why 00_CUL.pm
was re-read. What can be done to have FHEM handle temporary outages more
gracefully? Usually FHEM copes well with CUN (or a socat-connected CUL)
not being there, the "get CUL2 version" restarts communication with CUN after
e. g. a reboot of CUN on a regular basis.

But this time, CUN did now reboot:

FHZ> get CUL2 raw t
CUL2 raw => 031BAAFE

=> 0x31B8264/0x7D/0x1518 ~ 4.828 days of CUN operation, if I'm not mistaken

Any tips on how to prevent this from happening again are greatly appreciated,
         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
-~----------~----~----~----~------~----~------~--~-

                                                   

> 2009.11.03 19:36:06 3: FHZ1 serial => ********
As I wrote it in different postings: Using an FHZ, a CUL with fhtid != 0000 and
FHT's will cause communication problems with the FHT's


> 2009.11.03 19:38:03 5: Cmd: >define CUL2 CUL 000.00.000.00:2323 3e06<
Is this really 000.00.000.00 ?


> 2009.11.03 19:38:03 5: Loading /usr/local/lib/FHEM/00_CUL.pm, order 00
This is a bug. To identify the problem I need your whole logfile, your
configuration file and the listing of the FHEM directory.


> FHZ> get CUL2 raw t
> CUL2 raw => 031BAAFE
??? The log above told me that you have no connection to CUL2.

--~--~---------~--~----~------------~-------~--~----~
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:
>> 2009.11.03 19:36:06 3: FHZ1 serial => ********
> As I wrote it in different postings: Using an FHZ, a CUL with fhtid != 0000 and
> FHT's will cause communication problems with the FHT's

FHZ can't reach reliably the FHT in question, so there's no way around
this setup for now. Using different fhtids for FHZ and CUL(s) is ok?

>> 2009.11.03 19:38:03 5: Cmd: >define CUL2 CUL 000.00.000.00:2323 3e06<
> Is this really 000.00.000.00 ?

Of course not. But it's a routed address, reachable from the Internet,
therefore I obfuscated it for posting this publicly.

>> 2009.11.03 19:38:03 5: Loading /usr/local/lib/FHEM/00_CUL.pm, order 00
> This is a bug. To identify the problem I need your whole logfile, your
> configuration file and the listing of the FHEM directory.

Ok, will send it directly.


>> FHZ> get CUL2 raw t
>> CUL2 raw => 031BAAFE
> ??? The log above told me that you have no connection to CUL2.

Sorry, I thought that would be obvious: after noticing the loss of CUL2
(responsible for 1 EM, 1 FHT, 2 HMS, 1 WS) this morning, I stopped and
restarted FHEM, then I checked CUN's uptime. While I do have an ps|grep-
based automated FHEM restart in place, I'm at loss right now how to cope
with a running FHEM process that's lacking sensors. As FHEM is not pro-
ductive currently (beyond T/H-measurement and timing the lights of the
terrarium), that's no big issue, yet.

Regards,
         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
-~----------~----~----~----~------~----~------~--~-

                                                   

> Using different fhtids for FHZ and CUL(s) is ok?

I put it the other way round: Using the same fhtid for the FHZ and the CUL is
even worse :)

--~--~---------~--~----~------------~-------~--~----~
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>

Just to be sure I understood the issue correctly, is the following true?

- When an FHT-80b sends out messages like measured-temp, it won't send
the code of the CUx/FHZ it wants to send the message to, but only its
own code to mark the origin of the message.
- These messages are bidirectional, there are several telegrams going
to and fro between the CUx/FHZ and FHT-80b until the message is
"through".
- The CUx devices will send answers to every telegram they receive,
regardless of whether the sending FHT-80b is paired with them or with
other CUx/FHZ devices.
- If the FHT-80b is already paired with another CUx/FHZ, it will
ignore the answers from the CUx as they don't contain the correct
housecode.
- If the radio reception is not good between the non-paired CUx and
the FHT-80b, the CUx might miss some of the telegrams sent to the
actually paired CUx/FHZ device.
- It will then conclude that its last telegram has not been received
and try forever to send it out. As the adressed FHT-80b is paired with
another CUx/FHZ, it will ignore these telegrams.

If this is true, more questions:

1. Will the CUx's connection to other FHT80bs be disturbed by that? In
other words, will it try to complete the dialog with the "wrong"
FHT-80b before it sends anything to other FHT-80bs?
2. Will the FHT buffer overflow at some point or does the CUx detect
that the FHT-80b in question is already sending another message, so
its previous answer can be taken out of the buffer? (Is taking sth out
of the buffer possible at all, as it is probably just a char buffer,
and it is unknown which message is at which offset?)
3. How do FHZ devices handle this?

Thank you,

Christian

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

                                                   

> - When an FHT-80b sends out messages like measured-temp, it won't send
> the code of the CUx/FHZ it wants to send the message to, but only its
> own code to mark the origin of the message.

The first (FHT_START_XMIT) telegram contains the one byte code of the
associated FHZ, the rest not. All telegrams contain the FHT id.

If the CUL receives an FHT telegram with the code of a foreign FHZ, then it
won't reply to the rest of the telegrams (in this slot). But if it misses
this message, then it automatically ack's the rest. The other way round (ack
only if I got my own FHZ code) would be better.


> - It will then conclude that its last telegram has not been received
> and try forever to send it out. As the adressed FHT-80b is paired with
> another CUx/FHZ, it will ignore these telegrams.

For the CUL forever == 2 times. The FHT won't really know who is the sender
(that is, for message number 2+), but both CUL's/FHZ's will reply at the same
time, disturbing each other.  The FHT will stop and start sending the data in
the next timeslot, 115+x seconds later.


> 1. Will the CUx's connection to other FHT80bs be disturbed by that? In
> other words, will it try to complete the dialog with the "wrong"
> FHT-80b before it sends anything to other FHT-80bs?

No, as a telegram is repeated only twice


> 2. Will the FHT buffer overflow at some point or does the CUx detect
> that the FHT-80b in question is already sending another message, so
> its previous answer can be taken out of the buffer? (Is taking sth out
> of the buffer possible at all, as it is probably just a char buffer,
> and it is unknown which message is at which offset?)

The CUL removes an FHT telegram from its buffer after it received the last ack
from the FHT for the whole message. If the FHT is not associated with the CUL,
it won't even reply to the initial start telegram.
-> Do not send commands to FHT's associated to a different FHZ/CUL, as only a
   reset (or T01HHHH) will remove these commands from the CUL buffer.


> 3. How do FHZ devices handle this?

Show me the source and I will tell you :)


--~--~---------~--~----~------------~-------~--~----~
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,

ich habe einen FHT80TF (aus einem FHT80B-Set) aktiviert, ich schätze mal,
folgendes ist die Willkommensnachricht?

2009.11.05 22:44:20 5: CUL/RAW: /T965AB00CE1

2009.11.05 22:44:20 3: CUL1: T965AB00C -89.5
2009.11.05 22:44:20 3: CUL: unknown message T965AB00C
2009.11.05 22:44:20 5: CUL/RAW: /T965AB00C4C

2009.11.05 22:44:20 3: CUL2: T965AB00C -36
2009.11.05 22:44:20 3: CUL: unknown message T965AB00C

Wenn ich den Magneten vom Reed-Kontakt weg- und wieder hin bewege, macht
die LED des FHT80TF etwas ("auf": kurzes Aufleuchten, "zu": langes Auf-
leuchten), CUL (oder FHZ) empfangen dann allerdings offensichtlich nichts.
Dafür tauchen nun diese Einträge immer wieder auf:

2009.11.05 23:04:41 5: CUL/RAW: /T965AB001E1

2009.11.05 23:04:41 3: CUL1: T965AB001 -89.5
2009.11.05 23:04:41 3: CUL: unknown message T965AB001
2009.11.05 23:04:42 5: CUL/RAW: /T965AB00149

2009.11.05 23:04:42 3: CUL2: T965AB001 -37.5
2009.11.05 23:04:42 3: CUL: unknown message T965AB001
2009.11.05 23:04:42 5: CUL/RAW: /T965AB081E1

2009.11.05 23:04:42 3: CUL1: T965AB081 -89.5
2009.11.05 23:04:42 3: CUL: unknown message T965AB081
2009.11.05 23:04:42 5: CUL/RAW: /T965AB08149

2009.11.05 23:04:42 3: CUL2: T965AB081 -37.5
2009.11.05 23:04:42 3: CUL: unknown message T965AB081

FHEM kennt derzeit das "FHT80TF-Protokoll" nicht, oder? Schade, ich würde
gerne die Türen-/Fensterkontakte auch außerhalb der FHT-internen Steuerung
nutzen. Gibt's Alternativen? "FS20 TFK" scheint die "Standalone-Variante"
zu sein, hat die einen anderen, FHEM bekannten, Code?

MfG,
         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,

kannst Du bitte folgendes Pruefen und uns mitteilen:
- wie oft/haeufig kommt T965AB00C
- wann genau kommt      T965AB001
- wann genau kommt      T965AB081

Mit diesen Infos kann man ein Modul bauen (siehe 09_BS.pm).

Meines Wissens nach meldet der FHZ den 80TF nicht direkt, diese Daten kommen
ueber den FHT80b (warnings: Window open).

Gruss,
  Rudi

--~--~---------~--~----~------------~-------~--~----~
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>

On 4 Nov., 19:53, "Dr. Boris Neubert" wrote:
> Hi,
>
> LB_ORL schrieb:> 2009.11.03 23:45:20 5: Cmd: >set m232 io1 1<
> > 2009.11.03 23:45:20 4: M232: Sending D11
> > 2009.11.03 23:45:22 4: M232: ?
>
> this occurs at FHEM/80_M232.pm in sub M232GetData(). The return value is
> the default value set in line 289. I cannot see from the code how this
> might happen. Could you please add additional Log commands in the
> mentioned module to see where and why the subroutine bails out?
>
> Regards,
> Boris

OK, I am still struggling with Perl, but finally I succeeded in adding
some lines:

 for(;;) {
    if ($^O eq 'MSWin32') {
      $nfound=M232_Ready($hash,undef);
    }else{
      my ($rout, $rin) = ('', '');
my $FN = $serport->FILENO;
      vec($rin, $serport->FILENO, 1) = 1;
my $RI = unpack("b*",$rin);
    $nfound = select($rin, undef, undef, 1.0); # 3 seconds timeout
Log 4, "nfound:  $nfound FN: $FN rin: $RI";
      if($nfound < 0) {
        next if ($! == EAGAIN() || $! == EINTR() || $! == 0);
        $rm="M232:Select error $nfound / $!";
        last;
      }
    }

      last if($nfound == 0);



Now the log looks like this:

2009.11.06 01:14:42 5: Cmd: >get m232 octet<
2009.11.06 01:14:42 4: M232: Sending w
2009.11.06 01:14:53 4: nfound:  0 FN: 6 rin: 00000010
2009.11.06 01:14:53 4: M232: ?
2009.11.06 01:15:08 5: Cmd: >quit<
2009.11.06 01:15:08 4: Connection closed for 127.0.0.1:3343


I appreciate your helping me with this.

Regards,

LB_ORL

--~--~---------~--~----~------------~-------~--~----~
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>

Thanks for the clarifications.

2009/11/5 Rudolf Koenig :
> If the CUL receives an FHT telegram with the code of a foreign FHZ, then it
> won't reply to the rest of the telegrams (in this slot). But if it misses
> this message, then it automatically ack's the rest. The other way round (ack
> only if I got my own FHZ code) would be better.

>> 3. How do FHZ devices handle this?
>
> Show me the source and I will tell you :)

:-) I meant the behaviour that can be observed, i.e. when do FHZs send
telegrams and when not.

Most problematic cases I thought were there in fact are not, so it's
all in all not as big a problem as I thought, anyway. Only the case
above remains, so: Do FHZs ack messages where they missed they
start-xmit telegram? (I can't try to find that out myself as I don't
own one.)

Best regards,

Christian

--~--~---------~--~----~------------~-------~--~----~
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,

On Nov 5, 11:21 pm, Kai 'wusel' Siering
wrote:
> Wenn ich den Magneten vom Reed-Kontakt weg- und wieder hin bewege, macht
> die LED des FHT80TF etwas ("auf": kurzes Aufleuchten, "zu": langes Auf-
> leuchten),

Meine älteren FHT80TFs blinken 3 mal kurz beim Schließen (Reedkontakt
geschlossen) und einmal lang beim Öffnen.
Hast Du das neuere Gerät im kleinen Gehäuse?

> FHEM kennt derzeit das "FHT80TF-Protokoll" nicht, oder? Schade, ich würde
> gerne die Türen-/Fensterkontakte auch außerhalb der FHT-internen Steuerung
> nutzen. Gibt's Alternativen? "FS20 TFK" scheint die "Standalone-Variante"
> zu sein, hat die einen anderen, FHEM bekannten, Code?

IMHO macht das FS20TFK einfache FS20-Schaltbefehle (ich habe mal
"versehentlich" einen gekauft und hier rumliegen).
Damit kommt FHEM bekannterweise gut klar.


Gruß,
Jürgen
--~--~---------~--~----~------------~-------~--~----~
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,

habe auch diverse FHT80TF...auch die im kleinen Gehäuse...
Die melden sich regelmäßig:

06:44:01 0: MyCUL: T4BE79902 -92.5
06:44:01 0: MyCUL: T4BE79982 -92.5
06:48:15 0: MyCUL: T4BE79902 -92.5
06:48:16 0: MyCUL: T4BE79982 -92.5
06:52:30 0: MyCUL: T4BE79982 -93.5
07:00:58 0: MyCUL: T4BE79982 -93
07:05:11 0: MyCUL: T4BE79902 -92
07:05:12 0: MyCUL: T4BE79982 -92
07:09:25 0: MyCUL: T4BE79902 -91.5
07:09:26 0: MyCUL: T4BE79982 -92.5
07:15:46 0: MyCUL: T4BE79901 -89
07:15:47 0: MyCUL: T4BE79981 -88.5
07:16:50 0: MyCUL: T4BE79901 -89
07:16:50 0: MyCUL: T4BE79981 -88.5
07:21:04 0: MyCUL: T4BE79901 -89.5
07:21:04 0: MyCUL: T4BE79981 -89
07:25:18 0: MyCUL: T4BE79901 -88.5
07:25:18 0: MyCUL: T4BE79981 -88
07:29:32 0: MyCUL: T4BE79901 -89
07:29:32 0: MyCUL: T4BE79981 -88.5
07:33:46 0: MyCUL: T4BE79901 -89
07:33:46 0: MyCUL: T4BE79981 -88.5
07:38:00 0: MyCUL: T4BE79901 -90
07:38:00 0: MyCUL: T4BE79981 -89.5
07:42:14 0: MyCUL: T4BE79981 -88
07:46:28 0: MyCUL: T4BE79901 -89
07:50:42 0: MyCUL: T4BE79901 -90

Was ich bis jetzt feststellen konne:
-  Die senden immer zwei Meldungen T4BE79981 bzw T4BE79901
-  Device-Code: 4BE799 ?? Oder ist das 4BE7 und die 99 ??
- "Fenster zu" T4BE79902 und T4BE79982..Endung 02 bzw. 82
- "Fenster auf" T4BE79901 T4BE79981..Endung 01 bzw. 81

Gruß,
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
-~----------~----~----~----~------~----~------~--~-

Originally posted by: <email address deleted>

Moin,

vorweg das Management Summary ;)

Format ist "TCCCCCCXX", mit CCCCCC als der zufällige Gerätecode
(16 Mio. unterschiedlicher Werte lt. Handbuch FHT80TF), XX als
Statuswert des Sensors:

XX   Bedeutung
----------------------------------------------------------------
02   "Fenster geschlossen", initiale Sendung
82   "Fenster geschlossen", zweites Telegramm
01   "Fenster offen", initiale Sendung
81   "Fenster offen", zweites Telegramm
0C   "Bin da, wer noch?" - 1 Minute im Sekundentakt: "Synchronisierung"
??   "Batterien leer, bitte wechseln" (noch rauszufinden)

Normaler "Meldeabstand" scheint ~255 Sekunden zu sein mit "0" an
vorletzter Position, Retransmission mit "8" dort ~1 Sekunde später.

Comments?



Details folgen:

Axel wrote:
> Hallo Zusammen,
>
> habe auch diverse FHT80TF...auch die im kleinen Gehäuse...
> Die melden sich regelmäßig:
>
> 06:44:01 0: MyCUL: T4BE79902 -92.5
> 06:44:01 0: MyCUL: T4BE79982 -92.5
[...]
> 07:38:00 0: MyCUL: T4BE79901 -90
> 07:38:00 0: MyCUL: T4BE79981 -89.5
> 07:42:14 0: MyCUL: T4BE79981 -88
> 07:46:28 0: MyCUL: T4BE79901 -89
> 07:50:42 0: MyCUL: T4BE79901 -90
>
> Was ich bis jetzt feststellen konne:
> -  Die senden immer zwei Meldungen T4BE79981 bzw T4BE79901
> -  Device-Code: 4BE799 ?? Oder ist das 4BE7 und die 99 ??
> - "Fenster zu" T4BE79902 und T4BE79982..Endung 02 bzw. 82
> - "Fenster auf" T4BE79901 T4BE79981..Endung 01 bzw. 81


Druck auf TF-Taster zur Anmeldung an FHT80B-II:

2009.11.06 12:05:30 5: CUL/RAW: /T965AB00255

2009.11.06 12:05:30 3: CUL2: T965AB002 -31.5
2009.11.06 12:05:30 3: CUL: unknown message T965AB002
2009.11.06 12:05:30 5: CUL/RAW: /T965AB002E6

2009.11.06 12:05:30 3: CUL1: T965AB002 -87
2009.11.06 12:05:30 3: CUL: unknown message T965AB002
2009.11.06 12:05:31 5: CUL/RAW: /T965AB08256

2009.11.06 12:05:31 3: CUL2: T965AB082 -31
2009.11.06 12:05:31 3: CUL: unknown message T965AB082

cam-serv2:~# grep T965A /var/log/fhem/fhem-2009-11.log | grep CUL1 | cut -d " " -f 5 | sort | uniq -c
      19 T965AB001
     166 T965AB002
     103 T965AB00C
       1 T965AB00F
      23 T965AB081
     168 T965AB082

cam-serv2:~# grep T965A /var/log/fhem/fhem-2009-11.log | grep CUL1 | gawk  'BEGIN{hlast=0; minlast=0; seclast=0; num=0;} /2009.11.06/ {nf=split($2, a, ":"); if(nf==3) { if(num>0) {v1=hlast*3600+minlast*60+seclast; v2=a[1]*3600+a[2]*60+a[3]; printf("delta
sec: %4d\n", v2-v1) }; num++; hlast=a[1]; minlast=a[2]; seclast=a[3]; } }' | sort | uniq -c | sort -n
       1 delta sec:  127
       1 delta sec:  191
       1 delta sec:  384
       1 delta sec:   64
       2 delta sec:  511
       3 delta sec:  257
       4 delta sec:   63
      75 delta sec:  255
      82 delta sec:    1
      83 delta sec:    0
      91 delta sec:  256

Mit den Werten von Axel:

       1 delta sec:  380
       1 delta sec:  508
       1 delta sec:   63
       2 delta sec:  253
       4 delta sec:    1
       7 delta sec:    0
      10 delta sec:  254

Auch sonst bei mir ähnliche Werte wie bei Axel:

cam-serv2:~# grep T965A /var/log/fhem/fhem-2009-11.log | grep CUL2 | grep 2009.11.06 | tail -20
2009.11.06 12:26:51 3: CUL2: T965AB002 -38
2009.11.06 12:26:51 3: CUL2: T965AB082 -38.5
2009.11.06 12:31:06 3: CUL2: T965AB002 -41
2009.11.06 12:31:07 3: CUL2: T965AB082 -44
2009.11.06 12:35:23 3: CUL2: T965AB082 -36
2009.11.06 12:39:39 3: CUL2: T965AB002 -39
2009.11.06 12:43:54 3: CUL2: T965AB002 -39
2009.11.06 12:43:55 3: CUL2: T965AB082 -39.5
2009.11.06 12:48:10 3: CUL2: T965AB002 -39
2009.11.06 12:48:11 3: CUL2: T965AB082 -39.5
2009.11.06 12:52:27 3: CUL2: T965AB002 -39
2009.11.06 12:52:27 3: CUL2: T965AB082 -39   /* Hiernach "Fenster auf" proviziert */
2009.11.06 12:56:43 3: CUL2: T965AB002 -37
2009.11.06 12:56:43 3: CUL2: T965AB082 -37.5
2009.11.06 12:57:46 3: CUL2: T965AB001 -38.5
2009.11.06 12:57:47 3: CUL2: T965AB081 -39
2009.11.06 12:58:50 3: CUL2: T965AB001 -38.5
2009.11.06 12:58:51 3: CUL2: T965AB081 -39.5
2009.11.06 13:03:07 3: CUL2: T965AB001 -37.5
2009.11.06 13:03:07 3: CUL2: T965AB081 -37

=> 02/82 "zu", 01/81 "auf" scheint zu stimmen: um 13:08:35 wieder "zu":

2009.11.06 13:07:23 3: CUL2: T965AB001 -38
2009.11.06 13:07:23 3: CUL2: T965AB081 -38
2009.11.06 13:09:30 3: CUL2: T965AB002 -41
2009.11.06 13:10:34 3: CUL2: T965AB002 -38
2009.11.06 13:10:35 3: CUL2: T965AB082 -38
2009.11.06 13:14:51 3: CUL2: T965AB002 -43.5
2009.11.06 13:14:51 3: CUL2: T965AB082 -44

Normaler "Meldeabstand" scheint ~255 Sekunden zu sein mit "0" an
vorletzter Position, Retransmission mit "8" dort ~1 Sekunde später.

Die letzte Stelle scheint den Status anzugeben, die ersten sechs(?)
dürften der Gerätecode sein (16 Mio. Zufallswerte lt. Handbuch).
FHT80TF sendet auch Batteriestatus mit ("ok" oder "wechseln", abfrag-
bar am FHT80B) ... Als ich grade ältere, ausgemustert weil vermeint-
lich recht leere, Batterien einsetzte, ging der Punk ab:

cam-serv2:~# grep T965A /var/log/fhem/fhem-2009-11.log | grep "06 13:" | grep CUL2: | more
[...]
2009.11.06 13:14:51 3: CUL2: T965AB002 -43.5
2009.11.06 13:14:51 3: CUL2: T965AB082 -44
2009.11.06 13:16:17 3: CUL2: T965AB00C -41
2009.11.06 13:16:18 3: CUL2: T965AB00C -40
2009.11.06 13:16:19 3: CUL2: T965AB00C -40.5
2009.11.06 13:16:21 3: CUL2: T965AB00C -39.5
[... im Sekundentakt - lt. Handbuch "ca. 1 Min. Synchronisierungsphase"]
2009.11.06 13:17:16 3: CUL2: T965AB00C -38.5
2009.11.06 13:17:18 3: CUL2: T965AB00C -38.5
2009.11.06 13:17:19 3: CUL2: T965AB00C -38.5
2009.11.06 13:20:38 3: CUL2: T965AB002 -41.5
2009.11.06 13:20:38 3: CUL2: T965AB082 -40
2009.11.06 13:21:42 3: CUL2: T965AB001 -42
2009.11.06 13:21:42 3: CUL2: T965AB081 -41
2009.11.06 13:22:46 3: CUL2: T965AB002 -39
2009.11.06 13:22:46 3: CUL2: T965AB082 -38.5

Der FHT80B zeigte beim Status des Fensterkontaktes allerdings *nicht*
"Batterie wechseln" an, sondern weiterhin aktuell den Status des Kon-
taktes ("AUF" oder ""). Vielleicht hat jemand mal definitiv fast leere
Batterien und kann damit auch noch den Code für "Batterie leer" ent-
schlüsseln?

HTH,
         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>

Moin,

Juergen Lennefer wrote:

>> Wenn ich den Magneten vom Reed-Kontakt weg- und wieder hin bewege, macht
>> die LED des FHT80TF etwas ("auf": kurzes Aufleuchten, "zu": langes Auf-
>> leuchten),
>
> Meine älteren FHT80TFs blinken 3 mal kurz beim Schließen (Reedkontakt
> geschlossen) und einmal lang beim Öffnen.
> Hast Du das neuere Gerät im kleinen Gehäuse?

Nein, ich meine, daß sind auch die "alten", recht großen. Und Du hast
recht, "auf" ist 1x laaaang, "zu" ist 3x kurz blinken. Sorry, da habe
ich mich gestern verschrieben.

>> nutzen. Gibt's Alternativen? "FS20 TFK" scheint die "Standalone-Variante"
>> zu sein, hat die einen anderen, FHEM bekannten, Code?
>
> IMHO macht das FS20TFK einfache FS20-Schaltbefehle (ich habe mal
> "versehentlich" einen gekauft und hier rumliegen).
> Damit kommt FHEM bekannterweise gut klar.

Nachdem das Protokoll und die Funktionsweise des FHT80TF ja doch etwas
anders zu sein scheint als beim FS20-Standard (s. andere Mails dazu),
was macht der FS20TFK? Da konfiguriert man dann den FS20-Schaltercode und
der TFK sendet entsprechend bei "auf" und "zu" sofort den entsprechende
Schaltcode? Hmm, wenn man das FHT80TF-Protokoll entschlüsselt hat, könnte
FHEM mit CUL basierend auf FS20TFK einen FHT80TF emulieren, man bräuchte
dann nicht zwei Kontakte, wenn man schnelle Reaktion und Integration in
FHT-Steuerung möchte. (Oder man macht's nur über FHEM+CUL, läßt den FHT80B
ganz raus. Aber das wäre bei Absturz des FHEM-Systems doof.)

34,95 für FS20TFK
19,95 für FHT80TF-2 ("Lieferbar in 7 Woche(n)")
14,95 für eQ-3 FHT 80 TF

Hmm. Ich möchte eigentlich gerne FS20TFK-Funktion (sofortige Meldung) zum
FHT80TF-Preis, grummel ;)
         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>

Hmm.

> Format ist "TCCCCCCXX", mit CCCCCC als der zufällige Gerätecode
> (16 Mio. unterschiedlicher Werte lt. Handbuch FHT80TF), XX als
> Statuswert des Sensors:

==> 09_CUL_FHTTK.pm (kopiert von 09_BS.pm, adaptiert auf Basis 14_CUL_WS.pm)
erstellt, darin u. a.:

[...]
sub
CUL_FHTTK_Initialize($)
{
   my ($hash) = @_;

   $hash->{Match}     = "^T........";
   $hash->{DefFn}     = "CUL_FHTTK_Define";
   $hash->{UndefFn}   = "CUL_FHTTK_Undef";
   $hash->{ParseFn}   = "CUL_FHTTK_Parse";
   $hash->{AttrList}  = "IODev do_not_notify:1,0 showtime:0,1 dummy:1,0 model:FHTTK loglevel:0,1,2,3,4,5,6";

}
[...]


Änderung in 00_CUL.pm:

--- 00_CUL.pm.org       2009-10-24 10:23:30.000000000 +0200
+++ 00_CUL.pm   2009-11-06 16:15:29.000000000 +0100
@@ -53,7 +53,7 @@
  # Provider
    $hash->{ReadFn}  = "CUL_Read";
    $hash->{WriteFn} = "CUL_Write";
-  $hash->{Clients} = ":FS20:FHT:KS300:CUL_EM:CUL_WS:USF1000:HMS:";
+  $hash->{Clients} = ":FS20:FHT:KS300:CUL_EM:CUL_WS:USF1000:HMS:CUL_FHTTK:";
    my %mc = (
      "1:USF1000" => "^81..(04|0c)..0101a001a5ceaa00....",
      "2:FS20"    => "^81..(04|0c)..0101a001",
@@ -62,6 +62,7 @@
      "5:CUL_WS"  => "^K.....",
      "6:CUL_EM"  => "^E0.................\$",
      "7:HMS"     => "^810e04....(1|5|9).a001",
+    "8:CUL_FHTTK"  => "^T........",
    );
    $hash->{MatchList} = \%mc;
    $hash->{ReadyFn} = "CUL_Ready";


Beim Neustart wird das auch ohne Meldungen akzeptiert:

FHZ> list
[...]
CUL_FHTTK:
   TK_TEST              (???)
[...]
FHZ> list TK_TEST
Internals:
    CODE       123456
    DEF        123456
    IODev      CUL2
    NAME       TK_TEST
    NR         37
    SENSOR     123456
    STATE      ???
    TYPE       CUL_FHTTK
Attributes:
    IODev      CUL2
FHZ>

Aber benutzt wird das Modul offensichtlich nicht -- was mache ich falsch?!

2009.11.06 16:33:52 5: CUL/RAW: /T965AB002E9

2009.11.06 16:33:52 3: CUL1: T965AB002 -85.5
2009.11.06 16:33:52 3: CUL: unknown message T965AB002
2009.11.06 16:33:52 5: CUL/RAW: /T965AB00247

2009.11.06 16:33:52 3: CUL2: T965AB002 -38.5
2009.11.06 16:33:52 3: CUL: unknown message T965AB002
2009.11.06 16:33:53 5: CUL/RAW: /T965AB082E9

2009.11.06 16:33:53 3: CUL1: T965AB082 -85.5
2009.11.06 16:33:53 3: CUL: unknown message T965AB082
2009.11.06 16:33:53 5: CUL/RAW: /T965AB08247

2009.11.06 16:33:53 3: CUL2: T965AB082 -38.5
2009.11.06 16:33:53 3: CUL: unknown message T965AB082

Offensichtlich matcht da was nicht. Eigentlich sollte da aber zumindest
ein Logeintrag erscheinen:

[...]
sub
CUL_FHTTK_Parse($$)
{
   my ($hash, $msg) = @_;

   my $sensor= substr($msg, 1, 6);
   my $state = substr($msg, 7, 2);

   my $def= $defptr{$sensor};
   if(!defined($def)) {
     Log 3, sprintf("FHTTK Unknown device %s, please define it", $sensor);
     return "UNDEFINED FHTTK";
   }

   # if it's not our device
   if($def->{IODev} && $def->{IODev}{NAME} ne $hash->{NAME}) {
     Log 3, sprintf("skipping device %s on this receiver", $sensor);
     return "";
   }

   # More to be done later.

   return "";
}
[...]

Any ideas?
         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>

Kai 'wusel' Siering wrote:

[...]
> Any ideas?
>          kai

Yepp: use the source, Luke!

Möchte man mit CUL spielen, muß man das Nachrichten-Format auch noch in
00_CUL.pm, CUL_Read() verewigen:


@@ -713,12 +714,15 @@
                          $len/2+7, substr($dmsg,1,6), substr($dmsg,7));
        $dmsg = lc($dmsg);

-    } elsif($fn eq "T" && $len >= 11) {              # Reformat for 11_FHT.pm
-
-      $dmsg = sprintf("81%02x04xx0909a001%s00%s",
+    } elsif($fn eq "T") {
+       if ($len >= 11) {                            # Reformat for 11_FHT.pm
+           $dmsg = sprintf("81%02x04xx0909a001%s00%s",
                          $len/2+7, substr($dmsg,1,6), substr($dmsg,7));
-      $dmsg = lc($dmsg);
-
+           $dmsg = lc($dmsg);
+       } else {
+           Log GetLogLevel($name,2), "CUL: falling thru on $dmsg";
+           ;                                        # => 09_CUL_FHTTK.pm
+       }
      } elsif($fn eq "H" && $len >= 13) {              # Reformat for 12_HMS.pm

        my $type = hex(substr($dmsg,6,1));


DANN kommt endlich die ersehnte Meldung "Unknown CUL_FHTTK device ..." ;)

2009.11.06 19:37:20 5: CUL/RAW: /T965AB001E4

2009.11.06 19:37:20 3: CUL1: T965AB001 -88
2009.11.06 19:37:20 3: CUL: falling thru on T965AB001
2009.11.06 19:37:20 5: CUL1 dispatch T965AB001
2009.11.06 19:37:20 3: CUL1: Unknown CUL_FHTTK device detected, define one to get detailed information.
2009.11.06 19:37:20 5: CUL/RAW: /T965AB00157

2009.11.06 19:37:20 3: CUL2: T965AB001 -30.5
2009.11.06 19:37:20 3: CUL: falling thru on T965AB001
2009.11.06 19:37:20 5: CUL2 dispatch T965AB001
2009.11.06 19:37:20 3: CUL2: Unknown CUL_FHTTK device detected, define one to get detailed information.
2009.11.06 19:37:21 5: CUL/RAW: /T965AB081E5

2009.11.06 19:37:21 3: CUL1: T965AB081 -87.5
2009.11.06 19:37:21 3: CUL: falling thru on T965AB081
2009.11.06 19:37:21 5: CUL1 dispatch T965AB081
2009.11.06 19:37:21 3: CUL1: Unknown CUL_FHTTK device detected, define one to get detailed information.
2009.11.06 19:37:21 5: CUL/RAW: /T965AB08158

2009.11.06 19:37:21 3: CUL2: T965AB081 -30
2009.11.06 19:37:21 3: CUL: falling thru on T965AB081
2009.11.06 19:37:21 5: CUL2 dispatch T965AB081
2009.11.06 19:37:21 3: CUL2: Unknown CUL_FHTTK device detected, define one to get detailed information.

Mal gucken ...

2009.11.06 19:40:21 5: Cmd: >define TK_TEST CUL_FHTTK 965AB0<
2009.11.06 19:40:21 5: Loading /usr/local/lib/FHEM/09_CUL_FHTTK.pm, order 09
2009.11.06 19:40:21 5: Cmd: >attr TK_TEST IODev CUL2<
[...]
2009.11.06 19:45:52 3: CUL1: T965AB001 -86.5
2009.11.06 19:45:52 3: CUL: falling thru on T965AB001
2009.11.06 19:45:52 5: CUL1 dispatch T965AB001
2009.11.06 19:45:52 3: FHTTK, parsed T965AB001 into 965AB0 and 01
2009.11.06 19:45:52 3: skipping device 965AB0 on this receiver
2009.11.06 19:45:53 5: CUL/RAW: /T965AB081E8

2009.11.06 19:45:53 3: CUL1: T965AB081 -86
2009.11.06 19:45:53 3: CUL: falling thru on T965AB081
2009.11.06 19:45:53 5: CUL1 dispatch T965AB081
2009.11.06 19:45:53 3: FHTTK, parsed T965AB081 into 965AB0 and 81
2009.11.06 19:45:53 3: skipping device 965AB0 on this receiver
2009.11.06 19:45:54 5: CUL/RAW: /T965AB08158

2009.11.06 19:45:54 3: CUL2: T965AB081 -30
2009.11.06 19:45:54 3: CUL: falling thru on T965AB081
2009.11.06 19:45:54 5: CUL2 dispatch T965AB081
2009.11.06 19:45:54 3: FHTTK, parsed T965AB081 into 965AB0 and 81

Na, sieht doch schon gut aus ;)
         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 Kai,

kannst mir das Modul mal schicken...


Gruß,

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
-~----------~----~----~----~------~----~------~--~-

Originally posted by: <email address deleted>

Axel wrote:
> Hi Kai,
>
> kannst mir das Modul mal schicken...

Die relevanten Unterschiede zu 09_BS.pm (was Rudolf mal als Beispiel
anführte) habe ich schon gepostet; mehr als ...

2009.11.07 04:34:57 5: CUL/RAW: /T965AB001EA

2009.11.07 04:34:57 3: CUL1: T965AB001 -85
2009.11.07 04:34:57 3: CUL: falling thru on T965AB001
2009.11.07 04:34:57 5: CUL1 dispatch T965AB001
2009.11.07 04:34:57 3: FHTTK, parsed T965AB001 into 965AB0 and 01
2009.11.07 04:34:57 3: skipping device 965AB0 on this receiver
2009.11.07 04:34:57 5: CUL/RAW: /T965AB00158

2009.11.07 04:34:57 3: CUL2: T965AB001 -30
2009.11.07 04:34:57 3: CUL: falling thru on T965AB001
2009.11.07 04:34:57 5: CUL2 dispatch T965AB001
2009.11.07 04:34:57 3: FHTTK, parsed T965AB001 into 965AB0 and 01
2009.11.07 04:34:58 5: CUL/RAW: /T965AB081E9

2009.11.07 04:34:58 3: CUL1: T965AB081 -85.5
2009.11.07 04:34:58 3: CUL: falling thru on T965AB081
2009.11.07 04:34:58 5: CUL1 dispatch T965AB081
2009.11.07 04:34:58 3: FHTTK, parsed T965AB081 into 965AB0 and 81
2009.11.07 04:34:58 3: skipping device 965AB0 on this receiver
2009.11.07 04:34:58 5: CUL/RAW: /T965AB08157

2009.11.07 04:34:58 3: CUL2: T965AB081 -30.5
2009.11.07 04:34:58 3: CUL: falling thru on T965AB081
2009.11.07 04:34:58 5: CUL2 dispatch T965AB081
2009.11.07 04:34:58 3: FHTTK, parsed T965AB081 into 965AB0 and 81

... macht es auch noch nicht, da ich jetzt rausfinden muß, wie man
Werte eines logischen Devices in FHEM setzt. Denke, das werde ich
am Wochenende rausfinden (vielleicht mit Hilfe? *hint, hint*).

Wonach modelliert man denn einen "Dekoder" für FHT80TF am besten --
es gibt ja insgesamt 3 sehr ähnliche Devices: FS20TFK, HMS100TFK und
eben FHT80TF ... FHT80TF sendet alle rd. 2,25 Minuten einen Status,
den FHT80B auswertet:

2009.11.07 04:39:25 4: FHT FHT1 warnings: Window open

Mit konkreter Auswertung von FHT80TF-Telegrammen geht das latent ge-
nauer, zumindest die Visualisierung in FHEM/PGM2.

MfG,
         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>

Moin,

vieleicht so.....als Entwurf...

##############################################
package main;
use strict;
use warnings;
my %fhttfk_codes = (
    "02" => "Window:Closed"
    "82" => "Window:Closed"
    "01" => "Window:Open"
    "81" => "Window:Open"
    "0C" => "Sync:Bin da, wer noch?"
    "??" => "Battery:empty");
my %defptr;
##############################################
sub CUL_FHTTFK_Initialize($)
{
   my ($hash) = @_;
   $hash->{Match}     = "^T........";
   $hash->{DefFn}     = "CUL_FHTTFK_Define";
   $hash->{UndefFn}   = "CUL_FHTTFK_Undef";
   $hash->{ParseFn}   = "CUL_FHTTFK_Parse";
   $hash->{AttrList}  = "IODev do_not_notify:1,0 showtime:0,1 dummy:
1,0 model:FHTTK loglevel:0,1,2,3,4,5,6";
}
##############################################
sub CUL_FHTTFK_Define($$)
{
# aus 12_HMS...noch anpassen
# define CUL_FHTTK
  my ($hash, $def) = @_;
  my @a = split("[ \t][ \t]*", $def);
  return "wrong syntax: define HMS CODE" if(int(@a) != 3);
  $a[2] = lc($a[2]);
  return "Define $a[0]: wrong CODE format: specify a 4 digit hex
value"
        if($a[2] !~ m/^[a-f0-9][a-f0-9][a-f0-9][a-f0-9]$/);
  $hash->{CODE} = $a[2];
  $defptr{$a[2]} = $hash;
  return undef;
}
##############################################
sub CUL_FHTTFK_Parse($$)
{
   my ($hash, $msg) = @_;
   my $sensor= substr($msg, 1, 6);
   my $state = substr($msg, 7, 2);
   my $def= $defptr{$sensor};
   my $self = $def->{NAME};
   if(!defined($def)) {
     Log 3, sprintf("FHTTK Unknown device %s, please define it",
$sensor);
     return "UNDEFINED FHTTK";
   }
# würd ich ev. weglassen....
   # if it's not our device
   if($def->{IODev} && $def->{IODev}{NAME} ne $hash->{NAME}) {
     Log 3, sprintf("skipping device %s on this receiver", $sensor);
     return "";
   }
   #...
# state definiert ???
   if(!defined($fhttfk_codes{$state}) {
       Log 3, sprintf("FHTTK $def Unknown CODE");
        return "";
   }
   #READINGS
   my ($reading,$val) = split(/:/,$fhttfk_codes{$state});
   $defs{$self}{READINGS}{$reading}{VAL} = $val;
   $defs{$self}{READINGS}{$reading}{TIME} = TimeNow();
   #CHANGED
   $defs{$self}{CHANGED}[0] = $reading . ": " . $val;
   return "";
}
1;

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-