@djmvt h
Would you be so kind and post your config for this button?
Thanks!
[solved]Use a 433mhz remote with homeduino as a trigger
@djmvt h
Would you be so kind and post your config for this button?
Thanks!
@leader21
How would i go about sending a HTTP GET request instead of “do something”?
You can use the pimatic shell execute plugin.
https://pimatic.org/plugins/pimatic-shell-execute/
Pimatic 0.9 i love it!
I got this error tyring to set a rule:
Could not find an provider that decides next predicate of "state of Button_1 is "false"".
I don’t seem to be able to get pimatic to act on the fact that i pressed the button on the remote.
Trying to create a rule i get
[pimatic] error: Could not find an provider that provides the next action of "execute...
What does this mean?
okay… try following
the if part
Button_1 is off
the then part
after 2 seconds turn Button_1 on
Ok this works … there seems to be someting wrong with the execute part of the rule
execute "curl --silent -m 3 http://192.168.0.149:8080/CMD?Light_1=OFF"
FIgured it out … i installed the Shell-execute plugin and I would swear that there was a popup saying that it was added to config, but apparently it wasn’t … i added it via GUI and now the execute part works.
did u have pilight beside pimatic-homeduino with the same Receiver/Transmitter running?? if yes it won’t work
@xCite86 said in Use a 433mhz remote with homeduino as a trigger:
did u have pilight beside pimatic-homeduino with the same Receiver/Transmitter running?? if yes it won’t work
No pilight installed …
back to the button issue:
i managed to solve the problem by using the “HomeduinoRFContactSensor” however this doesn’t make sense.
I suppose i need to somehow assign the function to a ON or OFF function of a button, but how?
this is my current devices config
"devices": [
{
"id": "Button_1",
"name": "Button-1",
"class": "HomeduinoRFSwitch",
"protocols": [
{
"name": "switch6",
"options": {
"systemcode": 10,
"programcode": "6"
},
"send": false,
"receive": true
}
]
},
{
"id": "homeduino-buttons",
"name": "Buttons",
"class": "HomeduinoRFButtonsDevice",
"buttons": [
{
"id": "test-button",
"text": "test",
"protocols": [
{
"name": "switch6",
"options": {
"systemcode": 10,
"programcode": 6,
"state": false
}
}
]
}
]
},
{
"id": "door-contact",
"name": "door-Contact",
"class": "HomeduinoRFContactSensor",
"protocols": [
{
"name": "switch6",
"options": {
"systemcode": 10,
"programcode": 6
}
}
],
"autoReset": true,
"resetTime": 500
}
],
if the HomeduinoRFContactDevice works for you, you can use “xxx was present”
if door-contact was present then execute "curl --silent -m 3 http://192.168.0.149:8080/CMD?Light_1=OFF"
Is there really no way to trigger an event for a HomeduinoRFSwitch device?
sorry for my late reply, have been kinda busy.
this is my doorbell device, wich is actually an input device from a signal sent by a remote controller:
{
"id": "DeurbelRF",
"name": "Deurbel",
"class": "HomeduinoRFButtonsDevice",
"buttons": [
{
"id": "deurbel",
"text": "Deurbel",
"protocols": [
{
"name": "switch5",
"options": {
"unit": 1,
"id": 716953,
"state": true
},
"send": false,
"receive": true
}
]
}
]
},
and this rule gets executed when the remote control button is pressed:
{
"id": "deurbel",
"name": "VoorDeurBel dag",
"rule": "if it is after 07:30 and Deurbel button is pressed and \"$deurbelactief\" = \"0\" then set $deurbelactief to \"1\" and execute \"hyperion-remote -a 192.168.1.41:19444 -p 50 -e Snake" and execute \"hyperion-remote --address 192.168.1.41:19444 --priority 50 --clearall \" after 12 seconds and set $deurbelactief to \"0\" after 20 seconds",
"active": true,
"logging": true
},
@djmvt Thanks for the config!
Would you be so kind as to also provide the homeduino debug - i’d like to know how the plugin decodes the received signal:
mostly i’m interested in why you have set
"state": true
in your device config?
State true is only there because of initialisation, I think.
Maybe you are overthinking this. You could easily have a switch device as “Doorbell switch”.
When doorbell switch is pressed (button on doorbell), switch changes states.
You can also reset the switch with a rule, like after 5 seconds or so.
(If doorbell switch is turned on, then after 5 seconds turn doorbell switch off)
This is what I had done with my door sensor (contact sensor) before contact protocols were around that much.
After this, you can make a rule to execute the task you wish to do. You haven’t specified what you want to do after, so you’re alone with that one …
If doorbell switch is turned on, then execute "task X"
Got this thing working … thank you all for the input…