-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Neato Component Error #11968
Comments
Interesting I saw this before on my D7 however everytime the error showed up my unit was dropping the wifi connection. I have not updated to 0.62 yet but when I do I will check to see if it works or not. Do you know if your unit is still online when you get this message in the Neato app? I noticed mine was dropping the connection as the wifi light would go out and come back on a minute later. |
@dshokouhi you're right. I just checked on my app and the neato is offline. If this is related to the connection then perhaps we shouldn't prevent the setup of the component. The component should set up correctly but then not work with an error message that is more revealing to the user to check the wifi connection on the vaccum. This way as soon as the connection is resolved on the vaccum HA is working without needing to reboot HA to setup the component. thoughts? |
I think that would be great however most of the platform components are designed to setup the entities upon restart. Normally if a component fails to setup I just restart again, honeywell has a tendency to do that due to the rate limiting they do. One thing I noticed is that when I get this error the map and schedule switch are marked as |
that's what i was seeing too until the update to .62 where the entire component failed to load |
yea but I think you happened to restart when the botvac was offline right, if you restart when the device is back online it should set it up correctly right? |
correct |
@dshokouhi tried rebooting again for a different reason and now am getting this:
|
Having a very similar problem. Botvac Connected. I've actually tried linking the Neato up with a second Neato account but get the same result. Neato is listed as online in the Neato App:
|
Hm, interesting. I got a Neato Botvac Connected today, created an account and hooked it up to 0.62.1 without any issues. What I am wondering is if the coverage-map is available for this model too. I see that you can get it for the D3 and the D5, but nothing about Connected. |
Coverage map is available but you have to update the firmware of the Botvac.
…On Sat, Feb 3, 2018 at 8:09 AM ScuttleSE ***@***.***> wrote:
Hm, interesting. I got a Neato Botvac Connected today, created an account
and hooked it up to 0.62.1 without any issues.
What I am wondering is if the coverage-map is available for this model
too. I see that you can get it for the D3 and the D5, but nothing about
Connected.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11968 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABATkG30p4gr-lY4Dq0vaev6axfKgyBDks5tRFqPgaJpZM4RvZKf>
.
|
Already running the latest firmware (2.2.0) |
Do u see the coverage map on the Neato app? If so, go to the dev panel and
see if u see a camera.neato entity. That is what has the coverage map.
…On Sat, Feb 3, 2018 at 12:04 PM ScuttleSE ***@***.***> wrote:
Already running the latest firmware (2.2.0)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11968 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABATkKpFeMZ738GbqSkv_MdDZL7ZnoF_ks5tRJGagaJpZM4RvZKf>
.
|
Oh...why didn't I see that... Aight, all good :) |
@uchagani were you ever able to resolve your issue? I'm in the same boat. Getting a 403 error with the Botvac Connected. |
After a bit of troubleshooting today I finally figured out my issue. The clock on my server was out of sync. Updating the time on the server fixed the problem. |
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 👍 |
Are you guys still seeing this error? So far the D7 works well as long as the wifi connection is solid. |
Yes I have this problem since months ago. "Invalid config" in UI and this:
Running HA 0.72.1 in Virtualenv. |
Changed logger config:
And got this:
|
I have this problem this week |
@bphermansson it looks like you may not have updated home assistant correctly if you used a virtual environment install. Did your install include a homeassistant user? Typically a venv install the files are referenced in @angelyangw how did you install homeassistant and can you post the error you received? |
@dshokouhi Sorry I think I thought wrong. This installation is not in a Venv. |
If you guys have terminal access see if you can interact with your neato account using the official repo: https://github.com/stianaske/pybotvac follow the steps there and see if it will print your robot serial in the terminal. Be a good step to troubleshoot where the issue is. Also what model of botvac do you guys have? |
@dshokouhi I received the error like this and my homeassistant already update to 0.73.1 |
@angelyangw can you double check your neato account and make sure that wifi is turned on the robot? The error you posted is looks identical to #15238 |
@dshokouhi I will try it again later. thanks! |
I have a spare Neato in my account, but the code should be able to handle that? |
@bphermansson the code was updated to allow for multiple robots that are connected and working. If you have one not in use try to remove it from your account and see if the component will setup properly. The component needs to setup each botvac found in your account. Edit: Also what model do you have? |
@bphermansson and @angelyangw in addition to checking the app, login to neato.com and see if anything unusual is in your account there as well. Other than that I still suggest you guys trying the command line for the official library so we can figure out what it is. If the issue is the with the underlying library we may need to file a bug there. https://github.com/stianaske/pybotvac |
@dshokouhi I try to use pybotvac. when I get from https://beehive.neatocloud.com/users/me/robots/ the response will see my robot like this:
but when I post for https://nucleo.neatocloud.com/vendors/neato/robots/GPC11418-7C3****E3F3/messages, I will get the error with "requests.exceptions.HTTPError: 404 Client Error: Not Found for url https://nucleo.neatocloud.com/vendors/neato/robots/GPC11418-7C3****E3F3/messages" |
What is interesting here is the format of your robot's serial number. It is different than what is listed in the main repo
Both of my botvacs start with OPS for the serial number. I also see that on the website when I login. |
yes, I saw this too. but, why the serial should be start with 'OPS' ... |
For this lets see what the repo maintainer says on the bug you created over there: stianaske/pybotvac#17 I am not sure why the serial needs to be that but this issue must be fixed there in order to work in Home Assistant. |
Tried this as @dshokouhi suggested:
Exactly the same error as given by HA:
And yes, I have two devices in my Neato account. But I don't think removing one of them would be a real solution to this problem, just a bad hack... |
@bphermansson then this is not a Home Assistant error, this is an error with the underlying library so we need to create a bug there and get it fixed there. The reason why I said you should try to remove the unused botvac is because if it is not connected then messages will fail to send to the robot. I am not sure when the main library would be fixed so it may be something worth trying if you want to see if you can get things to work. In your case you can't even get the serial for the botvac which is a different issue than what is being discussed in this bug. |
I filed a report upstreams but still no response. Maybe I'll have to learn to fix it my self. stianaske/pybotvac#18 |
@bphermansson I would give him some time to respond, the other bug report seemed to be a quick fix since it was only a URL change. Just a quick question....what version of Home Assistant are you on? I noticed that the version of python is 3.5.2 you linked in that issue, which is not supported in current versions of Home Assistant. |
Ok that can be my problem then.. I use Home Assistant 0.72.1. Which versions are recommended? |
Do you remember how you installed home assistant? Was it Hassbian or a virtual environment? It may or may not be worthwhile to see if the issue is with your install. You should back up your entire config directory and see if you need to reflash and restore the directory. If you look at the log you posted up above you can see python 3.6 but in pybotvac it shows python 3.5.2. I would say a reinstall may actually help so you can get your versions straightened out. Personally I am on python 3.6.3 with a virtual environment install. https://www.home-assistant.io/docs/installation/raspberry-pi/ |
Ok. I had trouble with python versions and ended up with both 3.5 and 3.6. I now removed the symlink to 3.5 which makes pybotvac run with 3.6.5. But it still fails like before. |
@angelyangw I have moved over your issue to a new one and have also submitted a PR to use the dynamic end points. @bphermansson I am still unsure what causes your issue as you cannot even login. While we wait for a response can you create a separate issue for this as it is not related to the original reported issue? |
@dshokouhi OK. Thanks a lot! |
I ran into this error just today, i.e. the neato component wouldn't load when starting home-assistant. Culprit in my case was that the robot wasn't charged and thus wasn't connected. Reading this thread there seems to be a number of different causes that lead to the approximately same symptoms. My particular issue with the robot simply not being connected has been discussed and a suggestion was made that the component should start even though the robot can't be reached during the start. I tend to agree with that. @dshokouhi gave somewhat of a rationale to the current design but no conclusion was really made. I think we should discuss it in more detail. I think overall HA should move into being more robust, not requiring a complete restart for as many operations / scenarios. Since there are already so many different causes leading to a discussion thread that is quite difficult to follow, I opted to create a new issue #16685 to discuss the particular issue of the component not loading on start when the robot is offline. |
Same issue here, but the upstream bug in the supporting library was closed w/out any fix...
(serial number changed) |
upstream bug is more likely now: stianaske/pybotvac#30 |
Also running into this issue:
|
@SeraphimSerapis the 404 error suggests your botvac maybe offline. Can you check if you can still control it in the Neato app? Try to restart the botvac to regain control and the 404 should go away. |
That worked! |
Neato component no longer works. I have a Neato Botvac Connected which was working fine. The error below started showing up in the update intervals a few days ago and with the update to HA 0.62.0 the component will no longer set up at all.
Home Assistant release (
hass --version
):0.62.0
Python release (
python3 --version
):3.5.3
Component/platform:
Neato
Description of problem:
Getting the following error:
Error during setup of component neato
which is caused byrequests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://nucleo.neatocloud.com/vendors/neato/robots/OPS31116-04A316B0F207/messages
Expected:
No errors when setting up and updating components.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
The text was updated successfully, but these errors were encountered: