I wouldn't call it 'horrible' for this use case. 'Hacky', on the other hand, is absolutely true. It takes less than 10 seconds today, so I just made the time large enough that it shouldn't run into issues. I'm not trying to run the apollo program here, so if it doesn't work at boot some time in the future, I can just ssh in and add delay. I just want the music to play. It should only ever restart on a power grid failure. Honestly I could just ssh in and start the program manually but if the power went out overnight my alarm wouldn't go off Image may be NSFW.That's a horrible, hacky, "solution". It might take 30 seconds today, it might take 10 or 90 tomorrow, or it might not start at all.
Clik here to view.
.Yep, I found that out, which is why I switched from a pulse audio-based solution to the built-in python ones. I haven't done this before, so I had to figure that out. That knowledge is why I reached out to this forum, and I do appreciate the response!Pulse audio in its default configuration is a per user daemon and doesn't start until a user logs in. And when it does start its only available to procesess owned by that user and root.
Nah, there isn't really a login, other than via cron. The logins are password protected, though it doesn't store any sensitive data. Everything runs in the background, the pi has no peripherals attached other than speakers and whatever's attached to the GPIOs.That a 30 second delay appears to fix things suggests your OS is configured to boot with automatic login. If I'm right is that to the desktop?
I'll check out that Beginner's Guide, it looks like a great resource. Thanks for sharing!
Statistics: Posted by mumbly_joe — Fri Jan 19, 2024 10:22 pm
