This just started happening a couple of days ago. Two separate rooms, both supposed to have 2 and 3 zones turn on by their respective occupancy sensors. Occasionally it doesn’t happen. What’s really odd is that the keypads in the rooms have buttons configured for those zones and the LEDs for those buttons turn on as if the zones turned on. I checked in the Connect app, it also shows that zones are on at the brightness percentage they are supposed to go to when occupancy is detected. Looking at the actual dimmers, they show that the zine itself is off. It’s as if the signal is sent, keypad and the app think it made it to the dimmer controlling the zone, but it the dimmer never turns on. Makes no sense cause in one of the cases the hybrid keypad controlling one of the zones is also the keypad that has the buttons that show incorrectly lit LED indicator. Same device not getting the command to turn on the zone and turning on LED indicating the zone was turned on. Also, when that happens, it’s ALL the zones in that room. Never happens where only some zones turn on. It either works properly or nothing turns on. Never happens when the room goes unoccupied. That always works correctly, they all properly turn off as programmed. This behavior happens about half of the time. I was suspecting signal issues, but when I had Caseta, the bridge, occupancy sensors and dimmers were all located in the same places and I never had any issues. I figure if Caseta could handle it, RA2 should be able to as well (my Caseta bridge had occupancy sensors linked to it, never officially possible, but it worked very well until lutron plugged that hole).
What should I be looking at? This is a new RA2 install. Don’t have many devices yet, not opposed to rebuilding from scratch. But would like to know what’s causing it.