Tomato
The tomato
platform requires an extra config 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.
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.
To use this device tracker in your installation, add the following to your configuration.yaml
file:
# Example configuration.yaml entry
device_tracker:
- platform: tomato
host: YOUR_ROUTER_IP_ADDRESS
username: YOUR_ADMIN_USERNAME
password: YOUR_ADMIN_PASSWORD
http_id: YOUR_HTTP_ID
Configuration Variables
- host
-
(string)(Optional)The IP address or hostname of your router, e.g.
192.168.1.1
orrt-ac68u
. - port
-
(int)(Optional)The port number of your router, e.g.
443
.Default value: 80/443 (automatically detected)
- ssl
-
(bool)(Optional)Whether to connect via
https
.Default value: false
- verify_ssl
-
(string | bool)(Optional)If SSL verification for https resources needs to be turned off (for self-signed certs, etc.) this can take on boolean values
False
orTrue
or you can pass a location on the device where a certificate can be used for verification e.g./mnt/NAS/router_cert.pem
.Default value: true
- username
-
(string)(Required)The username of an user with administrative privileges, usually admin.
- password
-
(string)(Required)The password for your given admin account.
- http_id
-
(string)(Required)The value can be obtained by logging in to the Tomato admin interface and search for
http_id
in the page source code.
See the device tracker component page for instructions how to configure the people to be tracked.
A description of the API s available in this Tomato API blog post.
SSL Certificate:
Gathering the SSL Certificate of your router can be accomplished with this (or a similar) command:
openssl s_client -showcerts -connect 172.10.10.1:443 </dev/null 2>/dev/null | openssl x509 -outform PEM > router_cert.pem