maragelis/paradoxrs232tomqtt

esp8266, serial bus to mqtt for Paradox alarm systems

paradoxrs232tomqtt's Issues

'StaticJsonBuffer' was not declared in this scope

Hi, if I try to compile the last version of .ino file I receive this message from the compiler

'StaticJsonBuffer' was not declared in this scope

I need to compile the ino files because I would use authentication and encryption (SSL).

All lib installed are the last stable version.
thanks

Inject panic event e.g. fire, medical?

I am interested in implementing a software panic button.
Typically I would need to press 1+3 to on the keyboard to activate panic mode, can that be achieved by injecting a command?
Thanks :)

Wiki: RX TX order

In the wiki on the figure (Paradox Side), the RX TX PIN order is wrong:

https://user-images.githubusercontent.com/12981331/52876366-b6339a00-315f-11e9-93ef-690577cf2ecf.png

The right order is (from top to bottom): TX RX GND VCC

ESP8266 and voltage regulator schema connection on MG5050

Hello,

I have one ESP8266 and one Voltage regulator (3V and 5V from 12V - YwRobot 545043).
Can you help me with a schema how to connect all these components to a Paradox MG5050 panel, please?

Thank you!

unable to compile sketch

Unable to compile sketch in Arduino IDE, version 1.8.9

esp8266 board installed in board manager, all libraries as per Git repo installed.

error:
ParadoxAlarmSystemOTA:1:19: error: FS.h: No such file or directory
compilation terminated.
exit status 1
FS.h: No such file or directory

File exists on PC in Arduino library, where is this looking for the file?3

Additional info here:
https://community.home-assistant.io/t/paradox-alarm-panel-wemos-d1-mini-communication/62003/12

Typo in the "Home Assistant in V2" wiki - commands sent to the incorrect command_topic

Hi Maragelis,

Thank you very much for sharing this project.

What I noticed, is that the Home Assistant V2 wiki has a typo and if not corrected, the commands are not sent to the proper topic:

alarm_control_panel:
 platform: mqtt
 state_topic: "paradoxdCTL/hassio/Arm"
 **command_topic:"paradoxCTL/in"**

The correct name of the command_topic is "paradoxdCTL/in"

WeMos R3

Hello @maragelis is there any reason this shouldn't also work on the R3 board?

Specifically this one...

https://robotdyn.com/uno-wifi-r3-atmega328p-esp8266-32mb-flash-usb-ttl-ch340g-micro-usb.html

I'm a complete retard with this and have never flashed one of these boards before so more than likely I'm just being an idiot but I get all sorts of complaints in Arduino IDE.

/home/user/Desktop/ParadoxRs232toMqtt-dev/ParadoxAlarmSystem/ParadoxAlarmSystemOTA/ParadoxAlarmSystemOTA.ino: In function 'inPayload Decodejson(char*)': ParadoxAlarmSystemOTA:852: error: 'DynamicJsonBuffer' was not declared in this scope DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:852: error: expected ';' before 'jsonBuffer' DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:853: error: 'jsonBuffer' was not declared in this scope JsonObject &root = jsonBuffer.parseObject(Payload); ^ ParadoxAlarmSystemOTA:854: error: 'class ArduinoJson650_0_0::JsonObject' has no member named 'success' if (!root.success()) ^ /home/user/Desktop/ParadoxRs232toMqtt-dev/ParadoxAlarmSystem/ParadoxAlarmSystemOTA/ParadoxAlarmSystemOTA.ino: In function 'void setup_wifi()': ParadoxAlarmSystemOTA:981: error: 'DynamicJsonBuffer' was not declared in this scope DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:981: error: expected ';' before 'jsonBuffer' DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:982: error: 'jsonBuffer' was not declared in this scope JsonObject& json = jsonBuffer.createObject(); ^ ParadoxAlarmSystemOTA:991: error: 'class ArduinoJson650_0_0::JsonObject' has no member named 'printTo' json.printTo(Serial); ^ ParadoxAlarmSystemOTA:992: error: 'class ArduinoJson650_0_0::JsonObject' has no member named 'printTo' json.printTo(configFile); ^ /home/user/Desktop/ParadoxRs232toMqtt-dev/ParadoxAlarmSystem/ParadoxAlarmSystemOTA/ParadoxAlarmSystemOTA.ino: In function 'void mountfs()': ParadoxAlarmSystemOTA:1081: error: 'DynamicJsonBuffer' was not declared in this scope DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:1081: error: expected ';' before 'jsonBuffer' DynamicJsonBuffer jsonBuffer; ^ ParadoxAlarmSystemOTA:1082: error: 'jsonBuffer' was not declared in this scope JsonObject& json = jsonBuffer.parseObject(buf.get()); ^ ParadoxAlarmSystemOTA:1083: error: 'class ArduinoJson650_0_0::JsonObject' has no member named 'printTo' json.printTo(Serial); ^ ParadoxAlarmSystemOTA:1084: error: 'class ArduinoJson650_0_0::JsonObject' has no member named 'success' if (json.success()) { ^ exit status 1 'DynamicJsonBuffer' was not declared in this scope

Maybe I should be using a different tool to upload it that I'm not aware of?

Panel commands

Hi
I've tried arming the panel through the commands outlined in the wiki however nothing happens.
I am receiving all status alerts as expected.
Please assist

Thanks

Test Branch needs yor help..

1.) Added mqtt username and password to wifi manager
2.) Added Partition Flag so reporting can be partition based

