Homebridge Pi CGate network problems

Discussion in 'Third-Party Solutions' started by scuddoo, Mar 15, 2022.

  1. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    Hi,

    I'm having a problem where all the cbus accessories stop working via the homebridge. In putty when I do a "net list" it shows the network state error:
    131 network=254 State=error InterfaceState=running

    It will not restart on its own unless I reboot the Pi. Sometimes it will lasts a week till I have to reboot. Sometimes just 1 day.
    Sorry I'm a noob here and not sure where to go for help.

    Not sure what to look for in the CGate logs but this looks like something in the 2 parts I pasted below is when the problem starts:

    20220308-205948 999 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Traffic: 0.0 mps, 0.0 mps 3s avg
    20220308-205948 756 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 SyncState=syncing
    20220308-205948 756 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 SyncSubState=init
    20220308-205948 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: started at Tue Mar 08 20:59:48 AEDT 2022
    20220308-205948 756 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 SyncSubState=pci
    20220308-205948 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: synchronising PCIs
    20220308-205948 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: ||
    20220308-205948 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: || processed by network.
    20220308-205949 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: @1A2001
    20220308-205950 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: @1A2001 after 2000ms, retry limit of 0 reached
    20220308-205950 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=1 unit=-1 reason=no response (@1A2001)
    20220308-205950 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: ~~~ ***
    20220308-205950 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: ~~~ *** processed by network.
    20220308-205950 824 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 unknown response: ~~~ ***
    20220308-205951 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: 1A2001
    20220308-205956 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: 1A2001 after 5500ms, retry limit of 0 reached
    20220308-205956 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=2 unit=-1 reason=no response (1A2001)
    20220308-205956 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd (fastpci): FAFF00g (254: \05FF00FAFF00g)
    20220308-210001 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00g after 5500ms, beginning retry 1 of 2
    20220308-210001 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\05FF00FAFF00g)
    20220308-210001 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: \461E001A2001
    20220308-210003 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220308-210007 834 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Restarting stuck transmitter
    20220308-210007 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd (fastpci): \05FF00FAFF00h (254: \05FF00FAFF00h)
    20220308-210009 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00h after 5500ms, beginning retry 2 of 2
    20220308-210009 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\05FF00FAFF00h)
    20220308-210009 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: \461E001A2001
    20220308-210011 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220308-210016 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00 after 5500ms, retry limit of 2 reached
    20220308-210016 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=3 unit=-1 reason=no response (\05FF00FAFF00)
    20220308-210016 754 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=error Previous=ok Reason=no response (\05FF00FAFF00)
    20220308-210016 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: Network Sync PCI reset failed.
    20220308-210016 844 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Network Sync PCI reset failed.
    20220308-210016 757 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=error Previous=(unchanged) Reason=Network Sync PCI reset failed.
    20220308-210016 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: The network cannot be reached.
    20220308-210016 844 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 The network cannot be reached.

    ~~~~~~~


    20220308-185503 899 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Debug: Polling PCI, objectState=3, syncState=idle
    20220308-185503 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): FAFF00o (254: \05FF00FAFF00o)
    20220308-185503 765 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 got packet confirm: o.
    20220308-185504 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D8FF006466A49696A9696A46002A0000000000000000000000A3 accepted by command: \05FF00FAFF00o
    20220308-185504 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00o
    20220308-185504 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00o
    20220308-185604 899 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Debug: Polling PCI, objectState=3, syncState=idle
    20220308-185604 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): FAFF00p (254: \05FF00FAFF00p)
    20220308-185604 765 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 got packet confirm: p.
    20220308-185604 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D8FF00A46A949A996555AA49001A00000000000000000000008D accepted by command: \05FF00FAFF00p
    20220308-185604 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00p
    20220308-185604 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00p
    20220308-185704 899 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Debug: Polling PCI, objectState=3, syncState=idle
    20220308-185704 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): FAFF00q (254: \05FF00FAFF00q)
    20220308-185710 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00q after 5500ms, beginning retry 1 of 2
    20220308-185715 834 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Restarting stuck transmitter
    20220308-185715 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): \05FF00FAFF00r (254: \05FF00FAFF00r)
    20220308-185715 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00r after 5500ms, beginning retry 2 of 2
    20220308-185721 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00 after 5500ms, retry limit of 2 reached
    20220308-185721 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=1 unit=-1 reason=no response (\05FF00FAFF00)
    20220308-185725 827 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 CBusSender waiting for flow control. txEnabled=false serialInputBytes=0
    20220308-185726 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461F002101 after 5500ms, beginning retry 1 of 2
    20220308-185726 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\461F002101 )
    20220308-185727 834 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Restarting stuck transmitter
    20220308-185727 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): \05FF00FAFF00s (254: \05FF00FAFF00s)
    20220308-185728 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461F001A2001 after 2000ms, retry limit of 0 reached
    20220308-185734 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461F002101 after 5500ms, beginning retry 2 of 2
    20220308-185734 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\461F002101 )
    20220308-185736 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461F001A2001 after 2000ms, retry limit of 0 reached
    20220308-185737 827 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 CBusSender waiting for flow control. txEnabled=false serialInputBytes=0
    20220308-185739 834 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Restarting stuck transmitter
    20220308-185739 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd (fastpci): \461F002101t (254: \461F002101t)
    20220308-185739 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc009 sent cmd: \461F001A2001
    20220308-185741 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461F002101t after 5500ms, retry limit of 2 reached
    20220308-185741 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=2 unit=31 reason=no response (\461F002101)
    20220308-185741 755 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 InterfaceState=closing, TargetState=closed
    20220308-185741 754 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=error Previous=ok Reason=PCI polling failed
    20220308-185741 754 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=sync Previous=error Reason=closing network
    20220308-185741 999 sys RegistrationQueue : removed syncer for network 254
    20220309-000156 999 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Traffic: 0.0 mps, 0.0 mps 3s avg
    20220309-000156 756 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 SyncSubState=init
    20220309-000156 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: started at Wed Mar 09 00:01:56 AEDT 2022
    20220309-000156 756 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 SyncSubState=pci
    20220309-000156 753 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Net Sync: synchronising PCIs
    20220309-000156 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: ||
    20220309-000156 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: || processed by network.
    20220309-000157 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: @1A2001
    20220309-000158 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: @1A2001 after 2000ms, retry limit of 0 reached
    20220309-000158 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=100 unit=-1 reason=no response (@1A2001)
    20220309-000158 757 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=error Previous=(unchanged) Reason=no response (@1A2001)
    20220309-000158 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: ~~~ ***
    20220309-000158 734 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 response: ~~~ *** processed by network.
    20220309-000158 824 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 unknown response: ~~~ ***
    20220309-000159 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: 1A2001
    20220309-000204 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: 1A2001 after 5500ms, retry limit of 0 reached
    20220309-000204 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command-fail-count=101 unit=-1 reason=no response (1A2001)
    20220309-000204 757 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 State=error Previous=(unchanged) Reason=no response (1A2001)
    20220309-000204 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd (fastpci): FAFF00z (254: \05FF00FAFF00z)
    20220309-000209 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00z after 5500ms, beginning retry 1 of 2
    20220309-000209 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\05FF00FAFF00z)
    20220309-000209 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd: \461E001A2001
    20220309-000211 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220309-000216 834 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Restarting stuck transmitter
    20220309-000216 735 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 cc004 sent cmd (fastpci): \05FF00FAFF00g (254: \05FF00FAFF00g)
    20220309-000217 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 command timed out: \05FF00FAFF00g after 5500ms, beginning retry 2 of 2
    20220309-000217 759 //27BEACON/254 6f6169b0-80e1-103a-a1c0-d3fa4e942331 Checking PCI before retrying command (\05FF00FAFF00g)
     
    scuddoo, Mar 15, 2022
    #1
    1. Advertisements

  2. scuddoo

    DarylMc

    Joined:
    Mar 24, 2006
    Messages:
    1,265
    Likes Received:
    44
    Location:
    Cleveland, QLD, Australia
    What PCI are you using to connect to CBus?
     
    DarylMc, Mar 15, 2022
    #2
    1. Advertisements

  3. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    I believe it's using the Wiser2 as the interface
     
    scuddoo, Mar 15, 2022
    #3
  4. scuddoo

    DarylMc

    Joined:
    Mar 24, 2006
    Messages:
    1,265
    Likes Received:
    44
    Location:
    Cleveland, QLD, Australia
    Do you have another interface to try?
    Perhaps someone else here has some tips for common problems or troubleshooting the Wiser PCI?
     
    DarylMc, Mar 15, 2022
    #4
  5. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    I only have a CTouch but I don't think I can use that through the Pi
     
    scuddoo, Mar 15, 2022
    #5
  6. scuddoo

    DarylMc

    Joined:
    Mar 24, 2006
    Messages:
    1,265
    Likes Received:
    44
    Location:
    Cleveland, QLD, Australia
    No you can't use CTouch.
    Check the Wiser PSU, CBus and network cabling.
    Dust? Overheating? Reboot?
     
    DarylMc, Mar 15, 2022
    #6
  7. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    I moved the wiser2 next to my router and run a new cbus cable from the C-touch to eliminate any network issues. The wiser is not dusty or overheating. I removed the PSU and is now PoE powered but it is still happening. I've narrowed down the logs to when it fails after trying to sync. The wiser never looses connection and the wiser app always works. If it was a network interruption why can't it resolve itself?

    20220404-131051 765 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e got packet confirm: q.
    20220404-131051 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: D8FF0054955456AA99555685001A000000000000000000000009 accepted by command: \05FF00FAFF00q
    20220404-131051 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: D8FF5800000000000000000000000000000000000000000000D1 accepted by command: \05FF00FAFF00q
    20220404-131051 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: D6FFB000000000000000000000000000000000000000007B accepted by command: \05FF00FAFF00q
    20220404-131129 999 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Traffic: 0.0 mps, 0.0 mps 3s avg
    20220404-131129 756 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e SyncState=syncing
    20220404-131129 756 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e SyncSubState=init
    20220404-131129 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: started at Mon Apr 04 13:11:29 AEST 2022
    20220404-131129 756 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e SyncSubState=pci
    20220404-131129 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: synchronising PCIs
    20220404-131129 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: ||
    20220404-131129 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: || processed by network.
    20220404-131129 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: @1A2001
    20220404-131131 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: @1A2001 after 2000ms, retry limit of 0 reached
    20220404-131131 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=1 unit=-1 reason=no response (@1A2001)
    20220404-131131 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: ~~~ ***
    20220404-131131 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: ~~~ *** processed by network.
    20220404-131131 824 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e unknown response: ~~~ ***
    20220404-131131 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: 1A2001
    20220404-131137 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: 1A2001 after 5500ms, retry limit of 0 reached
    20220404-131137 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=2 unit=-1 reason=no response (1A2001)
    20220404-131137 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): FAFF00r (254: \05FF00FAFF00r)
    20220404-131142 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00r after 5500ms, beginning retry 1 of 2
    20220404-131142 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Checking PCI before retrying command (\05FF00FAFF00r)
    20220404-131142 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: \461E001A2001
    20220404-131144 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220404-131147 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
    20220404-131147 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): \05FF00FAFF00s (254: \05FF00FAFF00s)
    20220404-131150 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00s after 5500ms, beginning retry 2 of 2
    20220404-131150 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Checking PCI before retrying command (\05FF00FAFF00s)
    20220404-131150 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: \461E001A2001
    20220404-131152 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220404-131157 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00 after 5500ms, retry limit of 2 reached
    20220404-131157 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=3 unit=-1 reason=no response (\05FF00FAFF00)
    20220404-131157 754 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=ok Reason=no response (\05FF00FAFF00)
    20220404-131157 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: Network Sync PCI reset failed.
    20220404-131157 844 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Network Sync PCI reset failed.
    20220404-131157 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=Network Sync PCI reset failed.
    20220404-131157 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: The network cannot be reached.
    20220404-131157 844 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e The network cannot be reached.
    20220404-131157 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=The network cannot be reached.
    20220404-131157 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: Next Sync scheduled for Mon Apr 04 13:16:57 AEST 2022
    20220404-131159 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
    20220404-131159 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): \05FF00FAFF00t (254: \05FF00FAFF00t)
    20220404-131211 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
    20220404-131700 999 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Traffic: 0.0 mps, 0.0 mps 3s avg
    20220404-131700 756 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e SyncSubState=init
    20220404-131700 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: started at Mon Apr 04 13:17:00 AEST 2022
    20220404-131700 756 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e SyncSubState=pci
    20220404-131700 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: synchronising PCIs
    20220404-131700 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: ||
    20220404-131700 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: || processed by network.
    20220404-131700 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: @1A2001
    20220404-131702 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: @1A2001 after 2000ms, retry limit of 0 reached
    20220404-131702 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=4 unit=-1 reason=no response (@1A2001)
    20220404-131702 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=no response (@1A2001)
    20220404-131702 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: ~~~ ***
    20220404-131702 734 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e response: ~~~ *** processed by network.
    20220404-131702 824 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e unknown response: ~~~ ***
    20220404-131702 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: 1A2001
    20220404-131708 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: 1A2001 after 5500ms, retry limit of 0 reached
    20220404-131708 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=5 unit=-1 reason=no response (1A2001)
    20220404-131708 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=no response (1A2001)
    20220404-131708 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): FAFF00u (254: \05FF00FAFF00u)
    20220404-131713 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00u after 5500ms, beginning retry 1 of 2
    20220404-131713 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Checking PCI before retrying command (\05FF00FAFF00u)
    20220404-131713 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: \461E001A2001
    20220404-131715 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220404-131719 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
    20220404-131719 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): \05FF00FAFF00v (254: \05FF00FAFF00v)
    20220404-131721 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00v after 5500ms, beginning retry 2 of 2
    20220404-131721 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Checking PCI before retrying command (\05FF00FAFF00v)
    20220404-131721 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd: \461E001A2001
    20220404-131723 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \461E001A2001 after 2000ms, retry limit of 0 reached
    20220404-131728 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command timed out: \05FF00FAFF00 after 5500ms, retry limit of 2 reached
    20220404-131728 759 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e command-fail-count=6 unit=-1 reason=no response (\05FF00FAFF00)
    20220404-131728 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=no response (\05FF00FAFF00)
    20220404-131728 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: Network Sync PCI reset failed.
    20220404-131728 844 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Network Sync PCI reset failed.
    20220404-131728 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=Network Sync PCI reset failed.
    20220404-131728 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: The network cannot be reached.
    20220404-131728 844 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e The network cannot be reached.
    20220404-131728 757 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e State=error Previous=(unchanged) Reason=The network cannot be reached.
    20220404-131728 753 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Net Sync: Next Sync scheduled for Mon Apr 04 13:22:28 AEST 2022
    20220404-131731 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
    20220404-131731 735 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e cc004 sent cmd (fastpci): \05FF00FAFF00w (254: \05FF00FAFF00w)
    20220404-131743 834 //27BEACON/254 f738fe80-8fb8-103a-af1d-86dd8a2cd69e Restarting stuck transmitter
     
    scuddoo, Apr 8, 2022
    #7
  8. scuddoo

    Pie Boy

    Joined:
    Nov 21, 2012
    Messages:
    201
    Likes Received:
    28
    Location:
    New Zealand
    When it happens, Can you connect toolkit to the gate with remote cgate connection, and see if the cbus network is open?

    I had an issue where home kit wasn’t responding, turned out when the pi reboots,
    If you have the homebridge and cgate scripts so the services boot on start up, by default cbus network is not opened, you have to alter in the cgate config file and tell it which project is default and to open that one on reboot.

    Could be your issue?
     
    Pie Boy, Apr 8, 2022
    #8
  9. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    That's one thing I haven't been able to get working. The toolkit to connect to the remote c-gate gives me: "An error occurred while initialising Secure Socket Layer. Cannot connect to C-Gate Server"
    Anyway the services all start up fine from a reboot of the Pi and will work for several days until the above error happens
     
    scuddoo, Apr 9, 2022
    #9
  10. scuddoo

    Pie Boy

    Joined:
    Nov 21, 2012
    Messages:
    201
    Likes Received:
    28
    Location:
    New Zealand
    Ohh yeah this happens because of tls1.0
    check this thread
    https://www.cbusforums.com/threads/c-gate-command-port-issue-with-toolkit.10610/

    do you think cbus is going offline? Or is it specifically the homebridge going offline

    ive generally found if cgate is stable homebridge doesn’t go flakey, probably something in Java is causing cgate to stop And then homebridge can’t communicate with cgate. What version of java do you have installed?
     
    Last edited: Apr 9, 2022
    Pie Boy, Apr 9, 2022
    #10
  11. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    Thanks! Now my toolkit is connecting
    I don't think anything is wrong with the cbus. I've never had any problems with it and never saw any problems with the wiser2 app. The homebridge also is fine because other all devices (non cbus) are still working fine even when the cbus accessories don't respond

    java -version
    openjdk version "1.8.0_312"
    OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-1+rpi1-b07)
    OpenJDK Client VM (build 25.312-b07, mixed mode)
     
    scuddoo, Apr 9, 2022
    #11
  12. scuddoo

    scuddoo

    Joined:
    Oct 10, 2018
    Messages:
    8
    Likes Received:
    0
    Ok I can't figure it out. I loaded Homebridge on a PC and setup c-gate to see if there was any difference. It's doing the same thing. Stops working at random times with the same error messages.
    Is there any way to check the c-bus health outside of c-gate?
     
    scuddoo, Apr 28, 2022
    #12
  13. scuddoo

    DarylMc

    Joined:
    Mar 24, 2006
    Messages:
    1,265
    Likes Received:
    44
    Location:
    Cleveland, QLD, Australia
    Did you setup CGate on the PC and get the same problem?
    It's pretty clear in the logs your PCI is the problem and that would confirm it.
    Wiser2 has 2 inbuilt PCI.
    One for Wiser to connect to CBus and one other PCI for Toolkit etc.
    The reason for having two PCI is because only one connection is allowed at a time to a PCI.
    If no one else pops in with some advice try reading the manual regarding the built in PCI settings.

    One other thing to check.
    If you have another PC running CGate or a PC running an instance of CGate service trying to connect to the same PCI as the raspberry pi this is more than one connection and will cause unstable results.
     
    DarylMc, Apr 28, 2022
    #13
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.