Hallo,
i was thinging about a plugin that would check the status of the devices (on or off) every Hour or so and send a signal to make sure it is/stays like that.
Do you thing there is a way to write a plugin like that? and if so, can you give me an hint where to start?
-
Repeater plugin
-
@newbe maybe you can simply use a rule for that
IF every 1 hour and device1 is OFF THEN turn on device1
is it what you are looking for?
pimatic rocks!
-
yes more or less, but if i do it like this i would have to add every single device manually, and if i add a new one i would have to write it in the plugin, is there a way to “automatic” that?
-
@newbe could you describe the use case here?
i am using a kind of repeater (with a rule) to trigger my gas boiler, but i don’t see many others area where it could be useful (maybe for a fish tank?)pimatic rocks!
-
it thought of somthing like, you wrote a rule that switches on your outside house lighs or something at a certain time, but the signal doesn’t arrive and with that plugin you can make sure it will turn on.
-
Okay i understand (so it’s the same reason than for my boiler, i constantly send on or off command to be sure that the receiver get it).
my rule for that:IF every 1 minutes and [$homeduino-temperature.temperature < $dummy-heating.temperatureSetpoint] THEN switch chaudiere on
Now you can also replace your receiver by some that are able to send back to pimatic their status (i personally don’t own one).
I think that using a repeater too much could give bad results mainly due to RF collision.
So maybe the best thing to do is to select which devices are important and those which are less and then repeat with rules every x depending on how they are crucial for youpimatic rocks!
-
isn’t there a way to read it back from pimatic, where you have the on/off switch surface? For example, it says the device is “on” but to make sure you send an “on” signal?
-
The RF lost commands is a real problem. I refresh orders with two rules:
{ "id": "rfrefreshbon", "name": "RFrefreshBon", "rule": "if state of DemaB is equal to on and every 5 minutes then turn DemaB on", "active": true, "logging": true }, { "id": "rfrefreshboff", "name": "RFrefreshBoff", "rule": "if state of DemaB is equal to off and every 5 minutes then turn DemaB off", "active": true, "logging": true },
but i think the optimal solution could be a device attribute, like that:
{ "id": "RFswitchB", "name": "DemaB", "class": "HomeduinoRFSwitch", "protocols": [ { "name": "switch6", "options": { "systemcode": 30, "programcode": 1, "refresh": 300000 <<<<<< 5 minutes to refresh } } ] },
-
"refresh": 300000 <<<<<< 5 minutes to refresh
that would mean repeat only 1 time after 5 min? what happens if you switch device off before that delay?
pimatic rocks!
-
I use 5 minutes to prevent RF colision. I accept sometime wrong. Also other refresh time could be good.
The most important for me is that pimatic status have priority. What I see is what I have.