RFX (Polling)

[CudaNet]

I installed a 5881ENH last night and a single PIR for test. When I load the firmware (dev) with a revised YAML (rfseriallookup), upon start, the MQ message is set to ON (and remains ON). I observe for a bit and no other log messages are received for the PIR (good so far).

When I wave my hand in front of the PIR, It appears that the panel see's the motion event and all is well within the logs. MQ events toggle from ON to OFF. Good so far. It's the phantom ON/OFF MQ events that occur afterwards with zero motion occurring. These phantom events (possible polling from the receiver) continue to occur. For an actual event, I do see the RFX (denoted with 0629444,80 and 0629444,00). All others 'phantom' events seem to be missing this detail.

Current setup:
[2] 6290 keypads
[2] 4219 zone expanders
Vista 20p
Envisalink (EVL-4)

# rfseriallookup: "0019994:2:66,0818433:4:22,0123456:1:55,0399512:1:17" # serial1:loop#:zone1,serial2:loop#:zone2
  rfseriallookup: "0629444:1:19"

external_components:
  - source: github://Dilbert66/esphome-components@dev
    components: [vista_alarm_panel]
    refresh: 10min

  - platform: vista_alarm_panel
    id: z19
    name: "Foyer Motion"
    device_class: motion

[15:37:32][D][vista_alarm:1605]: success message from 0
[15:37:34][I][CMD:814]: [2025-01-27 08:37] F9 83 02 53 2F 00 00 00 00 00 00 00 00 
[15:37:34][I][EXT:814]: [2025-01-27 08:37] F9 00 C3 04 00 00 00 39 00 00 00 00 00 
[15:37:34][I][CHK:814]: [2025-01-27 08:37] 78 C3 00 00 00 00 00 00 00 00 00 00 00 
[15:37:36][I][CMD:814]: [2025-01-27 08:37] FB 02 20 F1 F2 00 00 00 00 00 00 00 00 
[15:37:36][I][EXT:814]: [2025-01-27 08:37] FB 04 09 9A C4 80 00 00 00 00 00 00 00 
[15:37:36][I][vista_alarm:1521]: RFX: 0629444,80
[15:37:36][I][CMD:814]: [2025-01-27 08:37] F8 59 10 5A 00 03 0A 0A F6 80 04 00 00 
[15:37:36][I][CMD:814]: [2025-01-27 08:37] F2 12 06 00 00 00 00 62 6C 02 45 6C F5 EC 01 01 01 00 00 91 
[15:37:36][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:37][W][component:237]: Component vista_alarm_panel took a long time for an operation (55 ms).
[15:37:37][W][component:238]: Components should block for at most 30 ms.
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F2 16 06 00 00 00 00 63 63 02 45 43 F5 31 FB 45 6C F5 EC 03 02 01 06 E3 
[15:37:37][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:37][D][vista_alarm:1014]: Sending zone status request 1, header 69
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F7 06 00 FF 10 19 00 00 28 02 00 00 46 
[15:37:37][I][vista_alarm:1679]: Partition: 01
[15:37:37][D][text_sensor:064]: 'Line1 partition 1': Sending state 'FAULT 19 FOYER  '
[15:37:37][D][text_sensor:064]: 'Line2 partition 1': Sending state 'MOTION          '
[15:37:37][I][vista_alarm:1699]: Prompt: FAULT 19 FOYER  
[15:37:37][I][vista_alarm:1700]: Prompt: MOTION          
[15:37:37][I][vista_alarm:1701]: Beeps: 0
[15:37:37][D][vista_alarm:942]: Assigning partition 1, to zone 19
[15:37:37][D][binary_sensor:036]: 'Ready partition 1': Sending state OFF
[15:37:37][W][component:237]: Component vista_alarm_panel took a long time for an operation (158 ms).
[15:37:37][W][component:238]: Components should block for at most 30 ms.
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F6 01 00 00 00 00 00 00 00 00 00 00 00 
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F2 0E 02 00 00 00 00 52 FE FE EC 03 02 01 06 B8 
[15:37:37][D][vista_alarm:1565]: AUI cmd state: 1, pending: 1
[15:37:37][D][vista_alarm:1605]: success message from 1
[15:37:37][D][vista_alarm:1201]: Zones: ,
[15:37:37][D][binary_sensor:036]: 'Foyer Motion': Sending state OFF
[15:37:37][D][vista_alarm:1183]: Setting open zone 19 to 0,  partition 1
[15:37:37][D][vista_alarm:1014]: Sending zone status request 2, header 6A
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F6 01 00 00 00 00 00 00 00 00 00 00 00 
[15:37:37][I][CHK:814]: [2025-01-27 08:37] A1 00 00 00 00 00 00 00 00 00 00 00 90 
[15:37:37][I][EXT:814]: [2025-01-27 08:37] F6 01 A1 0C 00 6B 62 02 45 43 F5 31 FB 43 6C 2C 
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F2 0E 02 00 00 00 00 53 FE FE EC 03 02 01 06 B7 
[15:37:37][D][vista_alarm:1565]: AUI cmd state: 2, pending: 1
[15:37:37][D][vista_alarm:1605]: success message from 2
[15:37:37][D][vista_alarm:1201]: Zones: ,
[15:37:37][I][CMD:814]: [2025-01-27 08:37] F6 02 00 00 00 00 00 00 00 00 00 00 00 
[15:37:37][I][CHK:814]: [2025-01-27 08:37] A2 00 00 00 00 00 00 00 00 00 00 00 90 
[15:37:37][I][EXT:814]: [2025-01-27 08:37] F6 02 A2 0C 00 6F 62 02 45 43 F5 31 FB 43 6C 27 
[15:37:38][I][CMD:814]: [2025-01-27 08:37] F2 0E 04 00 00 00 00 57 FE FE EC 03 02 01 06 B1 
[15:37:38][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:38][I][CMD:814]: [2025-01-27 08:37] F6 02 00 00 00 00 00 00 00 00 00 00 00 
[15:37:38][I][CHK:814]: [2025-01-27 08:37] E2 00 00 00 00 00 00 00 00 00 00 00 90 
[15:37:38][I][EXT:814]: [2025-01-27 08:37] F6 02 E2 0C 00 68 62 02 45 43 F5 31 FB 43 6C EE 
[15:37:38][I][CMD:814]: [2025-01-27 08:37] F2 0E 04 00 00 00 00 50 FE FE EC 03 02 01 06 B8 
[15:37:38][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:38][I][CMD:814]: [2025-01-27 08:37] FA 01 02 25 F7 E7 00 00 00 00 00 00 00 
[15:37:38][I][EXT:814]: [2025-01-27 08:37] FA 07 F7 00 00 00 00 00 00 00 00 00 00 
[15:37:38][I][CMD:814]: [2025-01-27 08:37] F6 01 00 00 00 00 00 00 00 00 00 00 00 
[15:37:38][I][CHK:814]: [2025-01-27 08:37] E1 00 00 00 00 00 00 00 00 00 00 00 90 
[15:37:39][I][EXT:814]: [2025-01-27 08:37] F6 01 E1 07 00 6C 6B 02 43 43 B9 
[15:37:39][I][CMD:814]: [2025-01-27 08:37] F2 0E 02 00 00 00 00 54 FE EC 01 01 01 00 00 BD 
[15:37:39][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:39][D][vista_alarm:1605]: success message from 0
[15:37:39][I][CMD:814]: [2025-01-27 08:37] F6 02 00 00 00 00 00 00 00 00 00 00 00 
[15:37:39][I][CHK:814]: [2025-01-27 08:37] 22 00 00 00 00 00 00 00 00 00 00 00 90 
[15:37:39][I][EXT:814]: [2025-01-27 08:37] F6 02 22 07 00 69 6B 02 43 43 7B 
[15:37:39][I][CMD:814]: [2025-01-27 08:37] F2 0E 04 00 00 00 00 51 FE EC 01 01 01 00 00 BE 
[15:37:39][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:37:39][I][CMD:814]: [2025-01-27 08:37] FB 02 25 F1 ED 00 00 00 00 00 00 00 00 
[15:37:39][I][EXT:814]: [2025-01-27 08:37] FB 04 09 9A C4 00 00 00 00 00 00 00 00 
[15:37:39][I][vista_alarm:1521]: RFX: 0629444,00
[15:37:39][I][CMD:814]: [2025-01-27 08:37] F8 59 10 5A 00 03 0A 0A 00 00 00 00 00 
[15:37:39][I][CMD:814]: [2025-01-27 08:37] FA 01 04 25 F7 E5 00 00 00 00 00 00 00 
[15:37:39][I][EXT:814]: [2025-01-27 08:37] FA 08 F7 00 3F 00 00 00 00 00 00 00 00 

