EVO192 support

[yozik04]

I am working on EVO192 support. It has different LiveEvent message:

  struct ParadoxPacket { //37 byte
       byte armstatus;       //00
       byte requested_event_nr; //01 0xFF: Event just occurred (serial port only)
       uint16_t event_nr;    //02-03
       byte century;         //04
       byte year;            //05
       byte month;           //06
       byte day;             //07
       byte hour;            //08
       byte minute;          //09
       byte event_group;     //10
       byte partition;       //11
       byte event_1;         //12
       byte event_2;         //13
       char serial_nr[4];    //14-17
       LabelType label_type; //18
       char label[16];       //19-34
       byte not_used;        //35
       byte checksum;        //36
  };

Example Zone Open event:
b'\xe0\xffeb\x14\x12\n\x12\x132\x01\x01\x05\x00\x00\x00\x00\x00\x02Living room     \x00\x1c'

@jpbarraca I need some help make code flow to branch into SP/Magellan and EVO. I will populate EVO part and test with my system.

[yozik04]

BTW. Where you got struct documentation? Can you please share.

[jpbarraca]

In the initial versions of the paradox_messages file the structs were the ones from EVO . Later I switched to the MGSP format. If you go back in the commit history you will find parsers for EVO. Support for both series will be a nice feature

[jpbarraca]

Look in the openhab forum for a Dropbox link related to IP150

[yozik04]

Initial EVO192 added in my repo. But I did a large refactoring. Will be hard to merge. Doh...

[jpbarraca]

I also did a large refactoring :( as well as added several bugfixes. I propose we load your changes into a different branch, freeze the main branch and work on the new branch carefully. This would keep the commit history from both repositories.

Do you agree?

[yozik04]

I can try to integrate all your changes. There is only 3-4 conflicting files.

Jevgeni

13 нояб. 2018 г., в 12:47, João Paulo Barraca notifications@github.com написал(а):

I also did a large refactoring :( as well as added several bugfixes. I propose we load your changes into a different branch, freeze the main branch and work on the new branch carefully. This would keep the commit history from both repositories.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jpbarraca]

Great. Then issue a pull request. Because I do not have an EVO, can you maintain the code for these devices?

[yozik04]

Yes I can. I will be using it with my home automation system. So it will be tested throughly.

Jevgeni

13 нояб. 2018 г., в 13:21, João Paulo Barraca notifications@github.com написал(а):

Great. Then issue a pull request. Because I do not have an EVO, can you maintain the code for these devices?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[yozik04]

Linking pull request #10