Update alarm_control_panel.egardia.markdown #4282
Conversation
| - **report_server_codes** list (*Optional*): List of codes for the different states. | ||
|
|
||
| Note that this basic configuration will only enable you to read the armed/armed away/disarmed status of your alarm and will **not** update the status if the alarm is triggered. This is because of how Egardia built their system. The alarm triggers normally go through their servers. | ||
| You can change this, however, using the following procedure. This is a more advanced configuration. | ||
|
|
||
| 1. Log in into your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password. | ||
| 2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. Also, update the port number 85 or to anything you like. The provided software that you will set up in the next steps runs on port 85 by default. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'. | ||
| 2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want, because it removes the need to pay for their subscription. Make sure to save your settings by selecting 'OK'. |
There was a problem hiding this comment.
I'm not sure if we should mention the subscription. Maybe we should leave it out to stay neutral?
There was a problem hiding this comment.
it's kind of the whole purpose of the component, but sure, I am fine with leaving it out. I expect people to be able to read between the lines.
|
I removed the mention of the subscription. |
|
Should this not be on the current branch since it is docs for an existing component? I thought the next branch was only for new components and current for updates for docs for existing components.. |
|
Since the PR with the code changes will go in the next release, ie 0.61, this PR should target |
|
@MartinHjelmare then the docs on the HA site are not entirely in line with this. Have a look at the documentation on docs:
To me I was fixing things and expanding existing documentation, hence the current branch. |
|
A fix to the documentation, would be if something is wrong with the documentation and no code has changed. Since you have changed code, you're not fixing the documentation, you're updating it to match the added code. |
Description:
Updating docs reflecting changes in egardia component no longer requiring separate egardiaserver install.
Pull request in home-assistant (if applicable): home-assistant/core#11344
Checklist:
current. New documentation for platforms/components and features should go tonext.