Double homematic messages

[Guest]

Originally posted by: <email address deleted>

Hi,

I just started yesterday to add a homematic wall switch to my setup. i
used a older CULv1 with the proper firmware.
It works, but i get all messages double:
2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)
2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)

Anyone know why this happens?

and is there a better solution to connect a button to a lamp then:
define x1 notify CUL_HM_remote_1080B0  { if ("%" eq "Btn1 on (to
unknown)") { fhem "set Living.main on" } }
define x2 notify CUL_HM_remote_1080B0  { if ("%" eq "Btn1 off (to
unknown)") { fhem "set Living.main off" } }

Thanks in advance,
Remco

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

> It works, but i get all messages double:
> 2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)
> 2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)

double message: the remote is paired with a device, which is not sending acks
"to unknown"  : the name of this addressee is unknown to fhem.
To get rid of both: pair the remote with fhem.


> and is there a better solution to connect a button to a lamp then:

1. If the lamp is also homematic, than pair the remote first with the lamp,
   then with fhem -> No notifys are needed

2. Slightly shorter solutions:

   define x1 notify CUL_HM_remote_1080B0:on.* set Living.main on
   define x2 notify CUL_HM_remote_1080B0:off.* set Living.main off

   or

   define x1 notify CUL_HM_remote_1080B0 {\
     fhem "set Living.main $1" if("%" =~ m/^(on|off).*/);;\
   }

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

thats for the tips.

that procedure works fine with a door switch (reported as HM-SEC-SC,
threeStateSensor) and a dimmer, but this wall switch keeps complaining,
but it changed a bit.
this is what i get when i try to pair:


2011.07.16 11:21:03 4: CUL2:
A1A8684001080B00000001100354545513030343138343040040000 -60.5
2011.07.16 11:21:03 4: CUL_HM RCV L:1A N:86 CMD:8000 SRC:1080B0
DST:000000 1100354545513030343138343040040000 (DEVICE_INFO FIRMWARE:11
TYPE:0035 SERIALNO:EEQ0041840 CLASS:40 PEER_CHANNEL_A:04
PEER_CHANNEL_B:00 UNKNOWN:00)
2011.07.16 11:21:03 2: CUL_HM pair: Living.wallBtn is a remote, model
HM-PB-4-WM serialNr EEQ0041840
2011.07.16 11:21:03 4: CUL_HM SND L:1A N:86 CMD:A000 SRC:F14321
DST:1080B0 1000114648454d46313433323110010100
2011.07.16 11:21:03 4: CUL_HM SND L:10 N:87 CMD:A001 SRC:F14321
DST:1080B0 01051080B00104 (CONFIG_START CHANNEL:01 PEER_ADDRESS:1080B0
PEER_CHANNEL:01 PARAM_LIST:04)
2011.07.16 11:21:04 4: CUL2: A0A8780021080B0F1432184 -60
2011.07.16 11:21:04 4: CUL_HM RCV L:0A N:87 CMD:8002 SRC:1080B0
DST:F14321 84 (NACK_TARGET_INVALID)
2011.07.16 11:21:04 4: CUL_HM SND L:13 N:88 CMD:A001 SRC:F14321
DST:1080B0 010802010AF10B430C21 (CONFIG_WRITE_INDEX CHANNEL:01 DATA:
02:01 0A:F1 0B:43 0C:21)
2011.07.16 11:21:04 4: CUL2: A0A8880021080B0F1432180 -60
2011.07.16 11:21:04 4: CUL_HM RCV L:0A N:88 CMD:8002 SRC:1080B0
DST:F14321 80 (NACK)
2011.07.16 11:21:04 4: CUL_HM SND L:0B N:89 CMD:A001 SRC:F14321
DST:1080B0 0106 (CONFIG_END CHANNEL:01)
2011.07.16 11:21:04 4: CUL2: A0A8980021080B0F1432100 -60.5
2011.07.16 11:21:04 4: CUL_HM RCV L:0A N:89 CMD:8002 SRC:1080B0
DST:F14321 00 (ACK)


loglevel is 4.

i already performed a device reset from the device itself, and via the air.
when i press a button now, i get:

system log:
2011.07.16 11:23:27 4: CUL2: A0B8784401080B000000082C9 -69
2011.07.16 11:23:27 4: CUL_HM RCV L:0B N:87 CMD:A440 SRC:1080B0
DST:000000 82C9 (REMOTE BUTTON:2 LONG:0 LOWBAT:1 COUNTER:C9)

device log:
2011-07-16_11:23:27 Living.wallBtn Btn1 on (to broadcast)

is that supposed to be broadcast?

i will try it again when i found a full CR2032, just to make sure that
the (almost) empty battery is not the problem.

Remco


On 07/15/2011 01:26 PM, Rudolf Koenig wrote:
>> It works, but i get all messages double:
>> 2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)
>> 2011-07-15_07:20:06 CUL_HM_remote_1080B0 Btn1 off (to unknown)
> double message: the remote is paired with a device, which is not sending acks
> "to unknown"  : the name of this addressee is unknown to fhem.
> To get rid of both: pair the remote with fhem.
>
>
>> and is there a better solution to connect a button to a lamp then:
> 1. If the lamp is also homematic, than pair the remote first with the lamp,
>     then with fhem ->  No notifys are needed
>
> 2. Slightly shorter solutions:
>
>     define x1 notify CUL_HM_remote_1080B0:on.* set Living.main on
>     define x2 notify CUL_HM_remote_1080B0:off.* set Living.main off
>
>     or
>
>     define x1 notify CUL_HM_remote_1080B0 {\
>       fhem "set Living.main $1" if("%" =~ m/^(on|off).*/);;\
>     }
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