Need someone to add this project to platformio ....

BabyWare

Sooo i found myself here since the Paradox Gold upgrade, So my ipmodule is a waist of time now.

Do you think its possible to use the device as an serial gateway ?

WiFiTelnetToSerial - Example Transparent UART to Telnet Server for esp8266 EG that is included in IDE.

If i try derectly it seems there is an auth request it wants filled. but i am unable to check furhter:

⸮⸮

any help on this. pretty new to this - No such file or directory

Arduino: 1.8.7 (Windows 10), Board: "Arduino/Genuino Uno"

ParadoxAlarmSystemOTA:3:25: error: ESP8266WiFi.h: No such file or directory

compilation terminated.

exit status 1
ESP8266WiFi.h: No such file or directory

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

2 dead wemos

Hi I am trying to connect wemos d1 mini to Paradox sp 5500 alarm panel to serial and they burn.
What I am doing wrong?

Spectra (Paradox) 1738

Hi @maragelis any chance this will work on a Paradox 1738 or is that simply too old?

Also you stated you have added a Home Assistant config to the Wiki but I just don't see it. I assume the Wiki refers to one hosted here on Github and not somewhere else.

Very interested to play around with this, but would avoid the pain and trauma if I know beforehand it won't work.

Weird messages received in the OUT topic

Hello!
First of all, thanks for your work, I really appreciate what you have done.

I have tried to get this working in the past week, could not make it work on the wemos d1 mini, tried with all versions available (including dev) and all esp8266 core that I found referenced in the issues.
During the weekend I flashed one wemos d1 pro ... and wow, out of nowhere I started receiving messages in the out topic - I used 2.2.4 firmware with esp8266 2.5.2 and pubsubclient.h having the mqtt max packet size set at 256

The problem that I have now is that the messages that I received cannot be found in the events / sub-events list and from what I have followed they are changing for the same action and therefore the arm/disarm/sleep actions are not retrieved.

I do have some messages that are translated correctly, and these are the zones ON and OFF, and are sent to the hasio/ topic.

But the all of the arm / disarm actions (via remote or panel) are not translated or sent to any hassio topic. Further more, if I send any json command to the in topic the wemos disconnects in 15 seconds or so. Note that I let the wemos connected for more than 2-3 hours, no problems ... as long as I don't send any commands.

The connection I have to the board is temporary - I used an external 5v adapter and connected to the serial pins only the TX and RX via small jumper wires (could this be the issue?)
Here's the list of the messages I get:

