I have double check this , when thermostat is polling and I'm changing heater setpoint it couses all my zwave devices getting unresponding.
Why ?
When I was using Vera I was able to disable pooling for thermostats, does hubitat give me such possibility ?
I think most of your questions rely on the Driver your using for your thermostats but I have no experience with Thermostats.
Is it a custom Driver ?
I'm using Generetic z wave thermostat
Maybe there is an app for disabling pooling for thermostats ?
I have seen this topis , not usefull for me but thanks for help.
Anyone has different ideas?
what for is this value?
Hubitat does not poll devices automatically, devices are expected to notify the hub when they change state. So in the case of the thermostat driver, and all built in drivers for that matter there is nothing to disable.
When you say polling is set to 3 hours, where is this being set?
I can see on the specific device on the button ,there is like scheduled job and there is pollnode next run (date) and last run (date).
I'm now not at home so I can't send screen. I will do it tomorrow.
I have found solution , this hub is to weak for spirit zwave thermostats , when im changing temperature by lowering deegress "manually" from 28 to 8 , degrees step is 0,5 , so I need to click 40 times temperature down and after that hub stop responding 
Vera controller was far far better , maybe problem is in to small ram memory. Who knows.
Vera Plus 128MB Flash and 256MB RAM. HE 8GB Flash and 1GB RAM.
So there is problem with communication between device and hub
Your devices should have multiple neighbors to route the signal between the devices and the hub. The radios in Zwave devices are very low powered, especially important for battery powered devices. There is no point having a high power radio in the hub, if the devices can't respond to the hub. Make sure you have mains powered devices in your system to form a good strong mesh. How to Build a Solid Z-Wave Mesh - Hubitat Documentation
1 Like
Is that what support have indicated or just your guess ?
Support do not answered my question 
@krzyskonieczny15 your problem is likely to be that your Spirit TRVs are FLiRS devices and need the transmitting device to support "beaming".
Do you have any other mains-powered Z-Wave devices in your HE system? Specifically ones that support beaming?
I'm not sure if the HE hub supports beaming directly, perhaps @mike.maxwell can confirm that ..... what happens in HE if beaming isn't supported directly from the hub? In the case of these Spirit TRVs, if as @krzyskonieczny15 mentions he adjusts the temperature incrementally 0.5 degree at a time, how will HE handle that?
If HE doesn't support beaming then the Spirit isn't going to be woken up to take those commands, so it's feasible that communications would stack up and time out.
With a non-FLiRS TRV, does HE wait for wake-up before transmitting commands? Or does it "try" first, then queue for wake-up ...... then send a flood of all queued commands?
(this is a problem that used to plague Vera for years btw, it was only in the last year or so that it was resolved, somewhat).
1 Like
I couldn’t find your devices in the “compatible device list” so that will always make getting a device working, much harder.
Good to follow some suggestions and advice which comes from other users with similar products to you.
I have multisensor 6 and repeater from aeotec, and aboy 6 switches from neocoolcam. I do not know if this devices support beaming probably not if I have got problem.
