I use Ropieee on 2 devices – one in a Holo Red as an audio renderer connected to a dac, and the second in a raspberry pi 3b with a display and a flirc as a display and control for the Red. My usual practice is to switch everything off at night and everything gets switched on in the morning, i.e. the roon core, the dac, amp and the display Ropieee. Recently the display Ropieee doesn’t recognise the roon core unless I reboot the display Ropieee – then no problems and all is fine. It used to work fine, but recently it wont recognise anything until I reboot the display Ropieee.
It might be to do with timing, i.e. I switch the roon core and Ropieee display devices on at the same time, so is there any way of delaying the startup of the Ropieee display? I also tried telling the display ropieee to reboot at a specific time of day but it doesn’t do it. Any ideas? Here is some feedback before the reboot of the display Ropieee: 13304cd9df26b61b
Thanks in advance – all the effort in developing Ropeee is much appreciated – I have tried other things but none are as good as Ropieee.
There is no dependancy in startup order: your RoPieee unit(s) should be able act on the events that take place (roon server comes available etc.), so that’s not the issue.
I do see in your logs however, an issue with time synchronization. That is potentially an issue: so have you changed something in your firewall or router?
Thanks very much - I looked at the router and I dont think NTP was working properly (the date in the system log was 5 May and it is 3 May today) so I set a new NTP server. The router now looks like it has the right time. No change on the display Ropieee until I rebooted and then it worked fine - here is some feedback after the reboot 4e8783e81a00dd09 - hopefully there are no time sync errors now. Thanks again for the help.
Sorry for the bother but I am still having the same behaviour and I think I may have seen what is causing the problem.
I switch on the router and the raspberry pi hosting ropieee every morning at the same time (they are in the same electrical socket extension strip) and ropieee comes up before the router makes its connection to the internet. I see on the ropieee display that it thinks it has made internet connection before the router indicates that the ADSL connection to the internet has been made (a light comes on the router when internet connection is established and this light is off when ropieee says it has internet connection). Then ropieee says time sync failure and won’t connect to roon etc. After a while the display reverts to the screen saver and seems to show the right time and I can access it via the web ui and all looks fine there but it wont display or respond to remote commands until I reboot it via the web UI.
I don’t think I have changed anything in the router - I looked through the settings and can see nothing unusual and I have not changed settings there for quite a while and ropieee used to work fine given the same circumstances. I have even tried reinstalling ropieee from the iso and this gives the same behaviour. The odd thing is that until recently this was not a problem, and I don’t know what has changed.
This is not a serious problem so no worries if no solution can be found, but any ideas are appreciated! Thanks in advance for any!
As I said before: this is the problem. RoPieee requires a working internet to be working, especially during boot. The fact that it worked in the past could be purely because of timing: maybe the newer RoPieee version boots just a fraction quicker, and that causes these issues.
So to fix this you make sure your router boots earlier than RoPieee. Why do you turn your router off anyhow?
Thanks - I think I have fixed it by changing the network connection of the ropieee from wired to wireless. With wired, ropieee thought that it had internet connection before the router’s internet was connected and proceeded with time sync failure. With a wireless connection, ropieee waits until the ADSL connection is made – I watched the ropieee display along with the light on the router that indicates ADSL connection and with wireless, ropieee waits until the ADSL light comes on before saying it had internet connection. I did a cold test by switching everything off at the mains and it looks like it works.