Also, I don’t know since when, the automations that you carry out with the AND condition of 2 or more buttons are executed as OR. Any button you press in the combination triggers the automation.
This worked fine, since I had it done to control STHM.
I have been testing again and I see:
When it is inactive for a long time, it must be asleep and you have to do a long press to wake up, then it always works fine.
For “Hold push”, you have to press it as 1 sec, if you do it longer it interprets it as “pressed down” and when you release the button it sends a “Hold push”. This makes it difficult to use these two actions, they can be mixed.
Another funny thing is that it seems like the working condition comes and goes throughout the day (like right now…even though I can clearly see that the KeyFob is doing something by the quick green blink when I press a button, nothing happens in the system), and I haven’t been able to pinpoint any sort of correlation with anything else. I wonder if it’s just going to sleep like you mentioned.
After running the Z-Wave Network Repair, no change. None of the button presses are doing anything other than blinking the KeyFob green light. Well…I mean, there is some signal getting through into SmartThings (I can see it when it hits the logs in webCoRE, and intermittently in ST Live Logging), but no successful automations.
Immediately after typing EDIT1 above, I went back and tried again, and this time, 3 of the 6 button presses (once on each after waiting for reaction) resulted in successful automations. I have always HATED intermittently successful automations. Do you think this is due to something goofy with the KeyFob, or what?
For your information, I have received a response to the support team, about the problem that the actions are shown in the automations without indicating to which button each one action.
“Reported our Engineering Team for further review and resolution. Hopefully, they will implement a hotfix if required.”
About the AND condition fails in automations they have not said anything.
I really appreciate your willingness to walk through some of this with me.
OK…I went through all of that to test it to see whether SmartThings is even seeing the button presses, etc, and it is indeed seeing all of them.
However, only some of the related automations I’ve created in webCoRE are working.
Part of the problem is that I’m trying to use this KeyFob to turn lights on and off, etc in Alexa.
Since there is no native integration, and since Alexa can only react to sensor activities in SmartThings, I had to create a set of simulated contact sensors in SmartThings to represent each of the buttons (I’ve only done the main 6 so far) on the KeyFob.
Then I created Pistons in webCoRE (one each) to ‘translate’ button presses to simulated contact sensor actions.
Most of this is working, but now I have another problem (which may require a separate thread to ask for assistance with that)… Two of the simulated contact sensors are showing up as “Checking…” within the SmartThings mobile app, and they are the ones that aren’t working.
I deleted and then recreated one of them (AND went through all of the steps to make sure it is available in webCoRE AND Alexa), but the new one still says the same thing (“Checking…”) in the SmartThings mobile app, and is also not working in either webCoRE or Alexa.
I can’t contribute anything about webCore, I don’t even want to try it, I’m sure was going to love it and I’d be doing pistons all day, hahaha.
As long as I can do everything I need with automation and smart apps, I don’t want any more trouble.
I did reply seeking more information about the use case for this, since usually on a Remote only one button at at time can report “Pressed” (or “Held,” “Double Pressed,” etc). It seems like that part of my response was not sent to you.
This is new feedback for me, totally willing to report this portion (already reported the missing “Button” component labels as Fiona mentioned to you). I didn’t really understand very well the use case for this or if it would actually work as expected.