[nonflammable]

still is not working (clarus protocol)

Code:

pilight-send -p clarus_switch -u 22 -i "A2" -t

RAW is ok

Code:

pilight-send -p raw -c "183 549 183 549 183 549 183 549 183 549 549 183 183 549 183 549 183 549 183 549 183 549 549 183 183 549 549 183 183 549 549 183 183 549 183 549 549 183 549 183 183 549 183 549 549 183 549 183 183 6222"

Code:

pilight-daemon version 6.0, commit v6.0

year later ... something still is wrong

[m74]

Any news on this?
Cant get clarus_switch working.
Im on pilight-daemon version v7.0-59-g6f3a679 (nightly).

Result of pilight-receive

Code:

{
        "message": {
                "id": "F15",
                "unit": 63,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "clarus_switch",
        "uuid": "0000-b8-27-eb-1d98fc",
        "repeats": 1
}

Config (the device part)

Code:

"devices": {
                "Schalter1": {
                        "protocol": [ "clarus_switch" ],
                        "id": [{
                                "id": "F15",
                                "unit": 63
                        }],
                        "state": "on"
                }
},

Got an Arduino with an 433mhz Receiver acting as a sniffer.
Is the output of the sniffer interesting?

[alasdairc]

Hi,

I'm running pilight-daemon version v7.0-146-g001f2ea on a raspberry Pi (but using the pilight-usb-nano interface rather than GPIO).

I'm using clarus_switch to control these Baihoun sockets (http://switchcn.sh08.host.35.com/UK/). It's working great after reprogramming the sockets with pilight.

However receiving codes from the provided remote is giving false readings.

The remote has 5 buttons, and neither the state or the codes of any of them are being interpreted properly.

I'd love to use this remote. What can I do to help get these supported? I'm capable of writing C and compiling, I'd just need some pointers into the methodology.

[wo_rasp]

Start with the manual on http://www.pilight.org
Setup the pilight Environment (github Account, required tools and libs, download the pilight sources from github)
Fork a copy of pilight to your own pilight project and compile the development branch
Now you have a development environment that will allow you to modify and save the most recent pilight source and to modify existing code or to add new code and to issue Pull Requests for integrating them into the main pilight project.
Familiarize yourself with the various source code files and the directory structure of the tree starting at pilight/libs
The configuration file is located at /etc/config.json,
Once you have the environment up and running let us discuss your requirements.
send from tapatalk

[alasdairc]

Start with the manual on http://www.pilight.org
Setup the pilight Environment (github Account, required tools and libs, download the pilight sources from github)
Fork a copy of pilight to your own pilight project and compile the development branch
Now you have a development environment that will allow you to modify and save the most recent pilight source and to modify existing code or to add new code and to issue Pull Requests for integrating them into the main pilight project.
Familiarize yourself with the various source code files and the directory structure of the tree starting at pilight/libs
The configuration file is located at /etc/config.json,
Once you have the environment up and running let us discuss your requirements.
send from tapatalk

Sorry I should have been more specific..

I've got a dev environment already setup. I already submitted a successful PR for an issue in the nano firmware some time ago.

I'm just not clued up on the internals of pilight, in particular the receiving part. But I'll give it a go. Won't have time till the weekend to look at it. And first thing will be to move to the GPIO on the Pi rather than using the nano.

I already had doubts about the raw output on the nano as I mentioned in the other thread in the protocol dev forum. A captured raw output from a built in transmission was not accurate enough to be sent 'raw' itself. That set off alarm bells.

I'll get back in touch once I have made the changes and have started looking through the code.

[alasdairc]

Hi I'm all setup.

I'm not completely sure whether or not I should be hacking on the clarus protocol at all. Googling for clarus doesn't really give me much in the way of information. I understand that there's a lot of crossover between different protocols. The wiki page for clarus doesnt really relate to what I'm reading about the chip in my remote.

What I do know is that my remote control uses the HS2260A encoding chip. I've attached it's datasheet to this post. It has a good explanation which helps understand what's going in the transmission.

I've 'taught' the remote sockets using clarus codes transmitted via pilight and they work perfectly. The AVG_PULSE_LENGTH is similar (167 versus 180). I just want to make sure this isn't a coincidence and I would potentially be making breaking changes to another protocol.

So my first question is around terminology. In the source code I see

PULSE_MULTIPLIER
PULSE_DIV

PULSE_DIV is set to 34 in a header file.
In the clarus PULSE_MULTIPLER is set to 3.

What does PULSE_MULTIPLER and PULSE_DIV actually refer to?

My second question is about the raw codes output by pilight-debug. What are the numbers actually referring to? In my captures I see three different groupings of values,

120-140,
220-240,
580-610

What does this actually signify?

sorry for the most basic questions. the wiki and manual don't cover this, and no explanation in the source code.

[alasdairc]

Just read another post and it seems the numbers are the length of a pulse in microseconds.
Is it right to presume the first number is a high pulse length and each subsequent length is low-high-low-high etc?

[wo_rasp]

Yes it is.
send from tapatalk

[alasdairc]

Great.

And in this capture, what does 4 signify.

Code:

time:           Sun Apr 17 00:25:37 2016
hardware:       433nano
pulse:          4
rawlen:         50
pulselen:       166

[marco-f]

Hi,

i have a set of a noname remote and four power plugs and i would like to control the plugs with pilight. I installed pilight v7.0 on a raspberry pi 3 and scanned with pilight-receive for the signals from the remote. Now i'm a little bit confused about the results.

The remote has an ON and an OFF button for every single power plug and an ALL On and an ALL OFF button. Every one of the four single ON and OFF buttons sems to send the same signal, but different power plugs are switching correctly.

Button 1 - 4 ON:

Code:

"message": {
                "id": "D3",
                "unit": 61,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "clarus_switch",
        "uuid": "0000-b8-27-eb-bbb0c4",
        "repeats": 4

Button 1-4 OFF:

Code:

"message": {
                "id": "D3",
                "unit": 61,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "clarus_switch",
        "uuid": "0000-b8-27-eb-bbb0c4",
        "repeats": 19

The buttons ALL ON and ALL OFF are also making me confused, because they are working well and switching all power plugs together on and off, but pilight-receive says that both buttons send the same signal.

Button ALL ON:

Code:

"message": {
                "id": "D3",
                "unit": 61,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "clarus_switch",
        "uuid": "0000-b8-27-eb-bbb0c4",
        "repeats": 7

Button ALL OFF:

Code:

"message": {
                "id": "D3",
                "unit": 61,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "clarus_switch",
        "uuid": "0000-b8-27-eb-bbb0c4",
        "repeats": 15

Has anybody an explanation? It's unrealistic that the remote sends exact everytime the same signal but different power plugs are acting!

Regards,
Marco