search

ParadoxAlarmInterface / pai

Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others
https://gitter.im/paradox-alarm-interface
Eclipse Public License 2.0
347 stars 92 forks source link

IP150 v4 on mg5050 cannot reconnect after disconnect #87

Closed lhubaut closed 4 years ago

lhubaut commented 5 years ago

Alarm system

MG 5050 with ip150 v4 IP connection with pai

Environment

Git branch

Master and dev

Describe the bug

After a couple of hours running, the library disconnect from the panel (probably due to the paradox service) but is never able to reconnect by itself. I have to monitor mqtt events and eventually restart the docker

To Reproduce

let it run and wait

Logs

problem seems to appear at 2019-07-16 22:31:19,990 paradox.txt

lhubaut commented 5 years ago

Hi, new informations : I had very few disconnection during the past 2 weeks. And I discovered that those disconnection are due to internet issues with my ISP (a couple of minutes). So I have to discuss this issue with my ISP. But, even when internet is restarting, the library cannot reconnect to my panel and is looping indefinitly (here is the log with a grep): 2019-08-05 00:03:49,084 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:04:04,183 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:04:20,282 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:04:41,388 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:05:03,490 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:05:22,594 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:05:42,688 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:06:07,797 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:06:33,904 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:06:57,009 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:07:21,103 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:07:50,205 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:08:20,304 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:08:47,403 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:09:15,509 - ERROR - PAI - Unable to connect to alarm 2019-08-05 00:09:33,955 - ERROR - PAI - Unable to connect to alarm So may be a solution is to exit the script and restart it (with docker or a forever)

yozik04 commented 5 years ago

@jpbarraca Can you decrypt that log and send it to me? Thank you.

jpbarraca commented 5 years ago

Cannot decrypt the log until next week. I'm with very limited internet access and no laptop around :)

yozik04 commented 5 years ago

@lhubaut Then you need to send your log to me. < my nickname >@gmail.com

lhubaut commented 5 years ago

ok, but I will also send you side information that I discovered in private.... seems that the library allow to connect to panel of other people..... seems a serious security lack of paradox

lhubaut commented 5 years ago

@yozik04 Did you get the logs? And understand the strange behaviour?

yozik04 commented 5 years ago

I saw the logs. Paradox does not care if somebody can log in to your panel remotely. I read somewhere that somebody has already reported this to them already. They did not care as it is installation problem that default password was not changed.

yozik04 commented 5 years ago

I have downgraded my IP150 to 1.32 to block all their cloud 💩... I do not trust them. I see some actionable exceptions in your log. Will try to find time to look into it.

yozik04 commented 5 years ago

@lhubaut Please try latest dev branch

lhubaut commented 5 years ago

Hi, @yozik04 thanks I will try and let you know. Do you have a link for downgrading the IP150? Thanks

yozik04 commented 5 years ago

=) Try first and send me exceptions you get during session restart. Then I will give you a link 😈. Let's solve it first =)

lhubaut commented 5 years ago

Still waiting for a restart (seems my FAI is better thos days)...

JacoFourie commented 4 years ago

Hi. I have the same problem. Found Panel MG5050 version 5.33 build 2 Authentication Success. IP Module version 20, firmware: 4.16

I am running the Dev version

I connect via Site ID. It connects and the with start to gives errors and then will say it lost connection and will not reconnect. If I stop the script and start it again it will run for a while and do the same.

2019-09-13 19:14:49,471 - INFO     - PAI.paradox.hardware.panel - Partition: Area 1, Area 2
2019-09-13 19:15:05,575 - INFO     - PAI.paradox.hardware.panel - User: System Master, Master 1, Master 2, User 04, User 05, User 06, User 07, User 08, User 09, User 10, User 11, User 12, User 13, User 14, User 15, User 16, User 17, User 18, User 19, User 20, User 21, User 22, User 23, User 24, User 25, User 26, User 27, User 28, User 29, User 30, User 31, User 32
2019-09-13 19:15:13,158 - INFO     - PAI.paradox.hardware.panel - Bus-Module: Bus Module 01, Bus Module 02, Bus Module 03, Bus Module 04, Bus Module 05, Bus Module 06, Bus Module 07, Bus Module 08, Bus Module 09, Bus Module 10, Bus Module 11, Bus Module 12, Bus Module 13, Bus Module 14, Bus Module 15
2019-09-13 19:15:14,169 - INFO     - PAI.paradox.hardware.panel - Repeater: Repeater 1, Repeater 2
2019-09-13 19:15:18,231 - INFO     - PAI.paradox.hardware.panel - Keypad: Wireless Keyp 1, Wireless Keyp 2, Wireless Keyp 3, Wireless Keyp 4, Wireless Keyp 5, Wireless Keyp 6, Wireless Keyp 7, Wireless Keyp 8
2019-09-13 19:15:18,732 - INFO     - PAI.paradox.hardware.panel - Site: Your Alarm Site
2019-09-13 19:15:20,230 - INFO     - PAI.paradox.hardware.panel - Siren: Wireless Siren 1, Wireless Siren 2, Wireless Siren 3
2019-09-13 19:15:20,231 - INFO     - PAI.paradox.paradox - Connection OK
Exception in callback Paradox._process_status({'_io': <_io.BytesIO ...at 0x7518d3f0>, '_not_used0': None, '_not_used1': None, 'battery': 13.322352941176472, ...})
handle: <Handle Paradox._process_status({'_io': <_io.BytesIO ...at 0x7518d3f0>, '_not_used0': None, '_not_used1': None, 'battery': 13.322352941176472, ...})>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/home/pi/pai-dev/paradox/paradox.py", line 233, in _process_status
    self.update_properties(element_type, element_item_key, element_item_status)
  File "/home/pi/pai-dev/paradox/paradox.py", line 567, in update_properties
    elements[type_key][property_name] = property_value  # Initial value, do not notify
  File "/home/pi/pai-dev/paradox/models/element_type_container.py", line 14, in __getitem__
    return self.store[self.__keytransform__(key)]
KeyError: 16
Exception in callback Paradox._process_status({'_io': <_io.BytesIO ...at 0x75062540>, '_not_used0': None, '_not_used1': None, 'battery': 13.411764705882353, ...})
handle: <Handle Paradox._process_status({'_io': <_io.BytesIO ...at 0x75062540>, '_not_used0': None, '_not_used1': None, 'battery': 13.411764705882353, ...})>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/home/pi/pai-dev/paradox/paradox.py", line 233, in _process_status
    self.update_properties(element_type, element_item_key, element_item_status)
  File "/home/pi/pai-dev/paradox/paradox.py", line 567, in update_properties
    elements[type_key][property_name] = property_value  # Initial value, do not notify
  File "/home/pi/pai-dev/paradox/models/element_type_container.py", line 14, in __getitem__
    return self.store[self.__keytransform__(key)]

I also get these 2 warnings when I startup.

2019-09-13 19:19:03,977 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 48/2, message: Software log on
2019-09-13 19:19:04,268 - INFO     - PAI.paradox.paradox - Panel time synchronized
2019-09-13 19:19:04,268 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel
2019-09-13 19:19:04,497 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 45/6, message: Clock loss restore

After some time it will stop here.

2019-09-13 19:32:14,331 - ERROR    - PAI.paradox.connections.ip_connection - Connection to panel was lost
jpbarraca commented 4 years ago

There are several phases in PAI and a disconnect during the initial enumeration can fail. After the enumeration is complete, PAI should recover.

JacoFourie commented 4 years ago

Hi. Dev does not. It just sits there with no MQTT activity or anything else happening.

This is what I get with the master. It will work fine for a while and then start to go into a loop trying to connect. If I stop it an start it again it will run for a while and do the same again

BabyWare connects and works 100% from my PC so it cant be networking.

