IP150 & D1 mini about paradoxrs232tomqtt

[istvanszab]

Thank you. I'll give it a try after components purchasing.
I want the IP150 because my wife :) (she loves Insite Gold) and because the patrol service.
And I need only to observe the motion sensors status.

[cybertza]

Hi,

The 2 should work ok together in my opinion, I know people have done it before.

Albeit you may have better luck using the code for the IP150 module to Mqtt ?
https://github.com/Tertiush/ParadoxIP150v2

[istvanszab]

Hi,
no I can't use it. My IP150 has 4.1 firmaware.

[istvanszab]

When I power the D1 mini, mqtt sends:
/paradox/status: Paradox Connected
/paradox/status: ParadoxController V2.11
/paradox/out: { "armstatus":225, "event":44, "sub_event":19, "dummy":""}
/paradox/out: { "armstatus":225, "event":44, "sub_event":18, "dummy":""}
/paradox/out: { "armstatus":225, "event":2, "sub_event":10, "dummy":"House"}
/paradox/out: { "armstatus":224, "event":48, "sub_event":3, "dummy":""}
/paradox/status: panel logout
/paradox/out: { "armstatus":224, "event":2, "sub_event":16, "dummy":"House"}

After this messages I lost the IP150 module.

[cybertza]

Ok well I think there is a panel log void, maybe see if it gets called, and also an panel log in, if you somehow skip those and purely listen it should work? Regards

…

On 06 Dec 2018, at 17:44, istvanszab ***@***.***> wrote: When I power the D1 mini, mqtt sends: /paradox/status: Paradox Connected /paradox/status: ParadoxController V2.11 /paradox/out: { "armstatus":225, "event":44, "sub_event":19, "dummy":""} /paradox/out: { "armstatus":225, "event":44, "sub_event":18, "dummy":""} /paradox/out: { "armstatus":225, "event":2, "sub_event":10, "dummy":"House"} /paradox/out: { "armstatus":224, "event":48, "sub_event":3, "dummy":""} /paradox/status: panel logout /paradox/out: { "armstatus":224, "event":2, "sub_event":16, "dummy":"House"} After this messages I lost the IP150 module. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[istvanszab]

I'm sorry but I don't understand it.
The panel means the SP6000 or the TM50 keypad?
From the keypad I can log in, arm, disarm, etc.
I don't have BabyWare, NeWare or else software. Can I do what you wrote without those softwaress?

[maragelis]

There is no way for two devices to read and write at the same time on one serial port.
You will have to create a function in the code to write the serial data to another port and have the IP150 read it from that serial output. In the event of input the code will have to send the binary data back to the panel serial port.
You could disable the write event in my code and just get the event to mqtt.
If the wemos is working for you (arm and events) why do you want the IP150????

[maragelis]

/paradox/out: { "armstatus":225, "event":44, "sub_event":19, "dummy":""} IP module supervision loss
/paradox/out: { "armstatus":225, "event":44, "sub_event":18, "dummy":""} IP module no service
/paradox/out: { "armstatus":225, "event":2, "sub_event":10, "dummy":"House"} Ground start (partition 1 only)
/paradox/out: { "armstatus":224, "event":48, "sub_event":3, "dummy":""} Software log off
/paradox/status: panel logout
/paradox/out: { "armstatus":224, "event":2, "sub_event":16, "dummy":"House"} Report confirmation

acording to your log the ip150 has lost connection as soon as wthe wemos takes over the serial.

add the wemos in series with the IP150

Use the I/O 2 connection on your ip150 for the wemos