[15:38:04][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:38:04][D][vista_alarm:1605]: success message from 0
[15:38:06][I][CMD:814]: [2025-01-27 08:38] F9 C3 02 53 EF 00 00 00 00 00 00 00 00 
[15:38:06][I][EXT:814]: [2025-01-27 08:38] F9 00 03 04 00 00 00 F9 00 00 00 00 00 
[15:38:06][I][CHK:814]: [2025-01-27 08:38] 78 03 00 00 00 00 00 00 00 00 00 00 00 
[15:38:10][I][CMD:814]: [2025-01-27 08:38] FA 01 02 20 F7 EC 00 00 00 00 00 00 00 
[15:38:10][I][EXT:814]: [2025-01-27 08:38] FA 07 F7 00 00 00 00 00 00 00 00 00 00 
[15:38:11][I][CMD:814]: [2025-01-27 08:38] FA 01 04 20 F7 EA 00 00 00 00 00 00 00 
[15:38:11][I][EXT:814]: [2025-01-27 08:38] FA 08 F7 00 3F 00 00 00 00 00 00 00 00 
[15:38:11][D][binary_sensor:036]: 'Foyer Motion': Sending state ON
[15:38:12][I][CMD:814]: [2025-01-27 08:38] F6 01 00 00 00 00 00 00 00 00 00 00 00 
[15:38:12][I][EXT:814]: [2025-01-27 08:38] F6 01 E1 07 00 68 6B 02 43 43 BD 
[15:38:12][I][CHK:814]: [2025-01-27 08:38] E1 00 00 00 00 00 00 00 00 00 00 00 90 
[15:38:12][I][CMD:814]: [2025-01-27 08:38] F2 0E 02 00 00 00 00 50 FE EC 01 01 01 00 00 C1 
[15:38:12][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:38:12][D][vista_alarm:1605]: success message from 0
[15:38:13][I][CMD:814]: [2025-01-27 08:38] F7 06 00 FF 10 08 00 1C 28 02 00 00 20 
[15:38:13][I][vista_alarm:1679]: Partition: 01
[15:38:13][I][vista_alarm:1699]: Prompt:  DISARMED CHIME 
[15:38:13][I][vista_alarm:1700]: Prompt:   Ready to Arm  
[15:38:13][I][vista_alarm:1701]: Beeps: 0
[15:38:13][D][binary_sensor:036]: 'Foyer Motion': Sending state OFF
[15:38:13][W][component:237]: Component vista_alarm_panel took a long time for an operation (138 ms).
[15:38:13][W][component:238]: Components should block for at most 30 ms.
[15:38:13][I][CMD:814]: [2025-01-27 08:38] F6 01 00 00 00 00 00 00 00 00 00 00 00 
[15:38:13][I][EXT:814]: [2025-01-27 08:38] F6 01 21 0C 00 69 62 02 45 43 F5 31 FB 43 6C AE 
[15:38:13][I][CHK:814]: [2025-01-27 08:38] 21 00 00 00 00 00 00 00 00 00 00 00 90 
[15:38:13][I][CMD:814]: [2025-01-27 08:38] F2 0E 02 00 00 00 00 51 FE FE EC 03 01 01 01 BF 
[15:38:13][D][vista_alarm:1565]: AUI cmd state: 0, pending: 0
[15:38:13][D][vista_alarm:1605]: success message from 0

Attaching the full log for your analysis. Assuming I'm not the cause (ouch).

vista-ecp_012725.txt

[Dilbert66]

Yes, there is definitely something odd here. It's in the code logic. Your setup is fine. I'll check into it. The logs are a great help.

[Dilbert66]

I did find a couple issues with the aui cmd processing that was causing some invalid responses and corrected those. Also, it almost looks like you have a couple touch panels on your system and one might be conflicting with the auiaddr: you have set in the yaml config. Can you set the auiaddr: 0 (to zero) and try your motion tests again to see how it works now. I've pushed the new changes to dev.
Please post logs as well.

[CudaNet]

Yes, [2] 6290's (AUI 1 and 2) and the Envisalink (address = 18), which, assuming my understanding is correct, acts as a standard keypad (non AUI). However, can the Vista20 manage 3 AUI devices ? This may account for the unpredictable behavior observed in the logs. Perhaps I need to jump to a 21ip (up to 4 AUI devices).

auiaddr: "0"

Logs attached:
vista-ecp_012725_AUI-0.txt

[Dilbert66]

You can have multiple aui addresses as long as none conflict. Yes, you would need a newer vista20 model to support 4 addresses. Check out your panel programming to see if it can support 4. Some newer 20's can I think. The odd behaviour was due to that as well as some software bugs that were in the code, which I've corrected. There is one last issue in your logs and that is with your zone expanders', specifically your 2nd one. It has zone address conflicts with your rf zone 19. You have to be careful how you address those. This is why you are seeing zone's being set as the esp code looks at the "FA xx" zone expander updates to get zone status as well as looking at the rf FB cmds and the F7 keypad updates.

