-
Notifications
You must be signed in to change notification settings - Fork 398
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
After Powerup sound sometimes not initialized #406
Comments
Yesterday I put an extension calbe to the USB soundcard because there ist not much space when for the sound card when three USB Ports are used. After this I powered up the phoniebox for 20 times and everything was fine. Do other users have the same problems? |
Not sure where the audio service log files would be and what they would look like. The only thing I can think of that might also be the reason: a "mute" / sound off GPIO button that's dodgy or gets pressed accidently alongside the power off button - or is wired wrong? |
Thanks for the note with "muting". I don't use the feature "muting". I will check my wiring if I have a problem with BCM13 and GND. |
Hi there. I furthermore don't pull the power cable but use the button method to turn the device off. Perhaps there is a problem with the sound card not turning off correctly or beeing in a hibernate mode. I will check again this week, if the problem will also come up with the onboard sound. |
When I have this error I hear the startup sound. I will check my mopidy.log if there are any errors. |
So I made a fresh install multiple times and I again had sometimes this error. But after reordering the sound cards like already mentioned in here it seems to work. I'm not quite sure but perhaps also forgetting to scan the library after adding new files could lead into this. I have forgotten it sometimes. |
Thanks for the link. I just made the reordering of the soundcard. I will have a look if the problem is fixed with this adaption. |
After doing the reordering there was no startup sound and there was no music when I swiped a RFID card. I used my backup of the sd card to get the phoniebox working. At the end of the week I will have some time to try once again the reordering. @Berdsen : Did you just do the reording as described in the docs or did you do anything more? |
Reordering will not fix this issue. As I said, I set up a complete new sd card and the following setup: See also here |
I hope I will have some time on next weekend for testing your steps. |
@Berdsen : Can you please give the path where I can find the log file you looked at? |
@SpookyFishes After doing this I started a terminal and changed the loglevel in the logging section of the mopidy.conf from INFO to debug. Then I deleted the current logfile and rebooted the system.
After the next start you have a new log file and you can check what is done, when the box is initialized. |
Hello @Berdsen The debug level I changed in /etc/mopidy/logging.conf with this new value The logfile will be stored here: In file /etc/mopidy/mopidy.conf it looks like this:
How did you activate the cache in mopidy.conf? Or did your mopidy.conf looked different? At the moment I added one playlist with 50 songs to one rfid card. I will have a look if the problem is still there in the next days. If everything is fine I will add more spotify playlists to the accounts and to some new rfid cards. |
Hi |
Hello @iwishitwassummer ,
At the moment I have just one spotify playlist integrated in my phoniebox. The rest of the music is stored as mp3s. I just made a fresh install 7 days ago with 1.1.9-rc6 and mopidy 3.31.8 and at the moment I didn't have the problem. In the next days I will add some more spotify playlist and I will have a look if the problem is will come back again. |
@SpookyFishes thanks, I wanted to check my logs but I have the classic edition, hence it's mpd. |
I'm using the + Spotify version of Phoniebox 1.1.9 and I'm gonna add my two cents to this issue. Please see section "Debugging" for additional information that might be helpful to pin this down. Current behavior
Hint: It doesn't matter how long I wait between step 2 and 3. Every first swipe is followed by the delay in step 4. DebuggingInstead of swiping a card I've tried to start the rfid_trigger_play.sh script via SSH after hearing the startup sound. This throws the following error messages:
After 1-2 minutes the following messages appear and the sound is played.
After this the sounds are immediately played and executing the script doesn't throw any errors any more:
I don't have any coding experience hence I'm not able to use the error messages above to look at the code. But maybe it does ring a bell to anyone else? |
Hi, did you find a solution for that issue? Unfortunately I have the same problem. |
Unfortunately not. |
Ich habe das gleiche Problem, und bemerkt dass mopidy in dem Moment wo der Sound nicht geht nicht verbunden ist. Und glaube es liegt daran das die Zeit und das Datum nicht richtig sind. Evt kann man noch eine RTC nutzen. Bin mir aber noch nicht zu 100% sicher, |
Thanks for the update, @maddin78! Keep us posted if you find something out. Would be great if we could solve this issue. My 2 year old is understandably too impatient to wait for so long after the box has booted and has crashed the box several times now. 😬 |
I agree with @maddin78 finding assuming we are on the Spotify version. |
got it, i installed a ds3231 rtc (other should work also) and now mopidy only takes a few seconds to connect |
Great news! Thank you for sharing this. Now I have to wrap my head about how to add an rtc on top of the on/off shim. I will share my results once I have tested it. |
that is not a big deal, i use an on/off shim also. you only need to connect the rtc to pin 1-3-5-9 |
I have issues connecting the DS3231 to the Pi. I used the same pins you've mentioned and followed instructions on https://pimylifeup.com/raspberry-pi-rtc/ to configure the RTC. Unfortunately it doesn't show any ID when running sudo i2cdetect -y 1. Oddly it does show the ID when I use a freshly formatted SD card with a clean Raspbian Stretch on it. I still have the feeling that the On/Off-Shim prevents the RTC from working. How did you install the On/Off-Shim @maddin78? Did you use the official software from Pimoroni? And did you do anything else to get the RTC running? Thanks for your help! |
I use the original softtware from pimoroni. Did you try it on the same pi? I have first installed the on off shim and then the rtc. |
Yes, I used the same Pi. I did run a few more tests and it doesn't seem to be connected to the Shim though. On a fresh Stretch system the RTC and the Shim work perfectly together. Once I install the Jukebox, the RTC stops working. Did you do anything special to get the RTC running? Did you follow a tutorial on the web? |
Nothing special In the next days i will set up a new jukebox and write down the steps |
I think it has something to do with i2c. I installed yesterday a new raspberry pi 3 with 2 i2c devices attached. After the fresh install of raspian stretch i2cdetect found the the devices. After installing the jukebox software i2cdetect was not able to detect any devices anymore. I tried the same with a new raspberry pi 4 with the same result. The same happened with raspian buster. I then used a backup from a old raspian installation where I had installed the jukebox already. i2cdetect found the devices with that without any problems. It looks for me that something get installed which prevents i2c from working. |
I have both 3,3V Pins (1 & 17) used by the Hifiberry Miniamp and a KY040 Rotary Encoder. Is there any other possibility to wire a DS3231 without Pin1? |
@swissmaster1 have you managed to solve this issue? I think I can confirm the same behaviour. I have also attached a LCD display to I2C port. Interesting enough it seems to be initilized with date and time when the box is booted up. When I run I2C detect it does not show any device, so my guess is, that one of the phoniebox services blocks the I2C from working |
No. I got it running again when I installed the backup of an microSD Card with older raspian and phoniebox version. But I still have problems with Spotify. After startup I have to restart the mopidy server over the Iris interface. After that spotify works in my case. |
Thanks for all your helpful comments. I'm experience the issue with the lengthy connection times as well and have two questions for you:
|
@JuliH29 apologize for late answer... Agree with your point 3) |
Can anyone be more specific about the root cause of the issue? If it is the lack of an exact system time, then running ntp should help, shouldn't it? |
I dont know the root because; but from my point of view it is not the system time. I installed a RTC DS3231 and the issue is still present.
|
@dbffm I agree, same with me. Unfortunately I do not have a working backup anymore, so I cannot restore 🙁 by the way... I started a moneypool to fund a spotify prem accout for @MiczFlor with #737 to help debug spotify issues |
Mine is connecting mostly in no time. In seldom cases, it takes up to 10 minutes or so. I don't believe in the RTC thing. I guess it might only help if your rasp does not sync its time using ntp. System time might be of importance for SSL handshake, but the source of the system time does not matter in my opinion. Your laptop, personal computer, mobile phone do not have a RTC built in neither (asfaik) and SSL is working out just nicely. To me, this is somehow network related. I observe increased probability of occurence when WLAN signal is bad. I find the following in mopidy log files: 2020-01-31 19:27:58,413 ERROR [261:SpotifyEventLoop] spotify.session: Spotify login error: <ErrorType.OTHER_PERMANENT: 10> ErrorType.OTHER_PERMANENT seems to occur when spotify host cannot be resolved due to dns, proxy or connectivity issue. Mopidy-spotify has some retry logic with exponential backoff strategy in place, but this logic does only jump in in case of some particular http error codes. So there does not seem to be an immediate retry in case of network failures. I still wonder which meachnism makes it work after 10 minutes or so. |
@thomas-wolf totally agree with your observation. I have just bought a usb wifi stick with external antenna and going to build this into my box in the next couple of days. I'll do some testing and feedback into the group again. |
@domu83: Did the external wifi antenna help? Really looking forward to learning from your experience. |
@thomas-wolf thanks for the reminder. Actually not. I've done some further tweaks, I thought, which finally ended into unreliable boot of the pi at all. I have done a fresh buster lite install |
Hey everyone. I just recently installed the phoniebox with the newest one liner on raspi OS and have the same problem (4 minutes waiting). Could anyone solve this yet? Why do I need mopidy at all to play mp3 files? |
Unfortunately there's no final solution yet. You have Mopidy only installed, when you chose the Spotify edition. If you have installed the classic edition only MPD is used. |
I have some input towards this, although it's probably not really helpful. Using Phoniebox with Mopidy/Spotify I've also observed the issue that swiping any rfid card after the startup sound played did not work for quite some time. I did find the reason, but no satisfying solution. Issue is that mopidy will log into spotify and refresh playlists that are linked to that account. In my case this resulted in a 44 second delay: Snippet from output for
The really not satisfying "solution" for me was to disable spotify since for my use case it's a nice to have feature. Now, Mopidy only takes 2-3 seconds to be ready which is barely recognizable. So - in my case it would be smart to reinstall without spotify support, I'm probably to lazy to do that. To fix the issue and use spotify it will be necessary to somehow adress this issue. Use a "blank" user without personal or saved playlists? Request a feature for mopidy service? |
Spotify (and mopidy) integration has been rewritten in the latest release and this should be improved: https://github.com/MiczFlor/RPi-Jukebox-RFID/releases/tag/v2.7.0 closing now. Feel free to reopen, if the issue persists. |
Hello,
sometimes after power on the sound is not working with the phoniebox software. Actually I can't reproduce this behavior.
When there is no sound it looks like this in the web interface:
After rebooting the pi everything is fine and I can start playing music:
I have this behavior with a Pi 3b+ and Phoniebox SW 1.1.8-rc2 and with a Pi 3b and Phoniebox SW 1.1.8
I use this external USB sound card https://www.amazon.de/gp/product/B00C7LXUDY/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1 which is direktly plugged in the USB port of the Pi
Perhaps anybody can help me :-)
The text was updated successfully, but these errors were encountered: