AlarmDecoder Webapp "Test Timed Out" during setup

[jplee3]

Hey all,

So after not having played with the AlarmDecoder distro and webapp, I jumped back into it. Setup-wise, everything has mostly gone smooth but I did run into a hiccup with the webapp setup (I'm also seeing this when I "Test Device"):

Opening device ✔
Saving device configuration ⚠ Test timed out.
Keypad communication (Send) ⚠ Test timed out.
Keypad communication (Receive) ⚠ Test timed out.


Weird thing is, I ran "Test Device" while telnetted into my device on port 10000, and I see this series of messages:


!sn:00000436
!boot..
!wait
!load

[*I press enter here*]
!no
!sn:00000436
!boot....................

[100000010000--------],008,[f70000071008001c08020000000000],"****DISARMED**** Ready to Arm "
[100000010000--------],008,[f70000071008001c08020000000000],"****DISARMED**** Ready to Arm "


Is something wrong with my device? It's an older style AD2USB

[jplee3]

Agh, I screwed something up. I sorta recall, now I think I was trying to flash/update my device a while back and may have messed something up. I just tried running ad2-flashupdater with the 2.1f.10 firmware (mine's a 2.0 device I'm pretty sure) and now it seems my device is stuck in a bootloop doing this:

!sn:00000436
!boot....................
!wait
!load


The firmware is just timing out now:

root@alarmdecoder:/home/pi# ./ad2-firmwareupload ademcoemu_V2_1f_10.hex /dev/ttyUSB0 115200
Flashing device: /dev/ttyUSB0 - 115200 baud
Firmware: ademcoemu_V2_1f_10.hex
Rebooting device..
Rebooting device..
Rebooting device..
Waiting for boot loader..
Uploading firmware.Error: Timeout while waiting for line terminator

[jplee3]

Very strange, so I attempted using ad2-flashupdate to upload older versions of the FW and it failed. I thought all was lost, then I went back into the webapp and tried uploading the firmware through that and it appears like that may have gotten it back to a semi-working state where I'm back to the original issue with the "Test Timed Out" messages and getting this:

[100000010000--------],008,[f70000071008001c08020000000000],"****DISARMED**** Ready to Arm "
!sn:00000436
!boot..
!wait
!load

NOTE: I'm seeing the start of the boot process occur when it goes to the "Saving device configuration" phase of the "Test Device" cycle.

[kevin]

To be honest, we have never tested a 2.0 device and its firmware with the webapp so I am unsure of what the results would be. Let me see if we can replicate this at the office.

Please try using the Alarmdecoder keypad desktop software https://www.alarmdecoder.com/wiki/index ... der_Keypad to flash firmware to see if that helps.