{"event":1,"sub_event":7,"sub_eventD":"","eventD":"Zone open ","data":"one 07    09#���"}
{"event":1,"sub_event":7,"sub_eventD":"","eventD":"Zone open ","data":"����\t�����������"}
{"event":7,"sub_event":0,"sub_eventD":"","eventD":"","data":"on_L�ߐ$������"}
{"event":2,"sub_event":11,"sub_eventD":"Disarm partition","eventD":"Partition status","data":"��$$\nɕ��1    ��"}
{"event":2,"sub_event":12,"sub_eventD":"Arm partition","eventD":"Partition status","data":"`�b\nɕ��1"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"Ar���������"}
{"event":3,"sub_event":2,"sub_eventD":"Bell squawk arm","eventD":"Bell status","data":"���B"}
{"event":255,"sub_event":111,"sub_eventD":"","eventD":"","data":"Zone 07 # �����"}
{"event":80,"sub_event":177,"sub_eventD":"","eventD":"","data":"Area 1 �/��"}
{"event":2,"sub_event":9,"sub_eventD":"Squawk OFF","eventD":"Partition status","data":"��\t\nɕ��1      �"}
{"event":9,"sub_event":0,"sub_eventD":"","eventD":"","data":"A����������"}
{"event":7,"sub_event":0,"sub_eventD":"","eventD":"","data":"one �7;\t������"}
{"event":9,"sub_event":0,"sub_eventD":"","eventD":"","data":"A��zHL�����"}
{"event":147,"sub_event":26,"sub_eventD":"","eventD":"","data":"���O@"}
{"event":160,"sub_event":8,"sub_eventD":"","eventD":"","data":"A���'H����"}
{"event":15,"sub_event":141,"sub_eventD":"","eventD":"User code activated output","data":"��'"}
{"event":5,"sub_event":0,"sub_eventD":"","eventD":"","data":"one 050�'�����"}
{"event":16,"sub_event":194,"sub_eventD":"","eventD":"Wireless smoke maintenance signal","data":"one04 �����"}
{"event":66,"sub_event":77,"sub_eventD":"","eventD":"","data":"ne04���G@"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"stem Myer"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"p��"}
{"event":2,"sub_event":11,"sub_eventD":"Disarm partition","eventD":"Partition status","data":"\"��\nɕ��1     8"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"�Ov��1"}
{"event":2,"sub_event":11,"sub_eventD":"Disarm partition","eventD":"Partition status","data":"���\nɕ��1    8��"}
{"event":0,"sub_event":2,"sub_eventD":"","eventD":"Zone OK","data":"��<1     ^�"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"�����"}
{"event":194,"sub_event":15,"sub_eventD":"","eventD":"","data":"Area 1<Ҡ�"}
{"event":141,"sub_event":254,"sub_eventD":"","eventD":"","data":"Area(7 ���"}
{"event":2,"sub_event":14,"sub_eventD":"Exit delay started","eventD":"Partition status","data":"��  Area 1     `"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"��c 1"}
{"event":11,"sub_event":0,"sub_eventD":"","eventD":"","data":"�4��׮V�1"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"@��"}
{"event":35,"sub_event":2,"sub_eventD":"","eventD":"Zone bypassed","data":"x��"}
{"event":177,"sub_event":33,"sub_eventD":"","eventD":"","data":"Area�����b"}
{"event":3,"sub_event":154,"sub_eventD":"","eventD":"Bell status","data":"p���"}
{"event":2,"sub_event":251,"sub_eventD":"","eventD":"Partition status","data":"Area 1���b"}
{"event":0,"sub_event":0,"sub_eventD":"","eventD":"Zone OK","data":"ne ��"}
{"event":1,"sub_event":7,"sub_eventD":"","eventD":"Zone open ","data":"����07"}
{"event":2,"sub_event":9,"sub_eventD":"Squawk OFF","eventD":"Partition status","data":"���\nɕ��1   `��"}
{"event":3,"sub_event":2,"sub_eventD":"Bell squawk arm","eventD":"Bell status","data":"��"}

If you have any suggestion or if there is something that I can do to trace it further (the above list is from mqtt trace)

PS - in the wiki, is there a typo for the in topic, is there a missing "d" ???
--> paradoxCTL/in
instead of
--> pradoxdCTL/in
Thanks!

Wired connectivity possible?

Hello,

I would rather prefer not to use a wireless connection between the SP8266 and the Alarm panel. Does anybody know whether that is somehow possible?

many thanks everyone and hats off to this project!!! :)

commands

Hi Panagiotis,
Congratulations for your amazing job. i tested this with SP5500 and works perfectly with hassio.
But the commands "zonestate", "armstate" have no response. Everything else (arm, disarm, etc) working perfect. Any opinion???
Thanks in advance,
Christos

Integration of Telgram library.

Congratulations for this project. It works great.
However I missed to have some of the notifications push in the telephone. I tried to integrate Telegram library in the code but I am afraid I am not skilled enough and failed.
I do not know if somebody can assist with this.
Thx and regards.

Analyzing the Data

Hello, I got mine Paradox MG5050 running and I can arm/disarm it using mqtt json, however I am not receiving the armstatus, this is my json message
{ "armstatus":224, "event":2, "sub_event":9, "dummy":" Area 1 "}

Homeassistant help

Hi I have not tested as yet but i am not 100 percent sure how to add JSON commands into MQTT switches in home-assistant if that's what some are using for arm disarm i would also like some help in config of binary sensors to get zone open close state changes ill post the code i have written please help me fix any mistakes i am sure once i get the first ones working ill be off . thanks in advance...
maybe someone could share there home-assistant config files switch and binary any other please....

switch:

