-
Notifications
You must be signed in to change notification settings - Fork 51
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
Trouble setting up #5
Comments
see #3 |
Hopefully resolved with the latest code from |
|
This is a network error rather than a coding error. What Robovac device are you using? What firmware version is it on? Are your home assistant host and the robovac on the same subnet? |
Yes, robovac 30c firmware is 1.1.4 everything on the same subnet.
Jimmy White
…________________________________
From: Richard Mitchell <notifications@github.com>
Sent: Sunday, September 8, 2019 8:58:13 PM
To: mitchellrj/eufy_robovac <eufy_robovac@noreply.github.com>
Cc: Jimmy White <jimmy@deviousweb.com>; Author <author@noreply.github.com>
Subject: Re: [mitchellrj/eufy_robovac] Trouble setting up (#5)
This is a network error rather than a coding error.
What Robovac device are you using? What firmware version is it on? Are your home assistant host and the robovac on the same subnet?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#5?email_source=notifications&email_token=ABHVAB7JGWYNIH643NW2X4LQIVKNLA5CNFSM4IPGWMW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FYBOQ#issuecomment-529236154>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABHVAB32VDKAQM2JBBX4DZTQIVKNLANCNFSM4IPGWMWQ>.
|
Just did a full rebuild of HASS and retried this - still the same result. Im am using HTTPS for HASS if that has any bearing on it |
did you get a solution for the error above Traceback (most recent call last): As i have a 30C on firmware 1.1.6 and gettin gthe same error. |
Hi, I have my device ID and local key, and have followed the set up steps, however I get this in the logs:
The text was updated successfully, but these errors were encountered: