-
Notifications
You must be signed in to change notification settings - Fork 8
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
Not working with SmartCom #13
Comments
I think @nathsea had this working at one point. Have you followed the instructions re. changing the protocol to Crestron after configuring IP? |
I ended up with problems with smartcom in the end as the texecom system would only allow one connection so , I then wasn’t get my arm / disarm notifications from the texecom app. |
@nathsea did you manage to get the arm/disarm working through HomeKit? Not particularly bothered about the Texecom app if I can configure HomeKit notifications. My ideal is getting it working through Athoms Homey which I use but with it being a totally different system my hands are tied until someone develops an app. What did you use for the IP_PORT? 10001? Will try the Crestron instructions but may go down the COM IP or USB option as well as SmartCom. What ports do you have the SmartCom and other COM connected to? Thanks! |
I didn’t think arm / disarm was a built in function yet ... so never tried it 😬 I think I moved the com ip to the first expansion port in the texecom main unit and then added the smartcom to the second expansion ... |
You can get HomeKit notifications & automations for arming and disarming, but you can't arm or disarm. It isn't supported by the Crestron protocol. Personally I use Texecom's COM-GSM for remote arm/disarm as it's great to have a backup connection if the internet goes down. |
Hi, have now moved SmartCom to COM2 and COM3 - USB Com on COM1 Any ideas? |
Have amended the index.js file as the serialport.parsers.readline should have been Serialport.parsers readline I believe. Now I'm getting a different error ReferenceError: Serialport is not defined. The amend to the first condition was due to some googling, but I don't really know enough to know what I'm changing so have reverted back to the parsers error. Is there anyway this could be looked at if just a typo? Many thanks |
Hi @nigetech , think I may have ballsed up the serial port support in the last release, apologies. I don’t have a way of testing it here so I’ll need to ask someone else to test in future. Could you possibly open a new issue so others can see it’s been reported, and I’ll look at it soon? |
Did anyone manage to get this working with SmartCom? I changed the COM-IP of the SmartCom to Creston but HomeBridge seems pretty unresponsive. Says that it's connected via IP but nothing happens... Thanks |
Nope, had to install a COM IP to get it working in the end, moved the SmartCom to Com 2 and 3, COM IP on Com 1 |
That’s annoying! I don’t think I have a COM3 on my panel - and Elite 48 |
If you've got the smart com it should have came with a little adapter which goes in the communications expander at the top of the board and gives you a kinda virtual Com 3. Can pick them up on eBay pretty cheap if not, mine is a Elite 48 also. |
Did you need to do anything funky with your SmartCom/ComIP & Separate ComIP to get them working? I had a SmartCom on Com1, ComIP on Com2 and wanted to get this working. I got the adapter which slides into the DigiModule and a ComIP. When I try and reset settings and put my SmartCom on Com2 and it's ComIP on Com3, it doesnt play, despite setting the options via the keypad to Com2 (SmartCom) and Com3 (ComIP). Any ideas? |
Did you get this working? I'm having the same problems |
Not a sausage. I got fed up and binned the idea. I still have everything connected but as soon as I tell the panel there is a ComIP on COM3, it comes up with ATS path fault. |
I have got it working turns out the Com+ cable was the wrong way round changed it then done a Reset Digi and now it's working perfectly hope this helps you out. |
So just to summarise, you have both SmartCom and COM-IP attached, and are running this plugin successfully against the COM-IP? |
Negative Ghostrider. For me, just cant get it to work. I have a SmartCom on COM1/2 and COM-IP that refuses to work on COM3. I'm using the digi adapter to get COM3. I could have a faulty Digi adapter and/or COM-IP, but have lost interest now :( |
Never worked for me.
…Sent from my iPhone
On 22 Nov 2020, at 16:54, Speedbird979 ***@***.***> wrote:
So just to summarise, you have both SmartCom and COM-IP attached, and are running this plugin successfully against the COM-IP?
Negative Ghostrider. For me, just cant get it to work. I have a SmartCom on COM1/2 and COM-IP that refuses to work on COM3. I'm using the digi adapter to get COM3. I could have a faulty Digi adapter and/or COM-IP, but have lost interest now :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Just to update this I have COM-IP on COM1 for the plugin SmartCom on COM2 and COM3 in Com Port Setup I have COM1 as Crestron System COM2 as SmartCom and COM3 as COM-IP my issue was the cable that goes to the Digi adapter was the wrong way round I reversed the cable Reset Digi and it started working I'm guessing it might be the same for you as I was having the same fault message. |
I just fiddled and swapped the cable ends round round but didn’t make a difference. The cable has a couple of lugs meaning it can only go one way and has a blanking pin in the unused pin to ensure it can only go in one way. I’ve either got a duff digi module / ComIP or both. That said, the ComIP gets power via the cable, picks up an IP address but when ever I configure the panel to say COM3 is a Com-IP it has a wobble with ATS Path failure. |
Did you try swaping the cable that goes to the DIGI module the one with grey and red cables not the com port one that's the one I changed to get it working. |
Sorry - should have been clearer. I have the COM Port+ Adapter: JAL-0001 which then connects to the COMIP with the cable supplied. My mistake. Can grab a photo of it helps. |
I understand now mines different to yours my COM Port+ Adapter: JAL-0001 connects with a cable, not a header like you have try COM-IP on COM1 SmartCom 4 cable plug on COM2 and the SmartCom 2 cable plug on the COM Port+ also do you have Onboard Digicom set to anything this should be set to Nothing fitted |
Yup. Tried all combinations and nowt works. Onboard Digi is nothing fitted and as soon as I set COM3 to COMIP and set the IP, DG and port to 10002, it comes up failure. I see the power going on and off to the module under the diagnostics tab. Is anyone else using the Comport adapter? Maybe I need to try something else to rule it out. Got a pic? |
Hi, I'm new here and only started playing around with Homebridge this weekend and was astonished on how much I've been missing out on so started looking at getting my Texecom connected up after discovering this plugin. My apartment came with the alarm pre-installed with an unused Com IP when I moved in last year which I promptly replaced with a SmartCom for the app, but luckily kept the ComIP safe. So this morning I installed the digi expansion that came with the SmartCom and connected back up the ComIP to what's now COM3 as others have discussed here. Configured it with an IP address on the panel, initially setting COM3 to be a Com-IP, checked it responded to pings and then changed COM3 to Crestron and proceeded to configure the zone configuration on Homebridge. Rebooted homebridge and boom, instantly all my PIRs and door contact sensors detected and working - less than a second between triggering a PIR and motion detected on my iPhone. So to summarise, SmartCom is using COM1&2, and the ComIP is using the new Com3 port. My expansion board and cable looks like your Speedbird but I've a different panel. |
SmartCom goes on COM2 (4 wire) & COM3 (2 wire) ComIP goes on COM1 |
This is driving me bonkers; Have switched SmartCom/ComIP to COM2/3 and still getting the error for ATS Path Fault/COM3. With just the COMIP on COM1, I did manage to configure and get HomeBridge to connect, so I know that side of things is working. All went wrong when I tried to also configure the SmartCOM/ComIP on COM2/3 - same issue with ATS Path Fault. I've had my suspicions that the Elite 24 maybe limited, but looking at the SmartCom installation manual I've just seen this nugget: "A Premier Elite ComPort+ is provided which may be used to utilise the digi modem connection to provide Com Port 3 on Premier Elite 48/64/88 & 168." Don't suppose anyone else has an Elite 24 and has this working? Thx. |
Being new to Hoobs Homebridge and Linux. How would I modify this to use Local Network Connection eg
At present Com 2 is set to Crestron Baud 19200 |
Hi @5xPa , here's a complete example for you:
|
Hi max-christian Thanks for such prompt reply. Installed the plugin. In config there is one box with and a button below "add accessory" In the first box should I enter |
For anyone looking to get the texecom plugin running on Hoobs Ethernet I Used Max Christains basic config, worked great. I was initially unsure. After installing the plug the config page had 1 config box and below a button "Add Accessories" I ignored this and entered the config info in the text box worked perfect. |
Hi Guys - sorry to say also new to homebridge, have a HOOBS running which at the moment pulls Hikvision in nicely to HomeKit. I have an existing texecom premier elite at the house we have moved into and would love to get this working. in addition to arm/disarm can you use the PIR's/door contact in texecom to show motion etc in Home app? anyone got any screenshots to share of it operational? |
Hi Sandy, yes there are screenshots on the front page: https://github.com/max-christian/homebridge-texecom Please note you cannot arm or disarm the unit using the plugin. |
Unsure if this plugin is now dead, but I'm coming here as a starting point for my integration. It is completely possible to Arm and Disarm the Alarm via Crestron serial as I am doing that right now with my own integration. However it's a bit cobbled together having a Homebridge plugin and a custom web service to talk to the alarm. I'm looking to maybe fork / modify this project to get the functionality that I need. I currently have HomeKit and Alexa working with the alarm but I'm looking to simplify the setup. |
Very much alive, it's just very stable and complete so not much to update. The only way to arm/disarm via crestron is to simulate key presses, and you'd have to parse the LCD screen contents to know the UI's current state... would never work reliably. |
It works completely reliably for me at the moment using the KEYx commands, however I also have an integration I wrote using the native Texecom IP / Serial protocol that is much more reliable but I was struggling to get the COMI IP working reliably on Com 3. However I can't even get the plugin installed, NPM craps out near the end..
|
I can do everything I want to do via the SmartComm on port 10001 that's where my current Alexa integration goes, but the issue is if you hold up the IP connection, it prevents the SmartComm sending Push Notifications to the Texecom app etc. Which is why I moved on to looking at a separate connection to Com 3, I then came across the Crestron protocol and it is much simpler than the native protocol for the SmartComm or the default serial ports. So figured I would investigate that, as I like the idea of having the Alarm zones as sensors for triggering other automations. My current plan is to put a Pi Zero in the alarm box directly connected to the serial port, and run HomeBridge on it. |
Have the same setup and the exact same issue as you. Issue was the digi module setup I had Onboard Digi set to comIP not COM3 set to ComIP. I set the onboard digi back to nothing fitted and set COM3 to ComIP and everything looked better immediately. The lights on the ComIP started blinking as expected. |
Sorry to bump and old thread; but I got this working perfectly with a raspberry pi zero 2w. Got everything showing in HomeKit too, great plugin! |
Hello, thanks for the update @max-christian I have upgraded from the COM IP to the SmartCom but this doesn't let me connect entering the IP.
If you're able to get this working with the SmartCom that would be amazing, if you need me to test anything that is not an issue.
It doesn't have to be IP with SmartCom and can use a Username/Password if that helps.
The text was updated successfully, but these errors were encountered: