search

anthonywebb / homebridge-cbus

CBus plugin for homebridge
MIT License
35 stars 20 forks source link

Plugin Requirements #130

Open kapps7 opened 1 year ago

kapps7 commented 1 year ago

Hi,

Im new to Cbus so please excuse the basic questions. I have a CNI which is the basic version of the Cbus network interface not the Shac or wise modules.

I can see the Cbus network online with the CNI. Should this be enough for me to use this plugin ? Thanks

TigerDad66 commented 1 year ago

That should be enough but you will need to know controlport no, network, cbusname, application etc

You will also have to manually edit the config file on Homebridge as there isn't a GUI config for this module.

Have you tested the CNI using a tool like putty and the ports and then the CBus commands?

From: kapps7 @.> Sent: Wednesday, August 3, 2022 11:31 am To: anthonywebb/homebridge-cbus @.> Cc: Subscribed @.***> Subject: [anthonywebb/homebridge-cbus] Plugin Requirements (Issue #130)

Hi,

Im new to Cbus so please excuse the basic questions. I have a CNI which is the basic version of the Cbus network interface not the Shac or wise modules.

I can see the Cbus network online with the CNI. Should this be enough for me to use this plugin ? Thanks

— Reply to this email directly, view it on GitHubhttps://github.com/anthonywebb/homebridge-cbus/issues/130, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AV5AHLZJUYE36LVQBE3B7W3VXHDUZANCNFSM55NCZDCQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

PUBLIC

DarylMc commented 1 year ago

@kapps7 CNI is a great device to use for Homebridge and Homebridge CBus. There is instructions to setup here. Slightly modifications needed though.

https://github.com/greiginsydney/Homebridge-cbus-installer/issues/22#issuecomment-1175601119

DarylMc commented 1 year ago

Quite detailed instructions here. If you can follow this just make the changes listed in the link above.

https://github.com/greiginsydney/Homebridge-cbus-installer/blob/master/SETUP.md

kapps7 commented 1 year ago

Thanks guys. that's great, I can give that a go. Will this allow the status of the accessories to synchronise in both directions eg. when the user operates the accessories via the Cbus switches.

DarylMc commented 1 year ago

Yes it will keep status both ways

kapps7 commented 1 year ago

@DarylMc I followed the instructions from both the pages ie GreginSydney as well as the primary setup. I have the following logs. Homebridge is up. Cbus hasn't populated the config with the accessories. As per the logs it seems to have connected to the CNI. Not sure if I missed anything or whether there is a separate issue. Thanks.

000007B accepted by command: \05FF00FAFF00j' } [30/10/2022, 11:31:03] [HB Supervisor] Stopping services... [30/10/2022, 11:31:03] Got SIGTERM, shutting down Homebridge... [30/10/2022, 11:31:08] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null [30/10/2022, 11:31:11] [HB Supervisor] OS: Linux 5.15.61-v7l+ arm [30/10/2022, 11:31:11] [HB Supervisor] Node.js v16.16.0 /opt/homebridge/bin/node [30/10/2022, 11:31:11] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge [30/10/2022, 11:31:11] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js [30/10/2022, 11:31:15] [Homebridge UI] Homebridge Config UI X v4.50.1 is listening on :: port 8581 [30/10/2022, 11:31:15] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution [30/10/2022, 11:31:15] [HB Supervisor] Started Homebridge v1.5.0 with PID: 13719 [30/10/2022, 11:31:16] Loaded config.json with 0 accessories and 2 platforms. [30/10/2022, 11:31:16] Loaded 0 cached accessories from cachedAccessories. [30/10/2022, 11:31:16] --- [30/10/2022, 11:31:16] Loaded plugin: homebridge-cbus@1.1.0 [30/10/2022, 11:31:17] Registering platform 'homebridge-cbus.CBus' [30/10/2022, 11:31:17] --- [30/10/2022, 11:31:17] Loading 2 platforms... [30/10/2022, 11:31:17] [CBus] Initializing homebridge-cbus.CBus platform... 2022-10-30T00:31:17.014Z cbus:client Opening connection to C-Gate… 2022-10-30T00:31:17.021Z cbus:client C-Gate connection open. 2022-10-30T00:31:17.024Z cbus:client Connected to C-Gate server v2.11.4 (build 3251), syntax v1.0 2022-10-30T00:31:17.024Z cbus:client Configuring C-Gate session… 2022-10-30T00:31:17.026Z cbus:client C-Gate session estabished and configured at 20023:127.0.0.1 2022-10-30T00:31:17.028Z cbus:platform Loading the accessories list… 2022-10-30T00:31:17.028Z cbus:platform Registering the accessories list… 2022-10-30T00:31:17.032Z cbus:client sent command '[100] dbgetxml //BRONTE' Setup Payload: X-HM://00249AD8W96NE Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     
│ 476-26-896 │     
└────────────┘

[30/10/2022, 11:31:17] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge F321) is running on port 51603. 2022-10-30T00:31:17.140Z cbus:client rx snippet 343 'Begin XML snippet' 2022-10-30T00:31:17.180Z cbus:client rx snippet 347 '<?xml version="1.0" encoding="utf-8"?>' 2022-10-30T00:31:17.180Z cbus:client rx snippet 347 '295f5240-21ec-103b-ac63-c083a6b601fa2.31.0…' 2022-10-30T00:31:17.187Z cbus:client rx response { commandId: 100, code: 344, matched: false, processed: false, type: 'response', raw: '[100] 344 End XML snippet' } 2022-10-30T00:31:17.188Z cbus:client matched request '[100] dbgetxml //BRONTE' with response '[100] 344 End XML snippet' (0 pending requests) 2022-10-30T00:31:17.258Z cbus:platform Successfully fetched 6 applications, 99 groups and 0 units from C-Gate. 2022-10-30T00:31:33.256Z cbus:client rx event { time: '20221030-113133', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00k (254: \05FF00FAFF00k)', type: 'event', raw: '#e# 20221030-113133 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00k (254: \05FF00FAFF00k)' } 2022-10-30T00:31:33.400Z cbus:client rx event { time: '20221030-113133', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: k.', type: 'event', raw: '#e# 20221030-113133 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: k.' } 2022-10-30T00:31:33.491Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:33.552Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:33.612Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:52.372Z cbus:client rx event { time: '20221030-113152', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0529FF001EFFE7BD51BF4DB5 processed by network.', type: 'event', raw: '#e# 20221030-113152 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0529FF001EFFE7BD51BF4DB5 processed by network.' } 2022-10-30T00:31:52.436Z cbus:client rx event { time: '20221030-113152', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0501FF001EFFE7BA05CE8DDD processed by network.', type: 'event', raw: '#e# 20221030-113152 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0501FF001EFFE7BA05CE8DDD processed by network.' } 2022-10-30T00:31:56.275Z cbus:client rx event { time: '20221030-113156', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 052DFF001EFFE7BA5C2ADAB1 processed by network.', type: 'event', raw: '#e# 20221030-113156 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 052DFF001EFFE7BA5C2ADAB1 processed by network.' } 2022-10-30T00:31:56.547Z cbus:client rx event { time: '20221030-113156', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0528FF001EFFE7BA5C28DCB6 processed by network.', type: 'event', raw: '#e# 20221030-113156 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0528FF001EFFE7BA5C28DCB6 processed by network.' } 2022-10-30T00:32:33.625Z cbus:client rx event { time: '20221030-113233', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00l (254: \05FF00FAFF00l)', type: 'event', raw: '#e# 20221030-113233 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00l (254: \05FF00FAFF00l)' } 2022-10-30T00:32:33.783Z cbus:client rx event { time: '20221030-113233', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: l.', type: 'event', raw: '#e# 20221030-113233 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: l.' } 2022-10-30T00:32:33.875Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00l' } 2022-10-30T00:32:33.939Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00l' } 2022-10-30T00:32:33.996Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00l' } 2022-10-30T00:33:34.008Z cbus:client rx event { time: '20221030-113334', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00m (254: \05FF00FAFF00m)', type: 'event', raw: '#e# 20221030-113334 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00m (254: \05FF00FAFF00m)' } 2022-10-30T00:33:34.166Z cbus:client rx event { time: '20221030-113334', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: m.', type: 'event', raw: '#e# 20221030-113334 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: m.' } 2022-10-30T00:33:34.258Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00m' } 2022-10-30T00:33:34.322Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00m' } 2022-10-30T00:33:34.379Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00m' } 2022-10-30T00:34:34.392Z cbus:client rx event { time: '20221030-113434', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00n (254: \05FF00FAFF00n)', type: 'event', raw: '#e# 20221030-113434 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00n (254: \05FF00FAFF00n)' } 2022-10-30T00:34:34.534Z cbus:client rx event { time: '20221030-113434', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: n.', type: 'event', raw: '#e# 20221030-113434 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: n.' } 2022-10-30T00:34:34.626Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00n' } 2022-10-30T00:34:34.690Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00n' } 2022-10-30T00:34:34.746Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00n' } 2022-10-30T00:35:34.760Z cbus:client rx event { time: '20221030-113534', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00o (254: \05FF00FAFF00o)', type: 'event', raw: '#e# 20221030-113534 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00o (254: \05FF00FAFF00o)' } 2022-10-30T00:35:34.901Z cbus:client rx event { time: '20221030-113534', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: o.', type: 'event', raw: '#e# 20221030-113534 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: o.' } 2022-10-30T00:35:34.994Z cbus:client rx event { time: '20221030-113534', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113534 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00o' } 2022-10-30T00:35:35.059Z cbus:client rx event { time: '20221030-113535', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113535 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00o' } 2022-10-30T00:35:35.114Z cbus:client rx event { time: '20221030-113535', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113535 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00o' } 2022-10-30T00:36:35.127Z cbus:client rx event { time: '20221030-113635', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00p (254: \05FF00FAFF00p)', type: 'event', raw: '#e# 20221030-113635 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00p (254: \05FF00FAFF00p)' } 2022-10-30T00:36:35.273Z cbus:client rx event { time: '20221030-113635', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: p.', type: 'event', raw: '#e# 20221030-113635 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: p.' } 2022-10-30T00:36:35.365Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00p' } 2022-10-30T00:36:35.425Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00p' } 2022-10-30T00:36:35.486Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00p' } 2022-10-30T00:37:35.498Z cbus:client rx event { time: '20221030-113735', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00q (254: \05FF00FAFF00q)', type: 'event', raw: '#e# 20221030-113735 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00q (254: \05FF00FAFF00q)' } 2022-10-30T00:37:35.657Z cbus:client rx event { time: '20221030-113735', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: q.', type: 'event', raw: '#e# 20221030-113735 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: q.' } 2022-10-30T00:37:35.749Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00q' } 2022-10-30T00:37:35.809Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00q' } 2022-10-30T00:37:35.869Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00q' } 2022-10-30T00:38:35.882Z cbus:client rx event { time: '20221030-113835', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00r (254: \05FF00FAFF00r)', type: 'event', raw: '#e# 20221030-113835 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00r (254: \05FF00FAFF00r)' } 2022-10-30T00:38:36.016Z cbus:client rx event { time: '20221030-113836', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: r.', type: 'event', raw: '#e# 20221030-113836 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: r.' } 2022-10-30T00:38:36.132Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00r' } 2022-10-30T00:38:36.196Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00r' } 2022-10-30T00:38:36.253Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00r' }

peterconn commented 1 year ago

I had the same issue. Check your config.json, that’s where my issue was.

Regards

Peter Constantopedos

From: kapps7 @.> Sent: Sunday, October 30, 2022 11:42:15 AM To: anthonywebb/homebridge-cbus @.> Cc: Subscribed @.***> Subject: Re: [anthonywebb/homebridge-cbus] Plugin Requirements (Issue #130)

@DarylMchttps://github.com/DarylMc I followed the instructions from both the pages ie GreginSydney as well as the primary setup. I have the following logs. Homebridge is up. Cbus hasn't populated the config with the accessories. As per the logs it seems to have connected to the CNI. Not sure if I missed anything or whether there is a separate issue. Thanks.

000007B accepted by command: \05FF00FAFF00j' } [30/10/2022, 11:31:03] [HB Supervisor] Stopping services... [30/10/2022, 11:31:03] Got SIGTERM, shutting down Homebridge... [30/10/2022, 11:31:08] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null [30/10/2022, 11:31:11] [HB Supervisor] OS: Linux 5.15.61-v7l+ arm [30/10/2022, 11:31:11] [HB Supervisor] Node.js v16.16.0 /opt/homebridge/bin/node [30/10/2022, 11:31:11] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge [30/10/2022, 11:31:11] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js [30/10/2022, 11:31:15] [Homebridge UI] Homebridge Config UI X v4.50.1 is listening on :: port 8581 [30/10/2022, 11:31:15] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution [30/10/2022, 11:31:15] [HB Supervisor] Started Homebridge v1.5.0 with PID: 13719 [30/10/2022, 11:31:16] Loaded config.json with 0 accessories and 2 platforms. [30/10/2022, 11:31:16] Loaded 0 cached accessories from cachedAccessories. [30/10/2022, 11:31:16] --- [30/10/2022, 11:31:16] Loaded plugin: @.*** [30/10/2022, 11:31:17] Registering platform 'homebridge-cbus.CBus' [30/10/2022, 11:31:17] --- [30/10/2022, 11:31:17] Loading 2 platforms... [30/10/2022, 11:31:17] [CBus] Initializing homebridge-cbus.CBus platform... 2022-10-30T00:31:17.014Z cbus:client Opening connection to C-Gate… 2022-10-30T00:31:17.021Z cbus:client C-Gate connection open. 2022-10-30T00:31:17.024Z cbus:client Connected to C-Gate server v2.11.4 (build 3251), syntax v1.0 2022-10-30T00:31:17.024Z cbus:client Configuring C-Gate session… 2022-10-30T00:31:17.026Z cbus:client C-Gate session estabished and configured at 20023:127.0.0.1 2022-10-30T00:31:17.028Z cbus:platform Loading the accessories list… 2022-10-30T00:31:17.028Z cbus:platform Registering the accessories list… 2022-10-30T00:31:17.032Z cbus:client sent command '[100] dbgetxml //BRONTE' Setup Payload: X-HM://00249AD8W96NE Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐

│ 476-26-896 │

└────────────┘

[30/10/2022, 11:31:17] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge F321) is running on port 51603. 2022-10-30T00:31:17.140Z cbus:client rx snippet 343 'Begin XML snippet' 2022-10-30T00:31:17.180Z cbus:client rx snippet 347 '' 2022-10-30T00:31:17.180Z cbus:client rx snippet 347 '295f5240-21ec-103b-ac63-c083a6b601fa2.31.0…' 2022-10-30T00:31:17.187Z cbus:client rx response { commandId: 100, code: 344, matched: false, processed: false, type: 'response', raw: '[100] 344 End XML snippet' } 2022-10-30T00:31:17.188Z cbus:client matched request '[100] dbgetxml //BRONTE' with response '[100] 344 End XML snippet' (0 pending requests) 2022-10-30T00:31:17.258Z cbus:platform Successfully fetched 6 applications, 99 groups and 0 units from C-Gate. 2022-10-30T00:31:33.256Z cbus:client rx event { time: '20221030-113133', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00k (254: \05FF00FAFF00k)', type: 'event', raw: '#e# 20221030-113133 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00k (254: \05FF00FAFF00k)' } 2022-10-30T00:31:33.400Z cbus:client rx event { time: '20221030-113133', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: k.', type: 'event', raw: '#e# 20221030-113133 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: k.' } 2022-10-30T00:31:33.491Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:33.552Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:33.612Z cbus:client rx event { time: '20221030-113133', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00k', type: 'event', raw: '#e# 20221030-113133 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00k' } 2022-10-30T00:31:52.372Z cbus:client rx event { time: '20221030-113152', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0529FF001EFFE7BD51BF4DB5 processed by network.', type: 'event', raw: '#e# 20221030-113152 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0529FF001EFFE7BD51BF4DB5 processed by network.' } 2022-10-30T00:31:52.436Z cbus:client rx event { time: '20221030-113152', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0501FF001EFFE7BA05CE8DDD processed by network.', type: 'event', raw: '#e# 20221030-113152 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0501FF001EFFE7BA05CE8DDD processed by network.' } 2022-10-30T00:31:56.275Z cbus:client rx event { time: '20221030-113156', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 052DFF001EFFE7BA5C2ADAB1 processed by network.', type: 'event', raw: '#e# 20221030-113156 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 052DFF001EFFE7BA5C2ADAB1 processed by network.' } 2022-10-30T00:31:56.547Z cbus:client rx event { time: '20221030-113156', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0528FF001EFFE7BA5C28DCB6 processed by network.', type: 'event', raw: '#e# 20221030-113156 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: 0528FF001EFFE7BA5C28DCB6 processed by network.' } 2022-10-30T00:32:33.625Z cbus:client rx event { time: '20221030-113233', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00l (254: \05FF00FAFF00l)', type: 'event', raw: '#e# 20221030-113233 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00l (254: \05FF00FAFF00l)' } 2022-10-30T00:32:33.783Z cbus:client rx event { time: '20221030-113233', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: l.', type: 'event', raw: '#e# 20221030-113233 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: l.' } 2022-10-30T00:32:33.875Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00l' } 2022-10-30T00:32:33.939Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00l' } 2022-10-30T00:32:33.996Z cbus:client rx event { time: '20221030-113233', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00l', type: 'event', raw: '#e# 20221030-113233 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00l' } 2022-10-30T00:33:34.008Z cbus:client rx event { time: '20221030-113334', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00m (254: \05FF00FAFF00m)', type: 'event', raw: '#e# 20221030-113334 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00m (254: \05FF00FAFF00m)' } 2022-10-30T00:33:34.166Z cbus:client rx event { time: '20221030-113334', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: m.', type: 'event', raw: '#e# 20221030-113334 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: m.' } 2022-10-30T00:33:34.258Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF00A86A59A6A5A9A986696AAAA596529AA600600A000000E7 accepted by command: \05FF00FAFF00m' } 2022-10-30T00:33:34.322Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00m' } 2022-10-30T00:33:34.379Z cbus:client rx event { time: '20221030-113334', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00m', type: 'event', raw: '#e# 20221030-113334 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00m' } 2022-10-30T00:34:34.392Z cbus:client rx event { time: '20221030-113434', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00n (254: \05FF00FAFF00n)', type: 'event', raw: '#e# 20221030-113434 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00n (254: \05FF00FAFF00n)' } 2022-10-30T00:34:34.534Z cbus:client rx event { time: '20221030-113434', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: n.', type: 'event', raw: '#e# 20221030-113434 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: n.' } 2022-10-30T00:34:34.626Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00n' } 2022-10-30T00:34:34.690Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00n' } 2022-10-30T00:34:34.746Z cbus:client rx event { time: '20221030-113434', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00n', type: 'event', raw: '#e# 20221030-113434 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00n' } 2022-10-30T00:35:34.760Z cbus:client rx event { time: '20221030-113534', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00o (254: \05FF00FAFF00o)', type: 'event', raw: '#e# 20221030-113534 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00o (254: \05FF00FAFF00o)' } 2022-10-30T00:35:34.901Z cbus:client rx event { time: '20221030-113534', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: o.', type: 'event', raw: '#e# 20221030-113534 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: o.' } 2022-10-30T00:35:34.994Z cbus:client rx event { time: '20221030-113534', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113534 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00o' } 2022-10-30T00:35:35.059Z cbus:client rx event { time: '20221030-113535', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113535 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00o' } 2022-10-30T00:35:35.114Z cbus:client rx event { time: '20221030-113535', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00o', type: 'event', raw: '#e# 20221030-113535 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00o' } 2022-10-30T00:36:35.127Z cbus:client rx event { time: '20221030-113635', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00p (254: \05FF00FAFF00p)', type: 'event', raw: '#e# 20221030-113635 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00p (254: \05FF00FAFF00p)' } 2022-10-30T00:36:35.273Z cbus:client rx event { time: '20221030-113635', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: p.', type: 'event', raw: '#e# 20221030-113635 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: p.' } 2022-10-30T00:36:35.365Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0064595A99A556AA4566A699AA9951996500900A000000BE accepted by command: \05FF00FAFF00p' } 2022-10-30T00:36:35.425Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00p' } 2022-10-30T00:36:35.486Z cbus:client rx event { time: '20221030-113635', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00p', type: 'event', raw: '#e# 20221030-113635 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00p' } 2022-10-30T00:37:35.498Z cbus:client rx event { time: '20221030-113735', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00q (254: \05FF00FAFF00q)', type: 'event', raw: '#e# 20221030-113735 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00q (254: \05FF00FAFF00q)' } 2022-10-30T00:37:35.657Z cbus:client rx event { time: '20221030-113735', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: q.', type: 'event', raw: '#e# 20221030-113735 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: q.' } 2022-10-30T00:37:35.749Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00q' } 2022-10-30T00:37:35.809Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00q' } 2022-10-30T00:37:35.869Z cbus:client rx event { time: '20221030-113735', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00q', type: 'event', raw: '#e# 20221030-113735 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00q' } 2022-10-30T00:38:35.882Z cbus:client rx event { time: '20221030-113835', code: 735, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00r (254: \05FF00FAFF00r)', type: 'event', raw: '#e# 20221030-113835 735 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa cc014 sent cmd (fastpci): FAFF00r (254: \05FF00FAFF00r)' } 2022-10-30T00:38:36.016Z cbus:client rx event { time: '20221030-113836', code: 765, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: r.', type: 'event', raw: '#e# 20221030-113836 765 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa got packet confirm: r.' } 2022-10-30T00:38:36.132Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF0068565A9999595645A5956AA9AA91656900900500000000 accepted by command: \05FF00FAFF00r' } 2022-10-30T00:38:36.196Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00r' } 2022-10-30T00:38:36.253Z cbus:client rx event { time: '20221030-113836', code: 734, processed: false, message: '//BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00r', type: 'event', raw: '#e# 20221030-113836 734 //BRONTE/254 296322d0-21ec-103b-ac9b-c083a6b601fa response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00r' }

— Reply to this email directly, view it on GitHubhttps://github.com/anthonywebb/homebridge-cbus/issues/130#issuecomment-1296040783, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCPDBRTW7OB2QDQJODLXI3WFW76PANCNFSM55NCZDCQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

DarylMc commented 1 year ago

Greig's script is how I last tested a build but there is some issues and a workaround here.

https://github.com/greiginsydney/Homebridge-cbus-installer/issues/22

DarylMc commented 1 year ago

@peterconn What was wrong with the config? Did you use Greig's setup script? The script should create all the config settings.

https://github.com/greiginsydney/Homebridge-cbus-installer/issues/22

peterconn commented 1 year ago

No, I followed your updated script then there was an issue with my json where the accessories were not populating. The issue was the top section of the script.

Regards

Peter Constantopedos

From: DarylMc @.> Sent: Sunday, October 30, 2022 11:51:15 AM To: anthonywebb/homebridge-cbus @.> Cc: peterconn @.>; Mention @.> Subject: Re: [anthonywebb/homebridge-cbus] Plugin Requirements (Issue #130)

@peterconnhttps://github.com/peterconn What was wrong with the config? Did you use Greig's setup script? The script should create all the config settings.

greiginsydney/Homebridge-cbus-installer#22https://github.com/greiginsydney/Homebridge-cbus-installer/issues/22

— Reply to this email directly, view it on GitHubhttps://github.com/anthonywebb/homebridge-cbus/issues/130#issuecomment-1296043044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCPDBTDZKSY7ZEM2FDO7JTWFXBAHANCNFSM55NCZDCQ. You are receiving this because you were mentioned.Message ID: @.***>

DarylMc commented 1 year ago

Even if Homebridge CBus and CGate are all setup and working properly another thing to check is if the IP address of the CNI in the project xml is the same as the CNI current IP address.

kapps7 commented 1 year ago

had the same issue. Check your config.json, that’s where my issue was.

What specifically. Currently its pretty stock standard there are no other plugins installed.

check is if the IP address of the CNI in the project xml is the same as the CNI current IP address.

It is correct, thanks. Reserved IP

DarylMc commented 1 year ago

Especially for a large network I would leave everything alone for 15 min after the first boot to allow the devices to populate. Also for a large number of CBus units ie 50+ you may need to increase the Homebridge startup delay to 10 minutes. It's always been my experience if Homebridge starts before CGate has synced the CBus network it leaves the Homebridge in a state it can't recover from.

That said It could be something else has change recently. I will test an install in the next few days.

kapps7 commented 1 year ago

@DarylMc thank you.

Pls dont waste time doing any testing until I follow through on the progress I have made and if I have further issues.

So I went through the last steps again. I thought the process of responding to these unknown groups, was to accept it. After reviewing the instructions, I responded to each one by C for Change and changed it to Light and there are 147 unknowns ! Why ? no idea. I dont know how Cbus works. The groups have populated, all as lights ofcourse. Must be a better way of configuring the xml so I dont need to do this

I would like to know whether the mods you have recommended to Greg and Anthony's contributions can be replicated on a home bridge instance on macOS since I already have that on my network. I can start a separate thread if you think that is possible.

Screenshot 2022-10-30 at 12 51 05 pm

DarylMc commented 1 year ago

@kapps7 I did just run up an install following these steps https://github.com/greiginsydney/Homebridge-cbus-installer/issues/22 It seems OK.

In CBus Toolkit you can look at CBus group addresses and some of them won't be devices or may not even be used in the project. Some of the unknown group addresses may be used elsewhere eg Touchscreen so you don't want to delete them either. When the project is installed at your home the installer should add some meaningful names to the group addresses. This is done with CBus Toolkit and is saved in the project xml file. If that hasn't been done you are just going to have a bunch of numbers for the group addresses and won't be easy to know what's what.

When running the script to create the config file it's probably easiest to skip any unknown type. You can always run the script again later.

DarylMc commented 1 year ago

I would like to know whether the mods you have recommended to Greg and Anthony's contributions can be replicated on a home bridge instance on macOS since I already have that on my network. I can start a separate thread if you think that is possible.>

Greig's script is made specifically for running Homebridge, Homebridge CBus and CGate on a Raspberry pi.

wrh75 commented 1 year ago

If you have a bunch of numbers for the group addresses and you don't know what's what, the easiest way to work it out is to open a telnet connection to the IP address that C-Gate is running on at port 20025. Then just go around your house switch on and off each light/group and see which groups get listed on the telnet connection. Then put those numbers into your config.json file. I wouldn't worry about going back and labelling them correctly with CBus Toolkit.

DarylMc commented 1 year ago

@peterconn I couldn't replicate a problem with the config file creation. Perhaps give it more time to populate and see if that helps.

peterconn commented 1 year ago

@DarylMc

Ok, I’ll try it again. I have 3 networks at home in which I only really use 2 as one was a wireless network for testing purposes.

Regards

Peter Constantopedos

From: DarylMc @.> Sent: Tuesday, November 1, 2022 2:57:11 PM To: anthonywebb/homebridge-cbus @.> Cc: peterconn @.>; Mention @.> Subject: Re: [anthonywebb/homebridge-cbus] Plugin Requirements (Issue #130)

@peterconnhttps://github.com/peterconn I couldn't replicate a problem with the config file creation. Perhaps give it more time to populate and see if that helps.

— Reply to this email directly, view it on GitHubhttps://github.com/anthonywebb/homebridge-cbus/issues/130#issuecomment-1297990746, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHCPDBVGRWMFTL3MW73QBYLWGCIJPANCNFSM55NCZDCQ. You are receiving this because you were mentioned.Message ID: @.***>

kapps7 commented 1 year ago

You guys have done an amazing job with this. So far it's been pretty responsive. Hope 16.2's architectural changes dont throw us a curve ball.

It's always been my experience if Homebridge starts before CGate has synced the CBus network it leaves the Homebridge in a state it can't recover from.

This is good advice. I'll use your post from here https://github.com/oznu/homebridge-config-ui-x/issues/999#issuecomment-811582012

@kapps7 I did just run up an install following these steps greiginsydney/Homebridge-cbus-installer#22 It seems OK.

In CBus Toolkit you can look at CBus group addresses and some of them won't be devices or may not even be used in the project. Some of the unknown group addresses may be used elsewhere eg Touchscreen so you don't want to delete them either. When the project is installed at your home the installer should add some meaningful names to the group addresses. This is done with CBus Toolkit and is saved in the project xml file. If that hasn't been done you are just going to have a bunch of numbers for the group addresses and won't be easy to know what's what.

When running the script to create the config file it's probably easiest to skip any unknown type. You can always run the script again later.

Then put those numbers into your config.json file

Right, so just default syntax and no customisation of names. I will manually identify them and create a document then update the type in the json to a supported type.

So when the script is rerun eg. if a new Cbus accessory is added, will it only prompt for those that have not been added to the config.json. ?

DarylMc commented 1 year ago

Greig's script already has a timer for delay start of Homebridge service. you can edit here. sudo nano /etc/systemd/system/homebridge.timer Only need to change if you are having problems

DarylMc commented 1 year ago

The script should identify all the lighting and dimmer type addresses no problem. I'd just add them and skip the others initially. You can also add some meaningful names in HomeKit without touching the config.json

kapps7 commented 1 year ago

Things seem relatively smooth. Just a couple of management qs

  1. Can I safely delete accessories in the config json that were picked in the initial xml file but are actually not connected to an accessory
  2. Similarly If the Cbus installer was to add an accessory, I expect I will need to reload the updated xml file ?
  3. lastly are there any known issues specifically with this integration that I should monitor eg. automations or scenes.

Thanks

DarylMc commented 1 year ago

Things seem relatively smooth. Just a couple of management qs

  1. Can I safely delete accessories in the config json that were picked in the initial xml file but are actually not connected to an accessory
  2. Similarly If the Cbus installer was to add an accessory, I expect I will need to reload the updated xml file ?
  3. lastly are there any known issues specifically with this integration that I should monitor eg. automations or scenes.

Thanks

Important note, you now have a few copies of your project xml, one on your Windows PC and one you copied to the pi. Don't forget to keep the CBus Toolkit created xml safely backed up and in sync with your CBus network.

TristanNBaker commented 1 year ago

Hi, Im just troubleshooting my issues and am trying to check my CNI IP address is listed correctly but can't find it in my project XML - is this the xml from the tags folder im using in the script? If so, where within the script should I be looking? I can find the 5500CN2, but no mention of an IP address?

here is the section of code from the tags xml.

5500CN2
31
PC_CNICD5500CN2101186.28485.5.005500CN2false
DarylMc commented 1 year ago

Image 31-12-2022 at 4 25 pm

DarylMc commented 1 year ago

Hi, Im just troubleshooting my issues and am trying to check my CNI IP address is listed correctly but can't find it in my project XML - is this the xml from the tags folder im using in the script? If so, where within the script should I be looking? I can find the 5500CN2, but no mention of an IP address?

here is the section of code from the tags xml.

5500CN2

31PC_CNICD5500CN2101186.28485.5.005500CN2false

It's easier to read an xml file in a chromium type browser or decent text editor. As you can see in the picture the interface address is close to the start of the xml file. Yes it's the xml file located in /usr/local/bin/cgate/tag

TristanNBaker commented 1 year ago

Hi DarylMc, Thanked for the quick feedback. It appears mine says in that exact space where your '192.168' address is 'COM3' I have no idea where it got 'COM3' - but my IP address of my CNI is '10.0.4.222'. If I update this ip, do I need a further extension of :10001 like yours? or what is this?

and if I simply update this xml sitting in /usr/local/bin/cgate/tag will this have gate look to my CNI from homebridge from now on?

TristanNBaker commented 1 year ago

Hi, Im just troubleshooting my issues and am trying to check my CNI IP address is listed correctly but can't find it in my project XML - is this the xml from the tags folder im using in the script? If so, where within the script should I be looking? I can find the 5500CN2, but no mention of an IP address? here is the section of code from the tags xml. 5500CN2 31PC_CNICD5500CN2101186.28485.5.005500CN2false

It's easier to read an xml file in a chromium type browser or decent text editor. As you can see in the picture the interface address is close to the start of the xml file. Yes it's the xml file located in /usr/local/bin/cgate/tag

I have played around and understand the 10001 is a port. I was able to ping mi CNI at ip[ 10.0.4.22 through port 10001 and was successful.

But, Homebridge still doesn't like this... It doesn't tell me the IP is wrong, but gives a message like this when I turn a light on or off from HomeKit.

2022-12-31T11:00:48.741Z cbus:client sent command '[278] ramp //JUSAKOSB/254/56/15 0% # setOn (off)' 2022-12-31T11:00:48.744Z cbus:client rx response { commandId: 278, code: 401, matched: false, processed: false, type: 'response', raw: '[278] 401 Bad object or device ID: //JUSAKOSB/254/56/15 (Network not found)' } 2022-12-31T11:00:48.744Z cbus:client matched request '[278] ramp //JUSAKOSB/254/56/15 0% # setOn (off)' with response '[278] 401 Bad object or device ID: //JUSAKOSB/254/56/15 (Network not found)' (0 pending requests)

Bad object or device id - what has the xml tags file told Cgate? and how can I check it against my Cbus network in toolkit?

TristanNBaker commented 1 year ago

reading another thread here there was advice:

I don't believe that you are connected to the c-bus network. The log says that it is trying to fetch the state of each c-bus accessory at startup as defined in the homebridge config.json file, but it cant find them...

This is where the "bad object or device ID" statement comes from. Homebridge is trying to "get" the C-Bus state of each accessory but can't.

Check that you are connected to the C-Bus network first. Try to connect to the remote c-gate on the pi from a windows PC via toolkit. If you can then see the logs etc and can control c-bus, you are connected. If not, the problem is with the RS-232 config in the pi.

You can define the default network in the cgate config file. Make sure you do this and load it at startup. There are other threads that describe this process.

Otherwise do what Daryl says and start again with Greig's instructions.

Cheers

I think this is exactly what's happening to me. I've started again so many times with so many time with grigs instructions so im not sure I will get a different outcome. My Tags file generated from toolkit on the PC ( im a Mac user so my PC is a small HP and im flying blind mostly there, although I know toolkit pretty well these days ) has issues with the CNI details. it listed my IP as 'COM3' and said my device was serial. I updated details with the correct ip and chi for device. as for the feedback above, I have no idea how to connect to connect remotely to cgate on the pi from the PC, but I think it will show im not connecting to the cbus network. If this is the case, how do I fix it and get connected?

TristanNBaker commented 1 year ago

Sorry for so many comments, just working through this. I have found my tags xml info was an issue on the networking side as I use a PV interface unit to talk from the pc to the cbus network usually. SO when I used this tag xml it pointed to the PC int, not the 5500CN2. I connected to my network through the 5500CN2 this time and used that xml tag file.

I was hoping all my problems were solved, but still no light turning on and off. log messages are like this.

754 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 State=error Previous=new Reason=no response (\05FF00FAFF00)' } 2022-12-31T12:18:32.166Z cbus:client rx event { time: '20221231-231832', code: 755, processed: false, message: '//JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=closing, TargetState=closed', type: 'event', raw: '#e# 20221231-231832 755 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=closing, TargetState=closed' } 2022-12-31T12:18:32.168Z cbus:client rx event { time: '20221231-231832', code: 754, processed: false, message: '//JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 State=sync Previous=error Reason=closing network', type: 'event', raw: '#e# 20221231-231832 754 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 State=sync Previous=error Reason=closing network' } 2022-12-31T12:18:32.169Z cbus:client rx event { time: '20221231-231832', code: 755, processed: false, message: '//JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=streamsclosed, TargetState=closed', type: 'event', raw: '#e# 20221231-231832 755 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=streamsclosed, TargetState=closed' } 2022-12-31T12:18:32.170Z cbus:client rx event { time: '20221231-231832', code: 755, processed: false, message: '//JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=closed, TargetState=closed', type: 'event', raw: '#e# 20221231-231832 755 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 InterfaceState=closed, TargetState=closed' } 2022-12-31T12:18:32.171Z cbus:client rx event { time: '20221231-231832', code: 754, processed: false, message: '//JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 State=new Previous=sync Reason=Interface Closed', type: 'event', raw: '#e# 20221231-231832 754 //JUSAKOSB/254 df4f9440-6b32-103b-8038-fae5ee636df5 State=new Previous=sync Reason=Interface Closed' }

Any final tips?

DarylMc commented 1 year ago

Hi CBus Toolkit creates the project xml and Toolkit is the safest way to make any changes.

Shut down the pi so you don't have two instances of CGate trying to connect to one CNI. Use CBus Toolkit on the Windows PC to edit the project "network" details. This will then be saved in the project xml file on the Windows PC.

Since your current xml has the wrong interface details my guess is the xml is out of date. Make sure you backup your project before going any further. With CBus Toolkit transfer the CBus network to the database to ensure the xml matches your actual network. Transfer this xml to the pi.

I'm happy to try talk you through some of that but it won't be tonight.

TristanNBaker commented 1 year ago

DarylMc - Brilliant! I'm all working. Using the CNI to connect to the Cbus network on the pc gave me a fresh xml tag, which had all the right info for a fresh load onto the Cgate on Pi. I just needed to wait 15/3-7 windermere ave, Northmead 215220 mins and it all started working! Thanks for the help - I learnt a lot about the process and thanks for the offer to help further, but I got there! Happy new year!

kapps7 commented 1 year ago

Things seem relatively smooth. Just a couple of management qs

  1. Can I safely delete accessories in the config json that were picked in the initial xml file but are actually not connected to an accessory
  2. Similarly If the Cbus installer was to add an accessory, I expect I will need to reload the updated xml file ?
  3. lastly are there any known issues specifically with this integration that I should monitor eg. automations or scenes.

Thanks

  • Yes you could delete the unused accessories in the config file. Or you could rerun the setup script sudo -E ./setup.sh copy and use the "s" option to skip the unwanted group addresses. If some new group units or group addresses are added to the CBus network and loaded project xml you could add to Homebridge the same way.
  • The project xml file loaded into CGate on the pi should reflect the current CBus network programming.
  • I'm not the person to ask about CBus scenes and Homebridge but you could search here or CBus forum. https://github.com/anthonywebb/homebridge-cbus/issues?q=is%3Aissue+is%3Aopen+scenes

Important note, you now have a few copies of your project xml, one on your Windows PC and one you copied to the pi. Don't forget to keep the CBus Toolkit created xml safely backed up and in sync with your CBus network.

Daryl, sorry I forgot to thank you for your reply. I have done that and keep a backup of home bridge and of the xml files backed up separately.

I am wondering if you or anyone has taken the brave step of upgrading the HomeKit architecture in 16.4 and if it has had any impact with their CBus integration.

DarylMc commented 1 year ago

Things seem relatively smooth. Just a couple of management qs

  1. Can I safely delete accessories in the config json that were picked in the initial xml file but are actually not connected to an accessory

  2. Similarly If the Cbus installer was to add an accessory, I expect I will need to reload the updated xml file ?

  3. lastly are there any known issues specifically with this integration that I should monitor eg. automations or scenes.

Thanks

  • Yes you could delete the unused accessories in the config file.

    Or you could rerun the setup script sudo -E ./setup.sh copy and use the "s" option to skip the unwanted group addresses.

    If some new group units or group addresses are added to the CBus network and loaded project xml you could add to Homebridge the same way.

  • The project xml file loaded into CGate on the pi should reflect the current CBus network programming.

  • I'm not the person to ask about CBus scenes and Homebridge but you could search here or CBus forum.

    https://github.com/anthonywebb/homebridge-cbus/issues?q=is%3Aissue+is%3Aopen+scenes

Important note, you now have a few copies of your project xml, one on your Windows PC and one you copied to the pi. Don't forget to keep the CBus Toolkit created xml safely backed up and in sync with your CBus network.

Daryl, sorry I forgot to thank you for your reply. I have done that and keep a backup of home bridge and of the xml files backed up separately.

I am wondering if you or anyone has taken the brave step of upgrading the HomeKit architecture in 16.4 and if it has had any impact with their CBus integration.

I've been running the upgraded HomeKit architecture since last year and not noticed any problems with Homebridge or my small Homebridge CBus test setups.

kapps7 commented 1 year ago

I've been running the upgraded HomeKit architecture since last year and not noticed any problems with Homebridge or my small Homebridge CBus test setups.

Thats great news. I'll do the same.

kapps7 commented 5 months ago

Hey Daryl, after what seems like forever, we had a power outage where the Rpi (Homebridge running Cbus) as well as the CNI were restarted. Since this I am getting this error in the home bridge logs: 2024-02-05T06:17:17.091Z cbus:client C-Gate socket error: Error: connect ECONNREFUSED 127.0.0.1:20023 2024-02-05T06:17:17.091Z cbus:client C-Gate connection could not be opened; exiting.

The CNI is connected and hasn't changed IP at 192.168.4.222 and is the same as the IP in the original XML. I can see the CNI is visible via its http port on that IP. I haven't modified the home bridge setup at all, still on 1.5.1. They are all on a single flat network.

Should homebridge be looking for 192.168.4.222 instead of 127.0.0.1 ? Thanks.

DarylMc commented 5 months ago

"platform": "homebridge-cbus.CBus", "name": "CBus", "client_ip_address": "127.0.0.1", "client_controlport": 20023,

DarylMc commented 5 months ago

Check cgate is running sudo systemctl status cgate

DarylMc commented 5 months ago

What is the pi IP-address hostname -I

kapps7 commented 5 months ago

The RPi is at 192.168.4.114 so the same subnet as the CNI

I get this when I check cgate from the Pi terminal `pi@homebridge:/var/lib/homebridge $ sudo systemctl status cgate ● cgate.service - cgate Loaded: loaded (/etc/systemd/system/cgate.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2024-02-05 17:11:44 AEDT; 33min ago Process: 598 ExecStart=/usr/bin/java -Djava.awt.headless=true -jar -noverify /usr/local/bin/cgate/cgate.jar (code=exited, status=2) Main PID: 598 (code=exited, status=2) CPU: 240ms

Feb 05 17:11:44 homebridge systemd[1]: cgate.service: Scheduled restart job, restart counter is at 5. Feb 05 17:11:44 homebridge systemd[1]: Stopped cgate. Feb 05 17:11:44 homebridge systemd[1]: cgate.service: Start request repeated too quickly. Feb 05 17:11:44 homebridge systemd[1]: cgate.service: Failed with result 'exit-code'. Feb 05 17:11:44 homebridge systemd[1]: Failed to start cgate.`

But on the browser http port :

Screenshot 2024-02-05 at 5 30 56 pm

DarylMc commented 5 months ago

Check java version java -version

kapps7 commented 5 months ago

_pi@homebridge:/var/lib/homebridge $ java -version openjdk version "1.8.0_312" OpenJDK Runtime Environment (build 1.8.0312-8u312-b07-1+rpi1-b07) OpenJDK Client VM (build 25.312-b07, mixed mode)

DarylMc commented 5 months ago

java version is ok

Try connect to the network with CBus Toolkit to verify the CNI is OK

kapps7 commented 5 months ago

Thanks mate, I will have to borrow a pc cause only on macOS. Couldn't locate a macOS version of it

DarylMc commented 5 months ago

The homebridge log shows cgate is shutting down. Not sure why Maybe CNI can't be reached?

DarylMc commented 5 months ago

In case you haven't already reboot everything. Maybe power cycle the CNI

kapps7 commented 5 months ago

Yep I have but I will do it again. Let you know. Thanks again for your quick response.

DarylMc commented 5 months ago

cgate logs will probably help too. /usr/local/bin/cgate/logs sudo nano /usr/local/bin/cgate/logs/events.txt Or copy the log files to your Mac with a file transfer app I've been using one called Cyberduck.

kapps7 commented 5 months ago

Thanks I might do that anyway to see what was going on but a 3rd power cycle of both devices fixed it. Thanks again for your help!