10-15-2014, 05:18 AM
10-15-2014, 05:19 AM
For trouble-shooting, change the virtual node mapping to a counter. Write EEPROM. Read EEPROM to confirm changes.
Then trigger VN via Vera/HS again. See if that counter changes state.
Then trigger VN via Vera/HS again. See if that counter changes state.
10-15-2014, 05:32 AM
Nice one...that works I can see the value change from 0 to 255 when the PIR is triggered.
10-15-2014, 05:40 AM
That is great! We are so close now.
Now revert VN mapping back to Virtual Input. Remember to write UCM/Zwave and Comfort.
Now revert VN mapping back to Virtual Input. Remember to write UCM/Zwave and Comfort.
10-15-2014, 06:00 AM
OK done that and back to no status change...I have assigned to input 18 and checked.
10-15-2014, 07:09 AM
lwillerton wrote:
Otherwise, zone 18 operates as what it is, be it security or automation.
Quote:OK done that and back to no status change...I have assigned to input 18 and checked.Did you program zone type for 18 as well? If it is blank, the zone is ignored and status is not updated.
Otherwise, zone 18 operates as what it is, be it security or automation.
10-15-2014, 10:46 AM
Hi,
It looks like I have removed this setting so will give it a go tonight. Will Zone type Monitor N/C or N/O do?
Cheers
Lee
It looks like I have removed this setting so will give it a go tonight. Will Zone type Monitor N/C or N/O do?
Cheers
Lee
10-15-2014, 11:17 AM
lwillerton wrote:
It depends on what you want to achieve.
Monitor N/C or N/0 triggers FamilyCare alarm in all security modes (by default). So I am not sure if that is really what you want.
Maybe you can test with \"SwitchNO\" or \"SwitchNC\" first.
Quote:Hi,
It looks like I have removed this setting so will give it a go tonight. Will Zone type Monitor N/C or N/O do?
Cheers
Lee
It depends on what you want to achieve.
Monitor N/C or N/0 triggers FamilyCare alarm in all security modes (by default). So I am not sure if that is really what you want.
Maybe you can test with \"SwitchNO\" or \"SwitchNC\" first.

10-15-2014, 09:46 PM
It\'s worked thank you so much...so what do you think caused the problem?
10-16-2014, 05:08 AM
lwillerton wrote:
The problem? Initially, it was the unsuccessful association with VeraLite. After that, the virtual input was not validated in Comfort (without setting zone type).
Quote:It\'s worked thank you so much...so what do you think caused the problem?That\'s great.
The problem? Initially, it was the unsuccessful association with VeraLite. After that, the virtual input was not validated in Comfort (without setting zone type).