hej again,
i still have probs with the rules…i tried serveral kind of rules, to start and stop a switch.
The start command works fine, but the stop command is still not working.
Problem with rules and a switch
hej again,
i still have probs with the rules…i tried serveral kind of rules, to start and stop a switch.
The start command works fine, but the stop command is still not working.
I don´t think that this is a rule related problem…
Does the wallplug switch everytime if you switch it with a button in pimatic?
with the button it works fine
@agentjk said in Problem with rules and a switch:
steckdose01
Is steckdose01 a pimatic button or a pimatic switch?
and when you say ‘the button’, do you mean the physical button on the device?
hej
it´s a 433mhz switch
the “button” is the pimatic software button
The software button works like a charm, just the “Off rule is a problem”
But on github someone had a work-around for this problem !
The working rule is this:
"“when its 20:05 then switch Steckdose01 on”
“when its 20:10 then switch Steckdose01 off then switch Steckdose01 off after 16 seconds”
so far it works
But i dont understand why the “normal Off rule” is not workign correct
hi, if you have a working button for on. You could also make a button for off and use that.
But i assume that that’s not the solution and the problem is in the plugin you use.
Which plugin are you using?
yes the off-button is a solution but as you mentioned not the best
at the moment i use the homeduino plugin
Hey, I here see partly similar problems. but as I see this, these mostly single and often not 100% re-producible problems often come along with the fact, that the 433Mhz protocol isn‘t that 100% reliable.
I‘m still controlling ~10 shutters and ~5 plug-switches on Basis of 433Mhz. Normally they all work fine, but from time to time, a signal/command is lost.
To cover this, I partly also doubled the commands, resp. send the same command again a view minutes later.
E. g. for the outdoor pool filter, or also if the alarm function is controlling the house, the shutters get an additional down command after a while.
In General, besides repeating the signal itself, I also took care for having a view seconds spare time between the different signals, which made e. g. the process of lowering the different shutters also more reliable.
However, everything which is driven by RF is mostly not 100% reliable.
Definitely less problems, but also happing there, I see in the usage of Zigbee devices. But, as said, from time to time, I also see there similar problems, that however, a device is not reachable, although it worked perfectly for weeks before … 🙃
thnx for the infos pedder !
This 433mhz switches are mystic …today i tried to connect an identical copy of my first Brennenstuhl rcr 1000n comfort switch.
My idea was, just copy the “old device” , rename it an the second switch will work. but surprise surprise it´s not working like this.
My working switch has this “code”
{
"protocols": [
{
"name": "doorbell1",
"options": {
"id": 3415,
"unit": 1877
},
"send": true,
"receive": true,
"rfrepeats": 10
}
],
"id": "steckdose01",
"name": "steckdose01",
"class": "HomeduinoRFSwitch",
"forceSend": true
},
I tried to get the ID for the second switch via debugging
debug [pimatic-homeduino]: doorbell1: { id: 2045, unit: 1879, state: true }
20:36:31debug [pimatic-homeduino]: led4: { id: 16401, command: 'code:01010001' }
20:36:31debug [pimatic-homeduino]: led3: { id: 16401, command: 'code:01010001' }
20:36:31debug [pimatic-homeduino]: led2: { id: 16401, command: 'code:01010001' }
20:36:31debug [pimatic-homeduino]: led1: { id: 16401, command: 'code:01010001' }
20:36:31debug [pimatic-homeduino]: contact3: { id: 786154, contact: false }
20:36:31debug [pimatic-homeduino]: contact2: { id: 786154, contact: false }
20:36:31debug [pimatic-homeduino]: pir6: { id: 8866, presence: true }
20:36:31debug [pimatic-homeduino]: pir1: { unit: 15, id: 8, presence: true }
20:36:31debug [pimatic-homeduino]: switch27: { channel: '1000', unit: '0101110', state: false }
20:36:31debug [pimatic-homeduino]: switch22: { id: 786154, command: 'A' }
20:36:31debug [pimatic-homeduino]: switch16: { id: 'B', unit: 1, state: false }
20:36:31debug [pimatic-homeduino]: switch15: { id: 262421, unit: 0, state: true, all: true }
20:36:31debug [pimatic-homeduino]: switch14: { id: 262421, unit: 4, all: true, state: true }
20:36:31debug [pimatic-homeduino]: switch7: { unit: 7, id: 5, state: false }
20:36:31debug [pimatic-homeduino]: switch5: { id: 786154, unit: 0, all: true, state: false }
20:36:31debug [pimatic-homeduino]: switch4: { unit: 15, id: 8, state: true }
20:36:31debug [pimatic-homeduino]: switch3: { houseCode: 15, unitCode: 8, state: false }
20:36:31debug [pimatic-homeduino]: switch2: { houseCode: 15, unitCode: 8, state: true }
20:36:31debug [pimatic-homeduino]: received: [ 332, 896, 9492 ] 01100101010101010101011001010110011001100101011002
20:36:31debug [pimatic-homeduino]: data: "RF receive 332 896 9492 0 0 0 0 0 01100101010101010101011001010110011001100101011002"
The “discover devices” option delivers a lot of switches, Pir, etc. i tried all switches but the best result was a only “turn on” modus.
So i am stuck again …
maybe someone can help…