+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Support (https://www.comfortforums.com/forum-2.html)
+--- Forum: Problems & Troubleshooting (https://www.comfortforums.com/forum-36.html)
+---- Forum: Troubles (https://www.comfortforums.com/forum-77.html)
+---- Thread: Reliability problem (/thread-3505.html)
Pages:
1
2
- emabonacchi - 09-05-2013
Hello and first of all scuse me for my bad english.
I am using Comfort from some years and i am happy because i think it is a very good system.
But in last months, i am seeing a strange behaviour.
I try to explain what is happening:
My Comfort, is connected via rs232 to a pc running Homeseer with pjcComfort2 plugin.
Very often, i open or close some windows or some doors and Homeseer does not see this. Some times, i arm or disarm system and Homeseer does not see this.
Initially, i think it was a Homeseer or pjc plugin problem, but now i am sure it is not, because yesterday i have done some experiments polling Comfort.
I have seen a window set as closed in Homeseer while it was really opened.
Well, polling the Comfort inputs from Homeseer, the window was reported as close.
This mean it was not Homeseer \'hearing\' wrong, but Comfort \'speaking\' wrong.
Closing window and opening it again, now, this was seen as \'opened\'.
It seems Comfort sometimes does not \'speak\' to homeseer well.
Can it be an \'ucm\' problem? Maybe \'ucm\' is defective?
How cai isolve this problem?
I hope i have explain and scuse me again for my bad english.
Thank you
Ema from Italy
- ident - 09-05-2013
When you encounter the problem where Homeseer is not getting the correct zine status, check the zone status from Comfort
Use Comfigurator > Zones and check get status box. See if it corresponds to the actual state
In monitor IO, use the I?ZZ command where ZZ is the zone number in hex
eg I?10 means Get Input state of zone 16
the reply is I?1001 for open I?1000 for closed
Comfort should not report the wrong status of zones. I am quite confident of that from our experience
- emabonacchi - 09-05-2013
Hello Ident and thenk you for the reply.
I have used the command \"Z?\" and the result is \'closed\' while the window was really opened.
Same problem, often occours when i arm/disarm the system. Often the arm/disarm status is not correct (for example, the system is armed but Homeseer sees it as disarmed).
- ident - 09-05-2013
What about I? command?
You mean it is different from Z? command which reports all the zones
Does comfort security check F32 report the zone open or closed?
show the full monitor IO result of I? and Z? so that we can verify
when you say armed status is incorrect, what cmmand is homeseer using?
Can you check that Comfort M? command gives the right or wrong result
- emabonacchi - 09-05-2013
I have not used the \"I?\" and \"M?\" commands, so, i will try and will tell you the result.
.....I am suspecting a ucm communication problem.
- emabonacchi - 09-05-2013
Well, test done. This is the result:
-Window in zone 24 is really open.
-In Comfigurator Zone, checking the \'status box\', the window is correctly opened.
-In \'UCM i-o monitor\', sending the command \"I?24\", the result is \"I?2400\", so, it\'s a wrong response.
So, this is an ucm problem, is it right?
- ident - 09-05-2013
The I? command like all commands uses hexadecimal notation
For zone 24 you must enter
I?16 not I?24
- emabonacchi - 09-05-2013
....ok, scuse me for the error.
The result is
>I?16
<Ok
<I?1600
It results closed.
- ident - 09-05-2013
I am sorry I did a wrong caluclation
zone 24 is 18 hex not 16
so the command is I?18 not I?16
24 decimal = 16 + 8 = 18 hex
- ident - 09-05-2013
Use a online decimal to hex converter eg http://www.binaryhexconverter.com/decimal-to-hex-converter