• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
rev switch: maybe mismatch in sending on and off codes
#1
dear list,

as the rev protocol seem to be supported only by the nightly builds I'm using this daemon:

Quote:$ pilight-daemon -V
pilight-daemon version v7.0-59-g6f3a679

I am trying to control some older REV switches. The product codes seems to be 8341 (3-way sender w/ separate on/off keys) and 8342 (receiver).

First I checked the codes. Among others "pilight-receive" got the 3 devices as protocol "rev1_switch" with the id's F7, E7 and D7 and all as unit "0". The state was recognized correctly as "on" while pressing the "on" key" and "off" while pressing "off".

Next I configured them in config.json only to find the GUI very - let me call it - "unstable". I had to press the keys in the web gui twice to swtch the devices on or off and get the correct state displayed in the gui.

As other elro_800_switch(es) are working pretty fine without this effect I tried to investigate the reason and tried control them with "pilight-send". Found out "pilight-send ... --off" switches them on and "pilight-send ... --on" switches them off. And yes I double checked this because I could not believe it too!

Can someone please have a look at pilight/libs/pilight/protocols/433.92/rev_v[123].c if the codes for switching the device on and off may have been misplaced for sending?


kind regards
 
Reply
#2
No answer from any maintainer since 4 days - maybe I should explain a little bit more:

To make things short, the following is only for channel 1 but valid for any other channel as well.

First I checked the codes from the remote, channel 1, on and got this log from pilight-receive:

Quote:{
"message": {
"id": 7,
"unit": 15,
"state": "down"
},
"origin": "receiver",
"protocol": "arctech_screen_old",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 54740,
"unit": 3
},
"origin": "receiver",
"protocol": "beamish_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 7,
"unit": 15,
"state": "off"
},
"origin": "receiver",
"protocol": "arctech_switch_old",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": "F7",
"unit": 0,
"state": "on"
},
"origin": "receiver",
"protocol": "rev1_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 0,
"unitcode": 28,
"state": "off"
},
"origin": "receiver",
"protocol": "elro_800_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"unitcode": 518698,
"state": "opened"
},
"origin": "receiver",
"protocol": "ev1527",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 53,
"systemcode": 7488,
"unit": 4,
"state": "off"
},
"origin": "receiver",
"protocol": "daycom",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 0,
"unitcode": 28,
"state": "off"
},
"origin": "receiver",
"protocol": "heitech",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 875840,
"unitcode": 4,
"state": "off"
},
"origin": "receiver",
"protocol": "logilink_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 0,
"state": "off"
},
"origin": "receiver",
"protocol": "ehome",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 0,
"unitcode": 28,
"state": "off"
},
"origin": "receiver",
"protocol": "silvercrest",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}

Next I did the same with channel 1 off key:

Quote:{
"message": {
"id": 7,
"unit": 15,
"state": "up"
},
"origin": "receiver",
"protocol": "arctech_screen_old",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 54740,
"unit": 4
},
"origin": "receiver",
"protocol": "beamish_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": 7,
"unit": 15,
"state": "on"
},
"origin": "receiver",
"protocol": "arctech_switch_old",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"id": "F7",
"unit": 0,
"state": "off"
},
"origin": "receiver",
"protocol": "rev1_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 0,
"unitcode": 28,
"state": "on"
},
"origin": "receiver",
"protocol": "elro_800_switch",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}
{
"message": {
"systemcode": 0,
"unitcode": 28,
"state": "on"
},
"origin": "receiver",
"protocol": "silvercrest",
"uuid": "0000-b8-27-eb-26a101",
"repeats": 1
}

As the only protocol with correct assigned on / off states was rev1_switch I tried to switch the devices using pilight-send.

For a pilight-send -p rev1_switch -i F7 -u 0 --on:

Quote:pi@raspberrypi:~ $ pilight-receive
{
"origin": "sender",
"protocol": "rev1_switch",
"message": {
"id": "F7",
"unit": 0,
"state": "off"
},
"repeat": 1,
"uuid": "0000-b8-27-eb-26a101"
}


And as cross check for pilight-send -p rev1_switch -i F7 -u 0 --off:

Quote:pi@raspberrypi:~ $ pilight-receive
{
"origin": "sender",
"protocol": "rev1_switch",
"message": {
"id": "F7",
"unit": 0,
"state": "on"
},
"repeat": 1,
"uuid": "0000-b8-27-eb-26a101"
}

And yes the receive session was open in parallel to the send commands.

Is there any possibility to correct this without recompiling the code by using special (maybe hidden) variables or maybe configure raw codes in config.json?

Andreas
 
Reply
#3
Noticed there are 2 threads for this REV 8341L.
Suggest to continue discussion here: https://forum.pilight.org/Thread-REV-Switch-Typ-8342L
EDIT: BTW, I managed to develop a working protocol for this switch. See the linked thread
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [SOLVED] Home Assistant switch gpio segalion 5 767 09-10-2018, 12:39 PM
Last Post: segalion
  pilight 8.1 and switch with date and time not working Pikeman 7 924 06-30-2018, 11:28 PM
Last Post: curlymo
  pilight no sending but Receiving works Tueftler1983 1 602 04-01-2018, 03:34 PM
Last Post: Ramirez
  pilight-send for like rc-switch "send" mindau 1 1,428 01-18-2018, 07:46 AM
Last Post: madmoses
  Sending does not work under Linux, only under Windows mark78 17 2,617 01-17-2018, 06:34 PM
Last Post: curlymo
  [Fully Supported] Conrad RSL Switch Hexcode 137 44,331 12-02-2017, 08:48 AM
Last Post: Micha_123
  Problem with sending after plight (or raspberry?) update _Jens_ 5 1,918 09-08-2017, 03:14 PM
Last Post: pilino1234
  pilight sending codes in infinite loop dazzlebit 4 1,581 05-18-2017, 09:37 PM
Last Post: pilino1234
  Problem with a Switch rule viper2035 2 1,267 01-12-2017, 04:33 PM
Last Post: viper2035
  Light Switch with integrated ON/OFF Button ilir@ademi.org 4 1,879 01-04-2017, 09:22 PM
Last Post: ilir@ademi.org

Forum Jump:


Browsing: 1 Guest(s)