[pimatic-pilight ] Predicate for 433MHz Remote Button press

[kwittwer]

Hi,
Is there a posibility to use a 433MHz remote as a sensor or trigger signal. For example I want to press a Button on the remotecontrol to activate a timer. Did anyone got something like this working?

Thanks for your answers!

[grant9742]

Hi, I use 433 to actuate the lights and also a 433 button as a doorbell sensor.

To sniff the 433 codes take a look at the ninjablocks 433utils and install wiringpi.

To control lights I execute a script that sends the codes to turn off and on.

For the doorbell setup a gpio device and setup a rule watching for a state change. You may also need a variable to debounce it.

Hope that helps

[grant9742]

Edit : doorbell isn't 433. Just a cheap $10 wireless doorbell.

[sweetpi]

To sniff the 433 codes take a look at the ninjablocks 433utils and install wiringpi.

Sounds interesting, could you provide a link?

The only way I know at the moment would be to create a switch in pilight and use that as trigger. I'll think about something more clever.

[grant9742]

Right here : https://github.com/ninjablocks/433Utils :)

[sweetpi]

Thanks
Am 26.04.2014 13:51 schrieb "grant9742" notifications@github.com:

Right here : https://github.com/ninjablocks/433Utils :)

Reply to this email directly or view it on GitHubhttps://github.com//issues/141#issuecomment-41466715
.

[georg90]

Anything new on this topic?
I want to use my remote and pimatic to control switches, but pimatic should always show the correct status of the switch.

[easy12]

Hi,

@georg90
Well, that's what pilight is doing. Use your remote (433Mhz) and pilight-receive to find out how ID and systemcode needs to be set. The setup config file. Now if your remote is in reach of receiver, pilight will notice this and it will simply update the status and of cause send update to pimatic. The culprit might be that you have a cheap receiver and those work just a few centimeter from receiver. The approved one with good antenna has much better range.

@kwittwer
See above. You don't need an actual receiver, the remote alone will work. Now at pimatic create a rule that does whatever you need when "switch" turns on and you may set it back with another rule. Make use of variables to trigger the second rule.

Regards Martin

[georg90]

I was refering to the post of @sweetpi
"The only way I know at the moment would be to create a switch in pilight and use that as trigger. I'll think about something more clever."

So I was wondering if there is anything already being developed to make it more "clever" of course I could use a switch.
I own the "good" receiver/sender pack - so I receive the signal :-)

[kwittwer]

Hi guys,
my pilight dose not update the switch state if I use a remote. I have tried the receiver with an arduino and I noticed a good reciving range.

[sweetpi]

I was refering to the post of @sweetpi

Not yet. My workload of other things is at the moment to high to write a single line of code for pimatic :(. Hope that gets better in a few weeks.

It sounds like a simple task but needs a complete rewrite of the pilight plugin. At the moment pimatic connects as "gui client" to pilight and so just gets the events that are needed to update the gui and not all received messages.

my pilight dose not update the switch state if I use a remote. I have tried the receiver with an arduino and I noticed a good reciving range.

Can't say much about that, because it is more pilight related to pilight than to pimatic.

[sweetpi]

Possible with pimatic-homeduino.