ZWave Switch -> to ZWave Outlet - Simple Automation Rule SOOOO slow

You could always try a SOFT RESET to see if your hub is spending cpu cycles dealing with some sort of database corruption issue. It is an easy, non-destructive process which has helped many hubs restore peak performance.

https://docs.hubitat.com/index.php?title=Soft_Reset

Be sure to follow all of the steps very carefully.

2 Likes

update...
installed innovelli red switch (really like these)
made no real difference (kinda would say ofcourse)
for the most part its responsive, but every now and then a DELAYED response...

its just horrible...
i just walked into room, pressed switch, the light turned on...
did something in room, pressed off on the switch... and long time later it went off
Hubitat, NOT GOOD
if you look at 10:10:12 the rule ran, but the action didnt happen till 10:10:29
17 seconds!!
now also look concidently app:41 (the Thermostat Scheduler App) got in there at 10:10:00
i have that app set to refresh ever 5 mins...
i would think it wouldnt take long to get the data, and be done so that another zwave action can happen
but maybe this is it... its an OLD Radio TStat CT100, im open to replacing it... it just came with the 2gig setup when i purchased home

thanks all!

dev:40  2020-05-05 10:10:29.434 pm infoOffice Torchiere Lamp was turned off [digital]
app:227 2020-05-05 10:10:12.442 pm infoTurn On Office Torchiere Lamp when Office Torchiere Lamp Switch turns on anti-Turn On
dev:41  2020-05-05 10:10:00.124 pm inforefresh...
dev:40  2020-05-05 10:09:45.513 pm infoOffice Torchiere Lamp was turned on [digital]
app:227 2020-05-05 10:09:45.121 pm infoTurn On Office Torchiere Lamp when Office Torchiere Lamp Switch turns on Turn On

I will say @mitchjs that this thread has been an interesting read as you have been tracking down and eliminating the cause of your Hub's slow performance.
It sounds like that thermostat might be the issue particularly if it is NOT a ZwavePLUS device as it seems to fit in with your observation that the delays are somewhat random in occurring.
Can you disable / halt the thermostat functions and retest ??

Yea I’m gonna do that, I’m getting from the wife, “don’t mess with my ac” but for a few days I can live without the scheduler

1 Like

more info.. .look how long it takes to get the information from the tstat
using the "Generic Z-Wave Thermostat" driver... but 15seconds
to get 10 things... man thats slow...
question is.. if during this time... which ill test... if i touch my wall switch...
what happens... delay?

dev:225 2020-05-06 01:10:15.558 pm infoCT-100 thermostatSetpoint is 74°F
dev:225 2020-05-06 01:10:14.459 pm infoCT-100 thermostatFanMode is auto
dev:225 2020-05-06 01:10:12.569 pm infoCT-100 thermostatOperatingState is cooling
dev:225 2020-05-06 01:10:10.470 pm infoCT-100 coolingSetpoint is 74°F
dev:225 2020-05-06 01:10:08.412 pm infoCT-100 heatingSetpoint is 70°F
dev:225 2020-05-06 01:10:06.418 pm infoCT-100 thermostatMode is cool
dev:225 2020-05-06 01:10:04.532 pm infoCT-100 humidity is 53%
dev:225 2020-05-06 01:10:02.368 pm infoCT-100 temperature is 75°F
dev:225 2020-05-06 01:10:00.371 pm infoCT-100 battery is 100%
dev:225 2020-05-06 01:10:00.114 pm debugrefresh() was called

You don't have any of your Z-wave devices 'paired securely', do you? (Except for Door Locks and Garage Door Openers which require it.) Securely paired Z-Wave devices use ~3x the bandwidth of a non-securely paired device.

Is there a reason you have to periodically refresh your thermostat? Shouldn't it update Hubitat on its own when data has changed?

2 Likes

nothing that im aware of is secure paired... shame this info not displayed nicely in maybe the zwave section...

i dont know if it updates on its own... its an older CT100, oddly in the thermostat scheduler there is no option to not have it refresh (i could just make it a long time, every 60 mins)
i can make a change on it and see if it shows up in log...

Ahhh, that's the piece I missed. The Tstat Sechduler App is the one doing the refreshes.

I use a pair of Ecobee3 Lite thermostats that I bought at a deep discount via the power company's 'energy saver' website/storefront. They are WiFi, but they work well and all scheduling is done within the tstat itself. While I have them integrated with Hubitat via Hubitat's cloud-2-cloud integration, I really don't control them via Hubitat. I just wanted the data feed for my InfluxDB/Grafana displays. The newer Ecobee's, like the 3Lite, are also HomeKit compatible, if that is of any value to you.

There are quite a few threads regarding thermostats here in the Community. Some prefer Z-wave, some like Zigbee (e.g. Lux KONOz), and others prefer WiFi. They all have their pros and cons. I like the Ecobee (WiFi) since I can still control it remotely via its native app or HomeKit even if Hubitat is down for some reason. For me, it's the best compromise of features.

@ogiewon, seems that if i do change (at lest the setpoint temp) i get the info sent into hubitat
so.. i prob dont need that 5 min, refresh in the scheduler... i can set it to say 30 mins
(as there sees to be no option for none)

i like the look of the ecobees, but i sure do want hubitat control...
i want to avoid 2 apps, key is "wife" friendly and need all home automation in one app on the iphone
and really she only uses, on/off and set temp... ie im too hot, and lowers temp :slight_smile:

im not familiar with hubitat's cloud-2-cloud
and i dont want to run another application on some dedicated pc... i purchased hubitat to do it all, and consolidate

now that i set refresh to 30 mins... im going to keep eye on delays
today.. i went into my office, pressed on and off a few times, no delay
(well about 1 sec and thats ok)

2 Likes

No extra hardware required. I was simply referring to the fact that Hubitat's built-in integration with Ecobee relies on using Hubitat's Cloud Server to talk to Ecobee's Cloud server. Nothing custom. Fully supported by Hubitat.

ah... now i might be interested in a ecobee :slight_smile:
im looking at the GoControl Zwave, and even the vivint SCT200 zwave
but not that i set the refresh to 30 mins, maybe that was blocking zwave a bit

2 Likes