-
Notifications
You must be signed in to change notification settings - Fork 1
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
various build errors #2
Comments
Thank you for reporting the issue. Could you provide some details about the system / operating system you are using? Thanks. |
|
To resolve the PyAudio issue can you try running
and then again
The python venv should then report successful dependencies. MX doesn't seem to use systemd by default addressing in #1 |
Tried your suggestion of installing python3-dev and then the install script. I think the output went a bit further this time, still shown some warnings along the way, ultimately didn't work, but the same error message mentioned in #1 overlapped the shell's output, so I can't even paste it here. |
I am playing with various python version via pyenv, but I think python3-dev installs the version that's applicable to the global version (3.11.2 currently). Any idea how to install/run oceaneyes within pyenv? |
I commented out the last line that replaces the shell output, if you could pull that update you should get more info. I need to look further into supporting non-systemd setups. The script does run a venv (in ~/python-apps), based on your system python version 3.11.2 before installing the requirements. The pip in the venv/bin may be troublesome at install; I can take a closer look at that in MX Linux. Currently the target system is Linux Mint and Raspberry Pi OS. Though the Pi upgraded to Bookworm since so it would be good to update the install anyway.
I recall a problem with the PyAudio in pypi needing that dev library so this should resolve the wheel issue:
|
Yes you could try the following to run in the venv without the systemd service:
Load a browser at the address: Replace the ipaddr with yours ( ifconfig | grep "192" ) And then after killing the script run a deactivate |
I have a radio itself on 192.168.1.250 and attempted to try using script from the description to see how to interact with it, but it failed to find/load module oceaneyes for starters. Should I file it as a separate ticket? FastAPI docs page opens fine (but I have no idea on how to use these various buttons). Thanks! |
Ah cool, it's up and running. The radio needs to be on for its web interface to be reachable. Try clicking /v1/device/scan then click buttons "Try It Out" > "Execute". Have the terminal visible in the background. This should scan the network for the radio, but wait for it to run all the way through 255. In the terminal it will print some output:
Make the device active by putting this in a browser address bar: Put this to get the favorites off the radio:
Or
To play preset 16
To mute and unmute copy these into a browser address bar after setting the device to 1 (I have three radios):
I do need to update the readme for how to use the endpoints. |
The text was updated successfully, but these errors were encountered: