-
-
Notifications
You must be signed in to change notification settings - Fork 28.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tomato.py timeout random #17269
Comments
still getting this in latest version 0.83.3
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
No longer using tomato component, switched to dd-wrt. |
Started having this same issue after recent updates to both h-a and freshtomato. Think the problem is on H-A side, as freshtomato easily serves the relevant data via browser (i.e. http://<YOUR_IP>:<YOUR_port>/update.cgi?_http_id=<YOUR_http_id>&exec=devlist). |
Home Assistant release with the issue:
0.79.3 (though noticed since roughly 0.75)
Last working Home Assistant release (if known):
uknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker running on intel nuc (ubuntu server 17.4)
Component/platform:
Tomato device tracker
Description of problem:
Intermittent errors with tomato.py component. Timeout and socket errors though config correct and router not under excessive load.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
Both router and hass have been restarted multiple times.
nmap check from within hass container confirms 80 is open on router.
The text was updated successfully, but these errors were encountered: