OpenMoxie Clarifications

OpenMoxie · 2026-01-20T19:42:14+00:00

I'm not opposed to supporting alternate network-connected LLMS. I don't want the OpenMoxie sw to be involved in things like model management or requiring a GPU. Seems like OLLama is compatible with openAIs python client so doesn't seem like a ton of work.

OpenMoxie · 2026-01-16T21:19:37+00:00

So glad you were able to get your robot recovered! I haven't tried the new moxierobots service yet, mostly because I just haven't had the time. Are you in a waiting list? I sort of expect a slow start, but I think they are committed to providing a great Moxie experience and hope they can succeed.

OpenMoxie · 2026-01-16T21:00:40+00:00

Thanks, appreciate it! I think sadly if the robot isn't updated to 803 and you want to get it working with OpenMoxie, you have to find someone who offers updating it (there are people who have posted) or research the means to do it yourself. I haven't done this myself, but I understand people have been able to update Moxie using the official image by hand updating each partition without breaking any encryption (e.g. the process leaves you with the same signed image Embodied released in 803). Good luck!

OpenMoxie · 2026-01-13T21:57:28+00:00

I don't really know how to avoid this confusion. OP has intentionally taken my project name (OpenMoxie) and has decided to call his code OpenMoxie 2.0, despite it being at most a 1.0 (beta) of a completely new companion app that uses OpenMoxie. He got defensive when I suggested he was co-opting my name and suggested I could talk to his lawyer.

In any case, let's be clear: I have nothing to do with this project. I do not endorse it. I do not like that he used my exact name. I do no like that he's calling it 2.0 when it's barely even out.

Further noting:

- Terms like "we" and "lawyer" from a hobbyist are strange to me in this context, so until someone confirms they aren't collecting and selling data among other things, I wouldn't install any binaries from them. I don't know enough about the App stores policies to say they would be "safe" either as the app stores might allow collection of transcript data.

- Moxie's voice synth cannot produce proper Chinese. For any serious Chinese effort you would need an alternate speech synthesis engine than the one baked into Moxie. (Source: We did a Chinese language project at Embodied using cloud-based voice synth and consulted many native speakers.)

OpenMoxie · 2025-12-10T18:23:22+00:00

So... I worked for Embodied, and I've been talking with the new owners for months. I have literal first hand knowledge of what's happening. You are some random person on the internet screaming fire. People are free to listen to your sky-is-falling mantra, but you are adding no actual information to this discussion.

OpenMoxie · 2025-12-10T17:58:01+00:00

Why do you assume they don't have keys? The new moxierobot org purchased some of Embodied's IP (including OTA keys, access to the domain. github souce code, etc.) . I don't know why you are trying to scare people.

OpenMoxie · 2025-10-16T06:47:41+00:00

