From 1a50f8f5480ba7a357997adac10447730dbdc3da Mon Sep 17 00:00:00 2001 From: sveip Date: Sat, 26 Jan 2019 13:03:58 +0100 Subject: [PATCH 1/4] Clarify polling. --- source/_docs/z-wave/devices.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown index 92d43f00948..0364575cd6e 100644 --- a/source/_docs/z-wave/devices.markdown +++ b/source/_docs/z-wave/devices.markdown @@ -61,7 +61,9 @@ As long as your device lists Hail or Association in its Controlled Command Class Where a device doesn't send updates on status changes to the controller, you can work around this by using a thing called Polling. That causes the controller to ask the device to provide an update on all its sensors and states. This will cause a lot of traffic on the network, and if you poll too many devices too quickly, you can effectively break your Z-Wave network. Polling should only be used where there is no other choice, and you should use as large a polling interval as possible. Ideally you should replace the device. -For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled, if a device can receive and acknowledge the poll within one second, then it will take 10 seconds to complete the polling list, which leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. +For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. + +Polling is by default disabled and needs to be anebled per device. You can also specify the interval by setting the *polling intensity* of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. ## {% linkable_title Central Scene support %} From 51e01ee76ba2ab57d4ffafd4086e5b3e587fdcc0 Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Sat, 26 Jan 2019 14:01:58 +0100 Subject: [PATCH 2/4] Update source/_docs/z-wave/devices.markdown typo Co-Authored-By: sveip --- source/_docs/z-wave/devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown index 0364575cd6e..baa41eeef8b 100644 --- a/source/_docs/z-wave/devices.markdown +++ b/source/_docs/z-wave/devices.markdown @@ -63,7 +63,7 @@ Where a device doesn't send updates on status changes to the controller, you can For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. -Polling is by default disabled and needs to be anebled per device. You can also specify the interval by setting the *polling intensity* of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. +Polling is by default disabled and needs to be enabled per device. You can also specify the interval by setting the *polling intensity* of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. ## {% linkable_title Central Scene support %} From 375b7817cc89ca692e8783139c5029027ab6727f Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 31 Jan 2019 14:03:11 +0100 Subject: [PATCH 3/4] :pencil2: Tweak --- source/_docs/z-wave/devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown index baa41eeef8b..5a94d330415 100644 --- a/source/_docs/z-wave/devices.markdown +++ b/source/_docs/z-wave/devices.markdown @@ -63,7 +63,7 @@ Where a device doesn't send updates on status changes to the controller, you can For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. -Polling is by default disabled and needs to be enabled per device. You can also specify the interval by setting the *polling intensity* of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. +Polling needs to be enabled per device. You can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. ## {% linkable_title Central Scene support %} From 95029cb1d71bad04a08c9845162a0977d12710ff Mon Sep 17 00:00:00 2001 From: Klaas Schoute Date: Thu, 31 Jan 2019 14:03:49 +0100 Subject: [PATCH 4/4] :pencil2: Tweak round 2 --- source/_docs/z-wave/devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/z-wave/devices.markdown b/source/_docs/z-wave/devices.markdown index 5a94d330415..e20afed3536 100644 --- a/source/_docs/z-wave/devices.markdown +++ b/source/_docs/z-wave/devices.markdown @@ -63,7 +63,7 @@ Where a device doesn't send updates on status changes to the controller, you can For example, with `polling_interval=60000` (which is the default) if you have 10 devices that are being polled at every interval, and each polling takes one secound (request/response round trip), then it will take 10 seconds to complete the polling list. This only leaves 50 seconds left for normal traffic. The more devices you poll, and the shorter the interval, the less bandwidth that's available for normal traffic. -Polling needs to be enabled per device. You can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. +Polling needs to be enabled per device, you can control this through the *polling intensity* (interval) of the device. See the [Node Management](/docs/z-wave/control-panel#z-wave-node-management) docs for details. ## {% linkable_title Central Scene support %}