+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Third Party (interfacing to Comfort) (https://www.comfortforums.com/forum-5.html)
+--- Forum: Zwave (https://www.comfortforums.com/forum-62.html)
+--- Thread: ZWave Setup (/thread-4241.html)
- juwi_uk - 06-29-2015
So I\'m using the latest UCM/ZWave3 firmware.
I setup my mappings to counters and can happily turn on/off from comfort by just setting the counter value associated with the device ID.
So now I want the counter to change when the physical switch is pressed; for that I need a create a virtual node and associate with the physical switch, right?
So now the challenge, both need to be mapped to the same counter don\'t they; Comfigurator only allows the counter to be mapped once so how can I achieve?
I\'m sure it used to be able to map both.
What have I missed. BTW don\'t want to use polling!
Julian
- slychiu - 06-29-2015
Comfigurator has that limitation in zwave mapping of virtual nodes which is being reconsidered
- juwi_uk - 06-29-2015
Thanks.
So at the moment all I can do in Comfort is push a value change to the Zwave network.
You are saying that there is currently no way I can get the Zwave network to tell me if the state is changed via either the primary controller or physical switch?
...or likewise if I can then it rules out setting the value of the counter to send the change; so both are mutually exclusive.
Please can I request someone creates a technote on what we can and cant do with Zwave at the moment to get full bi-directional comms as the manual doesn\'t cover and couldn\'t find anything already on the forum either.
Is it just me or is this all so....oooo confusing! :?
Julian
- slychiu - 06-29-2015
Create the virtual node for the and map if to a another counter, different from the counter that is mapped to the physical zwave node. Asociate the zwave switch to the virtual node. That means when you press the physical switch the value to sent to the virtual node and the mapped counter
This will start the ucm/zwave to poll all the nodes immediately if the Polling is set to 0 (Intelligent polling). Thus even though the virtual node is not mapped to the same counter, it will cause the actual counter to be updated faster
Z-wave is quite confusing. Some of the convcepts are not very suitable for automation interfacing, like the absence of automatic updating of its status. I understand this is due to a patent issue which protects the idea of a device automatically giving status. Shows how ridiculous the patent system can be
- juwi_uk - 06-29-2015
So we need to use 2 counters per Zwave node:
Counter1 = holds status of the mapped to the virtual Device ID
Counter2 = used purely to action/change the value (and mapped to) of the physical device ID?
ie so setting counter1 should report back to counter2 via the virtual node association and activating either physical switch or Primary Remote should also update Counter 2 right?
- juwi_uk - 06-29-2015
Sorry I just need this in plain English as you are confusing the hell out of me at the instructions seem totally conflicting.
HOW does the Zwave network report a status back to me that I can show the light state in a counter. How can this be a shared counter across all switches.
You have made this thing so difficult to setup!
- juwi_uk - 06-29-2015
..and how can it be a common counter anyway as once you\'ve added to the first virtual node mapping it is unavailable for the rest as filtered from the dropdown values!
- slychiu - 06-29-2015
Its best to wait till a new comfigurator comes out to avoid further confusion
- juwi_uk - 06-29-2015
Thanks.
Please, please can you do an illustrated set of steps on the forum as this is really driving me crazy so I need a storyboard to accompany the new Comfigurator version.
Regards
Julian
- slychiu - 06-29-2015
Its no point spending time giving a half baked storyboard which will change when the comfigurator is updated
Just set polling to 0 (smart polling). Comfort will change the polling frequency so that the polling is more frequent when zwave commands are sent or received and become less frequent with no activity. You do not need to assocaite any virtual node for feedback