• platform: mqtt
  name: "Arm Disarm"
  state_topic: "/paradox/status"
  command_topic: "/paradox/in"
  payload_on: '{"password":"1980","Command":"arm","Subcommand":"0"}'
  payload_off: '{"password":"1980","Command":"disarm","Subcommand":"0"}'
  optimistic: false
  qos: 0
  retain: true

libs

Thanks for the great program !

Is tha possibile to uplod the correct libraries what you are using to compile this code ?

Thx Robert.

This image of sp6000 differ from images in package

Hi all...
so understandably Paradox is not so sharing about what ports is what on the board, or well more than what i can find online atm.

Attached is the best image i can get of a current SP6000, which pins am I to use ?
as far as I can see the image shown as part of the package is the sp4000

Definitely not keen on blowing my board... :)

G

More a query - what version of ArduinoJSON is required

More a query - what version of ArduinoJSON is required.
It's not listed in the required libraries folder.
Firs time trying to get something compiled for Arduino.
since I have to specify the mqtt broker IP, username and password i guess making this available as a bin file is out of the hand. would have been nice if the build could have been available as a bin and if that could have been configured after first boot, after joining home network/SSID.
G

Arm, disarm payload with wrong password

Hi Panagiotis,
i realized by mistake that sending in the topic "paradoxdCTL/in" payloads with wrong password, the paradox alarm system is arming and disarming. As example i'm having as acount password 1234 and i'm sending from my HA payload_disarm: '{"password":"aaaaaaa","Command":"disarm","Subcommand":"0"}' and my system goes to disarmed. These happens when i send a command one time with the suitable code (1234), after that any commands with any wrong code is controlling my paradox system.

comms help

no info coming from panel even after sending JSON commands .

serial output from console Arduino below does this look correct as far as out put
does it look like im connected and talking to interface panel.
im kinda stuck

{"mqtt_server":"192.168.1.100","mqtt_port":"1883"}*WM: Adding parameter
*WM: server
*WM: Adding parameter
*WM: port
*WM:
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster
*WM: Connection result:
*WM: 3
*WM: IP Address:
*WM: 192.168.1.112
*WM: freeing allocated params!
_
Soft WDT reset

_ctx: sys 
sp: 3fffeff0 end: 3fffffb0 offset: 01b0