pi@Inverter:~/pai $ python3.6 run.py
2019-09-13 20:48:03,029 - INFO     - PAI - Starting Paradox Alarm Interface
2019-09-13 20:48:03,031 - INFO     - PAI - Console Log level set to 20
2019-09-13 20:48:03,032 - INFO     - PAI.paradox.interfaces.interface_manager - Using MQTT Interface
2019-09-13 20:48:03,168 - INFO     - PAI.paradox.interfaces.mqtt_interface - MQTT Broker Connected
2019-09-13 20:48:04,151 - INFO     - PAI - Using IP Connection
2019-09-13 20:48:04,985 - INFO     - PAI - Starting...
2019-09-13 20:48:04,987 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:48:04,988 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:48:04,988 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:48:04,989 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: xxxxxx
2019-09-13 20:48:04,990 - INFO     - PAI.paradox.connections.ip_connection - Getting site info
2019-09-13 20:48:07,293 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: xxxxxxx
2019-09-13 20:48:07,295 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
2019-09-13 20:48:07,703 - INFO     - PAI.paradox.connections.ip_connection - Authentication Success. IP Module version 20, firmware: 4.16, serial: xxxxxxxx
2019-09-13 20:48:08,883 - INFO     - PAI.paradox.connections.ip_connection - Session Established with IP Module
2019-09-13 20:48:08,883 - INFO     - PAI.paradox.paradox - Connecting to panel
2019-09-13 20:48:08,884 - INFO     - PAI.paradox.paradox - Initiating communication
2019-09-13 20:48:09,405 - INFO     - PAI.paradox.paradox - Found Panel MG5050 version 5.33 build 2
2019-09-13 20:48:09,407 - INFO     - PAI.paradox.paradox - Starting communication
2019-09-13 20:48:09,965 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Initializing communication
2019-09-13 20:48:10,482 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success
2019-09-13 20:48:10,676 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 48/2, message: Software log on
2019-09-13 20:48:10,997 - INFO     - PAI.paradox.paradox - Panel time synchronized
2019-09-13 20:48:10,998 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel
2019-09-13 20:48:11,252 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 45/6, message: Clock loss restore
2019-09-13 20:48:16,280 - ERROR    - PAI.paradox.connections.ip_connection - Connection to panel was lost
2019-09-13 20:48:17,115 - ERROR    - PAI.paradox.paradox - Failed to connect: Failed to write data to connection
2019-09-13 20:48:17,116 - ERROR    - PAI - Unable to connect to alarm
2019-09-13 20:48:20,119 - INFO     - PAI - Starting...
2019-09-13 20:48:20,120 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:48:20,122 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:48:20,124 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:48:20,125 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: xxxxxx
2019-09-13 20:48:21,247 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: xxxxx
2019-09-13 20:48:21,248 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
2019-09-13 20:48:21,757 - ERROR    - PAI.paradox.connections.ip_connection - Unable to establish session with IP Module. Timeout. Only one connection at a time is allowed.
2019-09-13 20:48:21,758 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: xxxxxxxx
2019-09-13 20:48:22,927 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: xxxxxxxxx
2019-09-13 20:48:22,928 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
2019-09-13 20:48:22,947 - ERROR    - PAI.paradox.connections.ip_connection - Connection to panel was lost
2019-09-13 20:48:23,448 - ERROR    - PAI.paradox.connections.ip_connection - Unable to establish session with IP Module. Timeout. Only one connection at a time is allowed.
2019-09-13 20:48:23,448 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: xxxxxxxxx
2019-09-13 20:48:24,646 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: xxxxxxxxx
2019-09-13 20:48:24,646 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
2019-09-13 20:48:24,659 - ERROR    - PAI.paradox.connections.ip_connection - Connection to panel was lost
2019-09-13 20:48:25,043 - INFO     - PAI.paradox.connections.ip_connection - Authentication Success. IP Module version 20, firmware: 4.16, serial: 71066a16
2019-09-13 20:48:26,248 - INFO     - PAI.paradox.connections.ip_connection - Session Established with IP Module
2019-09-13 20:48:26,249 - INFO     - PAI.paradox.paradox - Connecting to panel
2019-09-13 20:48:26,250 - INFO     - PAI.paradox.paradox - Initiating communication
2019-09-13 20:48:26,796 - INFO     - PAI.paradox.paradox - Found Panel MG5050 version 5.33 build 2
2019-09-13 20:48:26,798 - INFO     - PAI.paradox.paradox - Starting communication
2019-09-13 20:48:27,313 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Initializing communication
2019-09-13 20:48:27,838 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success
2019-09-13 20:48:28,400 - INFO     - PAI.paradox.paradox - Panel time synchronized
2019-09-13 20:48:28,401 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel
2019-09-13 20:48:28,573 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 45/6, message: Clock loss restore
2019-09-13 20:48:42,118 - ERROR    - PAI.paradox.hardware.spectra_magellan.panel - ChecksumError wrong checksum, read b'05', computed b'ca', message: b'0001b05a6f6e652032372020202020202020205a6f6e652032382020202020202020208e05'
2019-09-13 20:48:45,691 - INFO     - PAI.paradox.hardware.panel - Zone: DOORS, OFFICE DOOR, GEUST ROOM, DINING DOOR, PANIC, STUDIO, KITCHEN BEAM, DINING BEAM, TV ROOM, OFFICE, BEDROOMS, GARAGE, MAINBED BEAM, LAPA, AMONE ROOM, Zone 16, Zone 17, Zone 18, Zone 19, Zone 20, Zone 21, Zone 22, Zone 23, Zone 24, Zone 25, Zone 26, Zone 27, Zone 28, Zone 29, Zone 30, Zone 31, Zone 32
2019-09-13 20:48:53,755 - INFO     - PAI.paradox.hardware.panel - Pgm: Panic Radio, Burglary Radio, Status LED, Open/Close Radio, Output 05, Output 06, Output 07, Output 08, Output 09, Output 10, Output 11, Output 12, Output 13, Output 14, Output 15, Output 16
2019-09-13 20:48:54,780 - INFO     - PAI.paradox.hardware.panel - Partition: Area 1, Area 2
2019-09-13 20:49:11,078 - INFO     - PAI.paradox.hardware.panel - User: System Master, Master 1, Master 2, User 04, User 05, User 06, User 07, User 08, User 09, User 10, User 11, User 12, User 13, User 14, User 15, User 16, User 17, User 18, User 19, User 20, User 21, User 22, User 23, User 24, User 25, User 26, User 27, User 28, User 29, User 30, User 31, User 32
2019-09-13 20:49:18,737 - INFO     - PAI.paradox.hardware.panel - Bus-Module: Bus Module 01, Bus Module 02, Bus Module 03, Bus Module 04, Bus Module 05, Bus Module 06, Bus Module 07, Bus Module 08, Bus Module 09, Bus Module 10, Bus Module 11, Bus Module 12, Bus Module 13, Bus Module 14, Bus Module 15
2019-09-13 20:49:19,741 - INFO     - PAI.paradox.hardware.panel - Repeater: Repeater 1, Repeater 2
2019-09-13 20:49:23,768 - INFO     - PAI.paradox.hardware.panel - Keypad: Wireless Keyp 1, Wireless Keyp 2, Wireless Keyp 3, Wireless Keyp 4, Wireless Keyp 5, Wireless Keyp 6, Wireless Keyp 7, Wireless Keyp 8
2019-09-13 20:49:24,284 - INFO     - PAI.paradox.hardware.panel - Site: Your Alarm Site
2019-09-13 20:49:25,864 - INFO     - PAI.paradox.hardware.panel - Siren: Wireless Siren 1, Wireless Siren 2, Wireless Siren 3
2019-09-13 20:49:25,866 - INFO     - PAI.paradox.paradox - Connection OK
2019-09-13 20:53:21,821 - ERROR    - PAI.paradox.lib.async_message_manager - No handler for message 5
Detail: Container:
    fields = Container:
        data = b'R\x00\x80\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
        value = Container:
            po = Container:
                command = 5
                status = Container:
                    reserved = False
                    alarm_reporting_pending = False
                    Winload_connected = True
                    NeWare_connected = False
            validation = 128
            address = 5
            data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
        offset1 = 0
        offset2 = 36
        length = 36
    checksum = b'\xd7' (total 1)
2019-09-13 20:57:16,319 - ERROR    - PAI.paradox.connections.ip_connection - Connection to panel was lost
2019-09-13 20:57:17,044 - ERROR    - PAI - Connection to panel lost: Failed to write data to connection. Restarting
2019-09-13 20:57:17,045 - INFO     - PAI - Starting...
2019-09-13 20:57:17,046 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:57:17,047 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:57:17,047 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:57:17,048 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:17,793 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:17,794 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:18,540 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:18,541 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:19,284 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:19,285 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
2019-09-13 20:57:19,286 - ERROR    - PAI - Unable to connect to alarm
2019-09-13 20:57:19,287 - INFO     - PAI - Starting...
2019-09-13 20:57:19,288 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:57:19,289 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:57:19,290 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:57:19,290 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:20,037 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:20,038 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:20,782 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:20,782 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:21,526 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:21,527 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
2019-09-13 20:57:21,528 - ERROR    - PAI - Unable to connect to alarm
2019-09-13 20:57:22,530 - INFO     - PAI - Starting...
2019-09-13 20:57:22,533 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:57:22,534 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:57:22,535 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:57:22,536 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:23,279 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:23,280 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:24,016 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:24,017 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:24,756 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:24,757 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
2019-09-13 20:57:24,759 - ERROR    - PAI - Unable to connect to alarm
2019-09-13 20:57:30,764 - INFO     - PAI - Starting...
2019-09-13 20:57:30,765 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
2019-09-13 20:57:30,765 - INFO     - PAI.paradox.paradox - Clean Session
2019-09-13 20:57:30,765 - INFO     - PAI.paradox.paradox - Connecting to interface
2019-09-13 20:57:30,766 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:31,509 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:31,510 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:32,256 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:32,256 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: Fourie Smart House
2019-09-13 20:57:32,998 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-13 20:57:32,999 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
2019-09-13 20:57:33,000 - ERROR    - PAI - Unable to connect to alarm
yozik04 commented 4 years ago

"dev" is currently work in progress. So it may not work. Use master. Strange. It connected first time, then failed to load labels...

JacoFourie commented 4 years ago

As stated I tried both. Dev just gets stuck and master goes into a reconnection loop. Do you have a protocol doc for the Paradox system? I am also a developer and can have a look to see why it does this.

jpbarraca commented 4 years ago

AFAIK there is no public documentation about this process. I recommend you use wireshark and analyse what is happening.

langabi commented 4 years ago

+1 on this for me -- MG5050 panel, IP150 v4. I reset my home internet router, and had exactly the same issue as far as I can see. I can post logs, but they're essentially the same as the above. Thus, issue is not unique to JacoFourie. No further insight, sorry.

jpbarraca commented 4 years ago

Can you capture the packets transmitted using wireshark? This may allow us to diagnose the issue.

papaiatis commented 4 years ago

Same issue here. After a while the software stops working, disconnects from the panel and never able to recover. If I restart the software it successfully connects again.

Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,148 - INFO     - PAI.paradox.paradox - Clean Session
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,148 - INFO     - PAI.paradox.paradox - Connecting to interface
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,148 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,403 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,403 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,648 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,649 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,892 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,892 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
Sep 18 20:37:10 raspberrypi pai-paradox[8405]: 2019-09-18 20:37:10,893 - ERROR    - PAI - Unable to connect to alarm

