jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-21 08:16:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Recommendations on lost connection detection (#8441)

Browse Source 
* Recommendations on lost connection detection

After implementing the second option to detect lost connection I almost immediately ran into the issue that due to a network issue the connection between HASS and CCU was lost but HASS did not detect it.
Since Home Automation gas to be as reliable as possible I rephrased the introduction to the second option to address this problem and make anyone aware or this problem.

* Optimizing rephrasing
This commit is contained in:
CV 2019-02-10 22:38:23 +01:00 committed by Fabian Affolter
parent 11b8101b81
commit b2b0d8d0ee
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_components/homematic.markdown
View File

@ -406,7 +406,7 @@ When the connection to your HomeMatic CCU or Homegear is lost, Home Assistant wi
service: homematic.reconnect
```
- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot), this is a pretty reliable way to detect situations where you need to call *homematic.reconnect*. This is how this can be done:
- If you have a CCU you can also create a system variable on the CCU, which stores its last reboot time. Since Home Assistant can still refresh system variables from the CCU (even after a reboot) this is another option to call *homematic.reconnect*. Even though this option might look preferrable to many since it does not rely on a sensor, **it is less fail-safe** than checking for updates of a sensor. Since the variable on the CCU is only changed on boot, any problem that causes the connection between Home Assistant and the CCU to break but will not result in a reboot will not be detected (eg. in case of networking issues). This is how this can be done:
1. Create a string variable **V_Last_Reboot** on the CCU
@ -541,4 +541,4 @@ alert:
```
{% endraw %}
Please note that the first `data` element belongs to the service `my_hm`, while the second one belongs to the event payload.
Please note that the first `data` element belongs to the service `my_hm`, while the second one belongs to the event payload.