From 85935c44ef1996b92cfee09ec1958e47d94d7f59 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 14 Apr 2020 09:51:58 +0200 Subject: [PATCH 1/2] Update links and structure --- source/_integrations/tomato.markdown | 28 +++++++++++++++++----------- 1 file changed, 17 insertions(+), 11 deletions(-) diff --git a/source/_integrations/tomato.markdown b/source/_integrations/tomato.markdown index 9cbaabdc8165..d3c8f459dbc9 100644 --- a/source/_integrations/tomato.markdown +++ b/source/_integrations/tomato.markdown @@ -7,13 +7,22 @@ ha_release: pre 0.7 ha_domain: tomato --- -The `tomato` platform requires an extra configuration variable called `http_id`. The +The `tomato` device tracker integration allows one to tracker devices which are +conencted to a wireless router that is running [Tomato](https://tomato.groov.pl/) +as firmware. + +Because of a limitation in Tomato's API, this integration will only track wireless devices. + +It could be that the integration is also working with [AdvancedTomato](https://advancedtomato.com/) +but this was never tested. + +## Setup + +The integration requires an extra configuration variable called `http_id`. The value can be obtained by logging in to the Tomato admin interface and search for -`http_id` in the page source code. +`http_id` in the page's source code. -Because of a limitation in Tomato's API, this platform will only track wireless devices. -If tracking wired devices like a Philips Hue Hub is necessary, -it is possible to use another platform like [Nmap](/integrations/nmap_tracker). +## Configuration To use this device tracker in your installation, add the following to your `configuration.yaml` file: @@ -57,7 +66,7 @@ password: required: true type: string http_id: - description: "The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code." + description: "The value of `http_id`." required: true type: string {% endconfiguration %} @@ -65,14 +74,11 @@ http_id: See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked. -A description of the API s available in this -[Tomato API](https://paulusschoutsen.nl/blog/2013/10/tomato-api-documentation/) -blog post. - -SSL Certificate: +## SSL Certificate Gathering the SSL Certificate of your router can be accomplished with this (or a similar) command: + ```bash openssl s_client -showcerts -connect 172.10.10.1:443 /dev/null | openssl x509 -outform PEM > router_cert.pem ``` From ae335d7e74d4e801d8c72d9fd9db1a5a8bccd2be Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 14 Apr 2020 10:04:57 +0200 Subject: [PATCH 2/2] Update source/_integrations/tomato.markdown --- source/_integrations/tomato.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/tomato.markdown b/source/_integrations/tomato.markdown index d3c8f459dbc9..4927bfa9a60c 100644 --- a/source/_integrations/tomato.markdown +++ b/source/_integrations/tomato.markdown @@ -8,7 +8,7 @@ ha_domain: tomato --- The `tomato` device tracker integration allows one to tracker devices which are -conencted to a wireless router that is running [Tomato](https://tomato.groov.pl/) +connected to a wireless router that is running [Tomato](https://tomato.groov.pl/) as firmware. Because of a limitation in Tomato's API, this integration will only track wireless devices.