Closed Interface Error

[fcmarriott]

Hello - I followed your guide completely - really great stuff!! I was able to get through the entire setup, and I have the CBUS plugin running and was able to add all my lights from a Tags file exported from CBUS Toolkit. I got all the lights added to Homebridge and they all show on my iOS device. However, if I try to turn on / off any lights, they don't actually work.

I'm getting the following error on the Homebridge :

2021-01-21T04:09:43.495Z cbus:client rx event { time: '20210121-150943', code: 754, processed: false, message: '//1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 State=new Previous=sync Reason=Interface Closed', type: 'event', raw: '#e# 20210121-150943 754 //1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 State=new Previous=sync Reason=Interface Closed' }

I can't find much on the internet referring to that error - any idea why the error is reporting 'Interface closed'? Cheers. Bill (also in Sydney).

config.txt

[greiginsydney]

Hi Bill,

Fancy hearing from you. I only mailed Geoff about you half an hour ago, as he brought your issue to my attention.

The log you sent Geoff seemed to suggest that C-Gate wasn't running. I'd SSH to the Pi and do a “sudo systemctl status cgate” to see what it’s up to…

- G.

[fcmarriott]

Thanks - between the email that I sent to Geoff and the post above, I started from scratch and re-installed the Homebridge RaspPi, CBUS plugin, followed all your steps and seemed like it all worked. However, I'm getting the above error on the homebridge and none of the light controls on my iOS are working.

I should note, I have CBUS, a Wiser installed and running on 192.168.0.4 and the Homebridge Pi at 192.168.0.8. I haven't loaded any other plugins on the Homebridge RaspPi.

Seems like cgate is working properly :

pi@homebridge:~ $ sudo systemctl status cgate
● cgate.service - cgate
   Loaded: loaded (/etc/systemd/system/cgate.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2021-01-20 22:36:16 AEDT; 18h ago
 Main PID: 368 (java)
    Tasks: 25 (limit: 4915)
   CGroup: /system.slice/cgate.service
           └─368 /usr/bin/java -Djava.awt.headless=true -jar -noverify /usr/local/bin/cgate/cgate.jar

Jan 20 22:36:16 homebridge systemd[1]: Started cgate.
Jan 20 22:36:18 homebridge java[368]: Clipsal C-Gate(TM) v2.11.4 (build 3251)
Jan 20 22:36:19 homebridge java[368]: Logging to file: logs/event.txt
Jan 20 22:36:19 homebridge java[368]: 20210120-223619 800 cgate - C-Gate started.
Jan 20 22:36:20 homebridge java[368]: C-Gate is running.

Homebridge keeps giving me these two errors in logs :

2021-01-21T05:48:30.869Z cbus:client rx event { time: '20210121-164830', code: 755, processed: false, message: '//1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 InterfaceState=closed, TargetState=closed', type: 'event', raw: '#e# 20210121-164830 755 //1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 InterfaceState=closed, TargetState=closed' }
2021-01-21T05:48:30.870Z cbus:client rx event { time: '20210121-164830', code: 754, processed: false, message: '//1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 State=new Previous=sync Reason=Interface Closed', type: 'event', raw: '#e# 20210121-164830 754 //1CALDWEL/254 a419f300-3d41-1039-94ff-ee3ec4dac8f5 State=new Previous=sync Reason=Interface Closed' }

[greiginsydney]

Leave it with me and I'll have a tinker with my own tomorrow. It's overdue for some attention...

[fcmarriott]

Hi @greiginsydney - figured it out. In my original implementation, the Wiser was at 192.168.0.3, but then I switched it to 192.168.0.4 because there was a conflict. The CBUS Project .xml file was still referencing the .3 address. Restarted at Step 25 through 35 and it picked up the change.