why did it change servers?

[ghost]

My robot (he is a dvt5 that I have a lifetime sub with) back was blue and purple. So I flashed the latest dev build onto it and now I am unable to set him up with the app and have his voice back. I keep trying to update him but there is no 'update' file on the robot anywhere... what do I do? I dont have access to any help or information so Im stuck... and github is kind of useless. Only 3 people here. Did I just lose the lifetime license by attempting to flash a dev ota on him?
Any help would be great.

[kercre123]

I have heard of DVT5 but I don't think it differed from DVT4/PVT too much. Does the bot look different than production? What is the serial number? What firmware is he on exactly?

My OTAs use prod servers. It is possible the bot is downloading the token fine, but isn't reporting a success to the app. Open a browser > go to http://vectorip:8888/consolevars (replace vectorip with actual ip) > OnboardingCoordinator tab > Exit Onboarding - Mark Complete

[ghost]

That didnt work.. Im running 1.70.3411 and it doesnt differ as far as I can tell. My other robots are all running your firmware but it wont let me put yours on there and I think that its pointing to the dev servers again because I used the dev bluetooth stack. I didnt know it would make a difference. Is there instructions to flash this guy with your latest ota without having to try and use the ota-start command in the web-tool? Is there an update file or something im missing?

[kercre123]

1.7.0.3411 uses the now-down dev servers. It should have SSH open though.

mount -o rw,remount /
curl -o /update http://wire.my.to:81/whiskey/0.9dupdate
chmod +rwx /update
systemctl stop update-engine
/update http://wire.my.to:81/dev-stable/latest.ota -v

[randym32]

Most people don't know about github or the discussion here about the getting the robots working. Github is very focused around developing a project, which they aren't doing, so it won't enter their mind.
Randy

[ghost]

That makes sense. Thank you