Posted: Wednesday Sep 25th, 2024 07:06 am |
|
21st Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
If the option is not available it means that you may not be cionnected to the Internet. Pleaser checvk your internet connection. Also try 2 steps Download firmware upgrade to a folder and after that Upgrade from Local file, select the file that was downloaded. You also need internet con ectiion
|
Posted: Wednesday Sep 25th, 2024 08:38 pm |
|
22nd Post |
Posted: Thursday Sep 26th, 2024 02:52 am |
|
23rd Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
Can you enter U? in the Monitor I/O window, and let me know what is the reply
|
Posted: Thursday Sep 26th, 2024 07:17 am |
|
24th Post |
Posted: Thursday Sep 26th, 2024 07:30 am |
|
25th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
U?0A07E1110100 meaning is UCM Firmware 7.225.
The ucm firmware has been ugraded correctly, but for some reason you are not seeing the correct version. Usually scanning for modules again will show the correct versions. You can go ahead with upgrading the Controller firmware to 8.008 now
|
Posted: Thursday Sep 26th, 2024 08:06 am |
|
26th Post |
Howser
Member
back to top
|
While trying to upgrade to 8.008, am getting the error below.

|
Posted: Thursday Sep 26th, 2024 10:58 am |
|
27th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
Sorry about that . Your comfort is not the Arm processor so the file that I sent is not cmpatible. The possible bug only applied to the Arm processor
|
Posted: Monday Sep 30th, 2024 11:24 am |
|
28th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
We have managed to duplicate and fix the bug.
This happens when a Virtual Input is activated, and while still activated, a physical (non-virtual) zone comes on - This causes a zone trouble for the physical zone which immediately is restored (ie zone trouble is restored). Note that this may not always happen.
Apparently this bug has always existed since the introduction of Virtual Inputs. It rarely happens so had not been reported until now.
The firmwareare 8.009 will fix this.
Many thanks to Howser for bringing this to my attention
|
Posted: Wednesday Jan 29th, 2025 06:13 pm |
|
29th Post |
Howser
Member
back to top
|
This is another issue, but it might be related to this issue.
The virtual input on zone 81, when it there is an alarm trigger, the ucmPi reports this as zone 51. I have nothing connected to zone 51.
Event Logs.

UcmPi

Last edited on Wednesday Jan 29th, 2025 06:15 pm by Howser
|
Posted: Thursday Jan 30th, 2025 01:20 am |
|
30th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
I tink your zone number in the payload is in hexadecimal, ie 51 Hex is 81 in decimal
|
Posted: Thursday Jan 30th, 2025 08:02 am |
|
31st Post |
Howser
Member
back to top
|
Zone name in the payload shows Zone51
 Last edited on Thursday Jan 30th, 2025 02:18 pm by Howser
|
Posted: Friday Jan 31st, 2025 01:04 am |
|
32nd Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
I believe the zone 51 is in hexadecimal so it is actually 81 I am not familiar with how the contents of the payload are configured. Try another zone eg 21 and check if the payload shows zone 21 or zone 15. That will tell you if the contents are hexadecimal or decimal
|
Posted: Sunday Feb 2nd, 2025 06:54 pm |
|
33rd Post |
Posted: Monday Feb 3rd, 2025 01:53 am |
|
34th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
Have you upgraded the firmware to the latest version?
|
Posted: Monday Feb 3rd, 2025 06:35 am |
|
35th Post |
Posted: Monday Feb 3rd, 2025 06:45 am |
|
36th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
I have just configured zone 81 as a virtual input. then activated and deactivated it, and I can see that zone 81 is turning on and off as expected, see below Monitor IO
> I!5101
< OK
< IP5101
> I?5100
< I?5101
> I!5100
< OK
< IP5100
So I beleive that your problem may be due o the software running in ucm/Pi or node red
|
Posted: Monday Feb 3rd, 2025 07:44 am |
|
37th Post |
Howser
Member
back to top
|
It is only when the zone triggers an alarm, then we get zone 51 from the ucmPi Alarm Status.

|
Posted: Tuesday Feb 4th, 2025 05:03 am |
|
38th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
I have tested Zone 8 in alarm It does not cause zone 51 to be reported.
< PS00
< SM000040
< SM000140
< MD02F0
< AM09F0
< KL01000000
< S?00
< DT2025020412571800
< AL130000BF02F0
< KL01000000
< SM000140
< SM000000
> I!5101
< OK
< IP5101
< AM0051
< KL02000000
< S?03
< DT2025020412572500
< AL010303650151
< SM000140
< SM000140
> I!5100
< OK
< IP5100
open Monitor IO and create the alarm then save the monitor IO as above
This is certainly a problem with Node Red or the configuration.
I suggest to change to Comfort with Home assistant on Raspberry Pi, see http://www.comfortforums.com/forum143/
Unfortunately we are not able to support Node red on UCM/Pi as that as done by Alphawerks, and they are not contactable
|
Current time is 06:25 pm | Page: 1 2 |
|