• 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
Success Story - GT-FSI-05 and Rev Ritter 8342LC on RPI3 wt FS1000A/RF-5V
#1
Hi!

I dunno, if this is the right spot for this kind of information. So admins - if it's not, please move it to the right one Smile

The last 2 days I tried to get my switches to work on a raspberry pi 3 with a low-cost transceiver. while testing, I wrote a log to document my steps. Now, I want to share this, coz especially on these devices, information on the web is rather rare or cluttered...

So, I hope this will be useful - enjoy!

And thanks to Raspberry Pi – pilight mit 433MHz Modulen zur Hausautomatisierung for getting me on the road

My Switches:

Code:
Globaltronics:
switch:   GT-FSI-05
dimmer:   GT-FSI-05d
remote:   GT-8000
bought at Pollin for ~15.-€
These switches 'learn' their codes (id/unit) by holding a
button on the switch and pressing a key on the remote

Rev-Ritter:
switch:   Typ 8342LC
remote:   Typ 008341C
bought at OBI 9.99€
These switches go into a 'learn-mode' for 10 secs after
plugging them in. By pressing a key on the remote then,
the switch gets assigned to that key.


Hardware:
Code:
board:
Raspberry PI-3

transmitter:
superregeneration FS1000A
16,5cm simple wire-antenna
pins: trans-gnd----rpi-gnd  (=#6)
      trans-vcc----rpi-3.3v (=#1)
      trans-data---rpi-#11  (=gpio17, wiringPi #0)

receiver:
superregeneration RF-5V
16,5cm simple wire-antenna
pins: recv-gnd-----rpi-gnd (=#9)
      recv-vcc-----rpi-5v  (=#2)
      recv-data ---3k3---|---3k3---rpi-gnd (=#9)
                         |  
                         |
                         |---rpi-#12 (=gpio18, wiringPi #1)

The DATA(-out) of the receiver is level-shifted by a resistor-network. I used 3k3 coz I had them at hand. Other values might work fine too (not too small).


Software:
Code:
debian jessie
pilight-version: v7.0

config:
/etc/pilight/config.json
{
        "devices": { },
        "gui": { },
        "rules": { },
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-http-port": 80,
                "webserver-cache": 1,
                "whitelist": ""
        },
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
        "registry": { }
}


useful for me:
Code:
pilight-send -H
pilight-send -p quigg_gt7000 -H
pilight-send -p intertechno-switch -H



I used pilight-receive to get the id- an unit-numbers

GT-FSI-05 was decoded as quigg_gt7000 and quigg_screen
and that worked right away.

The Rev-Ritters showed up as arctech-protocol, hmmm. The
sending part of pilight seems to have abandoned that
protocol. I somehow figured out (by reading the
whole web two times), that the intertechno_switch protocol
could be used: et voila - tutti bene!

Finally, with the above setup, the following commands at the shell
drive my switches well:
Code:
# Globaltronics GT-FSI-05 / GT-FSI-05d on/off
pilight-send -p quigg_gt7000 -i 3071 --on  -u 0
pilight-send -p quigg_gt7000 -i 3071 --off -u 0
...
...
pilight-send -p quigg_gt7000 -i 3071 --on  -u 3
pilight-send -p quigg_gt7000 -i 3071 --off -u 3

# Globaltronics GT-FSI-05d Dimmer, ~ 20 steps
pilight-send -p quigg_screen -i 3071 --down -u 3
pilight-send -p quigg_screen -i 3071 --up   -u 3


# Rev-Ritter 8342LC switches on/off
pilight-send -p intertechno_switch -i 30553070 --on  -u 13
pilight-send -p intertechno_switch -i 30553070 --off -u 13

pilight-send -p intertechno_switch -i 30553070 --on  -u 14
pilight-send -p intertechno_switch -i 30553070 --off -u 14

pilight-send -p intertechno_switch -i 30553070 --on  -u 15
pilight-send -p intertechno_switch -i 30553070 --off -u 15

This was the output of pilight-receive:

Receive-Log Globaltronics:
Code:
me@mybox:~ $ pilight-receive
{
    "message": {
        "id": 3071,
        "unit": 0,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 2,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 3,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 0,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 2,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 3,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 3,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 1
}
{
    "message": {
        "id": 3071,
        "unit": 3,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "quigg_gt7000",
    "uuid": "0000-b8-27-eb-391d63",
    "repeats": 2
}

...

{
        "origin": "sender",
        "protocol": "quigg_screen",
        "message": {
                "id": 3071,
                "unit": 3,
                "state": "down"
        },
        "repeat": 1,
        "uuid": "0000-b8-27-eb-391d63"
}
{
        "origin": "sender",
        "protocol": "quigg_screen",
        "message": {
                "id": 3071,
                "unit": 3,
                "state": "down"
        },
        "repeat": 1,
        "uuid": "0000-b8-27-eb-391d63"
}

Receive-Log Rev-Ritter:
Code:
me@mybox:~ $ pilight-receive
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "down"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 15,
                "state": "closed"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "down"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "closed"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "down"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 14,
                "state": "closed"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 2
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "down"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
{
        "message": {
                "id": 30553070,
                "unit": 13,
                "state": "closed"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-391d63",
        "repeats": 1
}
 
Reply
#2
arctech_switch or intertechno_switch
There should be no difference.
 
Reply
#3
well, on the commandline it seems to matter:

pilight-send -p arctech_switch -i 30553070 --on -u 13
[Mar 20 23:09:32:872078] pilight-send: ERROR: this protocol is not supported or doesn't support sending
 
Reply
#4
You are right, and it is going back to the roots of pilight.

arctech protocol family
The arc_tech protocol family was the first one developed for pilight, based on a "chipset family" with certain design characteristics, requiring its own protocol driver, identified by the number of raw pulses used and reported by pilight-receive.
Various manufacturers are using those chipsets to sell products under their brand name. Based on their hardware design choosen, the devices will only listen to their specific remote controls. The difference between brands is in the addressing scheme, logic levels used, and the length of raw pulses.
Those protocols variants are known today as: kaku_switch, dio_switch, nexa_switch, coco_switch, intertechno_switch). Those five brands were known at the time when development for pilight started.
The original idea was to add device names to the protocol driver whenever new supported brands are identified and to ensure proper protocol driver assignment.

In a lot of cases the device name choosen is the same as the protocol driver name, but that was never done for the arctech protocol family and it should never have happened for the other protocol families either. If we fix that issue now we will break a lot of configurations.

QUIGG GT7000 protocol family
Before the question is raised again:
There is a second reason why we have different protocol drivers.
Let us have a look at your quigg_gt7000 and the quigg_screen protocol.
From an RF point of view they both belong to the same protocol family, but they are different device brands.

The quigg_gt7000 protocol implements the switch function for both devices (non-dimmable / dimmable switch).
In addition, the quigg_screen protocol implements the dim-up/dim-down functionality for the dimmable version.
The problem is that pilight currently does not provide the required UI elements.

This pilight GUI interface is independent from the pilight core.
It provides the different UI elements for all kinds of devices, like weather station devices, switches, dimmeres, or roller shutters of a window, etc. In the pilight design a dimmable device shall allow setting of dimlevels directly.

* In short:
The pilight UI element for dimmable switches can not be used.

* In long:
The dimmable quigg switches do not have such a provision (they do remember their last state, whenever they get turned on again, but do not report that state back). Thus a quigg_dimmer protocol won't support such a feature of setting the dimlevel directly, nor would it be able to the correct dimlevel on the GUI either and you never will have a chance to ensure that GUI and the device are synchronized; the only way of doing so is by providing a new synchronize button on the GUI, by setting the device to a know state (e.q. dim the device up or down - depending whether you tolerate darkness or bright light conditions) and then set the desired dimlevel by decr-/incrementing to the desired dimlevel step by step.

* The solution to the problem:
The pilight screen UI element supports increment/decrement features with the up/down function. Thus there was the quigg_screen protocol implemented for the time being (i actually do not now if there is a real roller shutter device around based on the quigg protocol).
 
Reply
#5
Aah, this sheds some light on this. Thanks for the comprehensive explanation and insight on that.

When implementing the devices into the config.json, I found out, that also kaku_switch besides intertechno_switch was working with the Rev-Ritter devices.

BTW, stopping the service and running sudo pilight-daemon -D after changing the configuration is a great way to hunt down config-errors.

Regarding the quigg_screen issue, I'm fine with the fact, that they're only up- or down-steppable. The original remote-control offers no other functionality, and neither the plugs do.

For the sake of completenes, I post my config.json with the abovementioned devices. FYI, the Globaltronics are named PollinX and the Rev-Ritter are named RitterX here.

/etc/pilight/config.json:
Code:
{
        "devices": {
                "Ritter1": {
                        "protocol": [ "intertechno_switch" ],
                        "id": [{
                                "id": 30553070,
                                "unit": 15
                        }],
                        "state": "off"
                },
                "Ritter2": {
                        "protocol": [ "intertechno_switch" ],
                        "id": [{
                                "id": 30553070,
                                "unit": 14
                        }],
                        "state": "off"
                },
                "Ritter3": {
                        "protocol": [ "intertechno_switch" ],
                        "id": [{
                                "id": 30553070,
                                "unit": 13
                        }],
                        "state": "off"
                },
                "Pollin0": {
                        "protocol": [ "quigg_gt7000" ],
                        "id": [{
                                "id": 3071,
                                "unit": 0
                        }],
                        "state": "off"
                },
                "Pollin1": {
                        "protocol": [ "quigg_gt7000" ],
                        "id": [{
                                "id": 3071,
                                "unit": 1
                        }],
                        "state": "off"
                },
                "Pollin2": {
                        "protocol": [ "quigg_gt7000" ],
                        "id": [{
                                "id": 3071,
                                "unit": 2
                        }],
                        "state": "off"
                },
                "PollinDimmer2": {
                        "protocol": [ "quigg_screen" ],
                        "id": [{
                                "id": 3071,
                                "unit": 2
                        }],
                        "state": "up"
                },
                "Pollin3": {
                        "protocol": [ "quigg_gt7000" ],
                        "id": [{
                                "id": 3071,
                                "unit": 3
                        }],
                        "state": "off"
                },
                "PollinDimmer3": {
                        "protocol": [ "quigg_screen" ],
                        "id": [{
                                "id": 3071,
                                "unit": 3
                        }],
                        "state": "down"
                }
        },
        "rules": {},
        "gui": {
                "Ritter1": {
                        "name": "Rev-Ritter 1",
                        "group": [ "The Ritters" ],
                        "media": [ "all" ]
                },
                "Ritter2": {
                        "name": "Rev-Ritter 2",
                        "group": [ "The Ritters" ],
                        "media": [ "all" ]
                },
                "Ritter3": {
                        "name": "Rev-Ritter 3",
                        "group": [ "The Ritters" ],
                        "media": [ "all" ]
                },
                "Pollin0": {
                        "name": "the Reds",
                        "group": [ "Lamps" ],
                        "media": [ "all" ]
                },
                "Pollin1": {
                        "name": "the Unused",
                        "group": [ "Lamps" ],
                        "media": [ "all" ]
                },
                "Pollin2": {
                        "name": "switch",
                        "group": [ "the Broken" ],
                        "media": [ "all" ]
                },
                "PollinDimmer2": {
                        "name": "dim",
                        "group": [ "the Broken" ],
                        "media": [ "all" ]
                },
                "Pollin3": {
                        "name": "switch the R",
                        "group": [ "the R" ],
                        "media": [ "all" ]
                },
                "PollinDimmer3": {
                        "name": "dim the R",
                        "group": [ "the R" ],
                        "media": [ "all" ]
                }
        },
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-http-port": 80,
                "webserver-cache": 1,
                "webserver-authentication": [ "xxxxxxx", "xxxxxxxxxxxxxx" ]
        },
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
        "registry": {
                "webgui": {
                        "tabs": 0
                },
                "pilight": {
                        "firmware": {
                                "version": 64512,
                                "lpf": 655350,
                                "hpf": 652790
                        },
                        "version": {
                                "current": "7.0"
                        }
                }
        }
}
 
Reply
#6
NEW RECEIVER:

arduino nano with above RF-Modules at usb-port like in pilight_firmware

I modded the firmware so you can use arduino-nano pin A5 as gnd for the receiver, since the nano has only 1 gnd-pin and I built the filter using only jumper-wires.

In pilight_usb_nano.c at line 155 after DDRB |= _BV(DDB5); I added:
Code:
// for having a 2nd 'gnd-pin'
//
PORTC &= ~( 1 << PC5 ); // val: low
DDRC  |= ( 1 << PC5 );  // dir: output
The power consumption of the receiver is about 4mA and an atmega can sink ~20mA.


connections:
Code:
nano-D5  ---- DATA-sender
nano-D7  ---- DATA-receiver
nano-5V  ---- VCC-receiver
nano-VIN ---- VCC-sender
nano-GND ---- GND-sender
nano-A5  ---- GND-receiver

nano-usb ---- rpi3 usb


ls -l /dev/ttyUSB* to get the port --> /dev/ttyUSB0

config:
Code:
"hardware": {
                "433nano": {
                        "comport": "/dev/ttyUSB0"
                }
},

works like a charm. cpuload dropping to <1% from ~20-25% before.



"I came into this game for the action, the excitement. Go anywhere. Travel light. Get in. Get out. Where ever there's trouble, a man alone."
H. Tuttle
 
Reply
#7
Hi, I've got the same setup (but a Model b+), got the data with pilight-receive (see below) but cannot send. The socket does not react. Any ideas how to hunt this down? Data was connected to #11 as suggested Crying

Code:
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "up"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "opened"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "up"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 14,
        "state": "opened"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "down"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11176882,
        "unit": 14,
        "state": "closed"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "down"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11176882,
        "unit": 11,
        "state": "closed"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "up"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "opened"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 1
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "up"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-e6563b",
    "repeats": 2
}
{
    "origin": "sender",
    "protocol": "arctech_switch",
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "off"
    },
    "repeat": 1,
    "uuid": "0000-b8-27-eb-e6563b"
}
{
    "origin": "sender",
    "protocol": "arctech_switch",
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "on"
    },
    "repeat": 1,
    "uuid": "0000-b8-27-eb-e6563b"
}
{
    "origin": "sender",
    "protocol": "arctech_switch",
    "message": {
        "id": 11439094,
        "unit": 15,
        "state": "off"
    },
    "repeat": 1,
    "uuid": "0000-b8-27-eb-e6563b"
}
 
Reply
#8
tell us exactly, what you have tried so far.

when posting code, tell us where that comes from - e.g. 'This is the output of "pilight-receive" or "my /etc/pilight/config.json:" ...

for sending, use intertechno_switch - not arctech_switch.

on the commandline try:
pilight-send -p intertechno_switch -i 11439094  --on  -u 15

adjust -i and -u parameters, e.g. -u 13/14/15

post your results!

good luck!
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  RPI3 b+ Raspbiam Stretch and pilight-7_oregon Tueftler1983 1 1,021 12-04-2018, 11:59 PM
Last Post: Tueftler1983
  Forum suggestion: Success Stories section Tamadite 1 467 08-06-2018, 07:33 AM
Last Post: curlymo
  pilight stopped working after updating RPi3 SmartValley 35 18,969 12-06-2017, 10:37 PM
Last Post: droptix

Forum Jump:


Browsing: 1 Guest(s)