XaF
Can't arm/disarm when panel is locked
I've enabled the 6 digit user code. If the panel is unlocked I can arm/disarm from HA. I only get this message if the panel is locked. Is this intended behavior? I have a correct 6 digit user code in my app.yaml since it unlocks when the panel is unlocked. I use partitions and was wondering if that was part of my problem.
2022-03-01 07:38:34.175743 DEBUG qolsys_panel: Unknown Qolsys event: {"event":"ERROR","partition_id":0,"error_type":"usercode","description":"Please Enable Six Digit User Code or KeyPad is already Locked","version":1,"nonce":"qolsys","requestID":"07090977-1fcb-4832-880e-8fb6c673f3cb"}
apps.yaml
qolsys_panel:
module: gateway
class: QolsysGateway
panel_host: redacted
panel_token: redacted
panel_user_code: redacted
panel_mac: redacted
# ha_user_code: 1234
# code_disarm_required: true
# code_arm_required: true
# ha_check_user_code: true
log_level: DEBUG
mqtt_namespace: mqtt
appdaemon.yaml
---
secrets: /config/secrets.yaml
appdaemon:
latitude: redacted
longitude: redacted
elevation: 100
time_zone: America/Los_Angeles
plugins:
HASS:
type: hass
# And we need to add the MQTT plugin
MQTT:
type: mqtt
namespace: mqtt # We will need that same value in the apps.yaml configuration
client_host: 192.168.0.60 # The IP address or hostname of the MQTT broker
client_port: 1883 # The port of the MQTT broker, generally 1883
client_user: mqtt
client_password: redacted
http:
url: http://127.0.0.1:5050
hadashboard:
admin:
api:
Could you please provide also the logs before that error? What is the action that was sent to the panel leading to that error?
2022-03-01 09:32:36.183496 DEBUG qolsys_panel: Received MQTT_MESSAGE with data={'topic': 'homeassistant/alarm_control_panel/qolsys_panel/set', 'wildcard': '#', 'payload': '{"partition_id": "0", "action": "ARM_HOME", "session_token": "a18bc975-6c13-4d23-a3e7-c09e362c7848"}'} and kwargs={'topic': 'homeassistant/alarm_control_panel/qolsys_panel/set', '__thread_id': 'MainThread'} 2022-03-01 09:32:36.184975 DEBUG qolsys_panel: Panel code is required for <QolsysControlArmHome partition_id=0 code=None session_token=a18bc975-6c13-4d23-a3e7-c09e362c7848> 2022-03-01 09:32:36.186987 DEBUG qolsys_panel: Sending: {"nonce": "qolsys", "source": "C4", "version": 0, "action": "ARMING", "arming_type": "ARM_STAY", "partition_id": "0", "usercode": "006789", "token": "vxzjzv"} 2022-03-01 09:32:36.240819 DEBUG qolsys_panel: Data received (len: 3): ACK 2022-03-01 09:32:36.242013 DEBUG qolsys_panel: ACK - ignoring. 2022-03-01 09:32:36.243254 DEBUG qolsys_panel: Data received (len: 216): {"event":"ERROR","partition_id":0,"error_type":"usercode","description":"Please Enable Six Digit User Code or KeyPad is already Locked","version":1,"nonce":"qolsys","requestID":"21534603-b6be-46f8-94ff-b7357f2a26c0"} 2022-03-01 09:32:36.244366 DEBUG qolsys_panel: Unknown Qolsys event: {"event":"ERROR","partition_id":0,"error_type":"usercode","description":"Please Enable Six Digit User Code or KeyPad is already Locked","version":1,"nonce":"qolsys","requestID":"21534603-b6be-46f8-94ff-b7357f2a26c0"}
There's something I might be missing about the panel here. What do we call "locked"? Is that a specific mode of the panel? Maybe it's not allowing to arm/disarm in that locked mode?
My iQpanel 2+ panel goes into a screensaver and lock mode after "X" amounts of inactivity. The max is 30 minutes. If you touch the panel screen it will ask you to input a user code. When it's unlocked there's a button called "lock screen" that will send it to this screensaver lock screen. This seems very similar to how an android tablet would function. I don't know of a way to force it to stay unlocked. I don't think the panel is very secure when unlocked anyways.
Mh that might be a configured option somewhere, as mine does not lock nor require a code to access the panel itself, but will ask a code to access the settings though! Not sure if there's a way to bypass the lock when using C4 :(
I think I found the problem. The IQpanel documentation indicates that partitions force a passcode on the lock screen. I'll consult management about removing the partitions, test, and report back.
I am actually wondering if there would be a way to unlock from the C4 interface, which is something I could add to the automation if needed
I got permission to remove the partitions. I'll wait a little bit to see if you see any way unlock method. Then I could test it. The partitions are sort of a pain and I probably won't miss them.
On Tue, Mar 1, 2022, 5:09 PM Raphaël Beamonte @.***> wrote:
I am actually wondering if there would be a way to unlock from the C4 interface, which is something I could add to the automation if needed
— Reply to this email directly, view it on GitHub https://github.com/XaF/qolsysgw/issues/16#issuecomment-1056028870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIHHNGD6UQZPWPUCDWNFXLU525TFANCNFSM5PUNDXKA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Hey there, I'm not really able to reproduce on my side (I could enable partitions but want to avoid disrupting stuff with my automation at the moment) so if you got the go-ahead to remove partitions, don't wait on me :)
I removed them and everything works. Thanks for everything!
[image: Company logo] http://www.cagewrx.com/ Eric Allen Engineer P 951-223-9118 <9512239118> | E @.*** 41680 Enterprise Cir S Ste. E Temecula, CA 92590 https://goo.gl/maps/CHNjTk2onU3Amr1h7 www.cagewrx.com [image: Instagram] http://www.instagram.com/cagewrx [image: Facebook] http://www.facebook.com/cagewrx [image: Youtube] http://www.youtube.com/cagewrx
On Thu, Mar 3, 2022 at 9:48 PM Raphaël Beamonte @.***> wrote:
Hey there, I'm not really able to reproduce on my side (I could enable partitions but want to avoid disrupting stuff with my automation at the moment) so if you got the go-ahead to remove partitions, don't wait on me :)
— Reply to this email directly, view it on GitHub https://github.com/XaF/qolsysgw/issues/16#issuecomment-1058850318, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIHHNHH6ZYA4I7SEFKTMQTU6GPZZANCNFSM5PUNDXKA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Is it mandatory to enable six digit codes to (dis)arm it with Home Assistant, the keypas is unlocked? With this option enabled, it does work. When six digits is disabled I get the error:
Received 20:35:35 QoS: 0 Payload: secure_arm: true alarm_type: null last_error_type: usercode last_error_desc: Please Enable Six Digit User Code or KeyPad is already Locked last_error_at: '2023-04-10T18:35:35.646475+00:00' disarm_failed: 0
