Support for multiple partitions on Vista 20P? #68

warnejo · 2022-03-26T21:50:58Z

warnejo
Mar 26, 2022

First of all, let me say I am a newbie hobbyist and not a developer, but I was able to set up a Raspberry PI running Home Assistant with ESPHome by following all of the good info found here. I built and configured an ESP32 circuit using the provided schematics and got vistaECP set up with everything working good in HA including the custom alarm keypad. Kudos to @Dilbert66 and all who have developed this! I think this is very cool!

My only problem is that I have two partitions on my Vista 20P panel (one for my house and one for my detached garage) so the vistaalarm sensors such as System Status, Line 1, Line 2, etc. continually toggle between the status of Partition 1 and Partition 2.

My question is: Does this support multiple partitions at this time? I wasn't sure if there's a way to mask the serial data from the panel for each partition or a way to set it up to use the partitions separately and even have two virtual keypads, one for each partition, similar to my physical equipment?

I appreciate any help, info, or examples or if this is currently not possible, any consideration of adding the capability in the future. Thanks!

Dilbert66 · 2022-03-27T16:56:34Z

Dilbert66
Mar 27, 2022
Maintainer

I just need to make a small change in the code to filter the display and status according to the partition flag. I was not doing this. Good suggestion. I'll have a new version on the "dev" branch later today. Now, what will happen is that when you switch partition on the keypad it will only display the zone and status data related to that partition.

0 replies

Dilbert66 · 2022-03-27T18:47:05Z

Dilbert66
Mar 27, 2022
Maintainer

ok, pushed updated version to dev and master. Only file changed was vistaalarm.h
Since the code currently emulations a keypad assigned to any one partion. You can then view another partion status/etc using the +*+<partition#> code sequence. This will allow you to control and view the other partitions. The panel will revert back to the default partition after 30 seconds of inactivity.Currently, if you want to thave HA monitor both partitions simulataneously, you will need to have a separate esp32 setup for a different keypad ID assigned to the other partition.


I suppose it would be possible to modify the code emulate multiple keypads from the one device. It's not somethign I looked into much.

0 replies

Dilbert66 · 2022-03-27T19:47:43Z

Dilbert66
Mar 27, 2022
Maintainer

Hold off on updating to this version. I have to make other changes to support this correctly.

Edit: Never mind, You can update to master and it will work as described above. I will see if I can add multi partition support for HA so that all partition statuses will be available.

20 replies

warnejo May 3, 2022
Author

Ok, that's what I thought but it doesn't appear to be doing anything even when I enter my code. I can use the vistaalarm_alarm_keypress_partition to disarm but not the vistaalarm_alarm_disarm.

warnejo Jul 30, 2022
Author

So, I've been using this for a while, and it works great for the most part except for a couple of things that I haven't been able to figure out.

I set up notifications in Home Assistant for zones such as garage doors. When I open a door, I do get the notification that it opens but when I close the door, I get notified that it closed, then another open, then another closed. If I add a 30 second delay to the notification, it will not do that but I'm not sure why the vista is bouncing it opened and closed again when it closes. This happens on all door zones I set up and I checked with a meter that it's not physically doing it. Does the TTL parm in the yaml have anything to do with this? It is at 30000.
I see in the logs that the ESPHome disconnects from the API. I see this message:

WARNING Disconnected from API
WARNING Can't connect to ESPHome API for vistaalarm.local: Hello timed out
INFO Trying to reconnect to vistaalarm.local in the background
INFO Successfully connected to vistaalarm.local
I have used other interfaces in the past with my vista and have had similar issues with it disconnecting from the API. I use the zone extender relays to open garage doors and it seems like it does this more when I am using the relays, but I am unsure. I am wondering if I have something programmed wrong in the panel or set wrong in the yaml? Can the LRR settings have anything to do with it? Attaching log and yaml if there's anything that can be looked at.

Thanks as always for this project and any assistance!

2022-07-30_logs_vistaalarm_logs.txt
2022-07-30_vistaalarm.yaml.txt

Dilbert66 Jul 31, 2022
Maintainer

Interesting. I had a look at your logs and cannot see anything there that would cause your bouncing notifications. If you do a search in the logs for any of the sensors you will find the sensor update message that goes to HA and what it sends. For example:
[11:25:31][D][text_sensor:067]: 'Center Garage Door': Sending state 'C'
If you search for "Center garage door" you will find all the update messages for that door. You might see the same message sent a multiple times since I have the code resend periodically but I don't see the messages going from O to C then O as you indicated. The message only changes when the event occurs.

As to the disconnection, I don't have an answer for that. It's a known issue with some devices or networks that they lose connection periodically. Thats' most likely an esphome thing and not related to this application. Using relays or LRR should not have any impact at all that i know of on the ESP.

Are you powering using USB? Make sure the usb brick can output at least an amp or two. Another possibility perhaps is that the garage opener/relay is causing rf interference and affecting wifi? Here's some info I found quickly when looking up the issue.
https://electronics.stackexchange.com/questions/379497/relay-circuit-interfere-with-rf-signal-how-to-improve

Dilbert66 Jul 31, 2022
Maintainer

FYI, the TTL time is used to allow the ESP time to detect when a fault message stops being sent by the panel. This way, the application can determine that the fault was cleared (closed). If the TTL is too short, then the EsP won't wait for the next fault message and assume the fault is cleared even if it's not. This depends on how many messages the panel is sending and such as many faulted zones. If the TTL is long, then it will appear as a long delay before the zone shows as closed. The balance is to have a minimal TTL for faster close response.

warnejo Aug 2, 2022
Author

Thanks for taking a look. I'll have to do some more testing and look closer at the logs as far as the bouncing. I'm pretty sure it does it on all zones including basic magnetic door and window switches. Maybe it is something with HA or ESPHome causing that. If I set the notification in HA to needing to be set for 30sec then it works as expected but I could miss faults that restore quickly with that setup. As far as the disconnects, it was strange that right after I posted my question the other day, it started disconnecting repeatedly every 3 minutes for about 45min so I power cycled my vista panel and it stopped. I wasn't doing anything with the panel at the time like using the relays. Then it went for over a day without disconnecting then it disconnected again today when nothing was happening. I haven't been able to correlate it with anything else so far. I have the ESP32 powered off the vista panel using the schematic with the optocouplers that was provided. I do have a good size power supply for the panel, but I think I need to double check my panel power budget because I have a lot of devices in the system: 6 keypads including a touchscreen tuxedo, 3 zone/relay expanders, etc.. I doubt the Wi-Fi is a problem because I had similar disconnect issues with other devices such as the Envisalink and AlarmDecoder that were direct connected. That was one of the reasons I started playing with this in the first place. I like this a lot better even with my issues. I really don't need it to be Wi-Fi but the ESP32 I used is Wi-Fi only. I did get an ESP32 dev board with an ethernet chip but I wasn't able to get it to work yet. Thanks for the info on the relay interference and TTL. I'll have to dig into more when I get some time and try to get better information.

TimerZero13 · 2022-03-28T22:57:55Z

TimerZero13
Mar 28, 2022

I'm testing your code on Vista 50P and it seems to work. But full support for multiple partitions is very necessary.

0 replies

Dilbert66 · 2022-04-06T16:09:23Z

Dilbert66
Apr 6, 2022
Maintainer

I've pushed an update to the "dev" branch for multi partition support. Have a look at the multi-partition yaml file for an example setup. Modify to your environment. The important part is to first program new keypad entries in your panel for each partition to use in the config.

0 replies

TimerZero13 · 2022-04-14T16:56:27Z

TimerZero13
Apr 14, 2022

Everything works for me on Vista P50 except for displaying the state of the zones. At the same time, they are displayed on the virtual keyboard display. Could this be because I'm using multiple partitions?

0 replies

Dilbert66 · 2022-04-14T17:26:05Z

Dilbert66
Apr 14, 2022
Maintainer

I don't see an issue in my testing here. Zones will only show on the display assigned to the partition. Can you post your yaml config so we can see what the issue is. Just remove any sensitive areas you don't want others to view. The yaml was changed for multi partitions.

Just to clarify though, you can have separate virtual keyboard displays for each partition, independent of each other and each will only display the associated partition messages for it.

0 replies

TimerZero13 · 2022-04-14T19:16:33Z

TimerZero13
Apr 14, 2022

Everything is clear with the virtual keyboard, everything is fine there. Thank you!
I meant zone sensors. They show me "C" all the time.
configuration.yaml is standard after installation. Consider empty.

2 replies

Dilbert66 Apr 14, 2022
Maintainer

Are you using esphome or mqtt? I meant the yaml for the esphome config for the vista.

TimerZero13 Apr 14, 2022

I am using Esphome.
Here is my config file:
VistaAlarm.zip

Dilbert66 · 2022-04-14T21:01:28Z

Dilbert66
Apr 14, 2022
Maintainer

Ok, I see the issue. You have not customized the esphome yaml to your own needs for the zone definititions. ie. the z1, z2, egs. You need to modify those to your own zones and assign them names to suit their location. What is in that yaml is only an example. You'll need to add or remove any zxx id that is not used by your system. You will need to change this in two places. The Case statement and the text_sensors block.

6 replies

Dilbert66 Apr 15, 2022
Maintainer

Yes, you are correct if the zone number is the same it doesnt matter but I thought you were using the dev version which has full multi partition support. The master version really only supports showing zones/messages for one partition which is the partition that the keypad address belongs to (default in this case is 17). For any other partion, they will be ignored.

Can you post an example esphome log showing the zones in question?

Do you have keypad address 17 programmed in your system for the partition?

For multi partition, I would recommend you try out the dev version instead which is better suited for multi partition installations.

Dilbert66 Apr 16, 2022
Maintainer

I've pushed an update to master branch to allow zone messages to get processed no matter what partition. Only system messages will be filtered out. This should address your issue for this branch. Eventually I will merge the dev branch to master as the algorithm coded in dev is the better approach. I won't do that yet until that branch has been tested a bit more.

TimerZero13 Apr 16, 2022

Thank you very much for your help. But the zone sensors still do not change, apparently something is wrong with Vista P50.
I couldn't install the dev version. Gives errors:
INFO Reading configuration /config/esphome/VistaAlarm.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing vistaalarm (board: d1_mini; framework: arduino; platform: platformio/espressif8266 @ 3.2.0)

HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
Dependency Graph
|-- 1.0
|-- 1.2
Compiling /data/vistaalarm/.pioenvs/vistaalarm/src/main.cpp.o
Compiling /data/vistaalarm/.pioenvs/vistaalarm/lib67b/ESP8266WiFi/ESP8266WiFiGeneric.cpp.o
/config/esphome/VistaAlarm.yaml: In lambda function:
/config/esphome/VistaAlarm.yaml:105:17: error: 'class esphome::vistaECPHome' has no member named 'partitionKeypads'; did you mean 'partitions'?
105 | VistaECP->partitionKeypads[1]=$keypadAddr1;
| ^~~~~~~~~~~~~~~~
| partitions
/config/esphome/VistaAlarm.yaml:106:17: error: 'class esphome::vistaECPHome' has no member named 'partitionKeypads'; did you mean 'partitions'?
106 | VistaECP->partitionKeypads[2]=$keypadAddr2;
| ^~~~~~~~~~~~~~~~
| partitions
/config/esphome/VistaAlarm.yaml:107:17: error: 'class esphome::vistaECPHome' has no member named 'partitionKeypads'; did you mean 'partitions'?
107 | VistaECP->partitionKeypads[3]=$keypadAddr3;
| ^~~~~~~~~~~~~~~~
| partitions
/config/esphome/VistaAlarm.yaml: In function 'void setup()':
/config/esphome/VistaAlarm.yaml:105:17: error: 'uint8_t esphome::vistaECPHome::partitions [3]' is private within this context
105 | VistaECP->partitionKeypads[1]=$keypadAddr1;
| ^~~~~~~~~~~~~~~~
In file included from src/main.cpp:84:
src/vistaAlarm.h:225:13: note: declared private here
225 | uint8_t partitions[3];
| ^~~~~~~~~~
Compiling /data/vistaalarm/.pioenvs/vistaalarm/lib67b/ESP8266WiFi/ESP8266WiFiGratuitous.cpp.o
Compiling /data/vistaalarm/.pioenvs/vistaalarm/lib67b/ESP8266WiFi/ESP8266WiFiMulti.cpp.o
*** [/data/vistaalarm/.pioenvs/vistaalarm/src/main.cpp.o] Error 1
========================= [FAILED] Took 64.31 seconds =========================

Dilbert66 Apr 17, 2022
Maintainer

Had missed a file in the latest push. Updated dev now. Could you post a log of the esphome traffic data either with the master or dev code versions. This way I can see why your system is not showing the zone statuses. Just a section which shows open/close of any zone

Dilbert66 Apr 17, 2022
Maintainer

Honestly though, I have no idea if the Vista50p is compatible with my code since I've never seen or tested with one. That's why i need to see logs to see if thats the case. If it's not compatible there is nothing I can really do to fix that since I would need access to one to view the bus.

Edit, you did indicate that they show on the virtual keypad so that means the data is captured correctly but there might be some status flag differences compared to the Vista20p. The logs will indicate this.

TimerZero13 · 2022-04-17T15:33:36Z

TimerZero13
Apr 17, 2022

Here is a piece from my log (version master). It can be seen that zone 8 is not ready. This is shown by the virtual keyboard, but not by the zone sensor. Incomprehensible words in the log - this is how words in non-English are transmitted.

Also, the virtual keyboard in the latest version of the wizard tries to display the general status of all partitions (a list of partitions with an indication of the status). Although Vista is configured to show the first partition.

Also, if the zone is not ready for a short time, then it does not get into the log and, accordingly, is not displayed anywhere.

[18:01:27][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:27][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:29][D][text_sensor:067]: 'vistaalarm Back door': Sending state 'C'
[18:01:30][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:30][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'HAP 08 H 08 '
[18:01:30][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:30][I][INFO:687]: Prompt: HAP 08 H 08
[18:01:30][I][INFO:688]: Prompt:
[18:01:30][I][INFO:689]: Beeps: 0

[18:01:30][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:30][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:30][I][CMD:439]: F7 02 00 00 00 20 80 0C 08 02 00 01 50
[18:01:32][D][text_sensor:067]: 'vistaalarm Family room window LF': Sending state 'C'
[18:01:32][D][text_sensor:067]: 'vistaalarm Basement windows9': Sending state 'C'
[18:01:33][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:36][I][CMD:439]: F7 01 00 02 00 20 80 40 08 02 00 01 50
[18:01:36][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'PAP. A'
[18:01:36][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'KKMTOP '
[18:01:36][I][INFO:687]: Prompt: PAP. A
[18:01:36][I][INFO:688]: Prompt: KKMTOP
[18:01:36][I][INFO:689]: Beeps: 0

[18:01:36][I][CMD:439]: F7 02 00 00 00 85 80 00 08 02 00 01 43
[18:01:37][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'CTATYC 12 '
[18:01:37][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'CUCTEM NR '
[18:01:37][I][INFO:687]: Prompt: CTATYC 12
[18:01:37][I][INFO:688]: Prompt: CUCTEM NR
[18:01:37][I][INFO:689]: Beeps: 0

[18:01:37][D][text_sensor:067]: 'vistaalarm Lrr Msg': Sending state ''
[18:01:37][D][text_sensor:067]: 'vistaalarm Garage door': Sending state 'C'
[18:01:39][I][CMD:439]: F7 00 00 00 00 20 80 50 08 02 00 01 50
[18:01:39][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'PAP. A'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'KKMTOP '
[18:01:39][I][INFO:687]: Prompt: PAP. A
[18:01:39][I][INFO:688]: Prompt: KKMTOP
[18:01:39][I][INFO:689]: Beeps: 0

[18:01:39][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:39][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:39][D][text_sensor:067]: 'vistaalarm Basement windows': Sending state 'C'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'KKMTOP '
[18:01:40][D][text_sensor:067]: 'vistaalarm zone 17': Sending state 'C'
[18:01:41][D][text_sensor:067]: 'vistaalarm Living room window': Sending state 'C'
[18:01:42][D][text_sensor:067]: 'vistaalarm Basement windows10': Sending state 'C'
[18:01:42][I][CMD:439]: F7 01 00 02 00 20 80 0C 08 02 00 01 2A
[18:01:42][D][text_sensor:067]: 'vistaalarm Line1': Sending state '***** CHT.*****H'
[18:01:42][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'APEH OH '
[18:01:42][I][INFO:687]: Prompt: ***** CHT.*****H
[18:01:42][I][INFO:688]: Prompt: APEH OH
[18:01:42][I][INFO:689]: Beeps: 0

[18:01:42][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:42][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:43][I][CMD:439]: F7 02 00 00 00 20 80 40 08 02 00 01 50
[18:01:43][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'PAP. A'
[18:01:43][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'KKMTOP '
[18:01:43][I][INFO:687]: Prompt: PAP. A
[18:01:43][I][INFO:688]: Prompt: KKMTOP
[18:01:43][I][INFO:689]: Beeps: 0

[18:01:44][D][text_sensor:067]: 'vistaalarm Dining room window': Sending state 'C'
[18:01:45][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:48][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:48][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:48][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'HAP 08 H 08 '
[18:01:48][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:48][I][INFO:687]: Prompt: HAP 08 H 08
[18:01:48][I][INFO:688]: Prompt:
[18:01:48][I][INFO:689]: Beeps: 0

[18:01:48][D][text_sensor:067]: 'vistaalarm Lrr Msg': Sending state ''
[18:01:48][I][CMD:439]: F7 02 00 00 00 20 80 0C 08 02 00 01 50
[18:01:50][D][text_sensor:067]: 'vistaalarm Front door': Sending state 'C'
[18:01:51][I][CMD:439]: F7 00 00 00 00 20 80 50 08 02 00 01 50
[18:01:51][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'PAP. A'
[18:01:51][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'KKMTOP '
[18:01:51][I][INFO:687]: Prompt: PAP. A
[18:01:51][I][INFO:688]: Prompt: KKMTOP
[18:01:51][I][INFO:689]: Beeps: 0

4 replies

Dilbert66 Apr 17, 2022
Maintainer

Well, this explains it. This panel is not compatible with the vista20p protocol as programmed. Much older version. the f7 cmd is not the same at all. Not much I can help with here unfortunately. I'd really need to see a logic analyzer trace of the protocol to know for sure how it differs.

Edit: on closer inspection, it might be an f7 but with the flag bytes in different locations. The logic analyzer trace would not be needed in this case.

Dilbert66 Apr 17, 2022
Maintainer

This is what the code is expecting to see in an f7. The f7 on your system is close on some fields. The mask byte (byte 3) which holds the info related to which keypad the cmd is for is 0 or 2 on your f7, so I'm not sure if that is the keypad mask on your system. The zone number field though looks to match ok (byte 7). Byte 8 also looks close. So what would need to happen is to identify what fields and associated bits on your f7 represent what status.

[12:16:42][I][CMD:497]: F7 00 00 8F 10 08 00 4C 08 02 00 00 53 
[12:16:42][I][INFO:768]: Display to partition: 01, Mask: 8F
[12:16:42][D][text_sensor:067]: 'vistaalarmtest Line1': Sending state 'SYSTEM LO BAT   '
[12:16:42][I][INFO:785]: Prompt: SYSTEM LO BAT   
[12:16:42][I][INFO:786]: Prompt:                 
[12:16:42][I][INFO:787]: Beeps: 0

[12:16:46][I][CMD:497]: F7 00 00 40 00 02 00 00 28 02 00 00 46 
[12:16:46][I][INFO:768]: Display to partition: 03, Mask: 40
[12:16:46][I][INFO:785]: Prompt: FAULT 02        
[12:16:46][I][INFO:786]: Prompt:                 
[12:16:46][I][INFO:787]: Beeps: 0

Dilbert66 Apr 17, 2022
Maintainer

What partitions do you have active? What partition is zone 8 assigned to? I know the messages displayed in the log don't make sense but can you provide the correct translation and partition they should belong to? This will help identify what the flags represent. You would also need to arm the partions and idenfity the associated f7 to see what flags get set. Do you have a separate physical keypad address for each partition? What are their addresses?

TimerZero13 Apr 17, 2022

In Vista, one real keyboard is registered at address 1 and configured for "partition 9". That is, to show the statuses of all partitions and work with any selected one.

Also in Vista, a keyboard with address 17 for the virtual keyboard (esp) is also registered and configured to display partition 1.

There are two partitions in total. Zone 8 belongs to partition 1.

"You would also need to arm the partions and idenfity the associated f7 to see what flags get set." This can only be done later. Now the baby is sleeping.

[18:01:27][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:27][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:29][D][text_sensor:067]: 'vistaalarm Back door': Sending state 'C'
[18:01:30][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:30][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'FAULT 08 '
[18:01:30][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:30][I][INFO:687]: Prompt: FAULT 08
[18:01:30][I][INFO:688]: Prompt:
[18:01:30][I][INFO:689]: Beeps: 0

[18:01:30][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:30][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:30][I][CMD:439]: F7 02 00 00 00 20 80 0C 08 02 00 01 50
[18:01:32][D][text_sensor:067]: 'vistaalarm Family room window LF': Sending state 'C'
[18:01:32][D][text_sensor:067]: 'vistaalarm Basement windows9': Sending state 'C'
[18:01:33][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:36][I][CMD:439]: F7 01 00 02 00 20 80 40 08 02 00 01 50
[18:01:36][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:36][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' LO BAT '
[18:01:36][I][INFO:687]: Prompt: SYSTEM A
[18:01:36][I][INFO:688]: Prompt: LO BAT
[18:01:36][I][INFO:689]: Beeps: 0

[18:01:36][I][CMD:439]: F7 02 00 00 00 85 80 00 08 02 00 01 43
[18:01:37][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'CTATYC 12 '
[18:01:37][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'CUCTEM NR '
[18:01:37][I][INFO:687]: Prompt: STATUS 12
[18:01:37][I][INFO:688]: Prompt: SYSTEM NR
[18:01:37][I][INFO:689]: Beeps: 0

[18:01:37][D][text_sensor:067]: 'vistaalarm Lrr Msg': Sending state ''
[18:01:37][D][text_sensor:067]: 'vistaalarm Garage door': Sending state 'C'
[18:01:39][I][CMD:439]: F7 00 00 00 00 20 80 50 08 02 00 01 50
[18:01:39][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT '
[18:01:39][I][INFO:687]: Prompt: SYSTEM
[18:01:39][I][INFO:688]: Prompt: LO BAT
[18:01:39][I][INFO:689]: Beeps: 0

[18:01:39][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:39][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:39][D][text_sensor:067]: 'vistaalarm Basement windows': Sending state 'C'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT'
[18:01:40][D][text_sensor:067]: 'vistaalarm zone 17': Sending state 'C'
[18:01:41][D][text_sensor:067]: 'vistaalarm Living room window': Sending state 'C'
[18:01:42][D][text_sensor:067]: 'vistaalarm Basement windows10': Sending state 'C'
[18:01:42][I][CMD:439]: F7 01 00 02 00 20 80 0C 08 02 00 01 2A
[18:01:42][D][text_sensor:067]: 'vistaalarm Line1': Sending state '***** DISARM *****'
[18:01:42][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'PRESS * TO VIEW'
[18:01:42][I][INFO:687]: Prompt: ***** DISARM *****
[18:01:42][I][INFO:688]: Prompt: PRESS * TO VIEW
[18:01:42][I][INFO:689]: Beeps: 0

[18:01:42][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:42][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:43][I][CMD:439]: F7 02 00 00 00 20 80 40 08 02 00 01 50
[18:01:43][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:43][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT '
[18:01:43][I][INFO:687]: Prompt: SYSTEM
[18:01:43][I][INFO:688]: Prompt: FAULT 08
[18:01:43][I][INFO:689]: Beeps: 0

[18:01:44][D][text_sensor:067]: 'vistaalarm Dining room window': Sending state 'C'
[18:01:45][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:48][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:48][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:48][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'FAULT 08 '
[18:01:48][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:48][I][INFO:687]: Prompt: FAULT 08
[18:01:48][I][INFO:688]: Prompt:
[18:01:48][I][INFO:689]: Beeps: 0

TimerZero13 · 2022-04-17T20:23:52Z

TimerZero13
Apr 17, 2022

In Vista, one real keyboard (Alpha Keypad) is registered at address 1 and configured for "partition 9". That is, to show the statuses of all partitions and work with any selected one.

Also in Vista, a keyboard with address 17 for the virtual keyboard (esp) is also registered and configured to display partition 1.

There are two partitions in total. Zone 8 belongs to partition 1.

"You would also need to arm the partitions and idenfity the associated f7 to see what flags get set." This can only be done later. Now the baby is sleeping.

[18:01:27][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:27][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:29][D][text_sensor:067]: 'vistaalarm Back door': Sending state 'C'
[18:01:30][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:30][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'FAULT 08 '
[18:01:30][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:30][I][INFO:687]: Prompt: FAULT 08
[18:01:30][I][INFO:688]: Prompt:
[18:01:30][I][INFO:689]: Beeps: 0

[18:01:30][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:30][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:30][I][CMD:439]: F7 02 00 00 00 20 80 0C 08 02 00 01 50
[18:01:32][D][text_sensor:067]: 'vistaalarm Family room window LF': Sending state 'C'
[18:01:32][D][text_sensor:067]: 'vistaalarm Basement windows9': Sending state 'C'
[18:01:33][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:36][I][CMD:439]: F7 01 00 02 00 20 80 40 08 02 00 01 50
[18:01:36][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:36][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' LO BAT '
[18:01:36][I][INFO:687]: Prompt: SYSTEM A
[18:01:36][I][INFO:688]: Prompt: LO BAT
[18:01:36][I][INFO:689]: Beeps: 0

[18:01:36][I][CMD:439]: F7 02 00 00 00 85 80 00 08 02 00 01 43
[18:01:37][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'STATUS 12 '
[18:01:37][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'SYSTEM NR '
[18:01:37][I][INFO:687]: Prompt: STATUS 12
[18:01:37][I][INFO:688]: Prompt: SYSTEM NR
[18:01:37][I][INFO:689]: Beeps: 0

[18:01:37][D][text_sensor:067]: 'vistaalarm Lrr Msg': Sending state ''
[18:01:37][D][text_sensor:067]: 'vistaalarm Garage door': Sending state 'C'
[18:01:39][I][CMD:439]: F7 00 00 00 00 20 80 50 08 02 00 01 50
[18:01:39][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT '
[18:01:39][I][INFO:687]: Prompt: SYSTEM
[18:01:39][I][INFO:688]: Prompt: LO BAT
[18:01:39][I][INFO:689]: Beeps: 0

[18:01:39][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'disarmed'
[18:01:39][D][binary_sensor:036]: 'vistaalarm Ready': Sending state ON
[18:01:39][D][text_sensor:067]: 'vistaalarm Basement windows': Sending state 'C'
[18:01:39][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT'
[18:01:40][D][text_sensor:067]: 'vistaalarm zone 17': Sending state 'C'
[18:01:41][D][text_sensor:067]: 'vistaalarm Living room window': Sending state 'C'
[18:01:42][D][text_sensor:067]: 'vistaalarm Basement windows10': Sending state 'C'
[18:01:42][I][CMD:439]: F7 01 00 02 00 20 80 0C 08 02 00 01 2A
[18:01:42][D][text_sensor:067]: 'vistaalarm Line1': Sending state '***** DISARM *****'
[18:01:42][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'PRESS * TO VIEW'
[18:01:42][I][INFO:687]: Prompt: ***** DISARM *****
[18:01:42][I][INFO:688]: Prompt: PRESS * TO VIEW
[18:01:42][I][INFO:689]: Beeps: 0

[18:01:42][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:42][D][binary_sensor:036]: 'vistaalarm Ready': Sending state OFF
[18:01:43][I][CMD:439]: F7 02 00 00 00 20 80 40 08 02 00 01 50
[18:01:43][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'SYSTEM'
[18:01:43][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'LO BAT '
[18:01:43][I][INFO:687]: Prompt: SYSTEM
[18:01:43][I][INFO:688]: Prompt: FAULT 08
[18:01:43][I][INFO:689]: Beeps: 0

[18:01:44][D][text_sensor:067]: 'vistaalarm Dining room window': Sending state 'C'
[18:01:45][I][CMD:439]: F7 00 00 00 00 20 80 1C 08 02 00 01 2A
[18:01:48][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'unavailable'
[18:01:48][I][CMD:439]: F7 01 00 02 00 08 80 00 08 02 00 01 48
[18:01:48][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'FAULT 08 '
[18:01:48][D][text_sensor:067]: 'vistaalarm Line2': Sending state ' '
[18:01:48][I][INFO:687]: Prompt: FAULT 08
[18:01:48][I][INFO:688]: Prompt:
[18:01:48][I][INFO:689]: Beeps: 0

4 replies

TimerZero13 Apr 17, 2022

As far as I know, Vista 20P and Vista 50P have compatible keypads. I have 6139 which should be compatible with 6160.

Dilbert66 Apr 17, 2022
Maintainer

Ok, it looks like your system is not that different after all. Most of the status bits are fine. The unknowns are bytes 1, byte 6 and byte 11 where on your system there are bits set while on the vista20p, those bytes are always zero. I have no idea at this time what those bits are for. As to the mask byte that matches fine with your address 17 keypad (byte 5=02) for partition 1 status. The one unkown there is when that byte is 0. Perhaps that is destined for the address "1" keypad. I've never seen that so can't say for sure.

Now, as to why the zone statuses are not working, I should have realized before. The system looks for a text match for the message sent from the panel. For example, it looks for the word "FAULT" to determine that this is an open zone. Well, in your case your panel is a different language, so the word lookups will need to be changed to match the panel. This is done here at the top of the vistaalarm.h file. You need to put the correct language equivalen there.:

  const char *
      const FAULT = "FAULT";
    const char *
      const BYPAS = "BYPAS";
    const char *
      const ALARM = "ALARM";
    const char *
      const FIRE = "FIRE";
    const char *
      const CHECK = "CHECK";
    const char *
      const CLOSED = "CLOSED";
    const char *
      const OPEN = "OPEN";
    const char *
      const ARMED = "ARMED";

FYI, the reason I used the word description to determine the status is that it was the most accurate method of determining the message type. I'll look again to see if I can see a flag combination to accomplish the same result without resorting to text lookups.

Dilbert66 Apr 17, 2022
Maintainer

Ok, i realized my confusion as far as the keypad addressing. Bytes 1, 2 ,3 and 4 are all address masks for keypads. I had that in the code originally but never saw those other addresses used in the vista20p so ignored them. So in effect those 4 bytes will cover addresses 0 to 30 which the vista50p fully supports. I have to modify the code to support those extended address masks.

TimerZero13 Apr 17, 2022

Partition 2 on ARM.

[00:19:46][I][CMD:439]: F7 00 00 02 00 20 80 0C 0C 02 00 01 2A
[00:19:46][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'PARTITION'
[00:19:46][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'ARMED '
[00:19:46][I][INFO:687]: Prompt: PARTITION
[00:19:47][I][INFO:688]: Prompt: ARMED
[00:19:47][I][INFO:689]: Beeps: 0

[00:19:47][D][text_sensor:067]: 'vistaalarm System Status': Sending state 'armed_away'
[00:19:47][D][binary_sensor:036]: 'vistaalarm Away': Sending state ON
[00:19:47][D][binary_sensor:036]: 'vistaalarm Armed': Sending state ON
[00:19:50][D][text_sensor:067]: 'vistaalarm Basement windows': Sending state 'C'
[00:19:51][I][CMD:439]: F6 01 00 00 00 00 00 00 00 00 00 00 00
[00:19:51][I][EXT:439]: F6 01 00 41 02 0A B3 00 00 00 00 00 00
[00:19:51][I][CMD:439]: F7 02 00 00 00 85 80 00 08 02 00 03 43
[00:19:51][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'STATUS 12 '
[00:19:51][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'SYSTEM NA '
[00:19:51][I][INFO:687]: Prompt: STATUS 12
[00:19:51][I][INFO:688]: Prompt: SYSTEM NA
[00:19:51][I][INFO:689]: Beeps: 0

Dilbert66 · 2022-04-17T21:44:26Z

Dilbert66
Apr 17, 2022
Maintainer

Ok, i see data address to 17,1 and also address 0. Do you have a keypad addressed to zero?

0 replies

TimerZero13 · 2022-04-17T22:15:34Z

TimerZero13
Apr 17, 2022

Yes. I have keypads at 1 (real) and 17 (virtual) addresses. Keypad 0 is factory set in the system (not changeable). Physically, the keypad is not connected to address 0.

1 reply

Dilbert66 Apr 18, 2022
Maintainer

Let me know if you have success entering those language specific entries. Try just the "FAULT" for now and see if it works. If not, I can modify the code to instead allow using numeric ascii characters to do the lookup with so that unusual text characters won't be an issue . Apart from that, your system is supported fine. I got thrown off by the extra bits in your f7 as well as the wrongly displayed text messages. There is an interested flag that might help with the displaying of the characters perhaps that I see on your f7. I'll look into that.

TimerZero13 · 2022-04-18T05:13:15Z

TimerZero13
Apr 18, 2022

After the last update of the master version, my virtual keyboard stopped showing messages of only partition 1, but shows everything in a row.

I will try the translation. I just don't quite understand what to put in there. The virtual keyboard does not correctly display words in the Vista language. I'll try first the phrases that the real keyboard writes.

6 replies

Dilbert66 Apr 18, 2022
Maintainer

I've reverted the last change so you virtual keypad will only display messages destined for the partition that the keypad address belongs to.
As to the messages, I will see if I can add another method of adding the messages to the lookup. I'm looking into using a byte array instead of using text.

Dilbert66 Apr 18, 2022
Maintainer

ok, in an attempt to simplify the ability for the code to work with non-english panel messages, I've changed the lookup entries to support adding the messages as a list of decimal ascii characters. A user can then lookup the characters for each message in the language and enter them in the code instead of trying to copy a string. To aid in the process I've added a function to display the existing character string for the zone prompts that can be cut and pasted into the code.
The changes need to be done in vistaalarm.h (line70):

    //find the matching characters in an ascii chart for the messages that your panel sends
    //for the statuses below. Only need the first few characters plus a zero at the end.
    const char FAULT[6] = {70,65,85,76,84,0};  //the number 70 is the ascii char for "F", 65="A", etc. Change 
these to match the correct  translated message that the panel sends for a faulted zone.
//NOTE:  *** do NOT include the zone#.  
    const char BYPAS[6] = {66,89,80,65,83,0}; //"BYPASS"
    const char ALARM[6] = {65,76,65,82,77,0}; //"ALARM"
    const char FIRE[6]  = {70,73,82,69,32,0}; //"FIRE "
    const char CHECK[6] = {67,72,69,67,75,0}; //"CHECK"
    const char HITSTAR[6] = {72,105,116,32,42,0}; //  "Hit *";

Here is how the esphome log will show the data it sees for the panel prompt. You can also just copy this line to use in the section above.

[10:02:37][I][CMD:500]: F7 00 00 8F 10 03 00 00 08 02 00 00 46 
[10:02:37][I][INFO:779]: Display to partition: 01
[10:02:37][I][INFO:799]: Prompt: FAULT 03         {70,65,85,76,84,0}
[10:02:37][I][INFO:800]: Prompt:                 
[10:02:37][I][INFO:801]: Beeps: 0

I've pushed the changes to both master and dev.

Dilbert66 Apr 18, 2022
Maintainer

Edit I believe byte 11 is a flag to indicate an extended international character set for the prompt meaning each character takes 16 bits instead of 8 for display. I will modify the code to display accordingly and modify. Don't use the latest update yet. I have to tweak it.

TimerZero13 Apr 18, 2022

That's great. Thanks for the work done. I will wait.

"character takes 16 bits instead of 8 for display."

Yes, my system also uses English characters.

Dilbert66 Apr 18, 2022
Maintainer

I did not find any details to know for sure how that flag is used. I'll need to see how your panel sends the code. Can you run the master version and post a copy of the logs so I can see what characters it sends for the fault messages. This will help determine if it is using extended characters or just 8 bit versions for non standard ascii characters.

TimerZero13 · 2022-04-18T20:52:53Z

TimerZero13
Apr 18, 2022

Zones fault:

[23:26:42][I][CMD:445]: F7 00 00 00 00 85 80 0C 08 02 00 01 43 
[23:26:42][D][text_sensor:067]: 'vistaalarm Family room window RF': Sending state 'C'
[23:26:44][I][CMD:445]: F7 00 00 00 00 00 80 1C 08 02 00 01 2A 
[23:26:45][I][CMD:445]: F7 03 00 02 00 03 80 00 08 02 00 01 48 
[23:26:45][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'HAP 03 H 03     '
[23:26:45][D][text_sensor:067]: 'vistaalarm Line2': Sending state '             '
[23:26:45][I][INFO:709]: Prompt: HAP 03 H 03      {72,65,80,136,139,0}
[23:26:45][I][INFO:710]: Prompt:              
[23:26:45][I][INFO:711]: Beeps: 0

[23:26:47][D][text_sensor:067]: 'vistaalarm zone 17': Sending state 'C'
[23:26:48][I][CMD:445]: F7 00 00 00 00 85 80 00 08 02 00 01 43 
[23:26:48][D][text_sensor:067]: 'vistaalarm Living room window': Sending state 'C'
[23:26:50][I][CMD:445]: F7 00 00 00 00 00 80 1C 08 02 00 01 2A 
[23:26:51][I][CMD:445]: F7 03 00 02 00 06 80 00 08 02 00 01 48 
[23:26:51][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'HAP 06 H 06     '
[23:26:51][I][INFO:709]: Prompt: HAP 06 H 06      {72,65,80,136,139,0}
[23:26:51][I][INFO:710]: Prompt:              
[23:26:51][I][INFO:711]: Beeps: 0

[23:26:51][D][text_sensor:067]: 'vistaalarm Lrr Msg': Sending state ''
[23:26:53][D][text_sensor:067]: 'vistaalarm Back door': Sending state 'C'
[23:26:54][I][CMD:445]: F7 00 00 00 00 85 80 0C 08 02 00 01 43 
[23:26:56][I][CMD:445]: F7 00 00 00 00 00 80 1C 08 02 00 01 2A 
[23:26:57][I][CMD:445]: F7 03 00 02 00 08 80 00 08 02 00 01 48 
[23:26:57][D][text_sensor:067]: 'vistaalarm Line1': Sending state 'HAP 08 H 08     '
[23:26:57][I][INFO:709]: Prompt: HAP 08 H 08      {72,65,80,136,139,0}
[23:26:57][I][INFO:710]: Prompt:              
[23:26:57][I][INFO:711]: Beeps: 0

There is a larger log in the file.
log_vistaalarm.zip

10 replies

Dilbert66 Apr 18, 2022
Maintainer

Thank you! That's very helpful. It is odd though that using the codes from the text string from the panel I can't find a character lookup table that matches those last characters. I don't know what the panel uses to display those correctly but suspect it's a custom lookup table so they can represent many languages with one table since they don't need all characters. The keypad would also have a copy of this table. I would have to create a similar conversion table in my code but that is tricky to do without knowing all the prompts and the current ascii codes used.

Dilbert66 Apr 19, 2022
Maintainer

There was a filter that removed non-ascii characters from the prompts. I've taken it out so that the fields will now show those missing characters. They probably won't display correctly since the code is not correct for the character displayed. I did add a translate function to change those know cyrillic charaters. I use the windows 1251 encoding but don't know how that will display on your system. Give it a tray and let me know.

TimerZero13 Apr 19, 2022

Connection is not stable.

[00:13:22][W][api.connection:081]: Home Assistant 2022.4.4 (192.168.2.160): Connection reset [00:13:22][D][api:102]: Accepted 192.168.2.160 [00:13:23][D][api.connection:826]: Home Assistant 2022.4.4 (192.168.2.160): Connected successfully [00:13:24][W][api.connection:081]: Home Assistant 2022.4.4 (192.168.2.160): Connection reset [00:13:24][D][api:102]: Accepted 192.168.2.160 [00:13:24][D][api.connection:826]: Home Assistant 2022.4.4 (192.168.2.160): Connected successfully [00:13:24][I][CMD:445]: F7 02 00 00 00 20 80 50 08 02 00 01 50 [00:13:25][W][api.connection:081]: Home Assistant 2022.4.4 (192.168.2.160): Connection reset [00:13:25][D][api:102]: Accepted 192.168.2.160 [00:13:25][D][api.connection:826]: Home Assistant 2022.4.4 (192.168.2.160): Connected successfully [00:13:26][W][api.connection:083]: Home Assistant 2022.4.4 (192.168.2.160): Connection closed

Characters are displayed incorrectly:

[00:15:02][D][text_sensor:067]: 'vistaalarm Line1': Sending state '***** CH\x9dT.*****' [00:15:02][D][text_sensor:067]: 'vistaalarm Line2': Sending state 'HAP\xd3\xd8EH\x8e \x83OH\x8e ' [00:15:02][I][INFO:722]: Prompt: ***** CH\x9dT.***** [00:15:02][I][INFO:723]: Prompt: HAP\xd3\xd8EH\x8e \x83OH\x8e [00:15:02][I][INFO:724]: Beeps: 0

TimerZero13 Apr 19, 2022

It outputs four characters instead of one missing Cyrillic.

Dilbert66 Apr 19, 2022
Maintainer

Yes, I see that now. What was happening before is that all cyrillic were thrown away. This change allowed them to go through but they are causing issues. The non asci characters are causing ESPHOME to restart. Very odd. I've reverted the code and now will try to do a substitue to latin characters and for the unkown ones, a "?" will be placed instead. I've pushed the corrected version.

I don't have a solution at this time for how to display those prompts. As to the rest of the functions, it should work ok with your panel . Only the message display will be non optimal.

TimerZero13 · 2022-04-19T22:17:48Z

TimerZero13
Apr 19, 2022

Thank you. In principle, everything is so excellent.

3 replies

Dilbert66 Apr 19, 2022
Maintainer

You still need to identify the rest of the prompt characters for your panel for the messages below to complete the setup.

    const char BYPAS[6] = {66,89,80,65,83,0}; //"BYPASS"
    const char ALARM[6] = {65,76,65,82,77,0}; //"ALARM"
    const char FIRE[6]  = {70,73,82,69,32,0}; //"FIRE "
    const char CHECK[6] = {67,72,69,67,75,0}; //"CHECK"
    const char HITSTAR[6] = {72,105,116,32,42,0}; //  "Hit *";

TimerZero13 Apr 20, 2022

Testing for dev version.
This option doesn't work: const char FAULT[6] ={72,65,80,136,139,0};
The previous code works: const char * FAULT = "HAP??";

Dilbert66 Apr 20, 2022
Maintainer

Yes, you are correct. The fact of changing the non-text characters breaks the search. I've reverted the change. Just use the string lookups as you are doing and use ? instead of the non-printing cyrillic characters.

Support for multiple partitions on Vista 20P? #68

Replies: 16 comments · 56 replies

Dilbert66 Mar 27, 2022 Maintainer

Dilbert66 Mar 27, 2022 Maintainer

Dilbert66 Mar 27, 2022 Maintainer

warnejo May 3, 2022 Author

warnejo Jul 30, 2022 Author

Dilbert66 Jul 31, 2022 Maintainer

Dilbert66 Jul 31, 2022 Maintainer

warnejo Aug 2, 2022 Author

Dilbert66 Apr 6, 2022 Maintainer

Dilbert66 Apr 14, 2022 Maintainer

Dilbert66 Apr 14, 2022 Maintainer

Dilbert66 Apr 14, 2022 Maintainer

Dilbert66 Apr 15, 2022 Maintainer

Dilbert66 Apr 16, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 17, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 18, 2022 Maintainer

Dilbert66 Apr 19, 2022 Maintainer

Dilbert66 Apr 19, 2022 Maintainer

Dilbert66 Apr 19, 2022 Maintainer

Dilbert66 Apr 20, 2022 Maintainer

Replies: 16 comments 56 replies

Dilbert66
Mar 27, 2022
Maintainer

Dilbert66
Mar 27, 2022
Maintainer

Dilbert66
Mar 27, 2022
Maintainer

warnejo May 3, 2022
Author

warnejo Jul 30, 2022
Author

Dilbert66 Jul 31, 2022
Maintainer

Dilbert66 Jul 31, 2022
Maintainer

warnejo Aug 2, 2022
Author

Dilbert66
Apr 6, 2022
Maintainer

Dilbert66
Apr 14, 2022
Maintainer

Dilbert66 Apr 14, 2022
Maintainer

Dilbert66
Apr 14, 2022
Maintainer

Dilbert66 Apr 15, 2022
Maintainer

Dilbert66 Apr 16, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66 Apr 17, 2022
Maintainer

Dilbert66
Apr 17, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 18, 2022
Maintainer

Dilbert66 Apr 19, 2022
Maintainer

Dilbert66 Apr 19, 2022
Maintainer

Dilbert66 Apr 19, 2022
Maintainer

Dilbert66 Apr 20, 2022
Maintainer