Yeah I was wondering about that. It’s possible, As you’d move the sp specific keep alive and event number driven code to a mapping file and make a new one for evo.
But I’d assume given their direction for firmware that the numbers wanting to do this would be dropping.
I have posted IP150 downgrade instructions and tools to GitHub https://github.com/Tertiush/ParadoxIP150v2/issues/22 because GitHub allows file upload. I will read all comments ant questions there, but for answer periodically look at GitHub.
I confirm that nezmogus’ method works. After a few failures and trying I was able to downgrade my IP150 4.00 to 1.32 and now I can see my alarm’s messages on MQTT.
Hi everyone,
i also started to expirementing with the v2 script, but in my paradox/zone/zone1 topic i get ON and OFF but after them i also get a number different every time, so i can not map them. Am i doing something wrong?Am i missing something?
Thank you in advance.
If these are payloads (again post an example) from my fork of the ParadoxIP150v2 - then yes there is some json, but that’s only panel information (voltages, panel date time, it comes out as part of the heartbeat)
The example alarm.items (in a subfolder of the project on github) has been updated.
What i mean is that for a specific zone i get as payload OPEN/CLOSE although for another, i get ON/OFF with a number after it. See the attached images.
Ok so for a payload like for Paradox/Zone/LR/Windows you will need a JS transform to extract the value
I assume that ON will be OPEN and OFF closed
Create a file called paradox_windows.js in your transform folder with the following content:
(function(payload) {
var data = payload.split(" ")[0]; // "ON" or "OFF"
var result = "";
if (data == "ON") result = "OPEN";
if (data == "OFF") result = "CLOSED";
return result;
})(input)
Make sure the JS (Javascript) transformation in installed in the paperUI
Use the transformation for CONTACT items as it returns OPEN and CLOSED
i would be really interested in trying out that binding but unfortunately i’m not able to downgrade my firmware so that i can use it again.
Any ideas? That manuals which have been posted for downgrading did not work for me…