Weāre making progress! Thanks!!! I used the pre-built OVOS image and after some fiddling, have it listening and working.
Now Iām trying to figure out why it canāt do anything. I can ask it the time and weather but pretty much nothing else. I tried to set an alarm for 1 minute, get a random number and a couple of other things that I thought were built in but I get āproblem occurred while speaking with remote llamaā.
(ovos) ovos@raspOVOS:~ $ ovos-status
ovos-audio.service loaded active running OVOS Audio
ovos-ggwave.service loaded active running Open Voice OS - ggwave listener
ovos-gui.service loaded active running OVOS GUI Websocket
ovos-listener.service loaded active running OVOS Listener
ovos-messagebus.service loaded active running OVOS Messagebus (Rust)
ovos-phal.service loaded active running OVOS PHAL
ovos-skill-settings-ui.service loaded active running OVOS Skill Settings Editor
ovos-skills.service loaded active running OVOS Skills
ovos.service loaded active exited OVOS A.I. Software stack.
I also get errors trying to check the skils info and server status:
(ovos) ovos@raspOVOS:~ $ ovos-skills-info
Traceback (most recent call last):
File "/home/ovos/.venvs/ovos/bin/ovos-docs-viewer", line 4, in <module>
from ovos_docs_viewer.ovos_docs import launch
ModuleNotFoundError: No module named 'ovos_docs_viewer'
(ovos) ovos@raspOVOS:~ $ ovos-server-status
Traceback (most recent call last):
File "/home/ovos/.venvs/ovos/bin/ovos-docs-viewer", line 4, in <module>
from ovos_docs_viewer.ovos_docs import launch
ModuleNotFoundError: No module named 'ovos_docs_viewer'
The pre-built image doesnāt appear to have a desktop so maybe thatās the docs_viewer error?
I managed to get it to āplay a songā but I canāt seem to interrupt it to stop playing it or change the volume. Is there any full documentation on the baseline skills, operation, configuration, etc.?
Not sure if this is the right place for the report. ovos-installer fails, because https://whl.smartgic.io/ seems to be down (HTTP 503). Anyone else experiencing this issue?
TASK [ovos_installer : Create /home/user/.venvs/ovos Python venv with tflite_runtime] ****************************
Saturday 19 July 2025 23:02:19 +0200 (0:00:01.119) 0:00:13.732 *********
fatal: [127.0.0.1]: FAILED! => {"changed": false, "cmd": ["/home/user/.venvs/ovos-installer/bin/uv", "pip", "install", "--python", "/home/user/.venvs/ovos/bin/python", "--trusted-host", "whl.smartgic.io", "-f", "https://whl.smartgic.io", "tflite_runtime"], "msg": "\n:stderr: Using Python 3.12.3 environment at: /home/user/.venvs/ovos\nerror: Failed to read `--find-links` URL: https://whl.smartgic.io/\n Caused by: Request failed after 3 retries\n Caused by: Failed to fetch: `https://whl.smartgic.io/`\n Caused by: HTTP status server error (503 Service Unavailable) for url (https://whl.smartgic.io/)\n"}
I pulled a Mycroft Mark 1 that Iāve never used out of the closet and tried the install. The venv install completed successfully, but it doesnāt seem to hear anything I say. I tried re-installing a couple times just in case. The only error in the logs is inability to reach https://whisper.tigregotico.pt/stt which I donāt think should be required?
Iām wondering if Iām bumping into hardware problems (it is old!) or if these devices arenāt well supported anymore due to their low specs, I havenāt seen posts here about them lately. Any suggestions for debugging?
No errors, but also no wakeword detection logged. I also went into the venv and ran ovos-listen (and ovos-speak for good measure!), and the device didnāt seem to do anything.
I will try some more Linux-native debugging to see if itās a speaker/microphone hardware problem on the device, but I wanted to see if there was a known status for these older devices that I might be bumping into.
Iāve got a couple of Mark 1 devices and Iāve experienced that the audio hardware just stops working inexplicably. Eventually it starts again, which is very frustrating, but I havenāt been able to pinpoint anything specific. Could be a loose connection inside the enclosure.
Just installed on my mark 1 and it didnāt seem to detect it as a mark 1. Tho no errors in the install log, and the eye just spin.
Rerunning the installer gave an error detecting I2C, but that didnāt happen first time around.
reinstalled a few times, with the eyes spinning, without the eyes spinning, with apt upgrade, without.
Is there any way to force it to install the detection of a mark 1 ?
Iām also lucky enought to have a mk2, but that is deeper in my cupboard, i shall try testing on that soon.
for the mark 1, after enabling SPI & I2C in the raspi-config menu and rebooting it now fails to get the avrdude-aarch64 file. when in -d (debug) mode on the installer