No that’s the funny thing.
I’m using Hubitat with iris v2 motion sensors and tying it back to Homeseer via maker API.
Hmmmm 
Have you tried performing a Soft-Reset on your Hubitat hub? That seems to restore performance for most users who have issues.
Yep less then two weeks ago.
@mik3, can I summarize?
You have the following. ALL running through Hubitat
Iris V2 motion sensors
Lutron Connection
Running Motion Lighting through Hubitat "seems slow".
Now same hardware all running through Hubitat BUT the automation is controlled via HomeSeer with the Hubitat Plugin and the automation "seems faster".
Correct?
So the different piece is the "Rules Engine" being a HomeSeer event versus a "Simple Lighting" rule in Hubitat?
So even with the layer of HomeSeer -> Hubitat Plugin -> Hubitat Maker API the automation of turning on the light is faster than running native/local on Hubitat with Simple Lighting rules?
Am I following this correctly?
Yes most of that is right.
Homeseer to Hubitat for motion changes only. Homeseer talking directly to Lutron equates to faster motion lighting.
Homeseer to Hubitat for motion lighting and using Hubitats Lutron connection is slower.
Hubitat doing it all natively is slower but the same as Homeseer using Hubitats Lutron connection.
So my assumption is the lutron piece.
Now to gain some grins.
A full day of nursing a pulled back and working on Homeseer and Hubitat. I just reverted everything back to Hubitat.
I will be watching what the new Homeseer has to offer but I felt to mimic everything I have today still required Hubitat. The two main pieces I use the most are the following.
- Lutron hold down buttons
- Alexa text to speech and contact routines
- hsm
- ecobee (not going to pay for a plugin when hs4 will offer it for free)
But the motion lighting sure bugs me. Why it’s slower...
I would imagine a soft reset would of reinstalled the Lutron app.
Not sure why the speed difference as both are using the same telnet integration to Lutron.
I had a similar experience with HomeSeer vs ISY during my explorations where HomeSeer Events were much faster turning on lights versus the ISY Programs turning on the same lights. I dug into it and it was a difference in how each was handling the command delay before execution. I did some tuning on the ISY and now it's just as fast if not faster on execution of programs to turn on the lights.
I wonder if there is options to fine tune the command delays under Hubitat?
dunno.... ping support and ask?
Sent them off an email for results.
there isn't, we send commands ASAP...
Is there a buffer/timing or anything from sensor change to RM event firing to send the command to Lutron?
Don't know.
But using Hubitat's motion sensor and Hubitat's Lutron intergration, the delay is there.
But again, if I use Hubitat's motion sensors via maker api and Homeseer's lutron plugin, it's instant.
I think the delay or problem is with the Lutron plugin.
Mike just caught this reply.
Why such a delay? Do we know where the sticking points would be?
Question for you... When you go into a Lutron Switch/Dimmer device on your Hubitat Hub, and Click the ON or OFF buttons, do you perceive any delay with the actual Caseta light switch changing state?
When I do that test, the actual visible light changes state almost instantly. Less than a tenth of a second would be my guess.
That’s a good point.
I will test when I get home.
But I want to say it’s pretty instant if I go to the devices and I initiate an on command.
I will report back later.
Instant when doing it from the device page.
Huh, so maybe the delay I’m seeing when using Hubitat’s maker API Lutron plugin is the slight delay due to communication back and forth.
Either case, using Homeseer and the Hubitat maker API to motion sensor is instant.
Rule machine ?
Any other suggestions to test ?
Is "Hubitat's Maker API Lutron plugin" a HomeSeer plugin? Hubitat's Lutron app is a native, stock app and does not use the MakerAPI.
I have previously suggested seeing if your delay exists on anything besides the first execution of any particular app (e.g., set up a new Simple Lighting child app to turn the lights on with motion an off with inactivity, ideally with as much logging on the apps and devices as you can enable so you can look at live or pasts logs to see where the delay is happening, if any). Trigger the motion sensor once after setting up the app, then wait a few minutes (after it turns the lights off) and try again. This would help see if there's a consistent delay or of it might be something related to Groovy/Java complilation on first run.
Same results. I did two passes.
I’m 2 to 4 feet into the bathroom before it turns on.
Here is some videos for reference.
Don’t mind the ugly floor. 
Hubitat
Homeseer
That's helpful, but if you turn on sufficient logging, can you tell where the delay actually happens? For example, is it late sending the command to Lutron, or does it appear to send it (or log that it is) soon enough and it just takes a while to get there? It could be at another point, but those are my likely guesses based on what you're describing.
To clarify, I'm thinking about the "Logs" item in the left-hand menu (live would probably be easiest but you can also look at past). Some apps and drivers may need debug and info logging enabled (usually an option you have) to show enough useful information here.
