Closed FigJam23 closed 1 year ago
Door control where? If you can control it using Babyware then please capture these packets.
Unfortunately I only know the process for capturing comms between winload and ip150 with encryption disabled via config file in winload my EVOHD only supports babyware . Not sure how to do this with babyware. And I wouldn't know how to add that info into PAI lol
You can enable full debug and connect to babyware through PAI. This will log all incommeing and going packets. Reopen if you are still interested.
##Add Door control Please :) Log Shows Door (Front Door) But Nothing in Hassio
Dakotas PIR, Lincolns PIR, UpStairsHall PIR, Master Bed PIR, Front Door RS, Fire, Dakotas Door, Lincolns Door, LaundryHall PIR, Ellies Door, Ofice Door, Kitchen Entrance, Laundry Door, Office 2021-07-30 23:46:46,024 - INFO - PAI.paradox.hardware.panel - Pgm labels loaded (0.08s): FP Reset, PGM 02, Dakota Bell, PGM 04, PGM 05 2021-07-30 23:46:46,060 - INFO - PAI.paradox.hardware.panel - Partition labels loaded (0.04s): Intruder Alarm, Perimeter Doors 2021-07-30 23:46:46,107 - INFO - PAI.paradox.hardware.panel - User labels loaded (0.05s): Master Mike, Sarah, Dakota, User 004, User 005 2021-07-30 23:46:46,107 - INFO - PAI.paradox.hardware.panel - Module labels loaded (0.0s): 2021-07-30 23:46:46,124 - INFO - PAI.paradox.hardware.panel - _**### Door labels loaded (0.02s): Front Door**_ 2021-07-30 23:46:46,125 - INFO - PAI.paradox.paradox - Running 2021-07-30 23:46:46,135 - WARNING - PAI.paradox.interfaces.mqtt.basic - MQTT DASH Template not found: /etc/pai/mqtt_dash.txt 2021-07-30 23:48:26,975 - ERROR - PAI.paradox.hardware.evo.panel - ChecksumError Error in path (parsing) -> checksum wrong checksum, read b'00', computed b'd0', message: b'4780000009000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000