After I restart the software, the log shows this:

Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,015 - INFO     - PAI.paradox.paradox - Clean Session
Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,015 - INFO     - PAI.paradox.paradox - Connecting to interface
Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,015 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,016 - INFO     - PAI.paradox.connections.ip_connection - Getting site info
Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,760 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: MyPanel
Sep 18 20:43:42 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:42,761 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
Sep 18 20:43:43 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:43,293 - INFO     - PAI.paradox.connections.ip_connection - Authentication Success. IP Module version 20, firmware: 4.64, serial: 71070b37
Sep 18 20:43:43 raspberrypi pai-paradox[21829]: 2019-09-18 20:43:43,776 - INFO     - PAI.paradox.connections.ip_connection - Session Established with IP Module

Panel: sp7000 v6.16 IP Module: IP150 v4.64

jpbarraca commented 4 years ago

Can you provide a packet capture made with wireshark? https://www.wireshark.org/

papaiatis commented 4 years ago

Yes, I can. Any suggestion or example on capture filters? I have tshark installed, no wireshark available (no GUI).

papaiatis commented 4 years ago

I believe this is the main part below. Captured all traffic on the host.

 1050 27.898961894 192.168.1.99 → 192.168.1.1  DNS 84 Standard query 0xc995 A turn.paradoxmyhome.com
 1051 27.899985278  192.168.1.1 → 192.168.1.99 DNS 100 Standard query response 0xc995 A turn.paradoxmyhome.com A 35.156.86.205
 1052 27.900351163 192.168.1.99 → 35.156.86.205 TCP 76 45981 → 3478 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1839355838 TSecr=0 WS=128
 1053 27.946375895 35.156.86.205 → 192.168.1.99 TCP 76 3478 → 45981 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1452 SACK_PERM=1 TSval=3477397044 TSecr=1839355838 WS=512
 1054 27.946575166 192.168.1.99 → 35.156.86.205 TCP 68 45981 → 3478 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1839355884 TSecr=3477397044
 1055 27.947249436 192.168.1.99 → 35.156.86.205 TCP 68 40399 → 3478 [FIN, ACK] Seq=1 Ack=1 Win=229 Len=0 TSval=1839355885 TSecr=3477389524
 1056 27.947482925 192.168.1.99 → 35.156.86.205 STUN 112 Allocate Request TCP lifetime: 600
 1057 27.990329588 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 45981 [ACK] Seq=1 Ack=45 Win=27136 Len=0 TSval=3477397056 TSecr=1839355885
 1058 27.990494223 35.156.86.205 → 192.168.1.99 STUN 164 Allocate Success Response XOR-RELAYED-ADDRESS: 35.156.86.205:42843 XOR-MAPPED-ADDRESS: 78.92.10.208:45981 lifetime: 600
 1059 27.990553807 192.168.1.99 → 35.156.86.205 TCP 68 45981 → 3478 [ACK] Seq=45 Ack=97 Win=29312 Len=0 TSval=1839355928 TSecr=3477397056
 1060 27.991308545 192.168.1.99 → 35.156.86.205 STUN 88 Binding Request
 1061 28.003013218 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 40399 [RST, ACK] Seq=1 Ack=2 Win=53 Len=0 TSval=3477397059 TSecr=1839355885
 1062 28.033546876 35.156.86.205 → 192.168.1.99 STUN 160 Binding Success Response XOR-MAPPED-ADDRESS: 78.92.10.208:45981 MAPPED-ADDRESS: 78.92.10.208:45981 RESPONSE-ORIGIN: 10.2.43.12:3478
 1063 28.034312292 192.168.1.99 → 35.156.86.205 STUN 100 Connect Request XOR-PEER-ADDRESS: 18.184.231.237:25801
 1065 28.077850830 35.156.86.205 → 192.168.1.99 STUN 128 Connect Error Response error-code: 447 (Connection Timeout or Failure) Connection Timeout or Failure
 1066 28.081376346 192.168.1.99 → 192.168.1.1  DNS 84 Standard query 0x5cdc A turn.paradoxmyhome.com
 1067 28.082401032  192.168.1.1 → 192.168.1.99 DNS 100 Standard query response 0x5cdc A turn.paradoxmyhome.com A 35.156.86.205
 1068 28.083595666 192.168.1.99 → 35.156.86.205 TCP 76 45605 → 3478 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1839356021 TSecr=0 WS=128
 1070 28.125170456 192.168.1.99 → 35.156.86.205 TCP 68 45981 → 3478 [ACK] Seq=97 Ack=249 Win=29312 Len=0 TSval=1839356063 TSecr=3477397078
 1071 28.138089293 35.156.86.205 → 192.168.1.99 TCP 76 3478 → 45605 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1452 SACK_PERM=1 TSval=3477397093 TSecr=1839356021 WS=512
 1072 28.138197470 192.168.1.99 → 35.156.86.205 TCP 68 45605 → 3478 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1839356076 TSecr=3477397093
 1073 28.138817730 192.168.1.99 → 35.156.86.205 TCP 68 45981 → 3478 [FIN, ACK] Seq=97 Ack=249 Win=29312 Len=0 TSval=1839356077 TSecr=3477397078
 1074 28.139056323 192.168.1.99 → 35.156.86.205 STUN 112 Allocate Request TCP lifetime: 600
 1075 28.186515898 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 45981 [RST, ACK] Seq=249 Ack=98 Win=27136 Len=0 TSval=3477397104 TSecr=1839356077
 1076 28.192998754 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 45605 [ACK] Seq=1 Ack=45 Win=27136 Len=0 TSval=3477397107 TSecr=1839356077
 1077 28.193228493 35.156.86.205 → 192.168.1.99 STUN 164 Allocate Success Response XOR-RELAYED-ADDRESS: 35.156.86.205:57709 XOR-MAPPED-ADDRESS: 78.92.10.208:45605 lifetime: 600
 1078 28.193289379 192.168.1.99 → 35.156.86.205 TCP 68 45605 → 3478 [ACK] Seq=45 Ack=97 Win=29312 Len=0 TSval=1839356131 TSecr=3477397107
 1079 28.194100732 192.168.1.99 → 35.156.86.205 STUN 88 Binding Request
 1090 28.247506444 35.156.86.205 → 192.168.1.99 STUN 160 Binding Success Response XOR-MAPPED-ADDRESS: 78.92.10.208:45605 MAPPED-ADDRESS: 78.92.10.208:45605 RESPONSE-ORIGIN: 10.2.43.12:3478
 1091 28.248311443 192.168.1.99 → 35.156.86.205 STUN 100 Connect Request XOR-PEER-ADDRESS: 18.184.231.237:25801
 1092 28.306402358 35.156.86.205 → 192.168.1.99 STUN 128 Connect Error Response error-code: 447 (Connection Timeout or Failure) Connection Timeout or Failure
 1093 28.309756520 192.168.1.99 → 192.168.1.1  DNS 84 Standard query 0x8058 A turn.paradoxmyhome.com
 1094 28.310800164  192.168.1.1 → 192.168.1.99 DNS 100 Standard query response 0x8058 A turn.paradoxmyhome.com A 35.156.86.205
 1095 28.312351100 192.168.1.99 → 35.156.86.205 TCP 76 37869 → 3478 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1839356250 TSecr=0 WS=128
 1096 28.355182972 192.168.1.99 → 35.156.86.205 TCP 68 45605 → 3478 [ACK] Seq=97 Ack=249 Win=29312 Len=0 TSval=1839356293 TSecr=3477397134
 1097 28.356810626 35.156.86.205 → 192.168.1.99 TCP 76 3478 → 37869 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1452 SACK_PERM=1 TSval=3477397148 TSecr=1839356250 WS=512
 1098 28.356954376 192.168.1.99 → 35.156.86.205 TCP 68 37869 → 3478 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1839356295 TSecr=3477397148
 1099 28.357583073 192.168.1.99 → 35.156.86.205 TCP 68 45605 → 3478 [FIN, ACK] Seq=97 Ack=249 Win=29312 Len=0 TSval=1839356295 TSecr=3477397134
 1100 28.357823385 192.168.1.99 → 35.156.86.205 STUN 112 Allocate Request TCP lifetime: 600
 1101 28.403405045 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 37869 [ACK] Seq=1 Ack=45 Win=27136 Len=0 TSval=3477397159 TSecr=1839356296
 1102 28.403540461 35.156.86.205 → 192.168.1.99 STUN 164 Allocate Success Response XOR-RELAYED-ADDRESS: 35.156.86.205:34063 XOR-MAPPED-ADDRESS: 78.92.10.208:37869 lifetime: 600
 1103 28.403597805 192.168.1.99 → 35.156.86.205 TCP 68 37869 → 3478 [ACK] Seq=45 Ack=97 Win=29312 Len=0 TSval=1839356341 TSecr=3477397159
 1104 28.404350565 192.168.1.99 → 35.156.86.205 STUN 88 Binding Request
 1105 28.411341441 35.156.86.205 → 192.168.1.99 TCP 68 3478 → 45605 [RST, ACK] Seq=249 Ack=98 Win=27136 Len=0 TSval=3477397161 TSecr=1839356295
 1106 28.449533631 35.156.86.205 → 192.168.1.99 STUN 160 Binding Success Response XOR-MAPPED-ADDRESS: 78.92.10.208:37869 MAPPED-ADDRESS: 78.92.10.208:37869 RESPONSE-ORIGIN: 10.2.43.12:3478
 1107 28.450121131 192.168.1.99 → 35.156.86.205 STUN 100 Connect Request XOR-PEER-ADDRESS: 18.184.231.237:25801
 1108 28.495619666 35.156.86.205 → 192.168.1.99 STUN 128 Connect Error Response error-code: 447 (Connection Timeout or Failure) Connection Timeout or Failure
 1109 28.545200279 192.168.1.99 → 35.156.86.205 TCP 68 37869 → 3478 [ACK] Seq=97 Ack=249 Win=29312 Len=0 TSval=1839356483 TSecr=3477397182

Guess what happened after this. I executed another packet capture but this time I tried to use the command tshark -ni any "host 35.156.86.205", to get rid of the garbage. I did not get any output but the software somehow recovered and was able to connect to the module! And this was the log for this event:

Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,292 - INFO     - PAI - Starting...
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,293 - INFO     - PAI.paradox.paradox - Disconnecting from the Alarm Panel
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,294 - INFO     - PAI.paradox.paradox - Clean Session
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,294 - INFO     - PAI.paradox.paradox - Connecting to interface
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,295 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,621 - INFO     - PAI.paradox.connections.ip_connection - Connected to Site: MyPanel
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,622 - INFO     - PAI.paradox.connections.ip_connection - Authenticating with IP Module
Sep 26 13:54:05 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:05,740 - INFO     - PAI.paradox.connections.ip_connection - Authentication Success. IP Module version 20, firmware: 4.48, serial: 71084edb
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,009 - INFO     - PAI.paradox.connections.ip_connection - Session Established with IP Module
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,009 - INFO     - PAI.paradox.paradox - Connecting to panel
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,010 - INFO     - PAI.paradox.paradox - Initiating communication
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,205 - INFO     - PAI.paradox.paradox - Found Panel SP6000 version 6.144 build 10
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,206 - INFO     - PAI.paradox.paradox - Starting communication
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,395 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Initializing communication
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,628 - INFO     - PAI.paradox.hardware.spectra_magellan.panel - Authentication Success
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: Task exception was never retrieved
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: future: <Task finished coro=<Paradox.receive_worker() done, defined at /opt/pai/paradox/paradox.py:251> exception=AttributeError("'NoneType' object has no attribute 'read_message'")>
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: Traceback (most recent call last):
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:   File "/opt/pai/paradox/paradox.py", line 257, in receive_worker
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:     await self.receive()
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:   File "/opt/pai/paradox/paradox.py", line 273, in receive
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:     data = await data
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:   File "/opt/pai/paradox/connections/ip_connection.py", line 324, in read
Sep 26 13:54:06 raspberrypi pai-paradox[17522]:     result = await self.connection.read_message(timeout=timeout)
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: AttributeError: 'NoneType' object has no attribute 'read_message'
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,766 - WARNING  - PAI.paradox.paradox - Missing element ID in system/?, m/m: 48/2, message: Software log on
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,884 - INFO     - PAI.paradox.paradox - Panel time synchronized
Sep 26 13:54:06 raspberrypi pai-paradox[17522]: 2019-09-26 13:54:06,885 - INFO     - PAI.paradox.hardware.panel - Updating Labels from Panel

I'm not sure how or why tshark influenced in the communication between the software and turn.paradoxmyhome.com

jpbarraca commented 4 years ago

Try the latest dev branch as it is substantially different from the main.

jpbarraca commented 4 years ago

Now the IP Connection fully disconnects after the panel stops responding to status updates. It must be tested as I do not have an IP150 panel.

papaiatis commented 4 years ago

Thanks! Let me test it. It can take a couple of days though to make sure it works stable now.

papaiatis commented 4 years ago

Software stuck after 2 days and unfortunately the logs got rotated too so I have no idea what was the last log lines. I set up logging to file now, so next time I'll have more information.

jpbarraca commented 4 years ago

Great. I'm doing the same test using a serial connection

yozik04 commented 4 years ago

I have committed some more fixes to dev. Please try.

papaiatis commented 4 years ago

Software stuck again 2 days ago, and these are the last log lines:

2019-09-30 14:50:19,425 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
2019-09-30 14:50:19,627 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-30 14:50:19,628 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
2019-09-30 14:50:19,843 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-30 14:50:19,845 - INFO     - PAI.paradox.connections.ip_connection - Connecting to Site: MyPanel
2019-09-30 14:50:20,042 - ERROR    - PAI.paradox.connections.ip_connection - {'class': b'\x00\x00\x04', 'code': 47, 'reason': b'Connection Timeout or Failure\x00\x00\x00'}
2019-09-30 14:50:20,043 - ERROR    - PAI.paradox.paradox - Failed to connect to interface
2019-09-30 14:50:20,045 - ERROR    - PAI - Unable to connect to alarm
2019-09-30 14:50:24,050 - INFO     - PAI - Starting...

Now I'm doing git pull and will check the latest fixes by @yozik04

papaiatis commented 4 years ago

@yozik04 Ups, there's an exception that wasn't here before:

2019-10-02 21:51:29,628 - ERROR    - PAI.paradox.paradox - Loop
Traceback (most recent call last):
  File "/opt/pai/paradox/paradox.py", line 194, in async_loop
    result = await asyncio.gather(*[self._status_request(i) for i in cfg.STATUS_REQUESTS])
  File "/opt/pai/paradox/paradox.py", line 227, in _status_request
    return self.panel.handle_status(reply)
  File "/opt/pai/paradox/hardware/spectra_magellan/panel.py", line 165, in handle_status
    if time.time() - self.core.last_power_update >= cfg.POWER_UPDATE_INTERVAL:
AttributeError: 'Paradox' object has no attribute 'last_power_update'
yozik04 commented 4 years ago

Checking.

yozik04 commented 4 years ago

Should be fixed.

papaiatis commented 4 years ago

@yozik04 awesomely quick fix! So far so good now. Last log says Connection OK. Let's wait.

jpbarraca commented 4 years ago

It would be great if you could leave a tcpdump with a ring-buffer. The issue may be at the network level

yozik04 commented 4 years ago

It should detect disconnection and reconnect. I fixed some stuff there.

britsmarius commented 4 years ago

Hi, @yozik04 thanks I will try and let you know. Do you have a link for downgrading the IP150? Thanks

I have downgraded my IP150 to 1.32 to block all their cloud 💩... I do not trust them. I see some actionable exceptions in your log. Will try to find time to look into it.

Hi Yozik04

Please share how to downgrade to 1.32 my home automation has stopped working with the Paradox alarm because they upgraded the IP150 moving to Insight, I no longer want to be part of this cloud solution and want my system working again. I have tried PAI but with no luck and I believe it is due to MG5050 still running 4.92.

Please help to downgrade

yozik04 commented 4 years ago

Downgrade process is described here: https://github.com/Tertiush/ParadoxIP150v2/issues/22

jpbarraca commented 4 years ago

As an alternative you can also connect directly through the serial port, bypassing the IP150

britsmarius commented 4 years ago

thank you one problem

were can I find this file IP150_V1_32_001_ENG_downgrade_from_v4.xx.PuF

On Fri, Oct 4, 2019 at 1:04 PM Jevgeni Kiski notifications@github.com wrote:

Downgrade process is described here: Tertiush/ParadoxIP150v2#22 https://github.com/Tertiush/ParadoxIP150v2/issues/22

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ParadoxAlarmInterface/pai/issues/87?email_source=notifications&email_token=ANMOEMQ4Q3VDCO4SELDLLJTQM4PMBA5CNFSM4IENIJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALJZUI#issuecomment-538352849, or mute the thread https://github.com/notifications/unsubscribe-auth/ANMOEMWLVBL62F6ZS2HZYKDQM4PMBANCNFSM4IENIJMQ .

yozik04 commented 4 years ago

It is there in the same thread.

yozik04 commented 4 years ago

Did you tried to login with BabyWare with local IP? In latest IP150 there seems that this option is enabled again. No?

britsmarius commented 4 years ago

Are you revering to the swan on or off option I see my IP 150 is now on Firmware version 4.42.02

On Fri, Oct 4, 2019 at 1:23 PM Jevgeni Kiski notifications@github.com wrote:

Did you tried to login with BabyWare with local IP? In latest IP150 there seems that this option is enabled again. No?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ParadoxAlarmInterface/pai/issues/87?email_source=notifications&email_token=ANMOEMUMHBZGMSFFCXCWHNDQM4RS3A5CNFSM4IENIJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALLBVA#issuecomment-538357972, or mute the thread https://github.com/notifications/unsubscribe-auth/ANMOEMS3252LOCWBKTIU2MLQM4RS3ANCNFSM4IENIJMQ .

yozik04 commented 4 years ago

if you have an option to turn off swan, turn it off and try with babyware using IP/Static

britsmarius commented 4 years ago

When I log in to IP150 there Is no option to turn off swan

On Fri, 04 Oct 2019 at 13:55, Jevgeni Kiski notifications@github.com wrote:

if you have an option to turn off swan, turn it off and try with babyware using IP/Static

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ParadoxAlarmInterface/pai/issues/87?email_source=notifications&email_token=ANMOEMWZJFMIXS3F4JX2OGDQM4VJ5A5CNFSM4IENIJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALNDRA#issuecomment-538366404, or mute the thread https://github.com/notifications/unsubscribe-auth/ANMOEMSNDMFILYQRBLV4QYTQM4VJ5ANCNFSM4IENIJMQ .

yozik04 commented 4 years ago

Yes, according to changelog they have removed the option in 4.40.011

yozik04 commented 4 years ago

But still try Babyware.

britsmarius commented 4 years ago

So I will need to downgrade yes ?

On Fri, 04 Oct 2019 at 14:03, Jevgeni Kiski notifications@github.com wrote:

Yes, according to changelog they have removed the option in 4.40.011

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ParadoxAlarmInterface/pai/issues/87?email_source=notifications&email_token=ANMOEMRJD35HS6ZSI2DBGE3QM4WJPA5CNFSM4IENIJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALNWRY#issuecomment-538368839, or mute the thread https://github.com/notifications/unsubscribe-auth/ANMOEMUVWEGK752CQ6QMAF3QM4WJPANCNFSM4IENIJMQ .

yozik04 commented 4 years ago

Try first. Then if it won't connect you can try to downgrade. But if it will work let us know...