>>>stack>>>
3ffff1a0:  00000000 00000000 00000000 3fff045c  
3ffff1b0:  00000001 00000019 00000001 00000030  
3ffff1c0:  00000000 4bc6a7f0 9cac0831 00000000  
3ffff1d0:  00000000 00000000 4bc6a7f0 00000000  
3ffff1e0:  3ffefa08 000003bd 000003bd 4010020c  
3ffff1f0:  31996bb3 00418937 31996bb3 00000000  
3ffff200:  00000000 00000000 00418937 00000000  
3ffff210:  00000002 00000000 401067d9 4bc6a7f0  
3ffff220:  00000000 00000000 3fff0934 4020bced  
3ffff230:  0eae6fc0 00000001 3fff0934 4020bd65  
3ffff240:  7fffffff 3ffea52c 3ffef59c 00000001  
3ffff250:  00000019 00000024 3ffef59c 4020f625  
3ffff260:  0000003c 00000001 00002710 40215a72  
3ffff270:  40201d21 00000000 3ffef55c 40215ab5  
3ffff280:  00000001 00000024 3ffef804 00000001  
3ffff290:  00000019 00000024 3ffef804 40207cc9  
3ffff2a0:  3ffef55c 00000001 3ffff30f 4021737c  
3ffff2b0:  00000010 00000001 0000000f 3ffef55c  
3ffff2c0:  00000038 00000001 0000000f 40106889  
3ffff2d0:  3ffff30e 00000000 3ffef55c 4020a1d0  
3ffff2e0:  00000001 00000000 3ffff30d 402145ad  
3ffff2f0:  00000001 00000001 3ffe94ed 3ffe94ee  
3ffff300:  3ffef55c 00000001 3ffe94ed 4021737c  
3ffff310:  3ffef500 00000001 3ffe8ed9 00000000  
3ffff320:  3ffefa08 000003bd 000003bd 4010020c  
3ffff330:  3ffefa08 0000031e 0000031e 4010020c  
3ffff340:  00000019 00000000 3ffff370 401006dc  
3ffff350:  00000019 00000080 3ffef55c 402083c1  
3ffff360:  3fff1818 00000080 3ffef55c 40209f15  
3ffff370:  40201f6d 00000001 00000000 00000100  
3ffff380:  00048019 00000000 00000000 00000001  
3ffff390:  00000019 00000080 3ffef804 00000001  
3ffff3a0:  00000019 00000080 3ffef804 4020820b  
3ffff3b0:  00000000 00000000 00000000 00000000  
3ffff3c0:  00000000 00000000 00000000 00000000  
3ffff3d0:  00000000 00205f00 00000000 00000000  
3ffff3e0:  00000000 00000000 00000000 00000000  
3ffff3f0:  00000000 00010000 3ffe8000 00000001  
3ffff400:  0000000b 00000000 0000000b 40209fbd  
3ffff410:  00000000 00000000 00000000 4020f18b  
3ffff420:  007d0043 00000000 3fff17c4 0000003f  
3ffff430:  00000034 00048019 0000000b 40215ab5  
3ffff440:  7fffffff 000c97a2 3ffef59c 40216abc  
3ffff450:  00000019 000c97a2 3ffef59c 4020f770  
3ffff460:  3ffe9c01 00000001 00002710 40215a72  
3ffff470:  00000004 3ffef59f 00000043 40215ab5  
3ffff480:  00000001 00000024 00000000 00000001  
3ffff490:  00000019 00000024 3ffef804 40207cc9  
3ffff4a0:  3ffef55c 00000001 3ffff50f 4021737c  
3ffff4b0:  00000010 00000001 0000000f 3ffef55c  
3ffff4c0:  00000038 00000001 0000000f 40106889  
3ffff4d0:  3ffff50e 00000000 3ffef55c 4020a1d0  
3ffff4e0:  00000001 00000000 3ffff50d 402145ad  
3ffff4f0:  00000001 00000001 3ffe94ed 3ffe94ee  
3ffff500:  3ffef55c 00000001 3ffe94ed 4021737c  
3ffff510:  3ffef500 00000001 3ffe8ed9 00000000  
3ffff520:  3ffefa08 000003bd 000003bd 4010020c  
3ffff530:  3ffefa08 00000315 00000315 4010020c  
3ffff540:  00000019 00000000 3ffff570 401006dc  
3ffff550:  00000019 00000080 3ffef55c 402083c1  
3ffff560:  3fff17d0 00000080 3ffef55c 40209f15  
3ffff570:  40201f6d 00000001 00000000 00000100  
3ffff580:  00048019 00000000 00000000 00000001  
3ffff590:  00000019 00000080 3ffef804 00000001  
3ffff5a0:  00000019 00000080 3ffef804 4020820b  
3ffff5b0:  00000000 00000000 00000000 00000000  
3ffff5c0:  00000000 00000000 00000000 00000000  
3ffff5d0:  00000000 00205f00 00000000 00000000  
3ffff5e0:  00000000 00000000 00000000 00000000  
3ffff5f0:  00000000 00010000 3ffe8000 00000001  
3ffff600:  0000000b 00000000 0000000b 40209fbd  
3ffff610:  00000000 00000000 00000000 4020f18b  
3ffff620:  007d0043 00000000 3fff177c 0000003f  
3ffff630:  00000034 00048019 0000000b 40215ab5  
3ffff640:  7fffffff 000c8bde 3ffef59c 40216abc  
3ffff650:  00000019 000c8bde 3ffef59c 4020f770  
3ffff660:  3ffe9c01 00000001 00002710 40215a72  
3ffff670:  00000004 3ffef59f 00000043 40215ab5  
3ffff680:  00000001 00000024 00000000 00000001  
3ffff690:  00000019 00000024 3ffef804 40207cc9  
3ffff6a0:  3ffef55c 00000001 3ffff70f 4021737c  
3ffff6b0:  00000010 00000001 0000000f 3ffef55c  
3ffff6c0:  00000038 00000001 0000000f 40106889  
3ffff6d0:  3ffff70e 00000000 3ffef55c 4020a1d0  
3ffff6e0:  00000001 00000000 3ffff70d 402145ad  
3ffff6f0:  00000001 00000001 3ffe94ed 3ffe94ee  
3ffff700:  3ffef55c 00000001 3ffe94ed 4021737c  
3ffff710:  3ffef500 00000001 3ffe8ed9 00000000  
3ffff720:  3ffefa08 000003bd 000003bd 4010020c  
3ffff730:  3ffefa08 0000030c 0000030c 4010020c  
3ffff740:  00000019 00000000 3ffff770 401006dc  
3ffff750:  00000019 00000080 3ffef55c 402083c1  
3ffff760:  3fff1788 00000080 3ffef55c 40209f15  
3ffff770:  40201f6d 00000001 00000000 00000100  
3ffff780:  00048019 00000000 00000000 00000001  
3ffff790:  00000019 00000080 3ffef804 00000001  
3ffff7a0:  00000019 00000080 3ffef804 4020820b  
3ffff7b0:  00000000 00000000 00000000 000000⸮⸮iC2⸮

