mis-match between Rules UI and Sensor UI for key fobs, and can't use

[Mishakim]

Update, I see the same thing is reported and acknowledged in the Home Automation section of the forum

In the rules UI, the four buttons on the key fob are listed as Arm All, Disarm All, Panic (True/False), and Emergency (True/False).  In the Sensors tab, the house button results in status "Arm Perimeter", and the star button does nothing.  I also couldn't save a rule in which I tried to use the true or false state for the panic or emergency buttons.  So it seems like the Rules and Sensor's tab are using different info about what the key fob is capable of.

It seems from the sensors UI that at least the first three buttons are single-state (last button pressed is listed state), so I'm not sure what would toggle the true/false state that the rules seems to want (not that I can save such a rule). The Rules I created using arm and disarm list the triggering state as 0 for disarm and 3 for arm.

[LGNilsson]

This has already been discussed in another thread and as I mentioned there, we'll get this fixed. The two left buttons work, the two right don't at the moment.

[Fire69]

Sorry if this is a bit of a topic-hijack, but what rule do i need to create to use the arm button to activate the door and PIR sensors? Can't figure it out...

[LGNilsson]

That doesn't work as yet, currently the  fob is only working as a "dumb" remote.

[chitechguy]

I'd love it if you can select the buttons as a toggle.

[Pradeep]

Regarding the Keyfob, We have already changed according to the requirements, and that will be included in all the future releases. Coming to toggling the buttons, we would decide on that in our design meeting.