Intertechno_old with pilight on different Machine

[cyablo]

Hello,

I just installed Pilight on my Raspberry to control my Silvercrest Powerswitches. It is working fine using the commandline on my Raspberry:

pilight-send -p silvercrest -s 0 -u 16 -t / -f

Now I configured my FHEM Server for this Switch wich does not work. The Pilight Log says:

pilight-daemon: INFO: new client, ip: 192.168.1.3, port: 49270 pilight-daemon: INFO: client recognized as sender

FHEM log says:

pilight command: off pilight data: { "message": "send", "code": {"protocol":[ "silvercrest" ],}}

so the Communication between FHEM Server and Pilight RasPi seems to work.

This is my Config in FHEM:

I really dont see the Problem :(

[cyablo]

I tried another Switch with cogex Protocol which also does work from command line but not within FHEM. Im using the Pillight Version from the official Apt-Repo, if this helps.

[andreas-fey]

Can you verify that you are using version 5.0 of pilight?

[cyablo]

pilight-deamon -V was showing Version 5

I got it working with Silvercrest Switches by compiling pilight from Git and using latest pilight.pm (seems not to be updated by FHEM Updater). Dont know which one did the Trick.

But my second switch wich is shown as arctech old by receive command and works using cogex or intertechno_old using command line, does still does not work with FHEM.

pilight-send -p intertechno_old -i 21 -u 8 -f

Does work, here is my FHEM Config:

pilight command: on 2014.12.15 12:13:36 3: pilight data: { "message": "send", "code": {"protocol":[ "intertechno_old" ],"id":0, "unit":8,"on":1}}

Looks like id is not submitted correctly, this has to be 21 but seems to be 0!

Edit: My Fault! SORRY! Tought i had to use id like with command line but the Attribute is surely called systemcode. It is working now :)

Can be closed, Sorry!