+- 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: Using VeraLite to associate with comfort virtual node (/thread-3993.html)
- lwillerton - 10-10-2014
Hi
I have done a physical association and the PIR triggered the light it was associated to.
So I have downloaded homeseers trial again and added my aeon labs z-stick 2 as a secondary controller.
When the network transfer took place I got this information
Oct-09 17:39:38
Z-Wave Warning
Node 25 supports the MANUFACTURER_SPECIFIC command class but manufacturer information was not obtained. Cannot continue with this node.
Z-Wave Warning
Node 25 supports the MANUFACTURER_SPECIFIC command class but manufacturer information was not obtained. Cannot continue with this node.
So I am back to thinking that the virtual node info is missing detail.
I have tried a few groups, I am not sure what the group represents
I have had a little sucsess and I will follow this post with more info via pic\'s
The attached shows node 26 triggered in homeseers but node 25 doesn\'t change state
Cheers
Lee
- lwillerton - 10-10-2014
So in home seers we can see the association seems to to have worked (I did manage to get HS the aeon labs and comfort to work about 6 months ago)
the next couple of pic shows a connection test in for node 25 and 26 which complete sucsessfully, so in theory when node 26 is triggered node 25 should change state, but it doesen\'t.
Therefore, I believe the is a level of comms but there is someting missing overall in the data packets flowing between node 25 and 26
- lwillerton - 10-10-2014
So in home seers we can see the association seems to to have worked (I did manage to get HS the aeon labs and comfort to work about 6 months ago)
the next couple of pic shows a connection test in for node 25 and 26 which complete sucsessfully, so in theory when node 26 is triggered node 25 should change state, but it doesen\'t.
Therefore, I believe the is a level of comms but there is someting missing overall in the data packets flowing between node 25 and 26
- lwillerton - 10-10-2014
pic
- lwillerton - 10-10-2014
pic
- lwillerton - 10-10-2014
I have not yet contacted vera will try over the weekend, but this is the info from my z-wave supplier
Hi Lee,
I\'m not sure that this will work in VERA - not convinced it will work with any Z-Wave environment.
Firstly, lets just confirm terminology as you may be using \'Association\' in different ways.
Association in Z-Wave terms means that you \'pair\' two Z-Wave devices together so that they can communicate directly, without any traffic going through the controller, we have a Knowledgebase explaining this - http://www.vesternet.com/knowledgebase/technical/kb-27
So in this case, it would be an association between the PIR and a dimmer (or relay) - the PIR would detect motion and then turn the dimmer on, then off again when no motion is detected, the example in this guide shows just that - http://www.vesternet.com/resources/application-notes/apnt-15
But in your case you\'re trying to associate it with a virtual device, and I don\'t see how that can work as it is not a physical device. For VERA to add the association, both devices have to be on the VERA network, then VERA talks to the device you wish to associate the PIR with and sets the association in that device (for battery devices they have to be awake to accept this association). But with a Virtual device, this cannot happen as it is not a real Z-Wave device with the correct characteristics.
How is the Comfort Virtual Node shown in VERA - is it shown as a Virtual device or some other device?
If the Virtual node is showing in VERA, then the easy way would be to have the PIR trigger a VERA scene and then the Scene will activate the Virtual node - this is how you\'d do it with a normal virtual device in VERA - we do the same thing for LightwaveRF devices in VERA - you have the Z-Wave device trigger a scene to control the LightwaveRF device as they can\'t speak directly.
Does that make sense?
- lwillerton - 10-10-2014
Oh if I click audit nod 25 I get this info
- leonchue - 10-10-2014
It looks like the virtual node has a bug, concerning the Manufacturer query. We will investigate on this.
Nevertheless, it should not cause any problem on other operations, including the association process.
Can you confirm that the virtual node can be switch off and on, using Vera control (as attached)?
- leonchue - 10-10-2014
\"I have done a physical association and the PIR triggered the light it was associated to.
So I have downloaded homeseers trial again and added my aeon labs z-stick 2 as a secondary controller.\"
The physical association here is done via Homeseers? Not Vera?
\"I have tried a few groups, I am not sure what the group represents
I have had a little sucsess and I will follow this post with more info via pic\'s\"
I have downloaded and read the Everspring SP103 manual. Since SP103 supports only 1 association group with 5 nodes, my best bet will be \'1\' for the Group ID field in Vera. Please try it and let me know.
- leonchue - 10-10-2014
As shown in your attachment, there is an error message (in brown) \"... Node 26 is not a normally listening node, and an attempt to communicate with it has failed....\". So my guess is that the association did not materialised and it is not due to virtual node manufacturer info problem.
Battery operated device has the problem of \"falling asleep\", in order to save power. So likely that Homeseers reported this error, when attempting to associate and the sensor device is in \"sleep\" mode. So what you need to do is to make sure the device stay awaken during the association process.
The SP103 manual says \"The Motion Detector will stay ââ¬Åawakeââ¬Â for ten minutes when changing the status of tamper switch from being pressed to be released or from being released to be pressed to allow time for configuration.\"