partition topic issue about paradoxrs232tomqtt

[maragelis]

Just to be clear, disarming and arming works ? Just the hassio topic does not send partition number, correct ?

[zsoltkazda]

Yes, the disarming and arming works, and yes, the hassio topic does not send partition number.

[maragelis]

Test branch updated.
the topic on which arm status is sent has partition info.
eg. paradoxdCTL/hassio/Arm0 paradoxdCTL/hassio/Arm1
https://github.com/maragelis/ParadoxRs232toMqtt/tree/test

@zsoltkazda could you please provide your panel info because the arming process does not work for me.

I am using the MG5050 with "MG5050_4.73.72.PUF" firmware from 2011.

I can connect to the panel and receive the following topics:

• paradoxdCTL/out
• paradoxdCTL/status
• paradoxdCTL/hassio/zoneX
• paradoxdCTL/hassio/Arm0
• paradoxdCTL/hassio/Arm1

But the arming does not work.

[maragelis]

Change your code on the alarm and dont use 0 in the code

@maragelis my alarm panel user code is 4 non-zero digits.
Trace indicates that "sending command 0x5f to panel" is executed but nothing after that.
When I compare the login sequence by sniffing the serial port between the MG5050 and the Paradox BabyWare application I see there seems to be a different initialisation sequence.
When I first bought my panel around 2010, it worked with the WinLoad software. Then after upgrading the firmware the WinLoad software would no longer work and I needed to use the BabyWare application.
Could it be that there is a difference?
filtered_response.txt

[maragelis]

Looking at the trace I see a perfect login after 5f there is the 00 handshake and a 10 login. Then the is status command 50 52 issued. Do you get login failed from the status mqtt topic when trying to arm? If not it’s surly the code try the master code or change your code.

The trace provided is the communication between BabyWare and the MG5050, so the perfect login is expecetd. Let me first modify the code so that I initialise the communications with the "72 00 00 .... 00 00 72" packet and then see if the panel responds at all.

[zsoltkazda]

Dear john2oo2! I don’t know the firmware version. But ont he panel, I see the following nformation: SP6000 NR Q018 27aug19 Zsolt From: john2oo2 <[email protected]> Sent: Tuesday, March 10, 2020 5:12 PM To: maragelis/ParadoxRs232toMqtt <[email protected]> Cc: Kazda Zsolt <[email protected]>; Mention <[email protected]> Subject: Re: [maragelis/ParadoxRs232toMqtt] partition topic issue (#65) @zsoltkazda<https://github.com/zsoltkazda> could you please provide your panel info because this does not work for me? I am using the MG5050 with "MG5050_4.73.72.PUF" firmware from 2011. I can connect to the panel and receive the following topics: * paradoxdCTL/out * paradoxdCTL/status * paradoxdCTL/hassio/zoneX — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#65?email_source=notifications&email_token=ANCUA4SNE62SPBXNP42F3EDRGZRF3A5CNFSM4KJTS43KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOMCIDA#issuecomment-597173260>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANCUA4U2NEB6VDG7HSHFIULRGZRF3ANCNFSM4KJTS43A>.

[maragelis]

Do you get login failed from the status mqtt topic when trying to arm?

Feedback regarding the "login" issue:

• Turns out that my issue with the "login" was not a programatic error but rather a hardware issue!
• I first used a knock-off D1Mini version. The serial ports of this device did not handle the 5V TTL levels and popped receive port.
• I then got hold of the WEMOS D1 Mini and installed a 5V <-> 3V TTL level converter which also gave problems on the TX line (RX worked fine).
• Then I threw out the level converter and connected the WEMOS D1 Mini directly as indicated on the original WIKI page and so it seems that the WEMOS D1 Mini is 5V tolerant. (We will see how long this device survives!)

Feedback regarding the reporting of the Arm Status:

• The arm and disarm command is always reported correctly for both Partion 1 (0) and 2 (1).
• There is still an issue where the sleep and stay command is actioned, but the reporting only happens for the first partition that is put into the sleep or stay armed mode.

[bigjuanpa]

how can you get the panelstatus information for the panel 2 (Arm1)?
When I run
{
"Command": "panelstatus",
"Subcommand": "1",
}

I only get the Arm0 status

thanks

[maragelis]

Its not implemented in this project I have it implemented on my other project

[sparkydave1981]

So to get partition support we should swap to using an ESP32 with your other project?