Eltako FWZ12-16A

Begonnen von aicgazi, 12 Januar 2013, 15:58:11

Vorheriges Thema - Nächstes Thema

klaus.schauer

Zitat von: harryzz schrieb am Sa, 16 März 2013 14:13i get Eltako FWZ12-65 and found some bugs in 10_EnOcean.pm on latest dev verion:

line 1058 must be : if ($dataType == 4)
line 1061: push @event, "3:state:$meterReading";

if ($dataType == 4): The dateType queries has been corrected.

push @event, "3:state:$meterReading"; : What was wrong, I can not find anything.

The profile is otherwise OK? Can I mark it as tested?

harryzz

Zitat von: klaus.schauer schrieb am So, 17 März 2013 09:18
Zitat von: harryzz schrieb am Sa, 16 März 2013 14:13i get Eltako FWZ12-65 and found some bugs in 10_EnOcean.pm on latest dev verion:

line 1058 must be : if ($dataType == 4)
line 1061: push @event, "3:state:$meterReading";

if ($dataType == 4): The dateType queries has been corrected.

push @event, "3:state:$meterReading"; : What was wrong, I can not find anything.

The profile is otherwise OK? Can I mark it as tested?

for line 1061: in source is "3:status:$meterReading";[/quote]
i think must be state for reporting correct last value.
also may be will be nice attributes like "Cost", and "Period" to be calculated energy used.

br
harry

P.S.
also there will be problem with line 1062:
        } elsif ($db_0 == 0x8F && $manufID eq "00D") {
the right value is 0x80 not 0x8F i think.

All other is ok.
there are sniffed data:

55 00 0a 07 01 eb a5 48 08 0d 80 00 87 3d b9 00 01 ff ff ff ff 39 00 47
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 3c 00 b9
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 37 00 e4
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 3a 00 c7
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 3a 00 0d
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 3a 00 c7
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 39 00 32
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 37 00 2e
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 39 00 32
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 3d 00 ac
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 3d 00 66
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 41 00 f2
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 43 00 12
55 00 0a 07 01 eb a5 00 00 00 09 00 87 3d b9 00 01 ff ff ff ff 36 00 3b
55 00 0a 07 01 eb a5 00 00 00 0c 00 87 3d b9 00 01 ff ff ff ff 36 00 f1

harryzz

there are some new/old bugs found in EnOcean and TCM module.

2,3c2
< # $Id: 00_TCM.pm 2964 2013-03-22 06:03:51Z klaus-schauer $
<
---
> # $Id: 00_TCM.pm 2411 2013-01-03 13:05:04Z rudolfkoenig $
273,278d271
<
< # Schorsch M: dispatch corrections
< if(!Dispatch($hash, "EnOcean:$org:$d1:$id:$status:$odata", \%addvals)) {
< Log 1 , "Dispatch was called devices was not defined call Dispatch again";
< Dispatch($hash, "EnOcean:$org:$d1:$id:$status:$odata", \%addvals);
< }

becouse of this events are reported twice in log file.

in file 10_EnOcean.pm
line 1465
my $dataType = ($db_0 & 4) >> 3;
must be:
my $dataType = ($db_0 & 4) >> 2;


br
harry

klaus.schauer

Fehler in den Profilen autoMeterReading.<xx> werden in der nächsten Version von 10_Enocean bereinigt.