Comments (3)
I was confused there for a second because I haven't released a version of this module with the ability to arm/disarm etc through sending key presses, then I realised this is just a general query about the API spec. How are you sending the commands? Sending number keys etc is simply enough, just put into serial or TCP if you're doing it that way something like KEY3
However, what you'll find with this API is that some functions won't work, for example to enable something like quick arming on a regular Texecom keypad to enable that feature on that keypad address, with the API you aren't able to specify that the API has those permissions and so that feature can't be enabled if that makes sense? At least that is my understanding, it could be something like chime simply can't work via the API because you can't adjust what the API has permission to do because that virtual command keypad doesn't have an address or anything.
from homebridge-texecom.
Yeah, sorry, I haven't looked at your code, nor Homebridge. Mine is a native C++ tool. I've yet to receive a response to this question from Texecom, so was looking for others who have integrated with them.
I'm opening socket with the comIP interface, then following protocol specified in the two docs Texecom Connect [Payload] Specification supplied under NDA. i.e. login using UDL code, then issue various commands and parse responses. I am able to query everything I have tried so far, get/set LCD, query all the zones, status flags etc, [un]omit zones, arm and disarm the system etc.
I understand the limitations of the implementation over TCP, and can't monitor events, but for my purposes it's pretty good.
What I would like to do is turn chime on/off - and the spec implies I should do this sending a message to simulate key press on panel in similar way to others with properly formatted payload etc.
When I do this I get a response message back with matching sequence number and good CRC containing an ACK which implies that the command has been actioned, but it isn't.
If you don't have the Texecom paper to hand then I feel this might only confuse further.
from homebridge-texecom.
Sorry for slow reply, my theory on your issue is that it somehow relates to keypad permissions as certain functions must be expressly enabled on a keypad which you can’t do for the virtual keypad the protocol is pretending to be. Sadly the APIs for the alarm are far from well defined or thought out and so there are many many caveats and limitations. As this doesn’t relate to this project I’ve closed the issue, by all means message me on social media to discuss further.
from homebridge-texecom.
Related Issues (20)
- New owner? HOT 17
- SIGTERM when connected via USB-com
- Raspberry Pi4 install HOT 1
- Not working with SmartCom HOT 43
- Issue with SerialPort interface HOT 2
- Error during installation - @serialport/bindings HOT 3
- SIGTERM after IP connection closed
- Unable to install on Node 14 HOT 2
- Not working due to corrupted/encoded data being received HOT 6
- Weird Issue with strings from Texecom HOT 2
- Is there a way to map statuses against Homekit HOT 1
- Im having problem to make it work HOT 8
- Show temperature of sensors HOT 1
- Crestron on COM Port 3 HOT 1
- No messages on alarm activation HOT 1
- Upgrade HOOBS to Ver 3.3.3 CONNECT not working HOT 1
- Alarm Triggered, but didn't trigger on homebridge... HOT 6
- Feature request HOT 11
- Target alarm state is not set correctly HOT 1
- Communications failure bleeps on v3.2 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homebridge-texecom.