I’ve been struggling with the Aeotec WallMote Quad for some time now, trying to get it to work reliably with my SmartThings setup. Initially, the basic ‘touch’ actions worked as expected, but recently I’ve been trying to incorporate ‘hold’ actions, and that’s where things started to go south.
What I noticed in the API event list was very inconsistent ‘held’ messages. When I ‘touched’ a button, it consistently registered, but when I tried a ‘held’ action, the results were all over the place. Sometimes I’d get the final ‘held’ message, other times not. Without that final message, my programmed actions simply wouldn’t work.
I reached out to Aeotec customer support, but unfortunately, they couldn’t resolve the issue. They mentioned that the multiple ‘down_hold’ events are normal, depending on how long the button is held, but the missing ‘held’ message remained a mystery.
Frustrated, I decided to try the Aeotec NanoMote Quad. To my delight, it worked perfectly from the start. The ‘hold’ actions were consistent and reliable, with exactly the behavior I expected. This was a huge relief after the struggles with the WallMote Quad.
I’m curious if anyone else has had success with the WallMote Quad for ‘held’ actions, or if they’ve experienced similar issues. It would be great to hear if there’s a workaround or if others have found the NanoMote Quad to be a better solution.
In the meantime, I’m sticking with the NanoMote Quad for its reliability and consistent performance. It’s been a breath of fresh air compared to the WallMote Quad’s unpredictability.