OTA

Hi guys,
I’ve uploaded my code and changed setup wifi and MQTT address I can see the device on my network ip 192.168.1.9 now if I try browsing to that address it fails to connect.
Is this normal as I was thinking it should log me into the same setup page after first flashing it . Maybe my arduino library’s are out of date not sure .

Physical Connections to Paradox and ESP8266

Hello, I'am trying to intergrate this to my openhab2 setup at home, and having issues with the physical connections including the resistors and pins, could you provide some sourt of schematics?
The code section says 10k resistor and the wiki says 220 resistors, that's what got me confused, what resistors should I use, which pins of the ESP should I use[by the code im guessing 13,15], and I'm supposed to use the serial on my paradox alarm system right?

API Documentation

Hi there, thanks so much for this. I managed to receive the various events from my SP6000, but I am unable to arm / disarm, etc and trying to figure out why as I am not getting the log in response from the panel. I want to see what the response messages are that are returned from the panel within the "doLogon" method so that I can determine if I am specifying an incorrect password or not.

It would seem that you have the API documentation handy due to the info that you've posted to your wiki. Is it possible that you can make it available to me please?

Paradox EVO 192

I have a Paradox EVO 192 alarm system.
The board don't reveal the alarm through serial port.
Any advice?
Thanks,

Manuel

Hardware question

Hello

Sorry to open an issue for this hw issue of mine, but I would like to ask you asap about this one.
I connected a wemos board to paradox sp6000. The wemos is supplied via usb , thus only 3 cable is used for the serial connection (gnd, tx and rx). I uploaded your scripts to wemos and apparently is working because I received messages in paradoxdCTL/status, but not in paradoxdCTL/in. Over there is nothing :(
My questions are the following.
The 3 cable are enough or i have to use 4, aux+as well ? Do I have to do something on the SP6000, eg to let the pc communcitaion start ? I am stuck right now, I would appreciate any help ! :)

Thanks a lot and sorry for bothering you with this !

New Inception alarm Panel

Would anyone be interested on working on this system as well it's compatible with alot of paradox product and can talk on same bus as paradox. I have one ordered and will upload any modifications I make for this system if anyone is interested.
Link to inception system below .
https://atlasgentech.co.nz/products/access-control-intruder-detection/intruder-detection-access-control-combined-systems/inner-range-inception/inception-kits/inner-range-inception-starter-kit-with-elite-x-terminal-sifer-reader.html

https://atlasgentech.co.nz/inner-range-wireless-receiver-paradox-lan-module.html

Issue with commands. Help needed.

