Replies: 18 comments 18 replies
-
|
The same here |
Beta Was this translation helpful? Give feedback.
-
|
@cmasse1 did you got it working? |
Beta Was this translation helpful? Give feedback.
-
|
I couldn't, also the old ip150 I had had the firmware updated to a newer version and it doesn't connect anymore either, my evo was left out of my home assistant, sad |
Beta Was this translation helpful? Give feedback.
-
|
Ip150 should work. You are doing something wrong. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't change anything in my configuration and before it worked, after updating the firmware of my ip150+ it stopped connecting, now it has 6.10.010 |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
It looks that it does not expose port 10000 anymore. How you connect with Babyware? |
Beta Was this translation helpful? Give feedback.
-
|
With serial number and password from the evo, it no longer lets me do it
with a fixed IP
El mié, 12 jun 2024 a la(s) 1:42 p.m., Jevgeni Kiski (
***@***.***) escribió:
… It looks that it does not expose port 10000 anymore. How you connect with
Babyware?
—
Reply to this email directly, view it on GitHub
<#455 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6XY4MB63NJSYBO63IDZHB27HAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONJUGMZDK>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
There might be a setting to allow local connections somewhere. Did you check web UI of the IP150? |
Beta Was this translation helpful? Give feedback.
-
|
You can no longer enter the web interface on the ip150 with the new
firmware, they do not allow connections to internal networks according to
what I have read, even though I know the IP, you cannot enter through the
browser.
El mié, 12 jun 2024 a la(s) 2:51 p.m., Jevgeni Kiski (
***@***.***) escribió:
… There might be a setting to allow local connections somewhere. Did you
check web UI of the IP150?
—
Reply to this email directly, view it on GitHub
<#455 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6SQGZLCEO6RLQB4N7LZHCDCZAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONJUHE4TM>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi there - I was able to get the IP180 to connect via InField and BabyWare, but not to PAI. I tried to do a firmware update of the main board with it (Evo 192) but it seems to have failed and bricked it. I'll get a replacement board when I have a bit more spare time to tinker with the system. I do recall connection over IP being listed as a thing for the "future" for the IP180 as per Paradox's document... Although with the IP150 not connecting over IP after a firmware update I am doubtful it will ever happen. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/ParadoxAlarmInterface/pai/wiki/Compatibility I see that EVO fw does not influence. IP150 might. |
Beta Was this translation helpful? Give feedback.
-
|
I agree, for now only promises from paradox, the problem is that more and
more they are closing their systems, they are looking more and more like
Apple
El mié, 12 jun 2024 a la(s) 9:15 p.m., cmasse1 ***@***.***)
escribió:
… Hi there - I was able to get the IP180 to connect via InField and
BabyWare. I tried to do a firmware update of the main board with it (Evo
192) but it seems to have failed and bricked it. I'll get a replacement
board when I have a bit more spare time to tinker with the system. I do
recall connection over IP being listed as a thing for the "future" for the
IP180 as per Paradox's document... Although with the IP150 not connecting
over IP after a firmware update I am doubtful it will ever happen.
—
Reply to this email directly, view it on GitHub
<#455 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6SLEJXDBVQNDLE4QLTZHDQD5AVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONJXGQZDS>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Yesterday I was looking at that table that is very useful. I got an old
ip150, it arrives in a few days, I'll try that one and see what happens. I
have already closed all the ports on the router where it will supposedly
seek to update automatically.
El jue, 13 jun 2024 a la(s) 1:56 a.m., Jevgeni Kiski (
***@***.***) escribió:
… https://github.com/ParadoxAlarmInterface/pai/wiki/Compatibility
I see that EVO fw does not influence. IP150 might.
—
Reply to this email directly, view it on GitHub
<#455 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6ROJR4F4WYMYGYLF7LZHERADAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TONJYHA2TG>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
IP180 work with a new protocol from PARADOX, based on MQTT (probably proprietary, I don't own any MQTT device from PARADOX). For other IP150's, stay away from firmware jump to 6.x as you'll loose direct IP connection and, at this stage, compatibility with PAI. |
Beta Was this translation helpful? Give feedback.
-
|
After updating to its latest firmware, ip150+ became a 150MQ, I understand
that it is now MQTT, but everything does not connect to the panel, except
that something else has to be modified in the PAI configuration and I don't
know it.
[image: image.png]
El mar, 18 jun 2024 a la(s) 7:26 a.m., DrMaboul ***@***.***)
escribió:
… IP180 work with a new protocol from PARADOX, based on MQTT (probably
proprietary, I don't own any MQTT device from PARADOX).
Its little brother IP150MQ work also like this (supplied with firmware
v6.x)
For other IP150's, stay away from firmware jump to 6.x as you'll loose
direct IP connection and, at this stage, compatibility with PAI.
—
Reply to this email directly, view it on GitHub
<#455 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6XMGDIUL45TWXK46NTZIADOLAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMBUGY2DE>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
For now, only way would be to go back to firmware v5.x Option 1 : maybe is it possible to downgrade to 5.x. Do you see any different firmware version in InField ? It seems that with BabyWare 5.6.40, the included In-Field could offer a wayback "prod/IP150+5.6.14TURN.PUF". Do you see this option ? It's the case with people who upgrade their PCS265 from v7 to v8 (here v8 is the MQTT version). Fall-back to v7 is possible and mentioned in the installation manual. With a little luck, Paradox also previewed choice mistake for the IP150. Option 2 : (from IP150 installation manual) Firmware Version Fallback : to revert the IP150MQ module to its previously installed firmware version, unplug the power cable from the panel and insert a pin/straightened paper clip (or similar object) into the pinhole located between the two I/O LEDs. Press down gently until you feel some resistance; plug in the power cable while holding the pin down for approximately five seconds and release it when the I/O 2 LED starts flashing (figure 2). The I/O LED will turn solid and start blinking (resetting to the backup version). Once complete, the IP150MQ will reboot automatically to the previously installed firmware version. |
Beta Was this translation helpful? Give feedback.
-
|
But why would you need PAI if you have an official MQTT solution? Is it paid? Can you configure your own MQTT broker in the IP module? |
Beta Was this translation helpful? Give feedback.
-
I don't own one myself and a this point don't really want to upgrade an IP150 to v6 MQTT but as far as I've read until now, it's based on MQTT protocol and use the default SSL/TLS over MQTT port 8883 but you can't really edit a lot of thing apart from the IP but not sure it's so simple. Just curious but not enough yet to "maybe" sacrifice an IP150. Maybe if @mremedi2023 can go back to 5.x |
Beta Was this translation helpful? Give feedback.
-
|
With firmware 6.x+, you don't have direct IP access like before. As for Babyware like you already noticed. So it shouldn't work with PAI. Maybe in "swan cloud" mode which use serial but need a site ID and an email (look at the wiki). I never tested this mode with PAI. |
Beta Was this translation helpful? Give feedback.
-
|
It does not work, only for swan, according to the paradox site "Does not support static IP connection for now (should be supported in future firmware updates)" they are closing the possibility of connecting with third party software (in this case home assistant) for everyone On the other hand, I got an old ip150 with a fixed IP and I was able to connect, but I couldn't do it to the blueeye as the firmware was so old, the minimum to be able to use the blueeye is V4.10.000, I updated it to test and if I connect to the app but no more to the home assistant, I have 3 different evo panels and 1 ip150, 1 ip150+ and 1 ip180 and none of them are compatible between combinations of panels + ip modules that I have, according to the compatibility table of the PAI project https://github.com/ParadoxAlarmInterface/pai/wiki/Compatibility a crazy thing... to complete, I cannot put the desired firmware on any IP module, since when you connect to the infield it does not allow you to do anything other than take it to the latest firmware available, obviously they also removed the possibility of doing any downgrade class neither to the modules nor to the IP. |
Beta Was this translation helpful? Give feedback.
-
|
Firmware v4.x is real crap, only SWAN. Firmware v1.30 to 1.40 (IP150 and IP150S) are old but fully opened (ip direct access, web interface, work with PAI) Did you tried this :
What are your panels and firmware version of IPxxx ? |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm going to try it and then I'll buy the experience, the tested
compatibility table is here:
https://github.com/ParadoxAlarmInterface/pai/wiki/Compatibility
I have 3 panels
Evo192: v.7.70.001
Evo192: v 2.20.001
EvoHD: v.1.06.001
ip150: v.4.10.000
ip150+ (was modified to 150mq after an update): v.6.10.010
ip180: v.1.00.005
El jue, 20 jun 2024 a la(s) 11:58 a.m., DrMaboul ***@***.***)
escribió:
… Firmware v4.x is real crap, only SWAN.
Firmware v1.30 to 1.40 (IP150 and IP150S) are old but fully opened (ip
direct access, web interface, work with PAI)
In the v5.x series, some have web UI and IP direct access not all. I think
I have a list somewhere with which one allow not only Paradox cloud.
Did you tried this :
Option 2 : (from IP150 installation manual) Firmware Version Fallback : to
revert the IP150MQ module to its previously installed firmware version,
unplug the power cable from the panel and insert a pin/straightened paper
clip (or similar object) into the pinhole located between the two I/O LEDs.
Press down gently until you feel some resistance; plug in the power cable
while holding the pin down for approximately five seconds and release it
when the I/O 2 LED starts flashing (figure 2). The I/O LED will turn solid
and start blinking (resetting to the backup version). Once complete, the
IP150MQ will reboot automatically to the previously installed firmware
version.
What are your panels and firmware version of IPxxx ?
—
Reply to this email directly, view it on GitHub
<#455 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6XSJK2VZ3BWAUZ6EC3ZILU3HAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMZQGIZTM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Option 2: not working
El sáb, 22 jun 2024 a la(s) 11:25 a.m., Esteban Garcia ***@***.***)
escribió:
… Hello, I'm going to try it and then I'll buy the experience, the tested
compatibility table is here:
https://github.com/ParadoxAlarmInterface/pai/wiki/Compatibility
I have 3 panels
Evo192: v.7.70.001
Evo192: v 2.20.001
EvoHD: v.1.06.001
ip150: v.4.10.000
ip150+ (was modified to 150mq after an update): v.6.10.010
ip180: v.1.00.005
El jue, 20 jun 2024 a la(s) 11:58 a.m., DrMaboul ***@***.***)
escribió:
> Firmware v4.x is real crap, only SWAN.
>
> Firmware v1.30 to 1.40 (IP150 and IP150S) are old but fully opened (ip
> direct access, web interface, work with PAI)
> In the v5.x series, some have web UI and IP direct access not all. I
> think I have a list somewhere with which one allow not only Paradox cloud.
>
> Did you tried this :
>
> Option 2 : (from IP150 installation manual) Firmware Version Fallback :
> to revert the IP150MQ module to its previously installed firmware version,
> unplug the power cable from the panel and insert a pin/straightened paper
> clip (or similar object) into the pinhole located between the two I/O LEDs.
> Press down gently until you feel some resistance; plug in the power cable
> while holding the pin down for approximately five seconds and release it
> when the I/O 2 LED starts flashing (figure 2). The I/O LED will turn solid
> and start blinking (resetting to the backup version). Once complete, the
> IP150MQ will reboot automatically to the previously installed firmware
> version.
>
> What are your panels and firmware version of IPxxx ?
>
> —
> Reply to this email directly, view it on GitHub
> <#455 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BENWU6XSJK2VZ3BWAUZ6EC3ZILU3HAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMZQGIZTM>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I'd update EVO192 and HD panels to the last 6.x version. You could use Serial connection for these If you do not have an IP150 with supported local connection. |
Beta Was this translation helpful? Give feedback.
-
|
For those more knowledgeable in programming, now blue eye has information that it did not have before, I attach a screenshot. Additionally, ip180 allows fixed IP in its latest version, I still cannot connect through the normal PAI procedure. |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't it allow you to set your own mqtt broker address? What does it send there? |
Beta Was this translation helpful? Give feedback.
-
|
I really don't know, I wouldn't know what to change or put in each place to test. I gave up on making it work, I'm about to change my alarm to a Hikvision one. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, in the compatibility table regarding evo hd+ I assume that when it comes to version 1.3.1 or 1.4.1 it actually refers to [ V1.03.001] and [ V1.04.001] is that correct? |
Beta Was this translation helpful? Give feedback.
-
|
Most probably. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry but I can't edit the compatibility table, the last 3 lines should be
like this to be correct:
[image: image.png]
I was able to connect my Evohd+ with the latest firmware but I don't know
what happened to my old ip150+ but Paradox took pity and it seems that it
now allows firmware downgrade of the modules, at least mine.
El sáb, 28 sept 2024 a la(s) 3:29 p.m., Jevgeni Kiski (
***@***.***) escribió:
… Most probably.
—
Reply to this email directly, view it on GitHub
<#455 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BENWU6WU7D4YRYNLV76E6SLZY3YPPAVCNFSM6AAAAABGE5ZQT2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZYGUZTGMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
No image was attached. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
For an IP180 connected to a EVO 192, Can one put your own MQTT Broker address in the "MQTT development server" section and thus get it to work with HA/Openhab? |
Beta Was this translation helpful? Give feedback.
-
|
Would be interesting if somebody with IP180 would try and tell us. Then PAI will be obsolete. |
Beta Was this translation helpful? Give feedback.
-
Hi folks, I've been playing around with PAI for the last couple of days using an EVO 192 board and a IP180 using wifi with a fixed IP address. Has anyone had any success getting the IP180 to talk with PAI - is it even possible?
For reference, I'm treating it in terms of config as if it was an IP150.
Beta Was this translation helpful? Give feedback.
All reactions