Communication error - Zwave problem

[slychiu]

In Zwave, each primary controller has its own way of dong things, and its won set of problems, which is a difficult support issue
\"Import Node Info from Controller and scan devices\" seems strangfe. I dont know why they have to import node info when they should be adding devices

[Ian]

It is tricky - but it seems to have worked!

[slychiu]

Is this Homeseer? so that when others have the same problem we have some idea

[Ian]

It is indeed HomeSeer.There used to be a HomeSeer plugin for the Comfort alarm but when HomeSeer changed from version 2 to 3 the plugin was not upgraded.I use the z-wave board in Comfort purely to communicate with HomeSeer.

[Ian]

I have now re-created all the devices I previously had but things do not seem to be exactly the same.As I understand things a Z-wave can either be \'Instant\' or require polling.
This is from the Homeseer help file;\"Instant Status\" is a HomeSeer term that refers to Z-Wave devices which are capable of transmitting their status immediately upon being operated by a human.  Associations and Scenes (see the previous item) are used to set up which node will receive the status notifications.  In the case of many devices, patents may prevent the manufacturer from implementing instant status via associations; if instant status is required for your usage, be sure to check the product carefully to make sure it is supported.  Without instant status, \"polling\" or unsolicited reports are used to send the status of a device to another node.  \"Polling\" refers to the plug-in periodically requesting a status from a node.  Unsolicited reports are where a device may be configured to send a status update at a regular interval, or when a certain status change has been reached.  For example, a light sensor may be configured to send a light level report when the light level changes more than 30 Lux.  For the health of a Z-Wave network, the best way to report status is through instant status.  The next best method is through unsolicited reports because these are only travelling from the node to the destination node (one way), even though they may be transmitted more often than necessary.  The worst method of status updating is polling, because it generates two-way Z-Wave traffic which makes the network busy for a longer period of time; one node requests the status from another, and then the other node responds with its status.
I thought previously the Z-wave devices created by Comfort were Instant on, but this is clearly not the case now in that they only respond when polled.
Should they be Instat On?

[slychiu]

\"Instant On\" is the Homeseer term means you must create a Virtual Node in UCM/Zwave and Associate with your other device so that the change in state of the devicxe is instaly sent to the Virtual Node

You can create a Virtual Node in UCM/Zwave and associate the device, as shown in the manual

For all other devices which dont associate with a virtual node, Polling is used.
UCM/Zwave smart polling wil adjust the frequency of the polling to try to optmise the response time

[Ian]

I have a wired door sensor connected to a Comfort input.In Comfigurator I have an On Response for that Input.The On Response sets a flag.When I open the door the flag is set instantly.I have created a virtual node that is set as a flag, the flag the front door sets.
In the primary controller, Homeseer, I do not see an Instant change. I only see the change when the z-wave node is polled.
For me to program actions following the door being opened I need it be recognised as open by z-wave.
Is there a way to get the z-wave node recognised as Instant On?

[Ian]

I guess that is a No then......

[slychiu]

You can try to associate the virtual node with the device that is polling so it can get  the status immediaytely

[slychiu]

A better way to do this is to create a virtual node on the homeseer
In zone response, On response send a zwave On commmand to the virtual node and vice versa
This should work if homeseer can create virtual niodes