Light statuses not updated

[daveoxley]

When a light changes I'm not seeing it reflected in home assistant. I've attached a log from the latest version. I waited until auto-discovery had completed and then updated some lights both from switches and also via home assistant. The status of the lights didn't change from either place. There appears to be no C-Gate Recv (Evt) lines after the sync completes. Also the statuses are all Unknown after auto-discovery.

d72673d5_cgateweb_2026-06-21T01-35-15.051Z.log

[daveoxley]

I'm not sure if this is related or not as I'm pretty new to HA and haven't found an easy way to change the source for the addon on the HA box. But there seems to be some confusion on the event port. In the cgate-install.sh script it's setting the event-port in C-GateConfig.txt to ${event_port} which looks like it's set to 20025.

cgateweb/homeassistant-addon/rootfs/etc/cont-init.d/cgate-install.sh

Line 103 in 0b5be8f

_cgateweb_set_config_key "${config_file}" "event-port" "${event_port}"

However the default port for event-port in C-GateConfig.txt is 20024. 20025 is the load-change-port in C-GateConfig.txt.

#### event-port: 
# TCP port number for the event interface
# Default Value: 20024
# Scope:         global
# Effective on:  restart
###
event-port=20024 

#### load-change-port:
# TCPIP port to use for load change port
# Default Value: 20025
# Scope:         global
# Effective on:  restart
###
load-change-port=20025

[dougrathbone]

Thanks for the log and the event-port note, strong lead. The managed installer writes event-port=20025 into C-GateConfig.txt. In C-Gate the event interface default is 20024 and 20025 is the load change port, so forcing event-port to 20025 likely makes 20025 serve a stream that is not the status format cgateweb parses. Your log fits this: many Could not parse C-Bus event warnings and no lighting status lines.

Since this is managed mode config that persists on /data, I want to confirm before changing it. Can you telnet to 127.0.0.1 20025, toggle a light at the switch, and paste what comes through, and for comparison try 127.0.0.1 20024. A debug level log helps too.

Separately your log shows 401 on the getall path for //OXLEY26/254/56/*, which may be the tree addressing issue from #23. Your project shows as OXLEY26 there but OXLEY in #23, so please confirm the exact project name.

[daveoxley]

Can you telnet to 127.0.0.1 20025, toggle a light at the switch, and paste what comes through, and for comparison try 127.0.0.1 20024.

I haven't worked out a way to do this. I've got a Home Assistant Green box and it seems fairly locked down to remote access. Is there a way of exposing the 20023, 20024 and 20025 ports to the network? Or any other pointers to get onto the box to be able to telnet?

Separately your log shows 401 on the getall path for //OXLEY26/254/56/*, which may be the tree addressing issue from #23. Your project shows as OXLEY26 there but OXLEY in #23, so please confirm the exact project name.

Ah, so for #23 had actually switched to using a remote install of C-Gate 3.7.1 and I changed the project file from OXLEY26 to OXLEY for the remote install. The project name OXLEY26 is correct for this issue. I think the 401 in the log is due to the network sync not having completed at that point maybe?

[daveoxley]

Also, it's probably worth me mentioning that when I switched to the remote C-Gate 3.7.1 install the light statuses are coming through correctly. Not sure that's enough to confirm but the remote C-Gate is running with the default ports of event-port on 20024 and load-change-port on 20025.

[dougrathbone]

Fixed in 1.15.3 (auto-updates). Your comparison nailed it: the managed installer was forcing event-port=20025, which collides with C-Gate's load-change-port (also 20025), the status stream cgateweb reads on 20025. Your remote install worked precisely because it kept the defaults (event-port 20024, load-change-port 20025).

1.15.3 stops the installer setting event-port at all, so managed C-Gate keeps its default 20024 and the status stream stays on 20025, matching your working remote setup. It also strips a persisted event-port=20025 from an existing install so it self-heals on the next start.

Once you are on 1.15.3, restart the managed add-on and toggle a light. Statuses should update now. Let me know and I will close this.

[daveoxley]

I've just migrated back to a managed instance and tested the latest and it's working perfectly. Thanks!