Thank you very much for this awesome project.
I successfully connect to SP4000, can read alarm status, sensors event, but i cannot send commands.
I double checked wires, change pins, i can read status, but cannot control the panel :(
I tried with user code, pc code "0000", all kinds of combinations.

What i'm doing wrong ?

Here is my config:

partition topic issue

Hi Maragelis,

My paradox have two partitions. I would like to use these partition separate. Now the state and command topics is the same on the different partitions. This is the source of my problem.
Now when I disarm one of the partitions (onyl one), after that all partitions disarmed, and vice versa too.

Regards
Zsolt

PGM

Hi, I would like to have a pgm pulse command that turns a PGM on and then off a second later. My alarm has a PGM connected to a garage door opener.

MQTT authentication

Hi,
Does the project have authentication MQTT support?
thanks

Δεν αποκρίνεται το wemos

Καλημέρα,

Για αρχή θέλω να σου πω ένα μεγάλο ευχαριστώ για όλο αυτό που έχεις φτιάξει!!

Το πρόβλημα που αντιμετωπίζω είναι το εξής.

Ενώ το wemos κάνει connect κανονικά στον mqtt βλέπω και το page του αν βάλω την ip του στον browser, όταν κάνω οποιαδήποτε ενέργεια για όπλιση του συναγερμού αποσυνδέετε από τον mqtt και δεν είναι προσβάσιμο ούτε στο interface του, μόλις του κάνω restart κάνει πάλι connect κανονικά! Δεν μπορώ να καταλάβω τι γίνεται μήπως έχεις κάποια ιδέα.

Να σημειώσω ότι έχω Homeassistan σε PI 3 b+ και χρησιμοποιώ το Home Assistant in V2 με το V2 node red

Paradox Magelan MG-5050 alarm system

Hi,
you have created a great product. I replicate it.

When I connect to the Paradox Magelan MG-5050 alarm system.
Through MQTT I get only one status from
„paradoxdCTL/status“ - disarmed
and
"paradoxdCTL/hassio/Arm"- disarmed

I created binary sensors for Home Assistant but the statuses do not change :

• platform: mqtt
  name: Sensor_Tamburas_Durys
  state_topic: "paradoxdCTL/hassio/zone1"
  qos: 0
  device_class: door

• platform: mqtt
  name: Sensor_Virtuves_PIR
  state_topic: "paradoxdCTL/hassio/zone2"
  qos: 0
  device_class: motion

Please help find where the problem is and how to fix it.

Panel login failure with 5.23 firmware

Hello!

I have paradox sp4000.
The original firmware was 4.8 firmware, and the serial communication was not working at all.
I upgraded the firmware to 5.23, now the communication is working, i see all the information from the paradox sp4000, but i cannot send any command, it fails with panel login failure.
Can you help me with the problem finding (the paradox password sent is correct) ?
Which firmware do you use?
Can you share with me?

Thx!

IP150 & D1 mini

I have SP6000 with IP150 module.
I connect parallel to the serial port the IP150 and the D1 mini. with your code.
Now the D1 mini works, but the IP150 doesn't.
The leds seems to be OK (Internet, Link, RX/TX) on the IP150 but the panel says connection error.
The IP150 has IP address and I can access and login via web. But after the web login it say session expired.
Do you have an idea of the mistake?

Arming 2 zones with 1 json playload

Hi, any options to make 1 json playload to arm/disarm both zones at once ?

Events stop after some time

Hi,
I have a Magellan 5000 and I use a WemosD1 mini to connect to the alarm system.

At night I arm the alarm, but in the morning "ParadoxRs232toMqtt" seems to be down.
I can ping the wemos but I cannot receive MQTT Message.

What can I do? How can I do to debug it?

I use hassio on a rasperry and "Mosquitto broker" as a MQTT Server.

thanks
Fabio

Firmware download

Hi

Ian using 5.23 firmware version on sp4000.
Events are comming but I can not send arm commands. Arm commands rejected with 0x70 - login error.

I would like to downgrade the firmware.
Have you seen older version of firmware ?
As I see on this topic pictures its using older firmware version on sp4000

Home Assistant

Hello,
i am trying to get in the Home assistant the values of MQTT topic paradoxdCTL/out when i send the topic paradoxdCTL/in for panel status. I am trying this as a sensor but i get uknown state.

• platform: mqtt
  name: 'Paradox Voltage'
  state_topic: 'paradoxdCTL/out'
  unit_of_measurement: 'V'
  qos: 0
  value_template: '{{ value_json.BatteryDCVoltage }}'

readserial crash!

Hi panagiotis, i am using your code over a year with no problem. But now i make some modifications in ordered to stay online with the SP6000 the wemos. i am running the panelstatus commands evry 20 seconds in order to have the paradox status. But as it started well after it crashes. something goes wrong with serialread and serialreadquick.
as example. paradox is sending:
52 00 80 00 00 00 00 00 00 14 14 04 06 10 0a cd 9a 97 00 03 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20
52 00 80 01 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 02 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 d9
52 00 80 02 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 d4
at paradox status 0,1,2 request and the wemos is reading:
D4 52 08 00 00 00 01 41 44 61 01 9D 09 A9 70 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
20 52 08 01 00 00 00 00 00 00 03 00 20 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
D9 52 08 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Suddenly it crash and is reading as fisrt byte the checksum from the previous message and also loses some bytes.
Do you have any suggestion??
Its happening one or two hours later from the begining.

Is there a way to use Arduino UNO with ethernet?

Hi Maragelis,

One question is repeating in my mind for months.
Is there an easy way to use Arduino ethernet-based module instead WIFI?
Sometimes WIFI is weak.

Regards
Peter

Pending Status in HA

Hello,
how can i get the pending status for this component https://www.home-assistant.io/lovelace/alarm-panel/
Now i am using the https://github.com/alfredopironti/Paradox_IP150 so when i arm the panel in standby time until the alarm is armed i get the status pending.
Here is a picture https://www.home-assistant.io/images/lovelace/lovelace_alarm_panel_title_card.gif

Controlling alarms through the Android application

Hello, wanted to know, this allows you to watch only events with the protection of the Paradox panel?
Or it allows you to control the panel (arm, disarm)?
I did not quite understand how it works ...

And why are there two code: ParadoxAlarmSystemOTA and ParadoxAlarmSystem?

Wemos D1 Mini Pro - frequent reconnects

Hi,

I am using a Wemos D1 Mini Pro and a buck converter connected to the Gnd and + serial pins of the MG5050 alarm system. I have properly soldered the pins and checked the connections several times, confirmed that the system is working (I could read/arm/disarm using MQTT). However after ~20-30 minutes the Wemos D1 Mini Pro is disconnected (for no obvious reason) and does not come back online. I have resoldered the connections precisely, tested and connected back to the alarm system. Same thing happened again after a few minutes.

Now I have connected the power to the 3v pin (stepped down the voltage with the buck converter) and testing it for a few minutes but I still see disconnects - Socket error on client 84:F3:EB:DB:5B:06, disconnecting. (at least with quick reconnects this time).

Should I be targeting a faulty Wemos module? I have a NodeMCU board that I have already programmed and is waiting in the shelf. If those disconnects continue, I will be trying it instead of the Wemos board.

I have used the following libraries and settings, as it would not compile with some of the lib versions from the Readme:
#59 (comment)

Using Arduino IDE v1.8.12
Install this from "Tools" -> "Board: "some board" -> "Boards Manager":

ESP8266 Community v2.6.3
Install these from "Tools" -> "Manage Libraries":

WiFiManager by tzapu v0.15.0
PubSubClient by Nick O'Leary 2.6.0
Arduino JSON lib version 5.13.5 (does not currently work with version 6.x)
Files to be changed:

Open webpage.ino:
Change "String page = FPSTR(HTTP_HEAD);" to "String page = FPSTR(HTTP_HEADER);"
Change "page += FPSTR(HTTP_HEAD_END);" to "page += FPSTR(HTTP_HEADER_END);"

These are the Mosquitto logs:
1587933143: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933339: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933360: New connection from 192.168.0.170 on port 1883.
1587933360: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933405: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933405: New connection from 192.168.0.170 on port 1883.
1587933405: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933466: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933487: New connection from 192.168.0.170 on port 1883.
[INFO] found MQTT-user on Home Assistant
1587933489: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933669: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933679: New connection from 192.168.0.170 on port 1883.
1587933679: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933770: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933780: New connection from 192.168.0.170 on port 1883.
1587933780: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933835: Saving in-memory database to /data/mosquitto.db.
1587933885: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933898: New connection from 192.168.0.170 on port 1883.
[INFO] found MQTT-user on Home Assistant
1587933899: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').
1587933944: Socket error on client 84:F3:EB:DB:5B:06, disconnecting.
1587933967: New connection from 192.168.0.170 on port 1883.
1587933967: New client connected from 192.168.0.170 as 84:F3:EB:DB:5B:06 (p2, c1, k15, u'MQTT-user').

Version 2.2.3 Timeout

Hi @maragelis I just updated the new version and it is getting timeout again.
I think the problem is with the library NTPtimeESP.h
Please tell me how to fix it or remove it?

Nothing from paradoxdCTL/# after receiving Paradox Connected

Hello,

I have a Paradox 1759EX alarm and I flashed a Nodemcu ESP8266 with ParadoxAlarmSystemOTA.ino
I connected RX/TX and Ground between the Paradox board and the ESP8266 relevant pins.
The Nodemcu ESP8266 is powered by USB.
On mqtt.fx I have subscribed to topic paradoxdCTL/# and when i boot the ESP8266 I get:
"status":"Paradox connected"
and
"firmware":"SYSTEM PARADOX_2.2.3"

after that I don't get any other message from mqtt from any zone when it opens or closes.

Any ideas why and how to get the status from my zones?

Also when I try to send a command to paradox (e.g arm) I publish on topic paradoxdCTL/in the payload { "password":"1234", "Command":"arm", "Subcommand":"0" } nothing happens and after a few seconds I receive on paradoxdCTL/status the message "Paradox Disconnected" and after around 2 minutes I receive on the same topic the message "Paradox connected".

Any idea how to proceed?
Thank you in advance.

Wemos d1 mini pro losing connection to MQTT

Hello @maragelis,

I have been runnig this wonderfull piece of software for a while now but I have been having sometimes the following issue:
I noticed that the wemos get's disconnected from the MQTT brooker. I try to send a command and the alarm panel does not respond. The last status on the MQTT brooker is Paradox Disconnected. Sometimes when it is in this state, Paradox Disconnected, it does not change to anything else and I cannot issue any command. If I do something like passing in front of a sensor or arm/disarm the panel in the local keypad, it seems that the wemos connection to the MQTT brooker "wakes up" and everithyng is up and running again.

Could you please try and give me a hand on this subject.

Thanks in advanced for all your help and support.

Best regards.