Be careful. a lot of Aux repeaters are sold on Ebay. It has to be a "Main Repeater"
Yep....
Love to just see my problem resolved with Hubitat.
Iām starting to think I may actually require an RMA.
So another update if anyone cares... 
So I soft reset my hub again and removed all the apps including rule machine.
So basically I have nothing. Installed motion lighting and my results of lights are less then or equal to 200msec.
So Iām faced with rebuilding all my rules from scratch because I have no idea where things went wrong.
As of right now Iām using Homeseer since all my rules are already done. Difference is Iām using the Lutron switches exposed through Hubitat instead of using the dedicated Homeseer Lutron app.
My results are about the same time frame for lights turning on. Yes I can get 90msec with Homeseer and the Lutron app, but getting 180-200 msec with Hubitats Lutron intergration isnāt bad at all.
Lots of frustration and headaches trying to figure this out.
1 Like
Update,
Spent hours writing all my rules back into Hubitat and sure enough motion lighting has slowed down and errors are spitting out in the logs that point back to the root of rule machine.
Been working with Bobby.
My general thought is the hub needs replacing.
I was very careful to pay attention to my rules and simplify them this time around and to use the motion lighting app whenever possible.
Back to slow motion lighting and errors that make no sense.
Iām working with support and they do in fact see other issues on their end.
At this point in time all plugins have been removed and darksky has been disabled.
1 Like
Thanks for keeping us all updated. Hopefully others will benefit from what is being learned.
Another update....
I spent some time consolidating some motion rules that checked multiple motion sensors.
Iāve combined these which either turn on a occupancy virtual switch and updated the other motion rules to trigger off this change instead of looking at the same motion sensors.
Lights seem to be turning on around 200-350ms this morning....
Iāve also disabled darksky yesterday. Itās been suggested that it might be locking up the hub database.
1 Like
Just following up. Been running two days with the average motion lighting turning on around 350ms for the most part.
Not bad, seems like it's behaving as it should?
1 Like
Glad to hear you got things back to a good state.
Question on the Homeseer Hubitat plugin:
With say your zwave devices on homeseer and using the Hubitat plugin, are you able to have Hubitat see those devices so that your rules can be ran through Hubitat.
Or is it the other way around or both, to where Homeseer sees your Hubitat devices so your rules must be ran through Homeseer?
Both ends will see the states changes of your devices. Rules can be applied to both systems.
Does that help?
1 Like
Did you have the multiple motion sensors in a motion group, or were you selecting each motion sensor separately in the rule? I have been experiencing the slower motion lighting and hub slowdowns. I am curious about the details of what you were using in past and now present rules to speed things up.
I had a rules that (selected each motion sensor) looked at multiple motion sensors.
-
a rule looking at multiple msās to set my thermostat to away
-
a rule looking at multiple msās to turn on my roomba
-
a rule looking at multiple msās to turn off my Xbox
-
a rule looking at multiple msās to turn off some lights
-
a rule looking at multiple msās to decide when to go to bed
-
etc...
Basically all these rules were doing the same thing. Waiting for no movement with a delay action of 45 minutes.
What I did was created a virtual occupany switch and created a rule to turn this switch on or off when there was no movement for 45 minutes.
Then I updated and combined all my rules to trigger off this switch instead of motion sensors. Except my bed time rule.
I created another rule to pause the bed time rule and to enable it at 11pm and 5am.
Forgot to mention. My occupancy rule I included booleans in my rule to stop it from sending cancel delayed actions if it wasnāt actually running a delay. (Donāt think this one mattered)
Lastly, after doing something like the following, disable all custom drivers and apps. Reboot and start testing out your motion lighting. Watch your logs to get an idea on your motion lighting speed.
Forgot to mention.
Iām now using motion lighting for all rooms with motion sensors, but have most rooms to disable on during all modes.
I did this for a couple reasons, but mainly to speed up rule creations. I re-created every rule trying to narrow down my problem.
Just want to throw something out there.
Hubitat is soooo much nicer to work with then Homeseer!
The UI is much easier to work with an has excellent apps like motion lighting, HSM, Simple Lighting...
Are you still having issues with the speed of motion lighting, or did you get that resolved?
If you did get that resolved, can you tell us what you did to get it resolved, in order to help others?
See my post above regarding updating my motion rules to use a virtual switch as a trigger instead of a bunch of rules looking at the same motion sensors.
I think if the hub was beefier you wouldnāt have to worry about this. However, from a stand point of writing rules, it makes more logic sense to use a virtual occupancy switch. At least I think so..
That seemed to do the trick, but depending on your problem donāt rule out doing a soft reset.
Plus the number one thing to do first is to disable all custom apps and drivers before attempting the above.
Just an update on this...
Since I made these changes everything has been working well.
Been 13 days since I made these changes.
Thanks for the update. I believe many of us (or at least me) will benefit from your efforts.
Hope so...
My honest thought is multiple rules looking at multiple motion sensors slowed things down...
Kevin,
Are you implying there security-related deficiencies with Zigbee and Z-Wave?
If so, what are they?
