Skip to content
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

dscKeybusInterface disabled the Original keypad arm/disarm functions #257

Open
qighu21 opened this issue Nov 24, 2021 · 1 comment
Open

Comments

@qighu21
Copy link

qighu21 commented Nov 24, 2021

I built a dscKeybusInterface for my PC1616 security system based on ESP8266 HomeAssistant -MQTT example. It works great! Thanks for the great job!
I noticed an issue with using the original keypad to arm/disarm the security system. After pressing the "arm stay or arm away" key on the original physical keypad, the security system entered into "Exit delay ..." state, then I hear four beeps of accesscode being entered automatically into the system, as a result, the security system is disarmed. So I cannot arm the system from the original keypad.
The same issue happens when I try to disarm the armed security system from the physical keypad, After entering 4 digit access code, the system is disarmed, however, four beeps coming immediately after the system disarmed that arms the system again. So that I cannot disarm the system from the keypad.
Arm/disarm operations using HomeAssitant app are perfect.

@taligentx
Copy link
Owner

Hi @qighu21 - that's odd behavior, I'd recommend taking a look at the MQTT messages in the dsc/Get/Partition1 and dsc/Set topics on your MQTT broker to see if HomeAssistant is sending these commands to the ESP8266 when the physical keypad is used. That'll help narrow it down to HomeAssistant or the ESP8266 sketch itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants