Jevgeni Kiski

Results 319 comments of Jevgeni Kiski

ok. Updated HACS, restarted HomeAssistant and it started to work...

Regarding captures. Initially we do a InitiateCommunication round: https://github.com/ParadoxAlarmInterface/pai/blob/3d8e502a9c701ba8c4caeb9d7a43fa9925032da9/paradox/paradox.py#L140-L144 ![image](https://user-images.githubusercontent.com/2420038/209639778-a2c9079c-a964-4f44-9c35-f19b4d21fe44.png) Both 37 bytes RX translates to: ``` Container: fields = Container: data = b'r\xff\x04\x02\x00\x00\xa1Z\x01\x07p\x01\x05\x0b \xd4'... (truncated, total 36) value =...

@jpbarraca You are a crypto guru. Please take a look. Maybe you will see something interesting.

Most of the communication is not encrypted =) And I have found the difference in connection initialization. Now let me alter the code.

or maybe they did an exception for IP150 because for serial we send CommunicationSourceIDEnum as Winload_Direct=1 and IP Module sends Winload_IP=2 https://github.com/ParadoxAlarmInterface/pai/blob/3d8e502a9c701ba8c4caeb9d7a43fa9925032da9/paradox/hardware/parsers.py#L56-L68 https://github.com/ParadoxAlarmInterface/pai/blob/3d8e502a9c701ba8c4caeb9d7a43fa9925032da9/paradox/hardware/common.py#L74-L88

> This might be interesting too... This is the initial (power on) exchange between IP150+ and EVO192. No it is not. `E0 FF *` are live events and here are...

My latest commit? I did not commit anything related to encryption.

> But why does the panel return 00 as last byte of the response for the 72 00 00 ... command when it's IP150 sending it, and 01 when it's...

Two options: 1. Encrypted message slipped into live event handler (we are not protected from that yet) 2. 2023 dates are encoded somehow differently. You can raise log verbosity in...

> > Two options: > > > > 1. Encrypted message slipped into live event handler (we are not protected from that yet) > > 2. 2023 dates are encoded...