+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Products (https://www.comfortforums.com/forum-3.html)
+--- Forum: UCMs (https://www.comfortforums.com/forum-146.html)
+---- Forum: UCM/Pi (https://www.comfortforums.com/forum-138.html)
+---- Thread: Connection problem with final Alphawerks setup stage (/thread-5164.html)
- OhPinchy - 05-06-2020
Hi,
My UCMs seem to be polling correctly, and the DIP switches on the UCMPi are set to 5, and it is showing up accordingly after a scan, per the attached screenshot.
I have always had an issue with UCM ID = 1, nothing works when I tried to use it. So I thought it was protected.
The issue has regressed to where it was before I hit the reset button on the Comfort panels - I get an invalid login error when trying to connect via the UCM Eth, and a UCM connection issue when trying to connect via the UCM Pi. So something is up!
I have successfully managed to setup NodeRed and have it detecting events from all >60 nodes, which is fantastic!
But I cannot get any reading from the AlarmMode or AlarmStatus nodes - I\'m guessing that may be related to the same issue with connecting and authenticating via Comfigurator, so really need to resolve this blocker.
If I need to go back and try reset the ID of all UCMs, I can try that, but I lost time on it before and it didn\'t work so am wary of doing so unless other possibilities are exhausted.
- slychiu - 05-07-2020
This appears lije some sort of bus conflict or comunication problemCan you try Comfort Bus monitor as described herehttp://www.comfortforums.com/forum20/5171.html
This monitors all the commuications in ComfortPress the Bus Analyse buttonSave all to a text file and paste it here or send to support@cytech.biz
Sometimes people have reported a problem exiting from Comfort bus monitor, ie the monitor is still running. If that happens reset or power off the UCM
- OhPinchy - 05-07-2020
Thanks. I ran Bus Analyse for a few seconds and the text file of the output is attached.
I had to reset the UCM in order to be able to login in order to run the BusMonitor as it was again giving the invalid login error - seems to work for a while after a reset and then the issue kicks in.
- OhPinchy - 05-07-2020
The UCM Pi is now not found, I get a communications error. I did not change anything, just ran the Bus Analyse function, and since then, UCM Pi is unavailable, does not respond to ping, and the LEDs on it are stuck red, indicating error. Hitting all reset buttons on all panels does not change this.
The UCM Eth is now operating smoothly without issue, I can login without issue for first time since installing the UCM Pi, no need to reset the panel frequently as before.
So it seems there is some significant issue at play.
I also had issues with the UCM Zwave - I had that connected an ID set but it just would not be recognised. Just in case that was causing issues, I have disconnected it altogether. I tried changing the dip switches on the UCMPi to another value, but it didn\'t work.
Is this all tied back to the issue of UCM 1 not being the UCM Ethernet? Feels like I have had constant issues with UCM recognition over several months and so really need to bottom it out once and for all so any help is appreciated, and I\'m happy to reinstall/reconnect all UCMs for a fresh start if that helps (not sure how to connect to create the UCM Eth connection initially though).
I have: UCM Ethernet, UCM GSM, UCM Velbus, UCM Zwave, UCM Pi.
I am fine to disconnect the UCM Velbus permanently as despite following the manual steps precisely and trying it with the Velbus bus cable connected to my Velbus system at 3 separate points (to rule out wiring/connection issue), and trying it with 2 versions of the firmware, it just never worked properly and I am not convinced there is not a hardware or firmware issue preventing it from doing so. I\'ve made great progress on the NodeRed side so don\'t need the Velbus UCM module if I can rely on the Pi as that approach is really excellent to work with.
I did find that making changes to dip switches on UCMs with both the dip switch and the LED ID options didn\'t seem to work reliably. Is there any known issues with the dip switches to be aware of, or should that not be an issue?
Thanks
- OhPinchy - 05-07-2020
Current list of recognised UCMs attached.
- slychiu - 05-08-2020
When you change ID using the ID DIP switches, you need to reset the UCM in order to get the new setting in operation. There is no issue with the use of ID switches
Perhaps the UCM/Pi is causing some interference, since you were able to log in after you removed it. The UCM/Pi takes a lot of current so perhaps you should power up the UCM/Pi separately , say from a Slave instead of Comfort or from another 12V supplyThe combined current from Comfort may be too much, as it supplies only 1 Amp
- OhPinchy - 05-08-2020
Thanks. Did the bus analysis data provide any insights?
The UCMPi was already connected to a Slave. But as I happened to have separate 12volt power supply nearby, I connected it to that. I disconnected the 4-wire white cable and connected KA and KB to the Slave, and COM and 12v to my separate 12v supply.
Now I cannot log in to Comfort at all.Failed to connect to UCM. I tried it with and without the ethernet cable connected to the UCMPi and no change.
Busy D2 LED on the Pi is constantly red, ERR LED is not currently on.
- slychiu - 05-08-2020
the bus monitor results was nirmalIf you disconect UCM/Pi from powetr, can you log in on UCM/ETH03?
- OhPinchy - 05-08-2020
When I disconnected UCMPi from power and KA/KB, I could not login via UCMEth03, but then I hit reset on the UCMEth03 and then I could login no problem.
I then tried reconnecting the UCMPi both with the Pi CM3+ inserted and removed, no change (ethernet cable port LEDs do not light unless CM3+ is installed being the only difference). ERR LED on the UCMPi seems to not come on at first but comes on after a while.
I deleted the UCM Velbus and UCM GSM from Comfigurator and wrote module settings to Comfort, leaving only 1 UCM (General for Eth03) remaining. I can reinstall GSM later when everything else is fixed, and will try Zwave UCM after that, but will try keep it simple for now.
Seems it\'s best to set UCMEth03 to ID = 1? I moved all dip switches to On, and hit SW1 Reset (on the UCM06 board, not the UCMEth03 daughterboard - is that correct?). I then changed ID for this UCM in Comfigurator to 1, but got the attached error message.
If UCMEth03 having ID=1 is best practice, I\'d like to focus on getting that working first as I have a sneaking suspicion there may be some complications caused by not having any UCM set to ID = 1 - could that be an issue or do you feel it\'s likely irrelevant?
- OhPinchy - 05-08-2020
Just sharing an update that I tried it again and I did manage to get UCMEth03 recognised on ID =1. It is now the only UCM recognised. UCMPi is connected an dip switch 1 is off, 2-4 are ON, for ID=2. But it\'s not recognised.
In the morning, I\'ll get a monitor and HDMI cable and correct to the UCMPi directly just to ensure the RaspberryPi is functioning as it was before UCM dropped off the Comfort system (i.e. to rule out there being some form of corruption there).
After that, I\'m not sure what else to try, so all ideas welcome!