MG5000 fw 4.76 with IP150 v 4.10 - Problem logging in #22
Comments
Hi - I have not attempted this script with the later IP150 firmware versions, v4 and later. There's been reports of breaking changes in the new firmware. I see you are active on the OH forums, I suggest you try to downgrade the IP module and try again (not sure how to do a downgrade though...). |
Yep, it was a big mistake buying this module.
Are you kidding me? I payed a lot for their alarm system, I even bought another 100$ module and planned to buy others and they are sending me off to the distributors/installers which charge a lot and have no clue about IP150. I've spent a lot of time figuring out what is happening: |
I feel your pain and I fully agree! However, before I wrote this code I initially communicated serially to my MG5050. This works like a charm and I could monitor all the zones and alarm state. I never implemented any control, I simply snooped the Tx line going to the IP150. This line "broadcasts" all the events in the same format this code looks for. If you look at the forks of my project others have re-factored it to work with a serial connection (I used another older version of the code a friend made). All you need is a TTL serial interface (via USB-TTL serial or directly onto a ESP8266?). I know this is not what you had in mind initially, but it will work. If you cannot achieve controls through the serial interface you can always add a relay to some board and connect it to one of the alarm's inputs (zones) to arm/disarm or do something else... |
ah damn same issue here i guess, any plans on supporting the new ip150 FW ? |
Nope sorry. It's a pity no one has figured out how to downgrade the units. |
Same issue here on the V4.10. Will take it back to Communica with the receipt and see if I can beg them for the older unit. |
i figured out how to downgrade IP150 firmware bellow 4.00 ;) I will wait few weeks, until more people, who have same problem, will see this message ant then will share all the tools and instructions how to do downgrade. Until this time I’m recommending disconnect IP150 modules from internet. IP150 firmware from V4.xx updates itself on every IP150 module power cycle, so Paradox can fix their bugs and release update, which can remove possibility of downgrade. My final conclusion about Paradox - DO NOT TRUST THIS COMPANY AND DO NOT BUY THEIR PRODUCTS ANYMORE! I pointed them with finger to their security holes and they even didn’t fixed them all in two weeks time. They even didn’t said “Thank you” to me… because swear words are not allowed, i don’t have what to say anymore about this company. |
I also think that their remote connection is a large security hole. I need to downgrade my IP150 module to replace my EVO192-Serial to Arduino hack. |
I have the same problem with IP150 |
Please please please can you post the how-to-downgrade? I accidentally upgraded my IP150 not knowing about the "cold shower" afterwards I will never advise anyone to buy Paradox again - this is very unprofessional move from their side |
Ok, can we find out how to downgrade now please!! |
While we wait... Check this out. I don't know about you guys, but if/when I ever need to replace my SP6000 I'm going this route. https://www.kickstarter.com/projects/nateclark/konnected-alarm-panel-revive-your-wired-alarm-syst |
Yeah I was looking at those as well. Has a rest api. Someone on openHAB was looking at a binding.
…________________________________
From: saundersrg <notifications@github.com>
Sent: Sunday, June 17, 2018 6:21:08 PM
To: Tertiush/ParadoxIP150v2
Cc: Subscribed
Subject: Re: [Tertiush/ParadoxIP150v2] MG5000 fw 4.76 with IP150 v 4.10 - Problem logging in (#22)
While we wait... Check this out. I don't know about you guys, but if/when I ever need to replace my SP6000 I'm going this route.
https://www.kickstarter.com/projects/nateclark/konnected-alarm-panel-revive-your-wired-alarm-syst
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#22 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFGkc7OsLxYQGqpZX7AtHKq-vcAi5zLXks5t9fVUgaJpZM4PpuhG>.
|
I do not take any responsibility and I am not liable for any damage caused through use of this information. More than month past since I informed Paradox about their bugs. Actually, more than week ago I offered them to help fixing their systems. I received this answer: “I have escalate your suggestion to upper management. Unfortunately, nobody from paradox contacted me... But now about IP150. To downgrade firmware bellow V4.00: TVPfwd_v2.zip (edited: this version adds time with milliseconds to each packet in the log file) After that you need start (you need .net 4 for that) attached file TVPfwd.exe with these parameters:
54.165.77.37 is IP of upgrade.insightgoldatpmh.com Be sure, that IP150_V1_32_001_ENG_downgrade_from_v4.xx.PuF is in same folder as exe file. TVPfwd will work as proxy server for update process and will change firmware bytes from paradox server with bytes from attached file. All progress will be written to TXT file nearby exe. Finally, InField can show error, but don’t worry about that. Update progress you will see in console window. When packet 448 is reached, IP150 will reboot and you can try to connect to it. IMPORTANT THINGS! That's all for the moment. Later I will post bonus packs :) P.S. Sorry for my bad English :) |
Bonus pack 1. If anybody need any firmware for Paradox devices, you can download it directly from Paradox FTP server. Search for “.paradox.com” string (with dot in front) in InField.exe file and ignore everything who starts with www. You will find domain, and few bytes before this string you will find username and password in plain text. Decrypted firmware files for those, who want play with reversing engineering decrypted firmware.zip. To make life easier, there is cleaned firmware versions (all know for me embedded files are extracted): Maybe someone will find, how to downgrade bootloader from 2.13.001 to 2.12.000. I'm guessing, that bootloader won't downgrade with my method and it causes update process on each IP150 restart. If anybody interested in more detailed firmware file structure or communication protocol with paradox upgrade server, let me know. I will write what i know. |
I forgot to mention, that after downgrade you cannot use InField to upgrade or downgrade to other firmware versions. To do that, you need again use TVPfwd with different firmware version file and reset IP150 module. |
Thank you for sharing! |
Sorry, i'm not a programmer, so source code may look messy :) |
Well done, thanks!
This part is not clear to me. There is no way to 'upgrade' it here - I can hit "Get latest files" but that will download the real fw files from Paradox. |
You can also download lower FW version files from paradox using "Get Latest Files..." button and try downgrade using them. If InFiled will not offer lower FW version files, there is one |
Yes, I'm using the same version 5.0.11. I tried to download and "upgrade" 4.00 using INField however the txt file in TVPfwd directory didn't change so I suppose the upload file didn't go through it? Any idea what I am doing wrong? :) |
Firmware v4.00 is one of Paradox fails :) Let's leave this for tomorrow. I will write more details about this version and maybe will do more tests. |
Excellent, thanks. Hopefully I can also downgrade this little bastard and get it finally include into my home automation system. |
Firmware V4.00: how i know, Paradox somehow failed with this version, because it was quite problematic process to update this version to newer version. when i set V4.00 firmware on my IP150 even using this Paradox instructions i didn't managed how to properly configure my router for upgrade or downgrade procedure. After a lot of retries InField refuses connect to module directly or trough internet and I've give up. Just restarted IP150 module and put other FW file to TVPfwd proxy |
powerwade, try configure your router using Paradox instructions above and upgrade IP150 using lower FW version file. I see, that your boot loader still version 2.12.001 and can be, that it will allow you downgrade directly. Also can be, that you need use older InField versions, because latest InField version can refuse to send lower version FW to IP150 module because of Paradox new business plan with Insite GOLD App. |
Bonus Pack 2 :) One more tool to play with :) I was trying to analyze downgrade/upgrade communication protocol. Recognized bytes are defined as variables. First 4 bytes of packet are command bytes. All other bytes does make any known sense for upgrade process. Upgrade communication protocol for all FW versions is almost same except one thing: with FW bellow v4.00 after firmware bytes sent, InField sends FW verification packet. FW v4.00 and above - doesn't. How i understand, instead of verification packet, v4.xx connects himself and verifies FW validity using secure (SSL) connection to Paradox API server (api.insightgoldatpmh.com) Using this source as sample and log file from TVPfwd, you can write own firmware update server. |
I was surprised, when my module didn't connect to proxy server after power off and on. I did a lot of harmful tests with my IP150, but he always was sniffing for connection to Paradox servers. At least until now... WARNING! WARNING! WARNING! After that, i can't connect to my panel using internet (with panel serial number and password) and it means, i can't start IP150 upgrade process anymore. Also i can't start IP150 upgrade/downgrade process using direct connection. InField connects using direct connection, but shows error on IP150 firmware transfer. I didn't test, does panel firmware update works or not, because my panel is connected to security company and this early morning i don't want any calls from them about my alarm system failure :) For me this is not a big problem. Finally i have always working IP150 with firmware, which allows BabyWare connection and this is everything what i need. This was my final destination and i reached it! :) |
Hi Guys, Please help :( I am trying to downgrade my IP150 from V4.30.000 to V1.32.000.
This is where I got too before I noticed that i cannot connect to the IP150 via InsightGold or IP. |
Today I got few IP modules to play with, so, i have some results to share IP150 (don't remember FW version, but at least 4.00) - downgraded. IMOPORTANT: before downgrade - reset IP150 to factory defaults, to clear custom gateway and DNS server settings (press and hold reset button until IO LED's start blinking, then release and pres reset button again). Check using BabyWare or InField, is DHCP on on IP150 You should change DNS entries for: Check IP address for upgrade.insightgoldatpmh.com and upgr.insightgoldatpmh.com and use one of them in TVPfwd command line (i believe, both IP addresses always should be same) Now upgrade.insightgoldatpmh.com and upgr.insightgoldatpmh.com have IP address 3.95.136.210. It means, TVPfwd command line should be: TVPfwd.exe 192.168.1.5 10000 3.95.136.210 10000 IP150_V1_32_001_ENG.PuF **IMPORTANT: ** with some bootloaders downgrade process can be started by powering on IP150 module while reset button is pressed. Also use this method to update IP150 back to latest firmware (remove DNS entries from your router before update). I saw some interesting DNS queries directly to public DNS servers, like 4.2.2.2, 4.2.2.1, 4.2.2.3, 4.2.2.4, 4.2.2.5, 4.2.2.6, 8.8.8.8 8.8.4.4, 208.67.222.222, 208.67.220.220. It means, that sometimes TVPfwd can be avoided by downgrade process. Block temporary these IP (just idea, not tested yet) or set these IP as your router IP (of course, if you router can have multiple IP. Mikrotik routers - can. Thank you Mikrotik for that! ;) ) |
Hello, |
@hoebanx what is your email? |
|
Hello,
Thanks for your reply.
It is ***@***.***
Have a nice day,
L.
Le dim. 16 mai 2021 à 22:45, nezmogus ***@***.***> a écrit :
… @hoebanx <https://github.com/hoebanx> what is your email?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASNJJECBSSLS45IXM5NEKS3TOAVHHANCNFSM4D5G5BDA>
.
|
Thanks Omri! |
All Your IP150 Are Belong to Us...stack overflow :) nezmogus it seems we need a patch to your older prepared fw |
Can anyone post the IP150_V1_32_001_ENG.PuF file for download ? Seem to have disapeared from the Paradox site... |
BTW, from what i see at home, the DNS queries are for capi.insightgoldatpmh.com |
@nezmogus do you confirm the downgrade didn't actually work ? or did you manage in the end ? |
Currently no success with downgrade from FW v5.* but I still didn't give up. For next few weeks i will have no time for this. Will try later. There is firmware for you: |
WinLoad will not allow you downgrade firmware. WinLoad only initiates upgrade process and then IP150 works directly with paradox servers. |
Ah OK, hence the proxy... Not sure how to rewrite the DNS queries to redirect them to my laptop... |
Thanks for the file ! |
I used Mikrotik router
…On Fri, Jul 9, 2021, 19:52 abeldacosta33450 ***@***.***> wrote:
Ah OK, hence the proxy... Not sure how to rewrite the DNS queries to
redirect them to my laptop...
How did you do this @nezmogus <https://github.com/nezmogus> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJFM4SVLYQPGN2ODBH77F7DTW4SN5ANCNFSM4D5G5BDA>
.
|
OK thanks for the info... I'll try few things and revert with findings. Good weekend ! |
Shit, InField doesn't allo you to pick a PUF file for the IP150 module. Only for the other modules... Didn't notice this in the first place... Need to find a way to hack this thing... |
See, button in Step 3 for "browse" disapeared... |
Hello, everybody! Any help please ? I need the module to be latest version! |
Did you manage to get V5 downgraded? I had a weird anomaly here at home which caused the IP150 module to get on the internet and upgrade to V5.02.045 . I've followed the initial steps as with v4 but no success. I also observed that the module tries to make use of public DNS settings, even when you statically assign 2x local DNS servers. It keeps DNS1 but makes DNS2: 8.8.8.8 (which I blocked on my Mikrotik). pointed the following to my local PC IP: I block the rest of all the public DNS servers tonight and try again. Previously I e-mailed the CEO of Paradox telling him that he and his company is dodgy - forcing all of these upgrades limiting the features of the IP module, I just got some egotistical reply back in the line of "I'm god and my hardware is superior". I replied to him that he is a c*nt. He then got a local distributor to phone me and tell me that I don't know how to operate their hardware and must call a certified alarm company. What BS. |
Hi Everyone, any luck to downgrade the firmware from v5.* ? Thank you. |
================== I'm facing the same problem. I also have troubles updating an “old” IP150 module to the latest firmware version. The IP150 curently has the firmware (4.30) and bootloader(2.12) It seems there is a specific procedure to upgrade the FW for that specific combination of IP150 firmware and bootloader as the Standard procedure fails. I executed the specific prodedure but after several attempts it always return the same error code. Basically the procedure tells the following: ======
Note:
As my router does not have NAT lookback feature, I followed the second option (IP 150 Module in one network and Infield 4.26.6 in another) but it does not work. Just asking if there is someone that knows how to do it. |
Hello everybody, @nezmogus can i help you to achieve this ? Nico |
Hello Tertius,
First of all, thank you for your work and developing this software.
After managing to configure the MQTT server this is what I am getting when trying to connect to my control panel.
The text was updated successfully, but these errors were encountered: