Closed travisrroy closed 2 years ago
From the look of the logs, there is something very weird going with the tx line. Those F6 are send cmds to the panel. Looking at what you are sending, the format is incorrect. From what I see, your esp is sending bad data to the panel continuously. I have no idea what is causing that.
[02:45:41][D][Debug:412]: Writing keys: 12341
[02:45:42][I][CMD:445]: F6 12 00 00 00 00 00 00 00 00 00 00 00 #this is the panel response to a request to send. It's saying , ok device address 18 (hex 0x12) go ahead and send your keys
[02:45:42][I][EXT:445]: F6 12 00 22 0A 01 02 03 04 01 DD 00 00 #this is your ESP sending it's keys. The first 3 bytes are just to show that it's a response to the F6 12. The following bytes are 22 0a 01 02 03 04 01 dd . 22 is the message id, 0a should be the message length but it is incorrect. It should be 06 , then your 5 keys then the last byte is a checksum. I didnt validate the checksum to see if that is correct.
[02:45:42][I][EXT:445]: F6 12 00 92 01 6D 02 03 04 01 DD 00 00 # this is the following response. I have no idea where that is coming from. I
Honestly, to me it looks like you have 2 different devices sending on address 18?
Try changing your ESP address to another address.
Ah! That's what it was. Enabled address 19 and changed to 19 and now it's working!
I am still unsure about lrrSupervisor. Would you be able to clarify what that is for?
If you are using a long range radio (IP or GSM) interface and monitored by a central monitoring station , then set it to false. If you don't have this interface, then set it to true and the firmware will emulate one. It enables extra status messages sent from the panel to be captured by the firmware for display.
https://www.alarmgrid.com/videos/honeywell-vista-program-star-29-long-range-radio
Ok, good to know. thanks!
Would you know how to fix all these values being set to Unknown after an OTA update?
Try using the "dev" branch. It has been updated to support multi partitions as well as other bug fixes. Please note that the yaml file has changed so you will need to update it with your own config.
Ah! That definitely helped. After a couple minutes, it updated all the binary sensors to their proper values.
Although, I did have to make a few changes to the single partition config to get the keypad working. I'm sure you know what needs to be changed for that or would you rather I open a pull request with those changes?
Hello Alain! Thanks for creating this project to help us smartify our older alarm systems.
I'm having some odd issues with my setup that I haven't been able to figure out. I've read through many of the other issues people have had and still haven't been able to figure it out. I've tried to attach as much information and logs about my system as possible. Don't mind the Telco Fault, I had the system disconnected at this time to hopefully prevent a false alarm. I'm sure my issues are just a mistake (or mistakes) I've made trying to set this up.
System
Devices
Config
Sensor Issue
O
. This was working at some point, but I managed to break it while trying to get keypad presses to work.Things I've Tried
07
Log
This is the log from when I open the basement door, zone 12.
HA Keypad Issue
Log
When just hitting a key on the keypad
When using HA Developer Tools to send a code