FYI, the aui code is not technically needed but it does allow the esp to detect closure of internal and rf zones much faster instead of depending on the TTL.

[Dilbert66]

Glad it works! If you get bored you can try playing with the web_keypad and telegram components!

[CudaNet]

This is awesome stuff. I definitely plan on looking into the web keypad here in the next couple of days. Going to move from the 8266 to an ESP-32 (coming today). Once I have time I need to look in the LRR. Not quite sure (yet) if I enable this via Envisalink (shadowing) or through the YAML or ..... Currently not seeing this on Arm/Disarm/Bypass. Still in a quick learning phase. Looks as if this is a text sensor and cannot be defined in binary (which is fine).

lrrsupervisor: "false"

[Dilbert66]

it's yaml so uses true/false. Not the same as C++ :). The lrrsupervisor is to set the esp to emulate an LRR if you don't have one. I see some f9 messages in your logs so I assume you have an LRR device working (unless you just enabled the lrrsupervisor) . Envisalink does not do any emulation, only monitors an existing one.

Edit: In order to see all the arming/disarm/bypass data with the LRR, you need to enable those messages in the panel programming.

[CudaNet]

All is well, received my ESP-32 tonight and moved from the 8266 to that. Left LRR at false and things look really good.

[21:46:19][D][text_sensor:064]: 'Lrr Msg': Sending state 'CID_3441: Armed STAY by user 1, Partition 1'
[21:48:24][D][text_sensor:064]: 'Lrr Msg': Sending state 'CID_1441: Armed STAY by user 1 is Restored, Partition 1'

Envisalink requests that you key in a number of commands to execute at the keypad and supervisor (checked a bit ago) was one of them. So, I'm not surprised the log data revealed itself. For whatever reason the 8266 just didn't want to comply (acted a bit odd here and there). I basically copied over my config file and changed a few bits for the 32 and everything just worked.

Will take a look at the web keypad in the morning.

Cheers !

[Dilbert66]

I was reading through the Envisalink docs and it seems like you noted that it also does LRR emulation if needed. Good stuff.