-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with new Clipsal CGATE Server ver 3.2.0 #140
Comments
@PK2000GIT |
With the older CGate it was a requirement to edit CGate configuration files to automatically set the default project and start the project. |
"client_ip_address": "127.0.0.1", - which is that same as what I had in the previous "steppinghat/cgate-server" image I was running successfully. My access.txt has the IP address of the container stipulated for Program access just like before. Like I mentioned when I connect to "remote cgate" (to this new docker container) within Toolkit from my laptop, no problem at all. I can see the project and I can connect to bus accessories and make changes and apply them to both database and cbus devices on the network. |
The "C-GateConfig.txt" has been edited to include the name of your project in "project.default" & "project.start" sections. |
I've not used the new CGate but previously you could connect to CGate with telnet. |
I can connect via telnet and get a "200 OK" response and can see all the triggered events scrolling up the screen. |
This is what Homebridge Logs shows: [12/5/2023, 12:18:51 PM] [HB Supervisor] Restarting Homebridge... |
I see you have no accessories showing in the log. |
Might be worth mentioning on CBus forum too. |
I will try run a setup over the next few days |
Thank it will be great if someone can set it up as well and see if they are experiencing the same. Im starting to think the syntax in the config.json (that works perfectly fine with the previous docker image) may need to be modified now. Maybe the new sqlite or whatever format the project.db is in may need different syntax in the config.json. But thats just a wild guess. BTW I also posted the new docker image details on CBus forum for others to try https://www.cbusforums.com/threads/new-c-gate-server-3-2-0-docker-image.11185/ |
@PK2000GIT |
Here it is: |
@srpage @PK2000GIT Thanks |
I'm struggling to follow this. |
How would I set these variables? |
Clipsal have certainly over complicated things with this version. Otherwise If you follow their instructions you need to :
In Debian setting a variable will look something like this “export CGATE_HOME=/home/clipsal/cgate3/home” Hope this helps |
Another silly question. |
This will be wherever you extracted the cgate folder so either one will do as long as long as the cgate.jar is in there. |
Thanks |
Some success Now have to finish Homebridge install which is probably not going to be smooth due to Homebridge updates |
@PK2000GIT |
No I didn't have to touch any Java settings. |
20231230-231432 999 sys Socket accepted. |
@PK2000GIT |
2023-12-30T13:31:58.432Z cbus:client C-Gate session not ready -- unexpected message: 201 Service ready: Schneider Electric C-Gate Version: v3.2.0 (build 1674) #cmd-syntax=1. |
I have updated to CGate 3.2 and get the same error as above. Looking at the gate-client.js file there's a regex looking for a string containing the old Clipsal message - I'm thinking this is the first thing to resolve. |
I tried to raise a Pull Request to fix it but it looks like I don't have permission. |
Were you able to edit that for a fix? |
@thebergz @PK2000GIT homebridge-cbus/lib/cgate-client.js Line 178 in 8158d95
sudo nano /var/lib/homebridge/node_modules/homebridge-cbus/lib/cgate-client.js
My test setup is a bit flakey but could be due to using MAC with multiple VM's and USB interface. |
FWIW I also changed the regex constant in this line from Clipsal to Schneider Electric and everything seems to be working fine now with CGate 3.2. @anthonywebb looks like a relatively easy fix if/when you have time and if you wanted to maintain backwards compatibility the regex can potentially be updated to ignore the part of the line where the company name appears :) |
@thebergz |
@DarylMc Thats probably the easiest approach for now. Just edit the C-GateConfig file. For those following along, find the section "gate-name", add a "#" to remark the original "cgate-name" and add a new one as "cgate-name=Clipsal C-Gate". |
The CGate sync problem only seems to be an issue on arm64 platforms. |
Thanks @DarylMc :) |
This sync problem was fixed in a CGate update |
Hi all,
Cant seem to get homebridge-cbus plugin working with the new version of CGATE SERVER 3.2.0 that introduces the new database (.db as opposed to .xml) format.
Error: This plugin is taking long time to load and preventing Homebridge from starting.
I'm using the new CGATE Server docker image from here: https://hub.docker.com/r/pktechnology/cgateserver
Prior to this new version of cgate I was running "https://hub.docker.com/r/steppinghat/cgate-server" in the same manner with no issues.
The homebridge-cbus plugin (v1.1.0) and the new version cgateserver container are both running on Synology NAS.
When the container is up and running, I can connect to it from Clipsal Toolkit software to prove it is running and connectivity is all good. So the new version cgateserver docker image and container are working as expected with new .db project.
Is this a homebridge-cbus plugin fix that is needed for this new CGATE Server version?
Any ideas would be helpful.
The text was updated successfully, but these errors were encountered: