Polling seams do not work

My network currently contain 36 z-wave devices. I have a pooling issue - for example if I switch applince ON manualy - status will be not updated in Vera.

Is my understanding right that while Vera is pool devices each 10 seconds for my 36 devices the circle will be 6 minutes long? I waited more than that - status is not updating.

What is wrong?

@Axill

What firmware are you running?
You can check in the advanced section, tab “advanced” it will tell you your current firmware.

If you turn on the device from Vera, do you get any error messages? Depending on the location of your devices, Vera can send a command to the device, but it does not receive the response from the device.

If you poll it manually, does it update properly?

Is my understanding right that while Vera is pool devices each 10 seconds for my 36 devices the circle will be 6 minutes long?
I think that's the minimum it can take.

Thank you all for the replies.

I’m running the latest betta 1.1.1245
Commands are running well from Vera, and status is updated fast if I send command from Vera.
The problem is with the status if I switch outside Vera (pressing button on the appliance or using remote) - status did not updated even after 20 minutes.
It is still can be easely updated manualy by pressing “poll now”.

OK; well, then I think it’s reasonable to assume there are no communications issues involved and it is indeed the ‘slowness’ of the polling. Personally, I still want to take a closer look as to, or better yet, have an updated description from MCV about, how the polling currently works; there seem to be quite some parameters that play into it.

I also noticed the same thing. My light status is not updated when pressed at the switch. However vera can control it on and off with no problem (less than 1 second for response). I didn’t have this problem with 1183. It only stated when I went to 1245 and 3.20. I have around the same number of devices and haven’t added or deleted anything since upgrade.

Seeing the same issue on 1.1.1245

GE Dimmer does not update status for a long period of time. Can everyone post their poll settings to ensure we all have the same numbers? In the effected lights as well as the global settings within the zwave settings dialog…

I have 16 devices currently, most are GE Dimmers with 6 Leviton switches built into the leviton controllers.

Mine are
Ge Dimmer -12
Poll this node at most once every: [(blank)]

Global
Number of seconds to wait to start polling: [20]
Only poll a node if the Z-Wave network is idle at least [10] seconds.
Poll a node every [60] seconds.
Unless specified otherwise, poll each node at most once every [10] seconds.

Hi,

Same problem, I have two HSM-100 and I did an upgrade to 1.1.1245, everything was ok and then after a few days I upgraded the zwave firmware to 3.20 and the luminosity and temperature sensors from the HSM-100 stopped working.

I did a zwave repair several times and nothing. The motion sensors work fine.

regards.

Is “Poll this node at most once every” for each HSM100 set to something other than 0? (Mine are at ‘60’.)
And what is “Wakeup interval (seconds)” set to for each HSM100? (Mine are at ‘1800’.)

In response to the OP.
I’ve also seen similar polling issues but I have not taken the time to investigate further as to the cause.

Case in point.
I have a few wall switches that will never update in the UI when they are turned on at the device even after 3+ hrs…
Another instance with outlets that are associated to switches that do update at the UI when turned on at the device but never update at the UI when turned on from the associated switch.

Poll settings via ADD:
PollingEnabled : 1
PollDelayInitial : 20
PollDelayDeadTime : 10
PollMinDelay : 30
PollFrequency : 60

JOD.

Can you post the capabilities of the outlet in question? I wonder if they support associations. Even if they do, they may not send out a status update when controlled remotely.

Man: ACT/HomePro
Mod: ZRR150
Ver: 6,2,24,1,20
Cap:209,140,0,4,16,1,L,R,RS,|37,39,112,114,115,117,134

JOD.

[quote=“oTi@, post:10, topic:168291”]Is “Poll this node at most once every” for each HSM100 set to something other than 0? (Mine are at ‘60’.)
And what is “Wakeup interval (seconds)” set to for each HSM100? (Mine are at ‘1800’.)[/quote]
I tried differents values, right now “Poll this node at most once every” is at ‘60’.
The “Wakeup interval (seconds)” is at ‘600’
Those values are exactly the same in the four instances of the HSM-100 devices (combo device, motion sensor, light sensor and temp sensor)

Regards

My polling seems to work, when i manually flip my Duewi switch, my ivera iphone control shows the correct position of the switch after a minute or so.

My settings are;

PollingEnabled : 1 PollDelayInitial : 20 PollDelayDeadTime : 10 PollMinDelay : 30 PollFrequency : 60

-----edit------

Capabilities 210,156,0,4,16,1,L,R,B,RS,|37,39,114,117,130,134,135, Version 6,2,51,1,0 Manufacturer Duewi Poll this node at most once every 60 seconds (0=never poll, blank=default).

Double checked… that UI4 status changes correctly as well the the remote (ivera/iphone) after aproxx 60 sec.
This is in line with the poll settings.

PollOk 6821

This is also happening to my network. If I switch on a light with another controller it does not update on the vera. I have also noticed something quite wierd!
When I refresh the vera page the device shows its correct status breifly while the page loads but it switches back to the incorrect state once the page loads all the way! I am running .1245 and 3.2 also. It does not seem to help if I change the polling settings but if I do a manual poll then it shows the correct status.

Switching with another controller is different from switching the device locally. You are not likely to get an instant update on Vera when switching with another controller. However, after a while (i.e. many minutes), does Vera show the correct status; or does it never update?

It seems that eventually it updates. It definetly takes far longer than it should according to the polling rate!

OK; good.

It definetly takes far longer than it should according to the polling rate!
So more than the number of devices times 30 seconds? (I think that's the default.)

I have about 36 devices. If it takes 18 minutes to update thats horrible! Turning a device on or off with a secondary controller should not take that long to update.