Closed JamesDenby closed 4 years ago
Thanks for the report! I'm trying to replicate, but I'm not seeing it locally. Are you sure it's coming from eero_tracker? The only call out we make is to Eero's API server over HTTPS, and that hasn't changed or is changeable via config.
The error you're seeing would be applicable if we were calling an HTTPS server over HTTP, or vice-versa.
API_ENDPOINT = 'https://api-user.e2ro.com/2.2/{}'
Ok, thank you for responding. I am fairly new to HA so it maybe something else. Here is my configuration.yaml excerpt:
Since I commented it all out, I no longer get the error, but I will try again and let you know
… James
On 31 Dec, 19, at 04:48, jrlucier notifications@github.com wrote:
Thanks for the report! I'm trying to replicate, but I'm not seeing it locally. Are you sure it's coming from eero_tracker? The only call out we make is to Eero's API server over HTTPS, and that hasn't changed or is changeable via config.
The error you're seeing would be applicable if we were calling an HTTPS server over HTTP, or vice-versa.
API_ENDPOINT = 'https://api-user.e2ro.com/2.2/{}'
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jrlucier/eero_tracker/issues/14?email_source=notifications&email_token=AN63DXD5Q3Q4PJW7MD7GLTLQ3MWP3A5CNFSM4KAN6IWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4DYHY#issuecomment-569916447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN63DXDOH5DJVNZAWEC4KZDQ3MWP3ANCNFSM4KAN6IWA.
Good news! I reinstalled it and no longer have the error. I guess it was me, something I did, or something else. Thank you for your time and sorry if I wasted it.
… James
On 31 Dec, 19, at 04:48, jrlucier notifications@github.com wrote:
Thanks for the report! I'm trying to replicate, but I'm not seeing it locally. Are you sure it's coming from eero_tracker? The only call out we make is to Eero's API server over HTTPS, and that hasn't changed or is changeable via config.
The error you're seeing would be applicable if we were calling an HTTPS server over HTTP, or vice-versa.
API_ENDPOINT = 'https://api-user.e2ro.com/2.2/{}'
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jrlucier/eero_tracker/issues/14?email_source=notifications&email_token=AN63DXD5Q3Q4PJW7MD7GLTLQ3MWP3A5CNFSM4KAN6IWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH4DYHY#issuecomment-569916447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN63DXDOH5DJVNZAWEC4KZDQ3MWP3ANCNFSM4KAN6IWA.
Closing issue as it appears to not be an eero_tracker issue.
The tracker works, but it is filling my log with errors. Here is an example of what I am seeing:
Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 275, in data_received messages, upgraded, tail = self._request_parser.feed_data(data) File "aiohttp_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data aiohttp.http_exceptions.BadStatusLine: invalid HTTP method
I am on the latest versions (Hass.io and your tracker).