texecom2mqtt-hassio
texecom2mqtt-hassio copied to clipboard
dchesterton
Unknown Command - can anyone help?
Folks - I appreciate the original creator is not helping with development around this anymore, but I'm wondering if anyone is here and can help? I'm up to date on all versions, running managed HASS. I can disarm the alarm (if armed from a keypad), but I cannot arm the alarm system. My configuration is below:
`texecom: host: [removed] port: 10001 mqtt: host: core-mosquitto prefix: texecom2mqtt username: mqtt-user password: [removed] client_id: texecom2mqtt keepalive: 30 clean: true retain: true retain_log: false reject_unauthorized: false homeassistant: discovery: true prefix: home-assistant areas:
- id: a full_arm: armed_away part_arm_1: armed_night part_arm_2: armed_home part_arm_3: armed_custom_bypass code_arm_required: true code_disarm_required: false code: "[removed]" zones: [] cache: false log: info `
When I click the arm buttons in Home Assistant, the following is sent back on the logs:
2024-04-17 07:35:36 - WARNING: Unknown command ARM_HOME for area Area A 2024-04-17 07:35:44 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-17 07:35:53 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-17 07:35:54 - WARNING: Unknown command ARM_NIGHT for area Area A
I feel I am so close to getting this running. Any ideas???
Hi,Really pleased you’re making use of this. Comparing yours to my own I note two potential differences in that you are requiring the code to arm and not requiring it to disarm. If you change this requirement to false for both does this give you control? This obviously lacks an element of security but rules out the code element. Once proven you might want to turn it back to true for the disarm procedure. The only other thing to check is that your code is presented as “code” and not “[code]” as you indicate.Hope you get it up and running 👍🏼Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 17 Apr 2024, at 08:41, Infeconex @.***> wrote: Folks - I appreciate the original creator is not helping with development around this anymore, but I'm wondering if anyone is here and can help? I'm up to date on all versions, running managed HASS. I can disarm the alarm (if armed from a keypad), but I cannot arm the alarm system. My configuration is below: `texecom: host: [removed] port: 10001 mqtt: host: core-mosquitto prefix: texecom2mqtt username: mqtt-user password: [removed] client_id: texecom2mqtt keepalive: 30 clean: true retain: true retain_log: false reject_unauthorized: false homeassistant: discovery: true prefix: home-assistant areas:
id: a full_arm: armed_away part_arm_1: armed_night part_arm_2: armed_home part_arm_3: armed_custom_bypass code_arm_required: true code_disarm_required: false code: "[removed]" zones: [] cache: false log: info `
When I click the arm buttons in Home Assistant, the following is sent back on the logs: 2024-04-17 07:35:36 - WARNING: Unknown command ARM_HOME for area Area A 2024-04-17 07:35:44 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-17 07:35:53 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-17 07:35:54 - WARNING: Unknown command ARM_NIGHT for area Area A I feel I am so close to getting this running. Any ideas???
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing:
2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A
2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A
All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error?
2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Looks like your Area names are mismatched.Could this be a root cause?Kind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneKind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 11:44, Infeconex @.***> wrote: Thanks for the help on this. I've set the code required arming parameter to false, and I'm still getting the folllowing: 2024-04-19 10:38:00 - WARNING: Unknown command ARM_AWAY for area Area A. 2024-04-19 10:38:29 - WARNING: Unknown command ARM_NIGHT for area Area A All the zones are being read in correctly, see below for the startup logs (you'll also see my testing again with the code line removed entirely). This feels like the mapping does not work, is it possible that the alarm has a different 'name' in the texecom panel for overnight mode (part_arm_1)? Could that cause the log error? '2024-04-19 10:39:47 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)... 2024-04-19 10:39:47 - INFO: Connected to alarm, sleeping for 2 seconds... 2024-04-19 10:39:49 - INFO: Connection ready 2024-04-19 10:39:49 - INFO: Logging in to panel 2024-04-19 10:39:49 - INFO: Successfully logged in to panel 2024-04-19 10:39:49 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0) 2024-04-19 10:39:49 - INFO: Serial number: [removed] 2024-04-19 10:39:50 - INFO: Panel: Premier Elite 24 (V6.02.02LS1) 2024-04-19 10:39:50 - INFO: Fetched Area A: Area A 2024-04-19 10:39:50 - INFO: Fetched Area B: Area B 2024-04-19 10:39:50 - INFO: Fetched Zone 1: GARAGE DT (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:50 - INFO: Fetched Zone 2: BOOT ROOM DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 3: HALL DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:51 - INFO: Fetched Zone 5: PORCH DT (Type: Guard Access; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 6: BASEMENT STAIRS (Type: Guard; Areas: A) 2024-04-19 10:39:52 - INFO: Fetched Zone 8: FRONT DOOR (Type: Entry/Exit 1; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 9: OFFICE DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 10: LINK ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 11: OFFICE DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:53 - INFO: Fetched Zone 12: GRD FL B,ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 13: B,MENT HALL DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 14: KITCHEN DT (Type: Guard; Areas: A) 2024-04-19 10:39:54 - INFO: Fetched Zone 15: SWING ROOM DOOR (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 16: SWING ROOM DT (Type: Guard; Areas: A, B) 2024-04-19 10:39:55 - INFO: Fetched Zone 17: WARDROBE DT (Type: Guard; Areas: A) 2024-04-19 10:39:55 - INFO: Fetched Zone 18: LANDING DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 19: BEDROOM 1 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 21: BEDROOM 2 DT (Type: Guard; Areas: A) 2024-04-19 10:39:56 - INFO: Fetched Zone 22: LIVING ROOM DT (Type: Guard; Areas: A) 2024-04-19 10:39:57 - INFO: Fetched Zone 23: MASTER BEDROOM (Type: Guard; Areas: A) 2024-04-19 10:39:58 - INFO: Updating all zone states... 2024-04-19 10:39:58 - INFO: Updating all area states... 2024-04-19 10:39:58 - INFO: Application ready 2024-04-19 10:40:00 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:03 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:05 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:08 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 10:40:08 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:10 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 10:40:12 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:14 - INFO: KITCHEN DT status changed to Secure 2024-04-19 10:40:16 - INFO: KITCHEN DT status changed to Active 2024-04-19 10:40:19 - INFO: KITCHEN DT status changed to Secure'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
ok, so I have changed the configuration to the below, sensitive info removed:
`texecom: host: ip-addr-removed port: 10001 mqtt: host: core-mosquitto prefix: texecom2mqtt username: mqtt-user password: mypasswordremoved client_id: texecom2mqtt keepalive: 30 clean: true retain: true retain_log: false reject_unauthorized: false homeassistant: discovery: true prefix: home-assistant areas:
- id: area_a full_arm: armed_away part_arm_1: armed_night part_arm_2: armed_home code_arm_required: false code_disarm_required: false code: "000000" zones: [] cache: false log: info `
Still same response when I try either arming function:
2024-04-19 12:36:19 - WARNING: Unknown command ARM_AWAY for area Area A
2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A
2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A
Do you know of a way I can discover the area names from the alarm panel keypad itself? Maybe I could correlate these area names that way.
Hi, is this a panel you have installed yourself? If so the area names are in the global programming menu.Kind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 13:39, Infeconex @.***> wrote: ok, so I have changed the configuration to the below, sensitive info removed: `texecom: host: ip-addr-removed port: 10001 mqtt: host: core-mosquitto prefix: texecom2mqtt username: mqtt-user password: mypasswordremoved client_id: texecom2mqtt keepalive: 30 clean: true retain: true retain_log: false reject_unauthorized: false homeassistant: discovery: true prefix: home-assistant areas:
id: area_a full_arm: armed_away part_arm_1: armed_night part_arm_2: armed_home code_arm_required: false code_disarm_required: false code: "000000" zones: [] cache: false log: info `
Still same response when I try either arming function: 2024-04-19 12:36:19 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A 2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A Do you know of a way I can discover the area names from the alarm panel keypad itself? Maybe I could correlate these area names that way.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
I didn’t install it myself, but I know the installer. He would share the codes with me. I’m just not sure what buttons to press on the keypad!
On 19 Apr 2024, at 15:14, Smart-Techno1ogy @.***> wrote:
Hi, is this a panel you have installed yourself? If so the area names are in the global programming menu.Kind RegardsSimon BrownSent from my iPhoneOn 19 Apr 2024, at 13:39, Infeconex @.***> wrote: ok, so I have changed the configuration to the below, sensitive info removed: `texecom: host: ip-addr-removed port: 10001 mqtt: host: core-mosquitto prefix: texecom2mqtt username: mqtt-user password: mypasswordremoved client_id: texecom2mqtt keepalive: 30 clean: true retain: true retain_log: false reject_unauthorized: false homeassistant: discovery: true prefix: home-assistant areas:
id: area_a full_arm: armed_away part_arm_1: armed_night part_arm_2: armed_home code_arm_required: false code_disarm_required: false code: "000000" zones: [] cache: false log: info `
Still same response when I try either arming function: 2024-04-19 12:36:19 - WARNING: Unknown command ARM_AWAY for area Area A 2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A
2024-04-19 12:36:28 - WARNING: Unknown command ARM_NIGHT for area Area A
Do you know of a way I can discover the area names from the alarm panel keypad itself? Maybe I could correlate these area names that way.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/dchesterton/texecom2mqtt-hassio/issues/93#issuecomment-2066678351 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AYFC245BSNNJ646FJDO3DULY6EREPAVCNFSM6AAAAABGKYCTD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWGY3TQMZVGE . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AYFC245QSLVF35JI5JNHSU3Y6EREPA5CNFSM6AAAAABGKYCTD6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT3F4BE6.gif Message ID: @.***>