So I have got this up and running. I’ll write a fuller update on what I did in a short while when i have some time. Pretty straightforward with what has been brought up above.
I think what is causing the alarm going off to lock up the system has to do with the way the software handles the alarm state in the paradox system. I purposefully triggered the alarm system so that i could see the behaviour and true to form the system worked perfectly even with the alarm pending state with the timer before the system goes off.
What happened then is that the alarm creates a historical alarm log which is what i think locks it up. Not sure why yet, but i’ll look through it further. I reloaded the entire HASS but it still remained locked up. I tried to clear the alarm from the panel but it did not clear for some reason, still showing a historical message. I think that the timeout will occur in the next day or so and then i’ll see if the system unlocks itself then.
A question though it why is the WAN IP Logger portion of the IP150 system not used. In theory this should push the logs out to a remote monitoring site like ADT or something. Perhaps we could use this instead to send through to the MQTT broker for the firmware which is not usable anymore.