pai icon indicating copy to clipboard operation
pai copied to clipboard

Paradox DGP-848

Open lpaolini opened this issue 2 years ago • 17 comments

Is Paradox DGP-848 v.4.10 supported?

lpaolini avatar Jul 23 '21 16:07 lpaolini

Never heard of it. Is it something old/new.

yozik04 avatar Jul 24 '21 06:07 yozik04

It looks very similar to EVO. I'm pretty confident it's compatible, but I'm seeking confirmation.

Here are the Reference and installation manual and a photo of the board.

Thanks.

lpaolini avatar Jul 24 '21 07:07 lpaolini

I can not tell you for sure if it is supported. If it is supported by Babyware then chances are high. But we need to add product id to the list in PAI code.

yozik04 avatar Jul 30 '21 17:07 yozik04

Dgp848 is predecessor of evo48. Haven't seen them for many years. Programming was done via winload.

aelias-eu avatar Jul 30 '21 17:07 aelias-eu

The communication protocol is the same. The best thing you can do is to test it with ESP32.

vladimirzrnic avatar Sep 14 '21 16:09 vladimirzrnic

If you wire it up you can try to connect with PAI. I will need a product id that will be in logs. Then I can add that product id to the list of supported and you can try to connect. All of the above you can do yourself as well =)

yozik04 avatar Sep 14 '21 18:09 yozik04

Not certain how close a DGP-NE96 is to the DGP-848, but much of the serial protocol I'm seeing when wired into the panel... well, for e0 "live" updates, anyway ... seems to be nearly identical to EVO protocols (37 bytes and I can see zones opening/closing, event messages when keypad is used, etc.). One notable difference I've seen for live events is event / subevent data passed on bytes 7 and 8 on EVO systems get passed on bytes 10 and 12 in DGP. With this, I've modified Maragelis' ParadoxRs232toMqtt project to work for live updates using my DGP-NE96.

But - I can't get pai up and running (or the Maragelis code for that matter) because initialization of the panel fails. I see a 0x70 communication error response to the 0x72 sent by pai when initiating communication. I get a 'Timeout while connecting to panel. Is an other connection active?' response. There appears to be some material difference in what the DGP is expecting for initialization.

If anyone has any ideas on how I (and anyone else with an older DGP panel) might proceed here (suggestions of initialization strings to try, etc.) I'd be grateful!

brendankmurphy avatar Oct 22 '21 17:10 brendankmurphy

If you want to try to add support for it you need to start from dump from babyware and check what is the difference between what PAI sends and what Babyware sends. Unfortunately I can only provide minimal support as my core job and kids takes all of my time now.

yozik04 avatar Oct 23 '21 08:10 yozik04

Thanks @yozik04

I don't think Babyware is compatible with DGP series, but I think I should be able to use NEware or Winload to do the dump.

The only issue I'm running into now is trying to get either of those software applications running. NEware is downloadable from Paradox's website, but to use it one must register the software which requires a software serial number (that "conveniently" isn't included with the download). It appears you need to be a dealer and/or registered installer to contact Paradox to get a software serial number...?

Will update back on this thread once I have it and can shed more light on panel initialization for other DGP panel owners.

brendankmurphy avatar Oct 23 '21 14:10 brendankmurphy

Hey @lpaolini & @yozik04 - Good news. I found an older Erlang project for Digiplex series panels at https://github.com/tonyrog/digiplex. Initialization string and command calls from that project work for my DGP-NE96. There are definitely differences in the protocols from EVO panels, but as a proof of concept I'm now able to arm/disarm the panel using modified code from Maragelis' ESP8266 project with the changes to protocol.

Will create a fork of pai and see what I can do (coding isn't my primary job :-D).

brendankmurphy avatar Oct 25 '21 15:10 brendankmurphy

Good luck =)

yozik04 avatar Oct 25 '21 20:10 yozik04

Hi @brendankmurphy May I kindly ask if you can share your modified Maragelis' ParadoxRs232toMqtt project? I have DGP848 and it would be great to test it.

kovi44 avatar Dec 13 '21 11:12 kovi44

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Mar 02 '22 11:03 stale[bot]

Is there any news about DGP integration into pai ? @brendankmurphy could you share what you found or made here ? I'm also interested in plugin my DGP-848 into home assistant through this wonderful pai (thanks for your work guys ! ;-) )

avilleret avatar Nov 27 '22 13:11 avilleret

I made some tests with my DGP-848 and got an answer from the device to the init string :

init_string = b'5f 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f'
answer =      b'00 00 08 10 00 04 14 00 48 17 00 00 06 12 02 a0 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 df'

I read a bit of the pai code (which is btw very well written, congrats guys !) but I didn't understand on the first sight how to modify it to introduce this new device with this init string.

@yozik04 could you reopen this issue ? or should I duplicate it ?

avilleret avatar Nov 29 '22 22:11 avilleret

You might need to create a new folder in paradox/hardware as your panel's protocol might be very different. PAI was well written in my eyes but now I want to rewrite that :) Most probably that will never happen.

yozik04 avatar Nov 30 '22 08:11 yozik04

Hi @kovi44 and @avilleret

I've posted code here: https://github.com/brendankmurphy/ParadoxDGP-NE96Rs232toMqtt

I had the desire to try to modify a version of pai to work with the slightly different protocol, but once I got this up and running with HomeAssistant and "real work" projects took over, it has been on the back burner.

brendankmurphy avatar Nov 30 '22 16:11 brendankmurphy