• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
option "all" not sent in rules
#1
hi, i want to control a doorbell (intertechno MLR-1105). it works using the following device-settings:
Code:
"gong": {
                        "protocol": [ "intertechno_switch" ],
                        "id": [{
                                "id": 17242342,
                                "unit": 0
                        }],
                        "all": 1,
                        "state": "off"
                },
but i can only be controlled manually via the webgui. if i use it in a rule, the "all" option is not sent (and the device is not working)
for example:
Code:
"balkontuerauf": {
                        "rule": "IF balkontuer.state IS off THEN switch DEVICE gong TO on AFTER 3 SECOND",
                        "active": 1
                },

any way to get around this problem?
 
Reply
#2
What is the config of your "balkontuer" device?
 
Reply
#3
(06-25-2016, 05:05 PM)Niek Wrote: What is the config of your "balkontuer" device?
this is the config.
Code:
"balkontuer": {
                        "protocol": [ "intertechno_old" ],
                        "id": [{
                                "id": 2,
                                "unit": 2
                        }],
                        "state": "off"
                }
 
Reply
#4
So your rule should be executed 3 seconds after the transition of the state of "balkontuer" from "on" to "off".
That means that the action will not be executed (the execution of the rule will be stopped) if "balkontuer" reverts to "on" within 3 seconds. Could that be the case here?

If not you can try to analyze what is happening by running pilight in debug mode (pilight-daemon -D).
 
Reply
#5
(06-27-2016, 08:53 AM)Niek Wrote: So your rule should be executed 3 seconds after the transition of the state of "balkontuer" from "on" to "off".
That means that the action will not be executed (the execution of the rule will be stopped) if "balkontuer" reverts to "on" within 3 seconds. Could that be the case here?

No, thats the desired behavior.

(06-27-2016, 08:53 AM)Niek Wrote: If not you can try to analyze what is happening by running pilight in debug mode (pilight-daemon -D).

I think, the relevant output is the following.

Code:
[Jul 01 08:01:45:946594] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":1,"devices":["gong"],"values":{"timestamp":1467360105,"state":"on"}}

[Jul 01 08:01:45:946748] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":1,"devices":["gong"],"values":{"timestamp":1467360105,"state":"on"}}
[Jul 01 08:01:45:947658] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":1,"devices":["gong"],"values":{"timestamp":1467360105,"state":"on"}}

[Jul 01 08:01:45:947846] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":1,"devices":["gong"],"values":{"timestamp":1467360105,"state":"on"}}
[Jul 01 08:01:45:948228] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_switch","message":{"id":17242342,"unit":0,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-6ef1a9"}
[Jul 01 08:01:45:948418] pilight-daemon: INFO: started "switch" action for device "gong"

muecke
 
Reply
#6
In the part of the pilight-deamon  output I don't see any activity of your "balkontuer" device, which you defined in your config with the "intertechno_old" protocol.  What happened after this last line you posted?
Code:
[Jul 01 08:01:45:948418] pilight-daemon: INFO: started "switch" action for device "gong"
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [8.1.2] variables in rules -> error terrar 1 476 09-14-2018, 05:28 PM
Last Post: curlymo
  Rules wont work bdb 2 807 08-12-2018, 06:25 PM
Last Post: bdb
  Can't switch Relay device by rules: Error switch.lua:77 wobbi 6 964 07-31-2018, 06:25 AM
Last Post: curlymo
  Strange behavior of rules currock 4 912 06-28-2018, 05:57 PM
Last Post: currock
  feature request: switching rules terrar 7 1,307 05-05-2018, 09:23 PM
Last Post: trader23
  variable "label" not allowed in rules Niek 4 2,567 09-30-2017, 06:39 PM
Last Post: curlymo
  Rules make pilight freeze koos147 5 2,063 05-04-2016, 08:11 PM
Last Post: curlymo
  rules time interval kniazio 8 3,429 03-12-2016, 04:49 PM
Last Post: kniazio
  pilight eventing rules terrar 94 40,097 02-18-2016, 10:21 PM
Last Post: brombeerwilli

Forum Jump:


Browsing: 2 Guest(s)