I just started setting up a new RadioRA 2 system, and I purchased a Hubitat Elevation to handle the conditional logic and to bridge commands between my new RadioRA 2 system and my older Caseta system. The only thing I've tried so far is getting Radio Powr Savr occupancy sensors from the RadioRA 2 system to control a Caseta switch. It's working, but it's slower than I expected it to be and very noticeably slower than when the sensors were paired directly to the Caseta switch. I even changed the frequency of the RA 2 Main Repeater and sensors (from default 433.6 to 434.2) to make sure there wasn't interference between the two systems based on advice from an older thread.
Overall, it looks like it's generally taking in the ballpark of 550ms between when the motion event is printed and the dimmer update is printed. Does that sound normal? When not including Hubitat in the logic, the time is reduced all the way down to about 150ms. One thing that concerns me is how long the Hubitat seems to be taking for local processing (rules, motion lighting app, etc.). For example, in the screenshot below, why is there 211ms between motion event received (rcvd: DEVICE,33,2,3) and STARTING to send the command to turn the lights on (Setting dimmers [Closet Lights] to 100)? I would expect that once the Hubitat received the motion event, it would be sending out the command to turn on the lights less than 10ms later, not over 200. Is there something wrong with the Lutron integration here, is the processor in the Hubitat just extremely slow, or am I missing something?
Similarly, when using Rule Machine, I have noticed that there is usually about 200ms between when Rule Machine prints triggered and when it prints the action in a (simple) if statement. An if statement shouldn't take that long to run.
They didn't pair to the bridge. They were paired directly to switches / dimmers. A warning though, when you pair them directly to switches, the switches then can't be paired to the bridge either, so the switches will no longer be "smart" apart from being controlled by the motion sensor.
Using Motion Lighting and RA2 Occupancy Sensors, my timing is 246 msecs from motion active reported to RA2 phantom button press (that turns on several loads).
Start with a freshly refreshed Logs page. Trip the motion sensor. Take a screenshot of the logs for the motion sensor, and for Motion Lighting, and for the lights being turned on. Make sure first that logging is turned on for all elements. Post those screenshots. Also show the Lutron Telnet log.
Long and short of it, if I use another product tied into maker API that other HA software turns the light on faster.
The actual time once Hubitat makes the call out to Lutron in minimal. It’s the execution process of when motion lighting sees the active sensor and then reaches out to Lutron. That process is where the delay is happening.
Apples and oranges -- this topic was about Lutron Radio Power Savr occupancy sensors and RA2. Never mind about what I suggested to post.
Break the problem down into elements to find where the time is spent. It is typical for Motion Lighting to take 150 to 250 milliseconds to activate a light, depending on a lot of variables. The motion sensor throws an event, that fires an instance of Motion Lighting, and it sends a command to turn on a light. Each of those steps involves some time.
OK, then contact support@hubitat.com. The "rule machine error" is a database error. Is that new? That's not normal. Is your hub acting slow on other things? Is the web UI slow? Be prepared for the inevitable question of what custom apps and custom drivers do you have installed. One of those could be slowing your hub down. What you are showing is certainly not normal.
OK, that's very odd. This, however, would not have anything to do with your timing issue. Were you doing something with editing or creating a rule, or global variable? At the time of this error occurring?