> this is what i get when i try to pair:

Can you please change 10_CUL_HM.pm by altering
    if($stn ne "remote") {
into
    if($stn ne "remote" || $attr{$name}{model} eq "HM-PB-4-WM") {
and tell me the outcome?



> system log:
> 2011.07.16 11:23:27 4: CUL2: A0B8784401080B000000082C9 -69
> 2011.07.16 11:23:27 4: CUL_HM RCV L:0B N:87 CMD:A440 SRC:1080B0
> DST:000000 82C9 (REMOTE BUTTON:2 LONG:0 LOWBAT:1 COUNTER:C9)
>
> device log:
> 2011-07-16_11:23:27 Living.wallBtn Btn1 on (to broadcast)
>
> is that supposed to be broadcast?

DST = 000000 is broadcast.



> i will try it again when i found a full CR2032, just to make sure
> that the (almost) empty battery is not the problem.

I am quite sure that it is not a battery issue. HM is (IMHO) a confusing
protocol, additionally different devices with the same subType behave
differently. This is why fhem does not (yet) support every device correctly.

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

looks better, no NACK's:

2011.07.16 13:24:48 4: CUL2:
A1A8B84001080B00000001100354545513030343138343040040000 -72.5
2011.07.16 13:24:48 4: CUL_HM RCV L:1A N:8B CMD:8000 SRC:1080B0
DST:000000 1100354545513030343138343040040000 (DEVICE_INFO FIRMWARE:11
TYPE:0035 SERIALNO:EEQ0041840 CLASS:40 PEER_CHANNEL_A:04
PEER_CHANNEL_B:00 UNKNOWN:00)
2011.07.16 13:24:48 2: CUL_HM pair: Living.wallBtn is a remote, model
HM-PB-4-WM serialNr EEQ0041840
2011.07.16 13:24:48 4: CUL_HM SND L:10 N:02 CMD:A001 SRC:F14321
DST:1080B0 00050000000000 (CONFIG_START CHANNEL:00 PEER_ADDRESS:000000
PEER_CHANNEL:00 PARAM_LIST:00)
2011.07.16 13:24:48 4: CUL2: A0A0280021080B0F1432100 -62.5
2011.07.16 13:24:48 4: CUL_HM RCV L:0A N:02 CMD:8002 SRC:1080B0
DST:F14321 00 (ACK)
2011.07.16 13:24:49 4: CUL_HM SND L:13 N:03 CMD:A001 SRC:F14321
DST:1080B0 000802010AF10B430C21 (CONFIG_WRITE_INDEX CHANNEL:00 DATA:
02:01 0A:F1 0B:43 0C:21)
2011.07.16 13:24:49 4: CUL2: A0A0380021080B0F1432100 -59.5
2011.07.16 13:24:49 4: CUL_HM RCV L:0A N:03 CMD:8002 SRC:1080B0
DST:F14321 00 (ACK)
2011.07.16 13:24:49 4: CUL_HM SND L:0B N:04 CMD:A001 SRC:F14321
DST:1080B0 0006 (CONFIG_END CHANNEL:00)
2011.07.16 13:24:49 4: CUL2: A0A0480021080B0F1432100 -61.5
2011.07.16 13:24:49 4: CUL_HM RCV L:0A N:04 CMD:8002 SRC:1080B0
DST:F14321 00 (ACK)

but the button is still going to broadcast:
2011-07-16_13:26:11 Living.wallBtn Btn1 on (to broadcast)

is it possible that you must pair individual buttons too?

Remco


On 07/16/2011 01:03 PM, Rudolf Koenig wrote:
>> this is what i get when i try to pair:
> Can you please change 10_CUL_HM.pm by altering
>      if($stn ne "remote") {
> into
>      if($stn ne "remote" || $attr{$name}{model} eq "HM-PB-4-WM") {
> and tell me the outcome?
>
>
>
>> system log:
>> 2011.07.16 11:23:27 4: CUL2: A0B8784401080B000000082C9 -69
>> 2011.07.16 11:23:27 4: CUL_HM RCV L:0B N:87 CMD:A440 SRC:1080B0
>> DST:000000 82C9 (REMOTE BUTTON:2 LONG:0 LOWBAT:1 COUNTER:C9)
>>
>> device log:
>> 2011-07-16_11:23:27 Living.wallBtn Btn1 on (to broadcast)
>>
>> is that supposed to be broadcast?
> DST = 000000 is broadcast.
>
>
>
>> i will try it again when i found a full CR2032, just to make sure
>> that the (almost) empty battery is not the problem.
> I am quite sure that it is not a battery issue. HM is (IMHO) a confusing
> protocol, additionally different devices with the same subType behave
> differently. This is why fhem does not (yet) support every device correctly.
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

> is it possible that you must pair individual buttons too?

Yes. There is a way way to trigger it from the Central unit, but this is not
yet implemented in fhem. Alternatively (tested with the 4Dis) there is a way to
initiate pairing of a single button from the remote, just like when you are
pairing the remote directly with a switch.

For this purpose you need the old CUL_HM code again

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com