Device polling

Community Playground General Discussions
1

I have a fibaro door sensor on my backjard door,
And use the temperature sensor to check the room temp in the kitchen.

However, somehow the polling seems not to work properly.
In the ui5 dashboard are no device settings.

Only the sensor itself do have them,
I set there wakeup to 1080 sec and polling to 1070 or 1090 and now leave it blank.
But none of the settings had the effect to get regulary a updated temperature.

Sometime there are gaps for serval hours.
The device itself works perfectly.

Any suggestions on the settings? And where to set them ?

2

On the parent device (the door sensor part) , I would set the polling to 60 seconds. This should ensure that the device gets polled, every time it wakes up.

You can then check the [tt]LastWakeup[/tt] variable on the [tt]Advanced[/tt] tab (and convert it, e.g., on http://www.epochconverter.com/) and see if it wakes up as expected.

3

so as smaller the “poll at least” time the better ?

this is not waking the device up i hope (since is battery operated it wont be that wise).

4

it seems the “default value” is 10800 … thats 3 hours … would fit my data gaps

i set it now to wakeup 1080 sec and poll 60 sec …
lets see in few hours what it make out of it …

5

For battery-operated devices, anything less than the wake-up interval should guarantee the device is actually getting polled when it wakes up.

(If the device wakes up every [tt]W[/tt] seconds, Vera checks to see if she is allowed to poll the device at that time; if the minimum poll interval [tt]P[/tt] has not yet passed, she will skip polling. Thus, with [tt]P[/tt] < [tt]W[/tt], Vera is allowed to poll the device every time the device wakes up. MCV appear to have changed the defaults, so [tt]P[/tt] > [tt]W[/tt].)

6

seems like the temperatur polling need to be set too …

i try this now with Parent device 1080 wakeup poll 60 and the child (sensor) also set to 60

7

seems there is another issue still

with Wakeup interval of 1080 polling of less than 60 sec in both device tabs (see attachement)

i get “sometime” 30 minute data, but most of the time not.

here what i got over the night
time - temp - delay
22:13 - 32
03:44 - 31 - 5,5 hour
08:47 - 32 - 5 hour
09:17 - 32 - 0,5 hour
10:58 - 33 - 0,5 hour
13:16 - 34 - 2 hours

very disappointing …

sometime the 30 minute wakeup seems to work … but alot of data is missing

any clue ?

8

how about a Permanent powered Device ?

i just have the trouble that a Remote switched Switch not update its status to Vera,

any idea how i can force the polling of a device ?

9

never mind … i made a scene called every 2 minutes polling the devices in question.

not such a smart thing but it works (somehow)

10

is there any other way to have a permanently powered device polled in shorter times ?

the scene i made with a 2 minute schedule does greatly distrub the general operation of the vera.

every time something happen, and the device polling gets in between, the action or the poll does not happen.

very poor task management on the MCV Side!!

does anyone has an idea how to have the vera poll a device by itself in shorter times ?

11

in device settings : Poll this node at most once every xx secs
in setup z-wave settings :
Number of seconds to wait to start polling
Only poll a node if the Z-Wave network is idle at least seconds.
Unless specified otherwise, poll each node at most once every seconds.
Poll a node every seconds.

12

the device in question has set polling to 15 secounds (overrides the 60 sec default)

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

with this settings the device simply gets updated remote changes somewhat in between 10 sec. and 15 minutes.
unacceptable for a Alarm switch or anything supposed to trigger other actions …

the manufacturer has no clue, they say it does work, (well it does work but only if node 1 is the only mesh neighbor, and there is NO Retry required to send ack.)

13

this is setting for standard polling in vera. the device when having a alarm should give a signal to vera immediatly and vera answers that. my doorsensor from everspring reacts in like 0,5 seconds and i have standard polling settings in z-wave settings

14

BINGO !

but the device does not do that … well it does (sort of) … as i describe above.

the question still stands “how can i make vera Poll a Device more frequently without messing up the whole system”

15

the question is : how can i convince fibaro to wake up more frequent to pass the data to vera imho
the thing is … when nothing changed in the temperature variable then it does not require to send it to vera

16

thats a simple question with a simple answer.

go to the motion detector assigned with the device (not temperature)
device settings :

Wakeup interval (seconds): set to the time you want the device wake up
Poll this node at most once every: set MUCH lower as the time above … (does not matter since the vera will poll only if the device is really woken up)

there will be still gaps on the data but the device will report changes for sure.

17

yes the wake-up interval … but this drains battery a lot and doesnt make the temp update as it should right ?

18

if the temperature has changed, vera will store it.
the only way to fins out if the temp has changed is to wake the device up.

kinda logic

19

i think i have an idea now how it works :slight_smile:
nevertheless if the fibaro doesnt wake up then its the fibaro that need fixing…

20

mine wakes up every 1800 sec.
uses 4% of the original battery in 3 months.

reports every change accordingly to the settings. no issues at all.