-
Notifications
You must be signed in to change notification settings - Fork 19
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
Error with multiple robots since v0.7.0 #47
Comments
config.json looks like this:
|
Hi sorry to hear that. I think you can disable "spot" as a workaround until I fixed that. |
Doesn't help, I will stay on 0.6.3 till it is fixed. |
Alright thanks for reporting, I will look into this. |
I have the exact same problem:/ |
I have 2 D7 btw. |
This will be fixed in v0.7.2. I might need help in testing a beta from one of you because I have only one robot. |
Great! Thank you so much💪🏼 |
Alright, I might fixed the problem in v0.7.2-beta.1. I work on this problem like a blind taxi driver (I know the streets but without a second robot, I can only guess the traffic 😄). Could you check it please? You can install the beta version with |
Sorry, can’t test before the weekend, won’t be home until Sunday. :( |
Hello again:) i have just tested the beta, and it seems you have fixed the problem👍🏼 |
Glad to hear that. |
I am sorry to say but it doesn't work our me. My new config.json looks like this, I just need the dock command.
and it throws the following error:
If I add the dock back into the ignore list, it works again. |
Was your robot maybe offline? This looks like another error. |
My account [1/5/2020, 2:27:21 PM] [NeatoVacuumRobot] Error getting robot meta information: no serial or secret: null |
Thanks for the screenshot. I guess the problem occurs because of your other non smart robots. I will try to fix that. I created a new issue for your problem: #49 |
I’m also getting the “error getting robot meta information: request failed with status 404” One robot: Botvac Connected. Config file is pretty much identical to the others here. |
Same here. Detecting neither of my robots because of the 404. |
Hello @naofireblade, i bought my second Neato and also received the following message:
Can you help us? Alex |
Got the same problem... one of my 2 robots failed to load. I added a robots.pop(); in the code before the forEach to let at least one robot run. But I wonder how to fix the bug. Unfortunately I understand too little about programming. |
Everything was working correctly with my two D5 up to 0.6.3. After the update homebridge throws the following error log. went back to 0.6.3. and they switch to responding again.
The text was updated successfully, but these errors were encountered: