{"id":200,"date":"2019-11-09T13:48:28","date_gmt":"2019-11-09T13:48:28","guid":{"rendered":"http:\/\/www.beer.org\/blog\/?p=200"},"modified":"2019-11-09T13:48:28","modified_gmt":"2019-11-09T13:48:28","slug":"homeassistant-internet-monitor-and-reset","status":"publish","type":"post","link":"https:\/\/www.beer.org\/blog\/index.php\/2019\/11\/09\/homeassistant-internet-monitor-and-reset\/","title":{"rendered":"Homeassistant Internet monitor and reset"},"content":{"rendered":"\r\n<p>The Xplornet modem out at DR has decided to become unreliable and needs a sporadic restart. I&#8217;ve been pleased with how well the <a href=\"https:\/\/www.amazon.ca\/TP-Link-Required-Anywhere-Occupies-Fixtures\/dp\/B072T4NYL9\">TP-Link Kasa HS105<\/a> Wifi switches perform so I just needed to figure out how to get HomeAssistant to reliably monitor the internet connection and reset it without inducing an infinite power-cycle loop. This is what I ended up with. Seems to work ok.<\/p>\r\n<p>&nbsp;<\/p>\r\n<p>In configuration.yaml:<\/p>\r\n\r\n\r\n\r\n<pre>device_tracker:<br \/>  platform: ping<br \/>   hosts:<br \/>     google: 8.8.8.8<br \/>     beer: 67.205.176.146<\/pre>\r\n\r\n\r\n\r\n<p>In automations.yaml:<\/p>\r\n\r\n\r\n\r\n<pre>- id: Ensure Internet is on<br \/>    alias: Ensure Internet is on<br \/>    initial_state: on<br \/>    trigger:<br \/>      platform: state<br \/>      entity_id: switch.internet<br \/>      to: 'off'<br \/>      for:<br \/>        minutes: 1<br \/>  action:<br \/>    service: homeassistant.turn_on<br \/>    entity_id: switch.internet<br \/><br \/>id: Ensure Internet is on at HA startup<br \/>  alias: Ensure Internet is on at HA startup<br \/>  initial_state: on<br \/>  trigger:<br \/>    platform: homeassistant<br \/>    event: start<br \/>  action:<br \/>    service: homeassistant.turn_on<br \/>    entity_id: switch.internet<br \/><br \/>id: Restart internet connection<br \/>  alias: Restart internet connection<br \/>  initial_state: on <br \/>  trigger: <br \/>    - platform: state<br \/>      entity_id: device_tracker.google<br \/>      to: 'not_home'<br \/>    - platform: state<br \/>      entity_id: device_tracker.beer<br \/>      to: 'not_home'<br \/>  condition:<br \/>    condition: and<br \/>    conditions:<br \/>    - condition: state<br \/>      entity_id: device_tracker.google<br \/>      state: 'not_home'<br \/>    - condition: state<br \/>      entity_id: device_tracker.beer<br \/>      state: 'not_home'<br \/>  action:<br \/>    service: homeassistant.turn_off<br \/>    entity_id: switch.internet<\/pre>\r\n","protected":false},"excerpt":{"rendered":"<p>The Xplornet modem out at DR has decided to become unreliable and needs a sporadic restart. I&#8217;ve been pleased with how well the TP-Link Kasa HS105 Wifi switches perform so I just needed to figure out how to get HomeAssistant to reliably monitor the internet connection and reset it without inducing an infinite power-cycle loop&#8230;. <a class=\"moretag\" href=\"https:\/\/www.beer.org\/blog\/index.php\/2019\/11\/09\/homeassistant-internet-monitor-and-reset\/\">Continue reading &raquo;<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-200","post","type-post","status-publish","format-standard","hentry","category-tech-stuff"],"_links":{"self":[{"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=200"}],"version-history":[{"count":3,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/200\/revisions"}],"predecessor-version":[{"id":203,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/200\/revisions\/203"}],"wp:attachment":[{"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.beer.org\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}