Let's Control It

alexander90

I found a solution to this problem, although it is not my favorite ... At first I didn't know that in the new engine the rule name had to be the same as the event. So to stay with this example "W # Value". Only then is the rule actually carried out ... This does not change the problem that...

alexander90

Okay, but it's funny that the original threat gets a working rule.

If I create a dummy, I can also change it using the taskvalueset.

As soon as I do this in a rule it doesn't work. I don't know where to start. Can you take a look at it via anydesk?

alexander90

Something is completely weird here. If I enter the command: "TaskValueSet 1,1,0" via "Tools - Command" it doesn't change anything under my Task 1 RFID.
(In my Setup the RFID Task is 1 and not 2)

: espeasy taskvalueset.jpg (147.51 KiB) Viewed 17836 times

alexander90

Shardan wrote: ↑11 Feb 2020, 19:11 Try to add a "taskrun <task/devicenr>" after taskvalueset

Code: Select all

On W#Value do
 if [W#Value]>0
  timerSet,1,10
 endif
endon

On Rules#Timer=1 do
  TaskValueSet 2,1,0
  taskrun,2
endon

This is not working

alexander90

can it be that this is no longer possible with the current mega version? I cannot change the RFID value via taskvalueset. All that's left is to change a dummy.

Search found 5 matches

Re: How to reset the RDIF Wiegand code

Re: How to reset the RDIF Wiegand code

Re: How to reset the RDIF Wiegand code

Re: How to reset the RDIF Wiegand code

Re: How to reset the RDIF Wiegand code