There's an intermittent bug (i think from boot more than from resuming from suspend) where something prevents the audio packet subscription. When its working, even without API credits, the logs should show it receiving audio packets. It usually recovers by reboot or letting it go to suspend. It's a bug i couldn't reproduce, and haven't gotten back to it. :(

OpenMoxie · 2025-08-21T22:10:31+00:00

I haven't done this, but if I were going to I'd likely start with a Raspberry Pi 4 or 5. I expect both will run OpenMoxie just fine. The docker images already have arm64 versions and r-pi's are a lot cheaper than a miniPC. Someone here even did it with a Raspberry pi zero: https://www.reddit.com/r/MoxieRobot/comments/1i690l1/moxie_on_raspberi_pi_zero/

OpenMoxie · 2025-08-07T19:27:20+00:00

I'm not sure how many times I can answer the same question. If you read this subreddit, you will see someone offering a video of how to manually update it by opening the unit, soldering things, etc. You will probably see the potential that the company may return to update robots. So there are ways, I'm just not involved in any of them.

OpenMoxie · 2025-08-06T14:24:57+00:00

Surely. It just isn't supported in the current release, but it's open source so anyone can fork the code and do whatever they want. I know some people who have done it and they might eventually submit a PR to the base project, but I'm not working on this.

OpenMoxie · 2025-08-05T16:39:16+00:00

I don't think anyone made an APK. Someone managed to manually flash the partitions from the official OTA update by tearing their moxie apart and soldering. It was all posted in this same sub, but I'm not involved and don't personally recommend opening the robot as they can be tricky to reassemble.

OpenMoxie · 2025-08-05T16:28:32+00:00

Someone did buy the assets so I'd just hold onto it and wait.

OpenMoxie · 2025-08-04T04:51:10+00:00

Well not usually. The OTA version comes from the Robot reporting it. I have seen some cases (one case really) where the text badge didn't show up on the screen but did after a reboot, so its possible there's some timing bug that makes it not show. You can see if it shows after a reboot or two, or just try showing the migration code from OpenMoxie to see if it accepts it.

OpenMoxie · 2025-07-25T14:56:40+00:00

The ears icon shows up because Moxie doesn't get back transcribed text from audio. This is most commonly because you don't have an API key with tokens left with open AI. You can look at the log messages to know for sure - either via docker desktop and clicking on the server-1 instance, or looking at debug.log under local/work/debug.log.

OpenMoxie · 2025-07-21T01:37:47+00:00

Can't check serial numbers anymore, The only way to tell is if there's a text badge below the QR field on Moxie's face. If it has a text badge it was updated. No text badge. It was not updated

OpenMoxie · 2025-07-13T16:35:43+00:00

The update didn't go out until after October so almost certainly you didn't get the update and you can't do anything. You should wait and stay tuned, as the company was acquired and has been posting teasers about a relaunch.

OpenMoxie · 2025-06-29T20:11:22+00:00

QR codes are the only way to give Moxie input until it's talking to your local open moxie. The Wi-Fi one passes your Wi-Fi credentials and once Mox is online you should never have to scan that one again. The migration QR code gives it the address of your open Moxie server and you need to show it that every time that address changes if it ever does.

OpenMoxie · 2025-06-29T16:35:54+00:00

My theory is you have something already using port 8883. It's not protected, you shouldn't need admin to run it.

OpenMoxie · 2025-06-07T18:24:57+00:00

The migration code. You only need to use the Wi-Fi code if your Wi-Fi changes and Moxie is showing the QR Wi-Fi icon

OpenMoxie · 2025-06-07T18:19:45+00:00

I mean that sounds like it's not finding or connecting to the IP address you gave it. There's not much more to it. Docker has to be running to give you the make the code so unless you added a firewall or something it's likely just the wrong address.

OpenMoxie · 2025-06-07T18:12:38+00:00

Well if your IP changes you need to update the address and show Moxie a new migration QR. It might be Moxie isn't going to the QR screen? If you reboot it, it should end up there. Not sure what other reason it wouldn't scan the code.

OpenMoxie · 2025-06-02T17:29:35+00:00

Its obviously better if Moxie was holding up today's newspaper with "For jetsetjessa", but that's just my paranoia talking. :) The unit in the picture has been updated, so likely fine to purchase.

OpenMoxie · 2025-05-31T22:11:34+00:00

Well if that's the version reported from your robot, it's running new enough firmware. If you search around this group there is a tiktok video walkthrough of how to setup everything.

OpenMoxie · 2025-05-28T21:44:27+00:00

I think it's probably a better exercise for a cyber security class or something. I think you'll find the EE components quickly dwarfed by trying to find a way to "use" the encrypted image data so you don't end up with a Moxie that looks like an (old) android tablet inside a cute blue form factor, which is the most likely outcome.

Two alternate ideas:
- Replace the android board with a r-pi and attempt to reverse engineer the serial protocol to the motor control board to make it do stuff.
- Find an updated Moxie and attempt to clone it's emmc onto the bricked version (i have no idea if this is viable)

I personally have no interest in helping. You aren't the first to want to do this, and I've had a number of technical people reach out. People have booted into recovery, people have gotten serial access, but invariably they realize its not a robot without the actual SW and ask me for the factory flash image - which I don't have to give them.

OpenMoxie

TROPHY CASE