ParadoxAlarmInterface / ParadoxAlarmInterface/pai
problem: PAI - Unable to connect to alarm (after network glitch)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 424
- Forks
- 118
- PR merge metrics
- No merged PRs in 30d
Description
Alarm system
Magellan MG5050
Environment
Linux
Version 3.7.0
IP150
Question
Has anyone got the same issue that sometime the Addon loose connection to the IP150 and can't reconnect ? It seems like the IP150 did not close the socket when the connection dropped.
When this happens, i have the "PAI - Unable to connect to alarm" message in the log and the only way I have yet found to re-establish communication is to stop the addon, open a webbrowser and type in my ip150 device ip adress, then I have the infamous box asking the password to connect. Normally I should have the following with all check boxes apperaing confirming that the connection is established:
But when I have the PAI problem, I have to repeat this process 3-4 times until the check boxes filled, only then I can restart the Addon and coinnection will establish
Would anyone have a way (other than router reboot wich is not possible on this project) to clear what seems to be a pending connection on the IP150 preventing PAI to reconnect ?
Would there be any config in IP150 that i am not aware that could check connection lost and restart the device ?
Thanks for any help
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the dropped-network condition on Linux with PAI 3.7.0, using the Magellan MG5050 and IP150 setup described. Inspect the connection handling for a stale socket and define done as restoring alarm communication without stopping the addon, repeatedly opening the IP150 web page, or rebooting the router.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100