Unable to use alarm_keypress

[WiehanAu]

Hi @Dilbert66,

Thank you for making these efforts available to the community.

I have this set up with HA and all working great. Zones are reacting perfect. Can arm and disarm etc, all working good. The only issue I'm having is using alarm_keypress.

Whenever I try to send alarm_keypress to the alarm panel, the physical keypad shows a "System Unavailable" message for about 10 seconds. During this time the keypad is unresponsive. It clears up and the system returns to normal function. Any guidance or ideas on how to troubleshoot or what the problem could be?

---

EDIT:
When sending the keypress, I see the following in the log:

[16:12:34][D][Debug:794]: Writing keys: *64388 to partition 1
[16:12:34][D][info:799]: partition is 0
[16:12:34][I][Moduledata::874]: 05: FF 01 28 FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:34][I][Paneldata: :874]: 5D: 5D 00 00 00 00 00 00 5D 00 00 00 00 00 00 00 00
[16:12:34][I][Paneldata: :874]: E6: E6 00 18 01 00 00 00 00 00 FF 00 00 00 00 00 00
[16:12:34][I][Moduledata::874]: 0A: FF 01 1B FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:34][I][Paneldata: :874]: E6: E6 00 20 80 A5 00 00 00 00 80 AB 00 00 00 00 00
[16:12:34][D][info:2431]: procesprogramzones: 05,
[16:12:35][I][Paneldata: :874]: 05: 05 00 80 A5 81 01 00 C7 00 C7 01 00 00 00 00 00
[16:12:35][D][info:1593]: status A5, last status 01,line2status 00,selection 01,partition=1,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1': Sending state 'Enter '
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2': Sending state 'master code '
[16:12:35][D][info:1593]: status 01, last status 01,line2status 00,selection 01,partition=2,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1 partition 2': Sending state 'System is Ready'
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2 partition 2': Sending state 'Ready to Arm <>'
[16:12:35][D][text_sensor:067]: 'dscalarm01 Partition 1 Status ': Sending state 'unavailable'
[16:12:35][D][binary_sensor:036]: 'dscalarm01 Partition 1 Ready': Sending state OFF
[16:12:35][I][Moduledata::874]: 05: FF 01 11 FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:35][I][Moduledata::874]: 05: FF 01 0F FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:35][I][Moduledata::874]: 05: FF 01 1B FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:35][I][Moduledata::874]: 05: FF 01 11 FF FF FF FF FF FF FF 01 00 00 00 00 00
[16:12:35][I][Paneldata: :874]: 64: 64 00 06 6A 00 00 00 00 00 00 00 00 00 00 00 00
[16:12:35][D][text_sensor:067]: 'dscalarm01 beeps': Sending state '3'
[16:12:35][D][text_sensor:067]: 'dscalarm01 partition 2 beeps': Sending state '3'
[16:12:35][D][info:1593]: status A5, last status A5,line2status 00,selection 01,partition=1,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1': Sending state 'Enter '
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2': Sending state 'master code '
[16:12:35][D][info:1593]: status 01, last status 01,line2status 00,selection 01,partition=2,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1 partition 2': Sending state 'System is Ready'
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2 partition 2': Sending state 'Ready to Arm <>'
[16:12:35][I][Paneldata: :874]: 5D: 5D 00 20 00 00 00 00 7D 02 00 00 00 00 00 00 00
[16:12:35][I][Paneldata: :874]: E6: E6 00 18 01 20 00 00 00 00 1F 00 00 00 00 00 00
[16:12:35][I][Paneldata: :874]: A5: A5 00 22 56 B0 32 E6 00 E5 00 00 00 00 00 00 00
[16:12:35][D][text_sensor:067]: 'dscalarm01 event': Sending state '2022.05.21 16:12 P:1 Master code:40'
[16:12:35][I][Paneldata: :874]: 0A: 0A 00 80 A9 00 00 00 00 00 33 00 00 00 00 00 00
[16:12:35][D][info:2431]: procesprogramzones: 04,
[16:12:35][I][Paneldata: :874]: E6: E6 00 20 80 A9 00 00 00 00 80 AF 00 00 00 00 00
[16:12:35][D][info:2431]: procesprogramzones: 05,
[16:12:35][D][text_sensor:067]: 'dscalarm01 System Status': Sending state 'online'
[16:12:35][I][Paneldata: :874]: 05: 05 00 80 A9 81 01 00 C7 00 C7 01 00 00 00 00 00
[16:12:35][D][info:1593]: status A9, last status A5,line2status 00,selection 01,partition=1,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1': Sending state '*6: User functions'
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2': Sending state 'Time and Date'
[16:12:35][E][json:034]: Could not allocate memory for JSON document! Requested 496 bytes, largest free heap block: 496 bytes
[16:12:35][D][info:1593]: status 01, last status 01,line2status 00,selection 01,partition=2,skip=0
[16:12:35][D][text_sensor:067]: 'dscalarm01 line1 partition 2': Sending state 'System is Ready'
[16:12:35][E][json:034]: Could not allocate memory for JSON document! Requested 496 bytes, largest free heap block: 496 bytes
[16:12:35][D][text_sensor:067]: 'dscalarm01 line2 partition 2': Sending state 'Ready to Arm <>'
[16:12:35][E][json:034]: Could not allocate memory for JSON document! Requested 496 bytes, largest free heap block: 496 bytes

[Dilbert66]

Ok, I see the issue. You are using an ESP8266 and from the errors I see it's low on memory. That causes all kinds of issues. With all the latest changes on ESPHOME lately, a lot more ram is being used and of course, this new branch also also uses a good chunk of memory. That's why I recommend an ESP32 for this branch. I will see if can add some defines in the library to disable some functions to limit ram useage on the ESP8266 and allow it work ok

[Dilbert66]

Try setting the logging level to NONE or ERROR and see if that helps.

[WiehanAu]

Thanks @Dilbert66,

Also seeing the following errors when compiling:

Compiling /data/dscalarm01/.pioenvs/dscalarm01/src/dscKeybusPrintData.cpp.o
src/dscKeybusInterface.cpp: In static member function 'static void dscKeybusInterface::dscClockInterrupt()':
src/dscKeybusInterface.cpp:597:78: warning: 'static bool dscKeybusInterface::redundantPanelData(byte*, volatile byte*, byte)' is deprecated: Use IRAM_ATTR in place of ICACHE_RAM_ATTR to move functions into IRAM [-Wdeprecated-declarations]
597 | if (redundantPanelData(previousCmd05, isrPanelData, isrPanelByteCount)) skipData = true;
| ^
src/dscKeybusInterface.cpp:501:1: note: declared here
501 | dscKeybusInterface::redundantPanelData(byte previousCmd[], volatile byte currentCmd[], byte checkedBytes) {
| ^~~~~~~~~~~~~~~~~~
src/dscKeybusInterface.cpp:602:78: warning: 'static bool dscKeybusInterface::redundantPanelData(byte*, volatile byte*, byte)' is deprecated: Use IRAM_ATTR in place of ICACHE_RAM_ATTR to move functions into IRAM [-Wdeprecated-declarations]
602 | if (redundantPanelData(previousCmd1B, isrPanelData, isrPanelByteCount)) skipData = true;
| ^
src/dscKeybusInterface.cpp:501:1: note: declared here
501 | dscKeybusInterface::redundantPanelData(byte previousCmd[], volatile byte currentCmd[], byte checkedBytes) {
| ^~~~~~~~~~~~~~~~~~
src/dscKeybusInterface.cpp: In static member function 'static void dscKeybusInterface::processPendingResponses(byte)':
src/dscKeybusInterface.cpp:818:62: warning: 'static void dscKeybusInterface::updateWriteBuffer(byte*, int, byte, int, bool, bool)' is deprecated: Use IRAM_ATTR in place of ICACHE_RAM_ATTR to move functions into IRAM [-Wdeprecated-declarations]
818 | updateWriteBuffer((byte * ) moduleSlots, 9,1,maxFields11 );
| ^
src/dscKeybusInterface.cpp:788:1: note: declared here
788 | dscKeybusInterface::dscKeybusInterface::updateWriteBuffer(byte * src, int bit,byte partition,int len, bool alarm, bool star) {
| ^~~~~~~~~~~~~~~~~~
src/dscKeybusInterface.cpp:838:53: warning: 'static void dscKeybusInterface::updateWriteBuffer(byte*, int, byte, int, bool, bool)' is deprecated: Use IRAM_ATTR in place of ICACHE_RAM_ATTR to move functions into IRAM [-Wdeprecated-declarations]
838 | updateWriteBuffer((byte ) cmdD0buffer,9,1,6);
| ^
src/dscKeybusInterface.cpp:788:1: note: declared here
788 | dscKeybusInterface::dscKeybusInterface::updateWriteBuffer(byte * src, int bit,byte partition,int len, bool alarm, bool star) {
| ^~~~~~~~~~~~~~~~~~
src/dscKeybusInterface.cpp: In static member function 'static void dscKeybusInterface::processPendingQueue(byte)':
src/dscKeybusInterface.cpp:857:189: warning: 'static void dscKeybusInterface::updateWriteBuffer(byte, int, byte, int, bool, bool)' is deprecated: Use IRAM_ATTR in place of ICACHE_RAM_ATTR to move functions into IRAM [-Wdeprecated-declarations]
857 | updateWriteBuffer((byte * ) writeQueue[outIdx].data, writeQueue[outIdx].writeBit,writeQueue[outIdx].partition,writeQueue[outIdx].len, writeQueue[outIdx].alarm, writeQueue[outIdx].star); //populate write buffer and set ready to send flag
| ^
src/dscKeybusInterface.cpp:788:1: note: declared here
788 | dscKeybusInterface::dscKeybusInterface::updateWriteBuffer(byte * src, int bit,byte partition,int len, bool alarm, bool star) {
| ^~~~~~~~~~~~~~~~~~
Compiling /data/dscalarm01/.pioenvs/dscalarm01/src/dscKeybusProcessData.cpp.o

[Dilbert66]

Yes, the iram warning I'm aware. For now I need to leave the old IRAM declaration since if I update it, people with older versions of ESPHOME won't be able to compile. It won't cause issues.

[WiehanAu]

Compiling /data/dscalarm01/.pioenvs/dscalarm01/lib975/ESPAsyncTCP-esphome/SyncClient.cpp.o
In file included from src/main.cpp:86:
src/dscAlarm.h: In member function 'void DSCkeybushome::getNextIdx(std::string, byte)':
src/dscAlarm.h:767:46: warning: operation on '((DSCkeybushome*)this)->DSCkeybushome::partitionStatus[(((int)partition) - 1)].DSCkeybushome::partitionType::editIdx' may be undefined [-Wsequence-point]
767 | partitionStatus[partition - 1].editIdx = partitionStatus[partition - 1].editIdx + 1 < partitionStatus[partition - 1].digits ? partitionStatus[partition - 1].editIdx + 1 : partitionStatus[partition - 1].editIdx = 0;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiling /data/dscalarm01/.pioenvs/dscalarm01/lib975/ESPAsyncTCP-esphome/tcp_axtls.c.o

[Dilbert66]

Don't worry about that warning, it won't cause issues. I will fix it at some point though.

[WiehanAu]

I have set log level to Error.
The same happens with the keypad locking up, but not seeing the [16:12:35][E][json:034]: Could not allocate memory for JSON document! Requested 496 bytes, largest free heap block: 496 bytes error anymore

[WiehanAu]

I will order a ESP32 and swop it out in the week, see if that helps.

[WiehanAu]

Received a ESP32 this morning. I notice you mention the out of memory issues is addressed. Will test the update this evening with esp8266 first before swopping with with ESP32.

[WiehanAu]

Updated on ESP8266, same issue persists. Could this be caused by a wiring issue? Everything works, except for alarm_keypress?

Attempting to switch over to ESP32 but getting "WARNING GPIO2 is a Strapping PIN and should be avoided." when trying to build the image.
---Disregard above about ESP32, system hung. It compiles fine.

[Dilbert66]

If you can't send then you either have a wiring issue or you have a wrong pin configured for the write line.

[Dilbert66]

Don't worry about the gpio2, that's only the led config. You can remove that section or change it to point to whatever gpio your led is on. Most of the time it uses gpio2

[Dilbert66]

I just fired up my esp8266 with the latest "new" branch code and so far I dont' see any issues. i'll keep monitoring it. At this point I'm not sure why you are seeing the errors. Are you using the latest ESPHOME 2022.5.0?

Edit: spoke too soon. Seeing the out of memory errors now. Might still be the issue you are having. Anyhow , I will see if I can optimize a few things.

Ok, I had too many clicents connected to the esp so I see this is definively a ram issue. More tweaks needed

[slipx06]

Have you disabled the web server in your config? I had to disable that to compile on my ESP8266. Running the latest ESPHome and new branch without issues.

[Dilbert66]

By the way folks, if there are features you want to see or change let me know. Since I basically rewrote most of the library, I can add or tweak things since it's still in dev.

[Dilbert66]

Also disable or remove the time: section in the yaml if you have it. That's also uneeded on the esp8266.

[slipx06]

Oh wow, did not realise you had made so many updates. So I guess I'm not running the latest "new" branch. I see you removed the cmdWaitTime: "250" parameter needed for my panel so not sure if I should update now.

[Dilbert66]

Oh, I forgot it was your panel that had those issues. No worries, I had to tweak for ram useage so I moved the config to a #define.
FYI, the time was not needed. Only skipping the first new cmd is fine.

Uncomment this line at the top of dsckeybus.h

//#define DEBOUNCE  //for older panels that send bogus cmd05's during switchovers

[slipx06]

Thanks. Compiled and testing

[slipx06]

  - platform: template
    id: m1
    name: "$systemName Partition 1 Msg "
    icon: "mdi:alert-box"

This sensor is not working anymore?

Also when arming the sensor below goes to pending ->disarmed ->armed

• platform: template
  id: p1
  name: "$systemName Partition 1 Status "
  icon: "mdi:shield"

[Dilbert66]

Yes, that was my bad. I had removed the logic for it since I felt it was duplicating the line1/line2 status but in retrospect it has other uses so I put it back in. I've also added a fix for the pending/disarmed flip flop. Make sure you update your yaml

I've pushed the updates now.

Edit: This update should also fix the out of memory issues on the esp8266.

[slipx06]

Both issues fixed in the latest update. Thank you.