u/SonicSubculture

Ever since I starting using OpenAI Dots 2-3 days ago, I haven't worked any other way.

I was at a point with Codex where I was having to juggle a half dozen development threads in parallel, and the overhead was pretty heavy... with Dots, it's just gone now. It's AMAZING.

Except I keep getting interrupted with a notice that my dot is paused because an auto-reviewer flagged my activity as suspicious. On mobile, the message gives me a hyperlink to the specific report, but then I can't view it - says I'm logged in with the wrong account, which I know isn't true.

There's no way to resolve it except reboot my Dots. Then it works for a while until it trips again. The material I'm working on should not be raising suspicions. It's very mundane enterprise intranet PHP.

I'm hoping there's an update or something in the next few days because it's really annoying. For now I'm going to try to create a handoff and delete/recreate my Dots with instructions to avoid the content that was triggering the auto-reviewer...

edit: Deleting and recreating with a handoff seems to have helped… for now at least.

I just wanted to share my ownership and support experience that is ongoing.

My Luba 3 AWD H3000 came a little over 10 weeks ago and it has been doing a pretty good job of cutting my half acre lot until about a week ago when I noticed the grass getting long and saw that the mower was not completing its task, but instead progressing at a snail's pace. When I went out to it in the yard, I found it operating in a loop where it would get its bearings, play a little tune, spin up the blades and advance for a few seconds before stopping the blades, pausing, and repeating the whole cycle.

It was doing this for days without notifying me. Only once I tried to do Manual Mowing, it gave me an error alert that the right cutting disc reported error code 467.

A quick google search informed me of the process to troubleshoot... I removed the cutting disc, everything spins smoothly, there's minimal grass debris on the disc, and the bearing area and everything else looked pretty clean. I cleaned it very thoroughly. Ultimately I did this process to both cutting discs a total of 3 times to rule out any of my concerns, but nothing changed.

I started a chat with Mammotion and they had me upload my logs. I got a confirmation of my ticket in my email, and after that I heard no followup. I got response from the ticket. I opened a new chat and referenced my ticket, and they had no record of it, so I had to start over after several days...

My grass is getting pretty long by this point.

After filling them in on this frustrating experience, they told me to upload the logs again. I got confirmation that they got my log. A full 24 hours later they got back to me and said they looked at the logs, and they want me to remove and clean the discs and upload another log. They completely missed that I already did this 3 times.

Now I'm waiting probably another day before I expect to be given more unhelpful instructions.

What I really want:

- Bypass the fault detection so I can still mow

- Send me a new motor to replace the bad one if it's user-serviceable

- Send me a replacement mower and I'll mail this one back, if it is not user-serviceable

For $3000, I expect to be able to rely on this, and I expect better support when something goes wrong. There seems to be zero sense of urgency on Mammotion's part.

I'm going to have to resort to using my push mower.

There's still a chance for Mammotion to salvage this, but I wouldn't be surprised if I need to ultimately get my credit card company invovled.